RFC 7109
Flow Bindings Initiated by Home Agents for Mobile IPv6
RFC 7109: Flow Bindings Initiated by Home Agents for Mobile IPv6 🦋
Okay bestie, so RFC 7109 is an Independent Submission in the Experimental category (ISSN 2070-1721) 🧪. It was written by H. Yokota (KDDI Lab), D. Kim (JEJU Technopark), B. Sarikaya, and F. Xia (Huawei), and it's dated February 2014. The title block doesn't list anything it obsoletes or updates, so it's standing on its own 💅.
Abstract
So sometimes the home agent needs to trigger flow binding operations toward the mobile node 🫶, like moving a flow from one access network to another when network resource availability changes. This doc defines new signaling messages and sub-options for Mobile IPv6 so the home agent can start those interactions. Flow bindings initiated by a home agent work for mobile nodes enabled by both IPv4 and IPv6, which is literally so good 🎀.
Status of This Memo
Real talk, this document is not an Internet Standards Track specification. It's being published so people can examine it, experiment with implementing it, and evaluate it 🔍.
It defines an Experimental Protocol for the Internet community. It's a contribution to the RFC Series, independent of any other RFC stream. The RFC Editor chose to publish it at their discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor aren't a candidate for any level of Internet Standard, see Section 2 of RFC 5741 📚.
If you want the current status, errata, or a way to give feedback, check out http://www.rfc-editor.org/info/rfc7109 ✨.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved 💜.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, because they describe your rights and restrictions with respect to this document 📝.
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................3
3. Use Cases .......................................................3
3.1. QoS Provisioning ...........................................3
3.2. Traffic Offload from Congested Network .....................4
3.3. Flow Movement or Deletion in an Emergency Situation ........4
3.4. Service-Specific Data Cap ..................................4
4. Protocol Operation ..............................................4
4.1. Adding Flow Bindings .......................................5
4.2. Deleting Flow Bindings .....................................6
4.3. Modifying Flow Bindings ....................................6
4.4. Refreshing Flow Bindings ...................................6
4.5. Moving Flow Bindings .......................................7
4.6. Revoking Flow Bindings .....................................7
5. Handling of the Flow Bindings List ..............................8
6. Flow Binding Messages and Options ...............................9
6.1. Mobility Header ............................................9
6.1.1. Flow Binding Indication .............................9
6.1.2. Flow Binding Acknowledgement .......................10
6.1.3. Flow Binding Revocation Extensions .................11
6.2. New Options ...............................................12
6.2.1. Flow Binding Action Sub-Option .....................12
6.2.2. Target Care-of Address Sub-Option ..................13
7. Security Considerations ........................................13
8. Protocol Constants .............................................14
9. IANA Considerations ............................................14
10. References ....................................................16
10.1. Normative References .....................................16
10.2. Informative References ...................................171. Introduction ✨
Okay so [RFC6089] lets a mobile node (MN) bind a particular flow to a care-of address (CoA) without messing with other flows that use the same home address 🦋. BU/BA (Binding Update / Binding Acknowledgement) messages get extended so the mobile node can add, delete, modify, move, refresh, and revoke flow bindings in a home agent (HA). These operations are always initiated by the mobile node.
The mobile node handles flow bindings on its own because of things like user interaction or a change in the attached link condition 💅. But these operations are also needed for network-related reasons, like dynamic QoS control in the network, load balancing, or maintenance in mobility agent nodes. In the latter case, the mobile node isn't very aware of the transport network condition away from it, or of the policy and charging status the operator controls, so the network needs to request that the mobile node handle proper flow bindings 🫶.
This document defines a new Mobility Header and messages so the home agent can ask the mobile node to initiate flow bindings in a timely manner 🌸. Flow mobility is also supported for mobile nodes with an IPv4 home address and an IPv4 address of the home agent, as described in [RFC5555] 🌈.
2. Terminology 🎀
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
The terminology in this document is based on the definitions in [RFC6275] and [RFC6089] 📖.
3. Use Cases 💖
3.1. QoS Provisioning
Picture this: the user launches a video chat app and starts sending voice and video to the other end 📞. The network may need to give these media different QoS treatments based on the operator's policy. In that case, the network needs to request that the user or mobile node set up separate flows for voice and video 🎧.
3.2. Traffic Offload from Congested Network
The 3G operator may want to move traffic flows from the 3G access network to another network (e.g., Wi-Fi network) because traffic suddenly spikes in the 3G access network 📶. Fine-grained traffic offload is desirable. For example, Voice over IP (VoIP) flows based on IP Multimedia Subsystems (IMS) must stay in the mobile core network, while video-streaming flows from servers on the Internet could bypass the mobile core network via Wi-Fi access 🍓. Since the network knows more about its own conditions and has access to the policy server, more timely and well-controlled traffic offloading is possible 👑. The home agent sends an updated flow descriptor to be offloaded to the mobile node ✨.
3.3. Flow Movement or Deletion in an Emergency Situation
Okay this one is serious 😭. In an emergency caused by a natural disaster, it's necessary to accept as many voice calls as possible so people can check on the safety of family and friends, while non-critical services such as gaming would be considered lower priority. To save the 3G / Long Term Evolution (LTE) radio resources for emergency services, non-critical services may need to be moved to another access network or closed down 🚑. The home agent requests that the mobile node use Wi-Fi access for non-critical application flows, or terminate them gracefully. For example, it could let the user know about possible QoS degradation, or ask them to finish the corresponding applications before any action is taken 🫶.
3.4. Service-Specific Data Cap
The mobile operator offers a mobile broadband service with a flat rate subscription limited to 5 GB per month 📱. Once the allotment is used up, the service is downgraded to 64 kbits/s. This limit, however, doesn't apply to IMS-based services (e.g., Voice over LTE (VoLTE)), while video conversations over the Internet will be affected 🙈. The operator can let the user know by sending modified flow descriptors as a proposal to adjust the communication data rate or change access for an ongoing session 💅.
4. Protocol Operation 🔥
[RFC6089] uses BU/BA signaling to forward (i.e., register or discard) a flow binding in a home agent 💜. Flow binding operations are always initiated from the mobile node. The basic principle of this specification is that the home agent prompts the mobile node to perform flow binding operations 🦋. For this, a new Mobility Header and two new messages are defined: Flow Binding Indication (FBI) and Flow Binding Acknowledgement (FBA). The home agent uses an FBI to request flow binding operations from the mobile node, and an FBA is used to acknowledge an FBI 🎀. For the flow binding operation to be complete, a BU/BA exchange MUST be initiated by the mobile node after an FBI/FBA exchange ✨.
It's assumed that the home agent has already created binding cache entries for the mobile node before launching flow binding operations 🧚.
Due to an access-network change on the mobile-node side, some interfaces that used to be active may not be valid at the time of the flow binding operation by the home agent. In that case, even if the HA sends the FBI to the MN, the FBA won't return 😭. After retransmitting the FBIs for MAX_FBI_RETRIES times and not receiving the FBA, the HA determines that the target interface is not available 🙈.
If the mobile node doesn't support the FBI message, it responds with a Binding Error message with status set to 2 (unrecognized Mobility Header (MH) type value), as described in [RFC6275] 🌸. When a Binding Error message with status set to 2 is received in response to an FBI message, the home agent MUST NOT use an FBI message with that mobile node again 🚫.
4.1. Adding Flow Bindings ✨
Okay bestie, adding a flow binding basically means linking one particular flow to one of the care-of addresses on the mobile node 🦋. That care-of address shows up in the destination address of the packet or in the alternate care-of address option. It can also be indicated by the Target Care-of Address sub-option defined in Section 6.2.2 💅.
When a new flow binding gets added, the home agent sends an FBI with a Flow Identification Mobility option to the mobile node 🎀. In Figure 1, the mobile node is vibing with voice AND video over FID#1 (Flow Identifier #1) 🌸. Depending on the operator's policy, the network decides whether the video flow needs its own QoS, and if it does, the home agent sends the FBI. The Flow Identification Mobility option from [RFC6089] carries the current FID plus the Traffic Selector (TS) that picks out the video flow. The Flow Binding Action sub-option MUST indicate the Add operation defined in Section 6.2.1 🔥. The mobile node sends the FBA back to the home agent with the same options. Then the BU/BA exchange happens to set up the actual flow binding, as defined in [RFC6088], and the video traffic moves over FID#2 🫶.
+----+ +----+
| MN | | HA |
+----+ +----+
| FID#1(voice+video) |
|/==============================\|
|\==============================/|
| |
| FBI(add,FID#1,TS[video]) |
|<-------------------------------|
| FBA(FID#1,TS[video]) |
|------------------------------->|
| BU(FID#2,TS[video]) |
|------------------------------->|
| BA(FID#2,TS[video]) |
|<-------------------------------|
| |
| FID#1(voice) |
|<==============================>|
| FID#2(video) |
|<==============================>|
Figure 1: Example Call Flow for Adding a Flow Binding4.2. Deleting Flow Bindings 💀
When it's time to remove a flow binding, the home agent sends an FBI with a Flow Identification Mobility option. In that option, the Flow Binding Action sub-option says Delete. The Flow Identification Mobility option includes a unique FID, so the mobile node can find the flow binding and remove it 🧚.
4.3. Modifying Flow Bindings 🎀
When a flow binding needs to be modified (for example, changing the QoS attributes of the flow as defined in [PMIP6-QOS]), the home agent sends the mobile node an FBI message with the Flow Identification Mobility option. That option includes the FID to be modified. A Traffic Selector sub-option MAY come with the Flow Identification Mobility option and contain new attributes, e.g., the in Quality of Service option 💖.
4.4. Refreshing Flow Bindings 🌈
A flow binding gets refreshed by simply including the Flow Identification Mobility option with the Refresh Action field in the FBI message. The message should be sent before the flow binding expires ⏰. It updates existing bindings with new information. So all the information sent in the last refreshing message needs to be resent, otherwise that information will be lost 😭.
4.5. Moving Flow Bindings 🦋
The home agent can ask to move a flow that's tied to one interface of a multi-interfaced mobile node over to another interface, by sending an FBI message to the mobile node. The Action field of the Flow Binding Action sub-option is set to Move, and the address of the target interface is also included in the Target Care-of Address sub-option. Once the FBA is sent back to the home agent, the mobile node performs the flow mobility 🔥. Figure 2 shows a flow label moving as FID from the interface with sCoA to the one with tCoA, which is stored in the Binding Identity Mobility option 👑.
+----+ +----+
| MN | | HA |
+----+ +----+
|<=sCoA |
| |<=tCoA |
| | FBI(FID,tCoA) |
|<--------------------------------|
| | FBA(FID,tCoA) |
|-------------------------------->|
| | |
| | BU(BID[tCoA],FID) |
| |------------------------------>|
| | BA(BID[tCoA],FID) |
| |<------------------------------|
| | |
Figure 2: Example Call Flow for Moving a Flow Binding4.6. Revoking Flow Bindings 🙈
When the home agent or the network attached to it is overloaded, the home agent can revoke a flow binding that the mobile node registered. The home agent sends the mobile node an FBI message with a Flow Identification Mobility option in which the Flow Binding Action sub-option indicates the Revoke operation. When the MN gets an FBI with the Revoke operation, it decides whether the flow should be removed (de-registration) or moved to another interface. Then it returns the FBA with an appropriate status code. The mobile node SHOULD take an action by sending a new BU, for example, to deregister the flow 💅.
Now, the difference between revoking and deleting flow bindings (Section 4.2) is that the network can revoke the target flow using the procedures defined in [RFC5846], even if the mobile node doesn't do anything at all 💀✨.
5. Handling of the Flow Bindings List 📋
The flow bindings list defined in [RFC6089] needs to be updated like this after each protocol operation defined above is performed 🌸:
If an FBI contains a flow binding Add operation and the corresponding FBA has a status code equal to zero, the home agent MUST add a new entry to the flow bindings list. The FID, Flow Descriptor, FID-PRI, and Action fields are taken from the Flow Identification Mobility option. The binding identifier (BID) is copied from the Binding Reference sub-option. The Active/Inactive Flag is set to Active. Note that if BID is not available, it may be replaced by Target Care-of Address 🫶.
If an FBI contains a flow binding Delete operation and the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then delete the entry 🗑️.
If the home agent sends a Binding Revocation Indication message with the Flow Identification Mobility option, with the action field set to Revoke, and the corresponding Binding Revocation Acknowledgement message indicates acceptance, the home agent MUST locate the list entry corresponding to this flow and then delete the entry 💅.
If an FBI contains a flow binding Modify operation and the corresponding FBA has a status code equal to zero, the home agent MUST delete the list entry corresponding to this flow and then add a new entry, setting the values as defined in the Flow Identification Mobility option 🔥.
If an FBI contains a flow binding Refresh operation and the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then set the Active/Inactive Flag to Active 🌈.
If an FBI contains a flow binding Move operation and the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then change the BID value to the care-of address in the Flow Identification Mobility option 🦋.
If an FBI contains a flow binding Revoke operation and the corresponding FBA has a status code equal to zero, the home agent MUST locate the list entry corresponding to this flow and then delete the entry 👑.
Flow binding operations apply equally to IPv4 packets and IPv6 packets, as per Dual-Stack Mobile IPv6 [RFC5555]. To support the situation where there's a NAT/firewall between the mobile node and home agent, the NAT detection and NAT keepalive mechanisms defined in [RFC5555] MUST be used 🎀. When the mobile node and home agent are in IPv6-only and IPv4-only networks respectively, and NAT64 [RFC6146] sits in between, each node behaves as if the other node were in the same network domain. This scenario isn't fully described in [RFC5555], but the initial mobility binding is always performed by the mobile node, and the binding cache is created in the home agent. The destination address of the FBI SHALL be the mobile node's IPv4 care-of address in the binding cache entry 🧚.
6. Flow Binding Messages and Options 🦋
6.1. Mobility Header 💖
The messages described below follow the Mobility Header format specified in Section 6.1 of [RFC6275] ✨.
6.1.1. Flow Binding Indication ✨
okay bestie, so the home agent uses Flow Binding Indication messages to kick off flow binding operations toward the mobile node 🦋 These use MH Type value (21) for Flow Binding messages and a Flow Binding Type value of 1. Here's how the Message Data field in the Mobility Header is laid out 💅
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Binding Type = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Trigger |A| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Flow Binding Indication Mobility Header FormatSequence # 🎀 A 16-bit unsigned integer that the home agent uses to match a returned Flow Binding Acknowledgement with the Flow Binding Indication. It could be a random number ✨
Trigger 🔥 This is an 8-bit unsigned integer that tells you the event which made the home agent send the Flow Binding Indication message. The Trigger values currently defined are:
0Reserved1Unspecified2Administrative Reason3Possible Out-of-Sync BCE State250-255Reserved for Testing Purposes Only
All other values are unassigned.
Acknowledge (A) 🫶 The Acknowledge (A) bit is set by the home agent to request that a Flow Binding Acknowledgement be returned when the Flow Binding Indication is received.
Reserved 🙈 These fields are unused. They MUST be initialized to zero by the sender and MUST be ignored by the receiver.
Mobility options 🌈 This is a variable-length field, sized so the complete Mobility Header is an integer multiple of 8 octets long. Flow Identification Mobility options live in this field.
6.1.2. Flow Binding Acknowledgement 🦋
The Flow Binding Acknowledgement is how we confirm we got a Flow Binding Indication. The mobile node sends an FBA to acknowledge that it received an FBI to add, delete, modify, refresh, move, or revoke a flow binding. When it gets messages carrying Flow Identification Mobility option(s), the mobile node should copy each Flow Identification Mobility option into the Acknowledgement message. The FBA uses MH Type value (21) for Flow Binding messages and a Flow Binding Type value of 2. When that value shows up in the MH Type field, the Message Data field in the Mobility Header looks like this 🧚
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Binding Type = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Status | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Flow Binding Acknowledgement Mobility Header FormatSequence # 💖 The sequence number in the Flow Binding Acknowledgement is copied from the Sequence Number field in the Flow Binding Indication.
Status 👑 This is an 8-bit unsigned integer that shows how the receiving mobile node did with the Flow Binding Indication. Status values below 128 mean the Flow Binding Indication was processed successfully by the receiving node. Values greater than or equal to 128 mean it was rejected. The status values currently defined are:
0Success128Binding (target CoA) Does NOT Exist129Action NOT Authorized
All other values are unassigned.
Mobility options 🍓 This is a variable-length field, sized so the complete Mobility Header is an integer multiple of 8 octets long. It holds zero or more TLV-encoded mobility options, and Flow Identification Mobility options are included here too.
6.1.3. Flow Binding Revocation Extensions 💜
This spec lets Binding Revocation Indication and Binding Revocation Acknowledgement messages carry Flow Identification Mobility options, as defined in [RFC6089], with the extensions defined in this document ✨
6.2. New Options 🌸
This document defines new Flow Identification sub-options. They get included in the Flow Identification Mobility option specified in [RFC6089] 🎀
6.2.1. Flow Binding Action Sub-Option 🔥
This section defines a new sub-option for flow binding actions. It MUST be included in the Flow Identification Mobility option whenever the home agent sends it to the mobile node via the FBI message. Here's the format, shown in Figure 5 💅
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-opt Type |Sub-opt Length | Reserved | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Flow Binding Action Sub-OptionSub-opt Type 🦋 4
Sub-opt Length 🧚 This is the length of the sub-option in octets, not counting the Sub-opt Type and Sub-opt Length fields.
Action 💅 This is an 8-bit field that describes the processing required for the option. It can be assigned one of these new values:
11Add a flow binding12Delete a flow binding13Modify a flow binding14Refresh a flow binding15Move a flow binding16Revoke a flow binding
All other values are unassigned.
6.2.2. Target Care-of Address Sub-Option 🫶
This section introduces the Target Care-of Address sub-option, which may be included in the Flow Identification Mobility option. It's how we tell the mobile node that a flow binding is moving from one interface to another 🌈
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-opt Type |Sub-opt Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Target Care-of Address |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Target Care-of Address Sub-OptionSub-opt Type 🍓 5
Sub-opt Length 🎀 This is the length of the sub-option in octets, not counting the Sub-opt Type and Sub-opt Length fields.
Reserved 🙈 This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver.
Target Care-of Address 💖 This is the address of the interface that the flow is moved to. It could be an IPv4 or IPv6 address. This sub-option MUST be included when the action taken is "15 Move a flow binding" 🔥
7. Security Considerations 🚨
Okay, this part is SERIOUS 😭 Security issues for this document follow those of [RFC6088], [RFC6089], and [RFC5846]. This spec only lets the home agent manipulate the binding of flows that are currently registered with it, which is the same principle described in [RFC5846]. No additional security issue specific to this document is identified 🔐✨
8. Protocol Constants 💜
Maximum FBI retries (MAX_FBI_RETRIES) 🦋 This variable specifies the maximum number of times the HA MAY retransmit a Flow Binding Indication message when the FBA isn't returned within the time period specified by MAX_FBA_TIMEOUT. The default value for this parameter is 3.
Maximum FBA timeout (MAX_FBA_TIMEOUT) ⏱️ This variable specifies the maximum time in seconds the HA MUST wait before retransmitting another FBI message. The default for this parameter is 3 seconds.
9. IANA Considerations ✨
okay bestie, this is the part where we tell IANA (the folks who keep the official registries) what to do. it's giving admin energy but make it iconic 💅
IANA has taken the actions described below.
Action-1
This spec defines a new Mobility Header Type called "Flow Binding Message" 🦋. You'll find the message described in Section 6.1, and its type value is 21. That number was assigned in the "Mobility Header Types - for the MH Type field in the Mobility Header" registry. literally a whole new message type, we're so back 🫶
Action-2
This spec defines "Flow Binding Type" 🎀. IANA made a brand new sub-registry inside the "Mobile IPv6 parameters" registry for it. Flow Binding Type is described in Sections 6.1.1 and 6.1.2, which reserve these values:
+-------+------------------------------+--------------+
| Value | Description | Reference |
+-------+------------------------------+--------------+
| 0 | Unassigned | |
+-------+------------------------------+--------------+
| 1 | Flow Binding Indication | [RFC7109] |
+-------+------------------------------+--------------+
| 2 | Flow Binding Acknowledgement | [RFC7109] |
+-------+------------------------------+--------------+
| 3-255 | Unassigned | |
+--------------------------------------+--------------+Future assignments in the "Flow Binding Type" registry are to be made through RFC Required [RFC5226]. so if anyone wants a new number later, it's an RFC Required situation 💜
Action-3
This spec defines "Flow Binding Indication Triggers" 🌸. IANA made another new sub-registry inside the "Mobile IPv6 parameters" registry. The trigger values are described in Section 6.1.1, which reserves these:
+---------+------------------------------------+--------------+
| Value | Description | Reference |
+---------+------------------------------------+--------------+
| 0 | Reserved | [RFC7109] |
+---------+------------------------------------+--------------+
| 1 | Unspecified | [RFC7109] |
+---------+------------------------------------+--------------+
| 2 | Administrative Reason | [RFC7109] |
+---------+------------------------------------+--------------+
| 3 | Possible Out-of-Sync BCE State | [RFC7109] |
+---------+------------------------------------+--------------+
| 4-249 | Unassigned | |
+---------+------------------------------------+--------------+
| 250-255 | Reserved for Testing Purposes Only | [RFC7109] |
+----------------------------------------------+--------------+Future assignments in the "Flow Binding Indication Triggers" registry are to be made through RFC Required [RFC5226]. same energy as before, bestie 🧚
Action-4
This spec defines "Flow Binding Acknowledgement Status Codes" 💖. IANA made a new sub-registry inside the "Mobile IPv6 parameters" registry for these. The status codes are described in Section 6.1.2, which reserves these values:
+---------+-------------------------------------+--------------+
| Value | Description | Reference |
+---------+-------------------------------------+--------------+
| 0 | Success | [RFC7109] |
+---------+-------------------------------------+--------------+
| 1-127 | Unassigned | |
+---------+-------------------------------------+--------------+
| 128 | Binding (target CoA) Does NOT Exist | [RFC7109] |
+---------+-------------------------------------+--------------+
| 129 | Action NOT Authorized | [RFC7109] |
+---------+-------------------------------------+--------------+
| 130-255 | Unassigned | |
+---------+-------------------------------------+--------------+Future assignments in the "Flow Binding Acknowledgement Status Codes" are to be made through RFC Required [RFC5226]. 🔥
Action-5
This spec defines two new Flow Identification sub-options 👑: the "Flow Binding Action" sub-option and the "Target Care-of Address" sub-option. They're described in Sections 6.2.1 and 6.2.2, and their sub-option values are 4 and 5, respectively, as assigned in the "Flow Identification Sub-options" registry. two new sub-options, both with official numbers, iconic 🌈
Action-6
This spec defines "Flow Binding Action Values" 🧚♀️. IANA made a new sub-registry inside the "Mobile IPv6 parameters" registry. The action values are described in Section 6.2.1, which reserves these:
+--------+-------------------------------------+--------------+
| Value | Description | Reference |
+--------+-------------------------------------+--------------+
| 0-10 | Unassigned | |
+--------+-------------------------------------+--------------+
| 11 | Add a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 12 | Delete a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 13 | Modify a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 14 | Refresh a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 15 | Move a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 16 | Revoke a flow binding | [RFC7109] |
+--------+-------------------------------------+--------------+
| 17-255 | Unassigned | |
+--------+-------------------------------------+--------------+Future assignments in the "Flow Binding Action Values" registry are to be made through RFC Required [RFC5226]. ✨
10. References 🎀
10.1. Normative References
These are the must-read sources, the ones this spec leans on hard 💅
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts
and Routers", RFC 5555, June 2009.
[RFC5846] Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K.,
and P. Yegani, "Binding Revocation for IPv6 Mobility",
RFC 5846, June 2010.
[RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N.
Montavont, "Traffic Selectors for Flow Bindings", RFC
6088, January 2011.
[RFC6089] Tsirtsis, G., Soliman, H., Montavont, N., Giaretta, G.,
and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and
Network Mobility (NEMO) Basic Support", RFC 6089,
January 2011.
[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful
NAT64: Network Address and Protocol Translation from
IPv6 Clients to IPv4 Servers", RFC 6146, April 2011.
[RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility
Support in IPv6", RFC 6275, July 2011.10.2. Informative References
[PMIP6-QOS] Liebsch, M., Seite, P., Yokota, H., Korhonen, J., and S.
Gundavelli, "Quality of Service Option for Proxy Mobile
IPv6", Work in Progress, December 2013.Authors' Addresses 🫶
Hidetoshi Yokota
KDDI Lab
2-1-15 Ohara
Fujimino, Saitama 356-8502
Japan
EMail: yokota@kddilabs.jp
Dae-Sun Kim
JEJU Technopark
217, Jungang-ro (St)
Jejusi, Jeju Special Self-Governing Province 690-787
Korea
EMail: dskim@jejutp.or.kr
Behcet Sarikaya
Huawei USA
5340 Legacy Drive, Building 3
Plano, TX 75024
US
Phone: +1 469-277-5839
EMail: sarikaya@ieee.org
Frank Xia
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Phone: +86-25-56625443
EMail: xiayangsong@huawei.com📦 where this page comes from
- ietf: rfc7109 2014-02
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms