draft-ietf-mext-flow-binding-09.txt   draft-ietf-mext-flow-binding-10.txt 
IETF MEXT Working Group G. Tsirtsis IETF MEXT Working Group G. Tsirtsis
Internet-Draft Qualcomm Internet-Draft Qualcomm
Updates: 5648 (if approved) H. Soliman Updates: 5648 (if approved) H. Soliman
Intended status: Standards Track Elevate Technologies Intended status: Standards Track Elevate Technologies
Expires: February 18, 2011 N. Montavont Expires: March 18, 2011 N. Montavont
IT/TB IT/TB
G. Giaretta G. Giaretta
Qualcomm Qualcomm
K. Kuladinithi K. Kuladinithi
University of Bremen University of Bremen
August 17, 2010 September 14, 2010
Flow Bindings in Mobile IPv6 and NEMO Basic Support Flow Bindings in Mobile IPv6 and NEMO Basic Support
draft-ietf-mext-flow-binding-09.txt draft-ietf-mext-flow-binding-10.txt
Abstract Abstract
This document introduces extensions to Mobile IPv6 that allow nodes This document introduces extensions to Mobile IPv6 that allow nodes
to bind one or more flows to a care-of address. These extensions to bind one or more flows to a care-of address. These extensions
allow multihomed nodes to instruct home agents and other Mobile IPv6 allow multihomed nodes to instruct home agents and other Mobile IPv6
entities to direct inbound flows to specific addresses. entities to direct inbound flows to specific addresses.
Status of this Memo Status of this Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 18, 2011. This Internet-Draft will expire on March 18, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 4 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Mobile IPv6 Extensions . . . . . . . . . . . . . . . . . . . . 8 4. Mobile IPv6 Extensions . . . . . . . . . . . . . . . . . . . . 8
4.1. Definition Update for Binding Identifier Mobility 4.1. Definition Update for Binding Identifier Mobility
Option . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Option . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. Flow Identification Mobility Option . . . . . . . . . . . 8 4.2. Flow Identification Mobility Option . . . . . . . . . . . 8
4.2.1. Flow Identification Sub-Options definition . . . . . . 11 4.2.1. Flow Identification Sub-Options definition . . . . . . 10
4.2.2. Flow Summary Mobility Option . . . . . . . . . . . . . 15 4.2.2. Flow Summary Mobility Option . . . . . . . . . . . . . 14
4.3. Flow Bindings entries list and its relationship to 4.3. Flow Bindings entries list and its relationship to
Binding Cache . . . . . . . . . . . . . . . . . . . . . . 16 Binding Cache . . . . . . . . . . . . . . . . . . . . . . 15
5. Protocol operations . . . . . . . . . . . . . . . . . . . . . 19 5. Protocol operations . . . . . . . . . . . . . . . . . . . . . 18
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1.1. Preferred Care-of address . . . . . . . . . . . . . . 19 5.1.1. Preferred Care-of address . . . . . . . . . . . . . . 18
5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 19 5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 18
5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 20 5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 19
5.2.2. Sending BU with Flow Identification Mobility 5.2.2. Sending BU with Flow Identification Mobility
Options . . . . . . . . . . . . . . . . . . . . . . . 20 Options . . . . . . . . . . . . . . . . . . . . . . . 19
5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 22 5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 21
5.2.4. Removing flow bindings . . . . . . . . . . . . . . . . 23 5.2.4. Removing flow bindings . . . . . . . . . . . . . . . . 21
5.2.5. Returning Home . . . . . . . . . . . . . . . . . . . . 23 5.2.5. Returning Home . . . . . . . . . . . . . . . . . . . . 22
5.2.6. Receiving Binding Acknowledgements . . . . . . . . . . 23 5.2.6. Receiving Binding Acknowledgements . . . . . . . . . . 22
5.2.7. Return Routability Procedure . . . . . . . . . . . . . 24 5.2.7. Return Routability Procedure . . . . . . . . . . . . . 22
5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 24 5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 23
5.3.1. Handling Binding Identifier Mobility Options . . . . . 24 5.3.1. Handling Binding Identifier Mobility Options . . . . . 23
5.3.2. Handling Flow Identification Mobility Options . . . . 25 5.3.2. Handling Flow Identification Mobility Options . . . . 23
5.3.3. Handling Flow Summary Mobility Option . . . . . . . . 28 5.3.3. Handling Flow Summary Mobility Option . . . . . . . . 26
5.3.4. Flow Binding Removals . . . . . . . . . . . . . . . . 28 5.3.4. Flow Binding Removals . . . . . . . . . . . . . . . . 27
5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 29 5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 27
5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 29 5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 28
6. MTU Considerations . . . . . . . . . . . . . . . . . . . . . . 32 6. MTU Considerations . . . . . . . . . . . . . . . . . . . . . . 30
7. Security considerations . . . . . . . . . . . . . . . . . . . 33 7. Security considerations . . . . . . . . . . . . . . . . . . . 31
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 34
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 38 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 36
11.1. Normative References . . . . . . . . . . . . . . . . . . . 39 11.1. Normative References . . . . . . . . . . . . . . . . . . . 36
11.2. Informative References . . . . . . . . . . . . . . . . . . 39 11.2. Informative References . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
Mobile IPv6 [RFC3775], DSMIPv6 [RFC5555] and NEMO Basic Support Mobile IPv6 [RFC3775], DSMIPv6 [RFC5555] and NEMO Basic Support
skipping to change at page 5, line 34 skipping to change at page 5, line 34
bind a particular flow to a care-of address without affecting other bind a particular flow to a care-of address without affecting other
flows using the same home address. In addition, this specification flows using the same home address. In addition, this specification
allows to bind a particular flow to a particular care-of address allows to bind a particular flow to a particular care-of address
directly with correspondent node and mobility agents (i.e., home directly with correspondent node and mobility agents (i.e., home
agents [RFC3775] and mobility anchor points [RFC5380]). agents [RFC3775] and mobility anchor points [RFC5380]).
In this document, a flow is defined as a set of IP packets matching a In this document, a flow is defined as a set of IP packets matching a
traffic selector. A traffic selector can identify the source and traffic selector. A traffic selector can identify the source and
destination IP addresses, transport protocol number, the source and destination IP addresses, transport protocol number, the source and
destination port numbers and other fields in IP and higher layer destination port numbers and other fields in IP and higher layer
headers. This specification, however, does not define traffic headers. This specification, however, does not define traffic di
selectors and it is assumed that one or more ways of defining traffic going to be defined in other specifications. This specification,
selectors are going to be defined in other specifications. This however, does define the traffic selector sub-option format to be
specification, however, does define the traffic selector sub-option used for any specific traffic selectors.
format to be used for any defined traffic selectors.
Using the flow identifier option introduced in this specification a Using the flow identifier option introduced in this specification a
mobile node / mobile router can bind one or more flows to a care-of mobile node / mobile router can bind one or more flows to a care-of
address while maintaining the reception of other flows on another address while maintaining the reception of other flows on another
care-of address. The mobile node / mobile router assembles the flow care-of address. The mobile node / mobile router assembles the flow
binding request based on local policies, link characteristics and the binding requests based on local policies, link characteristics and
types of applications running at the time. Such policies are outside the types of applications running at the time. Such policies are
the scope of this document. outside the scope of this document.
It should be noted that the flow identification mobility option can It should be noted that the flow identification mobility option can
be associated with any binding update, whether it is sent to a be associated with any binding update, whether it is sent to a
mobility agent or a correspondent node. mobility agent or a correspondent node.
Note that per-packet load balancing may have negative impacts on TCP Note that per-packet load balancing may have negative impacts on TCP
congestion avoidance mechanisms as it is desirable to maintain order congestion avoidance mechanisms as it is desirable to maintain order
between packets belonging to the same TCP connection. This behaviour between packets belonging to the same TCP connection. This behaviour
is specified in [RFC2702]. Other negative impacts are also foreseen is specified in [RFC2702]. Other negative impacts are also foreseen
for other types of real time connections due to the potential for other types of real time connections due to the potential
skipping to change at page 7, line 21 skipping to change at page 7, line 21
special handling either by the Home Agent (HA), the Corresponding special handling either by the Home Agent (HA), the Corresponding
Node (CN) or the (Mobility Anchor Point) MAP. Node (CN) or the (Mobility Anchor Point) MAP.
Traffic Selector: One or more parameters that can be matched Traffic Selector: One or more parameters that can be matched
against fields in the packet's headers for the purpose of against fields in the packet's headers for the purpose of
classifying a packet. Examples of such parameters include the classifying a packet. Examples of such parameters include the
source and destination IP addresses, transport protocol number, source and destination IP addresses, transport protocol number,
the source and destination port numbers and other fields in IP and the source and destination port numbers and other fields in IP and
higher layer headers. higher layer headers.
Flow binding: It consists of a traffic selector, and an action. Flow binding: It consists of a traffic selector, and one or more
IP packets from one or more flows that match the traffic selector BIDs. IP packets from one or more flows that match the traffic
associated with the flow binding, are processed according to the selector associated with the flow binding, are forwarded to the
action associated with the same flow binding. BIDs associated with the same flow binding.
Flow Identifier: A flow identifier uniquely identifies a flow Flow Identifier: A flow identifier uniquely identifies a flow
binding associated with a mobile node. It is generated by a binding associated with a mobile node. It is generated by a
mobile node and is cached in the table of flow binding entries mobile node and is cached in the table of flow binding entries
maintained by the MN, HA, CN or MAP. maintained by the MN, HA, CN or MAP.
4. Mobile IPv6 Extensions 4. Mobile IPv6 Extensions
This section introduces extensions to Mobile IPv6 that are necessary This section introduces extensions to Mobile IPv6 that are necessary
for supporting the flow binding mechanism described in this document. for supporting the flow binding mechanism described in this document.
skipping to change at page 9, line 10 skipping to change at page 9, line 10
allows the receiver of a binding update to install policies on a allows the receiver of a binding update to install policies on a
traffic flow and route it to a given care-of address. Multiple traffic flow and route it to a given care-of address. Multiple
options may exist within the same binding update message. The options may exist within the same binding update message. The
alignment requirement for this option is 2n. alignment requirement for this option is 2n.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | FID | | Option Type | Option Len | FID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID-PRI | Action | Rsvd | Status | | FID-PRI | Reserved | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-options (optional) ... | Sub-options (optional) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: The Flow Identification Mobility Option Figure 2: The Flow Identification Mobility Option
Option Type Option Type
To be assigned by IANA To be assigned by IANA
skipping to change at page 9, line 35 skipping to change at page 9, line 35
FID FID
The Flow Identifier field is a 16-bit unsigned integer that The Flow Identifier field is a 16-bit unsigned integer that
includes the unique identifier for the flow binding. This includes the unique identifier for the flow binding. This
field is used to refer to an existing flow binding or to create field is used to refer to an existing flow binding or to create
a new flow binding. The value of this field is set by the a new flow binding. The value of this field is set by the
mobile node. FID = 0 is reserved and MUST NOT be used. mobile node. FID = 0 is reserved and MUST NOT be used.
FID-PRI FID-PRI
This is an 8-bit unsigned priority field to indicate the This is a 16-bit unsigned integer priority field to indicate
priority of a particular option. This field is needed in cases the priority of a particular option. This field is needed in
where two different flow descriptions in two different options cases where two different flow descriptions in two different
overlap. The priority field decides which policy should be options overlap. The priority field decides which policy
executed in those cases. A lower number in this field should be executed in those cases. A lower number in this
indicates a higher priority. Value '0' is reserved and MUST field indicates a higher priority. Value '0' is reserved and
NOT be used. FID-PRI MUST be unique to each of the flows MUST NOT be used. FID-PRI MUST be unique to each of the flows
pertaining to a given MN. In other words, two FIDs MUST NOT be pertaining to a given MN. In other words, two FIDs MUST NOT be
associated with the same FID-PRI value associated with the same FID-PRI value.
Action
This 8-bit unsigned integer field specifies the action that
needs to be taken by the receiver of the binding update
containing the flow identification option. The details of
these requests are discussed below. The following values are
reserved for the Action field in this option:
0 Reserved and MUST NOT be used
1 'Discard'. This value indicates a request to discard all
packets in the flow described by the option. No BIDs are
associated with this Action. Care should be taken when
using this Action as it will lead to disrupting applications
communication. Implementations may consider notifying
impacted applications in mobile nodes.
2 'Forward'. This value indicates a request to send the
flow to one or more addresses indicated in the binding
reference sub-option (see Section 4.2.1.3). One or more
BIDs MUST be associated with this Action. If only one BID
is associated with this action then it is essentially a
request to forward packets to that CoA, otherwise matching
packets are replicated and forwarded to all of the indicated
CoAs. Care should be taken when multiple BIDs are used in
combination with the 'Forward' action as some transport
layers may not be able to handle packet duplication and this
can affect their performance.
3-255 Reserved for future use
Rsvd
This field is unused. It MUST be set to zero by the sender and
ignored by the receiver.
Status Status
This 8-bit unsigned integer field indicates the success or This 8-bit unsigned integer field indicates the success or
failure of the flow binding operation for the particular flow failure of the flow binding operation for the particular flow
in the option. This field is not relevant to the binding in the option. This field is not relevant to the binding
update message as a whole or to other flow identification update message as a whole or to other flow identification
options. This field is only relevant when included in the options. This field is only relevant when included in the
Binding Acknowledgement message and must be ignored in the Binding Acknowledgement message and must be ignored in the
binding update message. The following values are reserved for binding update message. The following values are reserved for
skipping to change at page 11, line 14 skipping to change at page 10, line 24
129 Flow binding rejected, reason unspecified 129 Flow binding rejected, reason unspecified
130 Flow identification mobility option malformed 130 Flow identification mobility option malformed
131 BID not found 131 BID not found
132 FID not found 132 FID not found
133 Traffic selector format not supported 133 Traffic selector format not supported
134 Discard function not supported
135 Forward function not supported
Sub-options (optional) Sub-options (optional)
zero or more sub-options, defined in Section 4.2.1 zero or more sub-options, defined in Section 4.2.1
4.2.1. Flow Identification Sub-Options definition 4.2.1. Flow Identification Sub-Options definition
Flow identification sub-options are encoded within the remaining Flow identification sub-options are encoded within the remaining
space of the flow identification mobility option, using a sub-option space of the flow identification mobility option, using a sub-option
type-length-value (TLV) format as follows: type-length-value (TLV) format as follows:
skipping to change at page 13, line 32 skipping to change at page 12, line 37
receiver. receiver.
The PadN sub-option is used to insert two or more octets of padding The PadN sub-option is used to insert two or more octets of padding
in the flow identification mobility option. For N octets of padding, in the flow identification mobility option. For N octets of padding,
the sub-option Length field contains the value N, and the sub-option the sub-option Length field contains the value N, and the sub-option
data consists of N-2 zero-valued octets. PadN sub-option data MUST data consists of N-2 zero-valued octets. PadN sub-option data MUST
be ignored by the receiver. be ignored by the receiver.
4.2.1.3. Binding Reference Sub-option 4.2.1.3. Binding Reference Sub-option
This section introduces the binding reference sub-option, which may This section introduces the binding reference sub-option, included in
be included in the flow identification mobility option. A node MUST the flow identification mobility option. A node MUST NOT include
NOT include more than one binding reference sub-options in a given more than one binding reference sub-options in a given flow binding
flow binding identification option. The binding reference sub-option identification option. The binding reference sub-option includes one
includes one or more BIDs defined in MCoA [RFC5648]. When this sub- or more BIDs defined in MCoA [RFC5648]. This sub-option associates
option is included in the flow identification mobility option it the flow described in a a flow identification mobility option with
associates the flow described with one or more registered BIDs. one or more registered BIDs.
When binding a flow using this sub-option, the binding identifier When binding a flow using this sub-option, the binding identifier
mobility option, defined in [RFC5648], MUST be included in either the mobility option, defined in [RFC5648], MUST be included in either the
same or an earlier Binding Update (BU). The binding reference sub- same or an earlier Binding Update (BU). The binding reference sub-
option is shown below. The alignment requirement for this sub-option option is shown below. The alignment requirement for this sub-option
is 2n. is 2n.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 33 skipping to change at page 14, line 33
Traffic Selector Traffic Selector
A variable length field, the format and content of which is out of A variable length field, the format and content of which is out of
scope for this specification. The traffic selector defined in scope for this specification. The traffic selector defined in
[I-D.ietf-mext-binary-ts] is mandatory to implement. [I-D.ietf-mext-binary-ts] is mandatory to implement.
4.2.2. Flow Summary Mobility Option 4.2.2. Flow Summary Mobility Option
The flow summary mobility option is a new mobility option [RFC3775], The flow summary mobility option is a new mobility option [RFC3775],
which includes one or more flow identifiers (FIDs) for the purpose of which includes one or more flow identifiers (FIDs) for the purpose of
refreshing their state. A node MUST NOT include more than one flow refreshing their state. The alignment requirement for this option is
summary mobility option in a given binding update message. The 2n.
alignment requirement for this option is 2n.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | FID | | Option Type | Option Len | FID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID ........ | FID ........
+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-
Figure 6: The Flow Summary Mobility Option Figure 6: The Flow Summary Mobility Option
skipping to change at page 16, line 31 skipping to change at page 15, line 31
address, and the lifetime of the binding. The binding cache has been address, and the lifetime of the binding. The binding cache has been
extended by [RFC5648] to include more than one care-of addresses and extended by [RFC5648] to include more than one care-of addresses and
to associate each of them with a Binding Identifier (BID). to associate each of them with a Binding Identifier (BID).
This specification does not modify the mobile IPv6 binding cache any This specification does not modify the mobile IPv6 binding cache any
further. further.
Flow bindings can be thought of as a conceptual list of entries that Flow bindings can be thought of as a conceptual list of entries that
is separate from the binding cache. The flow bindings list contains is separate from the binding cache. The flow bindings list contains
an entry for each of the registered flow bindings. Flow binding an entry for each of the registered flow bindings. Flow binding
entries can point to an entry in the binding cache by means of the entries point to an entry in the binding cache by means of the BID.
BID. Each flow binding entry includes the following parameters: Each flow binding entry includes the following parameters:
o FID (Flow Identifier): For a given mobile node, identified by its o FID (Flow Identifier): For a given mobile node, identified by its
primary home address, the FID MUST uniquely identify an entry, primary home address, the FID MUST uniquely identify an entry,
i.e. a unique flow binding. Each mobile node can only have a i.e. a unique flow binding. Each mobile node can only have a
single entry identified by a given FID at any one time. A given single entry identified by a given FID at any one time. A given
FID number space is used for all the addresses associated to a FID number space is used for all the addresses associated to a
given MN by the HA (e.g., via [RFC3963]). Different mobile nodes given MN by the HA (e.g., via [RFC3963]). Different mobile nodes
use the same FID number space. use the same FID number space.
o A Traffic Selector: Included in a traffic selector sub-option. o A Traffic Selector: Included in a traffic selector sub-option.
o BID(s): The list of BIDs associated with the entry as defined by o BID(s): The list of BIDs associated with the entry as defined by
the binding reference sub-option included in the FID option that the binding reference sub-option included in the FID option that
created it. created it.
o Action: The action associated with a given entry as defined by the
Action field of the FID option that created it
o Active/Inactive flag: This flag indicates whether the entry is o Active/Inactive flag: This flag indicates whether the entry is
active or inactive. active or inactive.
o FID-PRI: This field indicates the priority of the flow and is used o FID-PRI: This field indicates the priority of the flow binding and
to break the tie between overlapping flows. is used to break the tie between overlapping flow bindings.
The flow bindings list is associated with a given mobile node, and The flow bindings list is associated with a given mobile node, and
the correspondent binding cache. An entry in the flow bindings list, the correspondent binding cache. An entry in the flow bindings list,
however, is identified by the FID and the list is ordered according however, is identified by the FID and the list is ordered according
to the FID-PRI field as defined in the FID option that created each to the FID-PRI field as defined in the FID option that created each
entry. entry.
For entries that take BIDs (i.e., entries that do not indicate a A valid BID is required to make the entry 'Active'. If all of the
'Discard' action), a valid BID is required to make the entry BIDs pointed to by a given entry are deregistered [RFC5648], the flow
'Active'. If all of the BIDs pointed to by a given entry are binding entry becomes 'Inactive', in other words it does not affect
deregistered [RFC5648], the flow binding entry becomes 'Inactive', in data traffic. Note that an entry becomes 'Inactive' only if all of
other words it does not affect data traffic. Note that if the action the BIDs are deregistered. If only some of the BIDs are still valid,
parameter in an entry indicates 'Forward' then the entry becomes the invalid BIDs are simply ignored.
'Inactive' only if all of the BIDs are deregistered. If only some of
the BIDs are still valid, the invalid BIDs are simply ignored.
Also note that the state described in this section is maintained by Also note that the state described in this section is maintained by
the mobile node as well as in mobility agents and correspondent the mobile node as well as in mobility agents and correspondent
nodes. As such the mobile node is fully aware of which are the valid nodes. As such the mobile node is fully aware of which are the valid
BIDs at any time and which flow binding entries are active/inactive. BIDs at any time and which flow binding entries are active/inactive.
Section 5 defines how these flow binding entries are manipulated by Section 5 defines how these flow binding entries are manipulated by
the mobile node in detail. the mobile node in detail.
As an example the following represents an ordered flow binding entry As an example the following represents an ordered flow binding entry
table for a mobile node that has registered multiple care-of table for a mobile node that has registered multiple care-of
addresses and flow bindings. addresses and flow bindings.
FID-PRI FID Traffic Selector BIDs Action A/I FID-PRI FID Traffic Selector BIDs A/I
------- --- ---------------- ---- ------- ------ ------- --- ---------------- ---- -------
10 4 TCP 2 Forward Active 10 4 TCP 2 Active
20 3 srcAddr=IPx N/A Discard Active 30 2 srcAddr=IPy 4 Inactive
30 2 srcAddr=IPy 4 Forward Inactive 40 5 UDP 1,3 Active
40 5 UDP 1,3 Forward Active
Ordered Flow Binding Entries Ordered Flow Binding Entries
According to the above list of flow binding entries, all TCP traffic According to the above list of flow binding entries, all TCP traffic
will match the first entry, and according to the Action indicated it will match the first entry, and will be forwarded to BID2,
will be forwarded to BID2, corresponding to a given care-of address corresponding to a given care-of address (IP3), as shown below.
(IP3), as shown below. Any traffic that is not TCP, but has as
source address IPx will match the second entry, and according to the
associated Action it will be discarded. Note that any TCP traffic
with source address IPx will match the first entry and thus it will
be forwarded as per that entry.
The third entry is marked as Inactive since the BID 4 does not exist The second entry is marked as Inactive since the BID 4 does not exist
in the ordered list of BID entries below. Inactive entries do not in the ordered list of BID entries below. Inactive entries do not
affect traffic, i.e., packets are not matched against them. affect traffic, i.e., packets are not matched against them.
Any UDP traffic that does not match any of the earlier entries will Any UDP traffic that does not match any of the earlier entries will
match the fourth rule and according to the Action indicated, it will match the third rule, at which point it will be replicated and
be replicated and forwarded to BIDs 1 and 3, corresponding to care-of forwarded to BIDs 1 and 3, corresponding to care-of addresses IP1 and
addresses IP1 and IP2 shown below. IP2 shown below.
Finally any remaining packets that do not match any of the entries Finally any remaining packets that do not match any of the entries
above will be simply forwarded to the care-of address indicated by above will be simply forwarded to the care-of address indicated by
the highest order BID in the table below. In the example, such the highest order BID in the table below. In the example, such
packets will be forwarded to BID1 corresponding to care-of address packets will be forwarded to BID1 corresponding to care-of address
IP1. IP1.
BID-PRI BID CoA BID-PRI BID CoA
--------- --- --- --------- --- ---
20 1 IP1 20 1 IP1
skipping to change at page 19, line 16 skipping to change at page 18, line 16
5.1. General 5.1. General
This specification introduces a flow bindings list of entries and an This specification introduces a flow bindings list of entries and an
ordered list of flow binding identifiers, allowing mobile nodes to ordered list of flow binding identifiers, allowing mobile nodes to
associate flow binding policies with the registered care-of associate flow binding policies with the registered care-of
addresses. addresses.
The flow identification mobility option defines how the mobile node The flow identification mobility option defines how the mobile node
can control a set of flow binding entries maintained in a mobility can control a set of flow binding entries maintained in a mobility
agent, or correspondent node. The fields of the flow identification agent, or correspondent node.
mobility option are necessary for ordering flow identification
mobility options, indicating the sort of action that should be
undertaken to the recipient's flow binding list of entries or for
carrying the results of such a petition.
This specification allows mobile nodes to direct flows to a This specification allows mobile nodes to direct flows to a
particular care-of address. The granularity of what constitutes a particular care-of address. The granularity of what constitutes a
flow depends on the traffic selector used. flow depends on the traffic selector used.
The remainder of this section discusses how mobile nodes can use the The remainder of this section discusses how mobile nodes can use the
options and sub-options defined in this document when sending binding options and sub-options defined in this document when sending binding
updates to the correspondent node, home agent, or mobility anchor updates to the correspondent node, home agent, or mobility anchor
point. In addition, refresh, deletion, and modification of flow point. In addition, refresh, deletion, and modification of flow
binding entries are all discussed below. binding entries are all discussed below.
skipping to change at page 20, line 20 skipping to change at page 19, line 16
binding. More than one flow identification mobility options MAY be binding. More than one flow identification mobility options MAY be
included in the same binding update but each of them MUST include a included in the same binding update but each of them MUST include a
different FID. In other words, two flow identification options in different FID. In other words, two flow identification options in
the same message can not be about the same flow binding. the same message can not be about the same flow binding.
All flow binding state MUST be refreshed in every binding update the All flow binding state MUST be refreshed in every binding update the
mobile node sends. Any previously registered flow binding that is mobile node sends. Any previously registered flow binding that is
not included in a given binding update will be deleted. So, any flow not included in a given binding update will be deleted. So, any flow
bindings that are not added or modified by a flow identification bindings that are not added or modified by a flow identification
mobility option, but have previously registered and need to be mobility option, but have previously registered and need to be
maintained MUST be included in a flow summary mobility option. Only maintained MUST be included in a flow summary mobility option.
one flow summary mobility option can be included in a given binding
update.
5.2.1. Sending BU with BID Options 5.2.1. Sending BU with BID Options
This specification (see Section 4.1) updates the definition of the This specification (see Section 4.1) updates the definition of the
binding identifier mobility option, originally defined in [RFC5648]. binding identifier mobility option, originally defined in [RFC5648].
According to this specification the BID option includes a BID-PRI According to this specification the BID option includes a BID-PRI
field assigning each registered care-of address a priority, and thus field assigning each registered care-of address a priority, and thus
placing them in an ordered list as also described in Section 4.3. placing them in an ordered list as also described in Section 4.3.
To ensure backwards compatibility with [RFC5648] for the purpose of To ensure backwards compatibility with [RFC5648] for the purpose of
skipping to change at page 21, line 13 skipping to change at page 20, line 7
binding entries maintained by the receiver. The care-of address(es) binding entries maintained by the receiver. The care-of address(es)
associated with each flow identification mobility options in the associated with each flow identification mobility options in the
binding update, must be logically registered by this binding update, binding update, must be logically registered by this binding update,
or must have already been registered by the receiver of the binding or must have already been registered by the receiver of the binding
update in an earlier binding update, as defined in Section 5.2.1. update in an earlier binding update, as defined in Section 5.2.1.
The flow identification mobility option MUST include a unique flow The flow identification mobility option MUST include a unique flow
identifier in the FID field. The FID needs only be unique for the identifier in the FID field. The FID needs only be unique for the
receiver of the binding update and for the same sender, i.e. the same receiver of the binding update and for the same sender, i.e. the same
FID can be used across different receivers of the binding update, for FID can be used across different receivers of the binding update, for
the same sender. the same sender. The FID-PRI field is set to the desired unique
priority of the FID, defining the order of the flow binding to be
The FID-PRI field is set to the desired unique priority of the added in the list of flow binding entries as defined in Section 4.3.
FID, defining the order of the flow binding to be added in the The Status field is set to zero in all binding update messages.
list of flow binding entries as defined in Section 4.3.
The Action field is set to one of the defined action codes (see
Section 4.2).
The Status field is set to zero in all binding update messages.
Since this flow identification mobility option is requesting the Since this flow identification mobility option is requesting the
addition of a new flow binding in the list of flow bindings addition of a new flow binding in the list of flow bindings
maintained by the receiver, the mobile node MUST include exactly one maintained by the receiver, the mobile node MUST include exactly one
Traffic Selector sub-option (see Section 4.2.1.4) describing the flow Traffic Selector sub-option (see Section 4.2.1.4) describing the flow
associated with the new flow binding. The TS Format field of the associated with the new flow binding. The TS Format field of the
Traffic Selector sub-option MUST be set to the non-zero value of the Traffic Selector sub-option MUST be set to the non-zero value of the
format used by the mobile node. format used by the mobile node.
The mobile node MAY also include up to one BID Reference sub-option The mobile node MUST also include exactly one BID Reference sub-
(see Section 4.2.1.3) to associate the flow binding with a given set option (see Section 4.2.1.3) to associate the flow binding with a
of BIDs and corresponding CoAs. Depending on the Action field of the given set of BIDs and corresponding CoAs.
flow identification mobility option, the following rules MUST be
followed with respect to the binding reference sub-option:
- if the Action indicates 'Discard', the binding reference sub-
option SHOULD NOT be included. If it is included it will be
ignored by the receiver.
- if the Action indicates 'Forward', a single binding reference
sub-option with one or more BIDs MUST be included.
5.2.2.2. Updating Flow Bindings 5.2.2.2. Updating Flow Bindings
Flow binding modification is essentially a process where parameters Flow binding modification is essentially a process where parameters
associated with an existing flow binding in the list of flow binding associated with an existing flow binding in the list of flow binding
entries is replaced by parameters included in the flow identification entries is replaced by parameters included in the flow identification
mobility option, and the same FID is maintained. With this procedure mobility option, and the same FID is maintained. With this procedure
the mobile node can change the action, the priority, the BID, and/or the mobile node can change the priority, the BID(s), and/or the
the traffic selector associated with a flow binding. traffic selector associated with a flow binding.
To modify an existing flow binding the mobile node MUST send a To modify an existing flow binding the mobile node MUST send a
binding update with a flow identification option, with the FID field binding update with a flow identification option, with the FID field
set to one of the FID values already in the list of flow binding set to one of the FID values already in the list of flow binding
entries. entries. The FID-PRI field MUST be set to the priority value for the
flow binding entry. The Status field is set to zero since this
The FID-PRI and Action fields MUST be set to the priority value option is in a binding update.
for the flow binding entry.
The Status field is set to zero since this option is in a binding
update.
The mobile node MAY include exactly one traffic selector sub-option The mobile node MAY include exactly one traffic selector sub-option
(see Section 4.2.1.4) describing the updated flow to be associated (see Section 4.2.1.4) describing the updated flow to be associated
with the flow binding. The mobile node MAY, however, omit the with the flow binding. The mobile node MAY, however, omit the
traffic selector sub-option if it wants the traffic selector traffic selector sub-option if it wants the traffic selector
currently associated with the flow binding entry identified by the currently associated with the flow binding entry identified by the
FID field to be maintained. FID field to be maintained.
The mobile node MAY include exactly one binding reference sub-option The mobile node MAY include exactly one binding reference sub-option
(see Section 4.2.1.3) to associate the existing flow binding with a (see Section 4.2.1.3) to associate the existing flow binding with a
new set of CoAs. If the mobile node includes a binding reference new set of CoAs. The mobile node MAY omit the binding reference sub-
sub-option then it should follow the rules described in
Section 5.2.2.1. The mobile node MAY omit the binding reference sub-
option if it wants the BIDs currently associated with the flow option if it wants the BIDs currently associated with the flow
binding entry identified by the FID field to be maintained. binding entry identified by the FID field to be maintained.
Note that it is also possible for the mobile node to effectively Note that it is also possible for the mobile node to effectively
modify the effect of a flow binding entry without actually changing modify the effect of a flow binding entry without actually changing
the entry itself. This can be done by changing the CoA associated the entry itself. This can be done by changing the CoA associated
with a given BID, which is a process defined in detail in [RFC5648]. with a given BID, which is a process defined in detail in [RFC5648].
5.2.3. Sending BU with a Flow Summary Option 5.2.3. Sending BU with a Flow Summary Option
When the mobile node sends a binding update it MUST refresh all flow When the mobile node sends a binding update it MUST refresh all flow
bindings it wants to maintain even if it does not want to change any bindings it wants to maintain even if it does not want to change any
of their parameters. of their parameters.
To refresh an existing flow binding the mobile node MUST send a To refresh an existing flow binding the mobile node MUST send a
binding update with a flow summary option. The flow summary option binding update with a flow summary option. The flow summary option
MUST include one or more FID fields as indicated in Section 4.2.2. MUST include one or more FID fields as indicated in Section 4.2.2.
Each FID field included MUST be set to one of the FID values already Each FID field included MUST be set to one of the FID values already
in the list of flow binding entries. in the list of flow binding entries. Each flow summary mobility
options can identify up to 127 FIDs, so more than one such options
can be included in a binding update message as required. A given FID
SHOULD NOT be included more than once in all of the flow summary
mobility options included a given binding update message.
Any flow bindings (active or inactive) that are not included in a Any flow bindings (active or inactive) that are not identified in a
binding update will be removed from the list of flow binding entries. binding update will be removed from the list of flow binding entries.
Note that any inactive flow bindings, i.e., flow bindings without Note that any inactive flow bindings, i.e., flow bindings without
associated BIDs that are marked as Inactive in the list of flow associated BIDs that are marked as Inactive in the list of flow
binding entries (see Section 4.3), MUST also be refreshed, or binding entries (see Section 4.3), MUST also be refreshed, or
modified, to be maintained. If they are not included in a BU they modified, to be maintained. If they are not included in a BU they
will be removed. will be removed.
5.2.4. Removing flow bindings 5.2.4. Removing flow bindings
skipping to change at page 23, line 33 skipping to change at page 22, line 8
binding itself. The procedure for removing a BID is defined in binding itself. The procedure for removing a BID is defined in
detail in [RFC5648]. detail in [RFC5648].
When all the BIDs associated with a flow binding are removed, the When all the BIDs associated with a flow binding are removed, the
flow binding MUST be marked as inactive in the list of flow binding flow binding MUST be marked as inactive in the list of flow binding
entries as shown in Section 4.3. In other words the state associated entries as shown in Section 4.3. In other words the state associated
with the flow binding MUST be maintained but it does no longer affect with the flow binding MUST be maintained but it does no longer affect
the mobile node's traffic. The MN can return an inactive flow the mobile node's traffic. The MN can return an inactive flow
binding to the active state by using the flow binding modification binding to the active state by using the flow binding modification
process described in Section 5.2.2.2, to associate it again with one process described in Section 5.2.2.2, to associate it again with one
or more valid BIDs. Remember that flow bindings indicating a or more valid BIDs.
'Discard' action do not take BIDs and thus cannot be rendered
inactive. Instead these entries can only be removed by omitting
their FID from a subsequent BU.
5.2.5. Returning Home 5.2.5. Returning Home
This specification is compatible to the home registration procedures This specification is compatible to the home registration procedures
defined in [RFC3775] and [RFC5648]. More specifically, if the mobile defined in [RFC3775] and [RFC5648]. More specifically, if the mobile
node performs an [RFC3775] style deregistration, all of its bindings, node performs an [RFC3775] style deregistration, all of its bindings,
including flow bindings are deleted. If the mobile node, however, including flow bindings are deleted. If the mobile node, however,
performs an [RFC5648] style home registration, then the home link is performs an [RFC5648] style home registration, then the home link is
associated with a specific BID and so, as far as this specification associated with a specific BID and so, as far as this specification
is concerned, it is treated as any other link associated with a given is concerned, it is treated as any other link associated with a given
BID. BID.
5.2.6. Receiving Binding Acknowledgements 5.2.6. Receiving Binding Acknowledgements
According to [RFC3775] all nodes are required to silently ignore According to [RFC3775] all nodes are required to silently ignore
mobility options not understood while processing binding updates. As mobility options not understood while processing binding updates. As
such a mobile node receiving a Binding Acknowledgement in response to such, a mobile node receiving a Binding Acknowledgement in response
the transmission of a binding update MUST determine if the Binding to the transmission of a binding update MUST determine if the Binding
Acknowledgement contains a copy of every flow identification mobility Acknowledgement contains a copy of every flow identification mobility
options included in the binding update. A Binding Acknowledgement options included in the binding update. A Binding Acknowledgement
without flow identification option(s), in response to a Binding without flow identification option(s), in response to a Binding
Update with flow identification mobility option, would indicate Update with flow identification mobility option, would indicate
inability (or unwillingness) on behalf of the source node to support inability (or unwillingness) on behalf of the source node to support
the extensions presented in this document. the extensions presented in this document.
If a received Binding Acknowledgement contains a copy of each flow If a received Binding Acknowledgement contains a copy of each flow
identification mobility option that was sent within the binding identification mobility option that was sent within the binding
update, the status field of each flow identification option indicates update, the status field of each flow identification option indicates
the status of the flow binding on the distant node. the status of the flow binding on the distant node.
5.2.7. Return Routability Procedure 5.2.7. Return Routability Procedure
A mobile node may perform route optimization with correspondent nodes A mobile node may perform route optimization with correspondent nodes
as defined in [RFC3775]. Route optimization allows a mobile node to as defined in [RFC3775]. Route optimization allows a mobile node to
bind a care-of address to a home address in order to allow the bind a care-of address to a home address in order to allow the
correspondent node to direct the traffic to the current location of correspondent node to direct the traffic to the current location of
the mobile node. Before sending a Binding Update to correspondent the mobile node. Before sending a Binding Update to correspondent
node, the Return Routability Procedure needs to be performed between node, the Return Routability Procedure needs to be performed between
the mobile node and the correspondent node.This procedure is not the mobile node and the correspondent node. This procedure is not
affected by the extensions defined in this document. affected by the extensions defined in this document.
5.3. HA, MAP, and CN Considerations 5.3. HA, MAP, and CN Considerations
This specification allows the mobility agents (Home Agents and This specification allows the mobility agents (Home Agents and
Mobility Anchor Points), and correspondent nodes to maintain several Mobility Anchor Points), and correspondent nodes to maintain several
flow bindings for a given home address and to direct packets to flow bindings for a given home address and to direct packets to
different care-of addresses according to flow bindings. This section different care-of addresses according to flow bindings. This section
details the home agent operations necessary to implement this details the home agent operations necessary to implement this
specification. These operations are identical for MAPs and CNs specification. These operations are identical for MAPs and CNs
skipping to change at page 25, line 18 skipping to change at page 23, line 41
identification mobility options might refer to BIDs defined in BID identification mobility options might refer to BIDs defined in BID
options included in the same message. options included in the same message.
The BID option is processed as defined in [RFC5648] but then the BID The BID option is processed as defined in [RFC5648] but then the BID
to care-of address mapping is placed in an ordered list according to to care-of address mapping is placed in an ordered list according to
the BID-PRI field of the BID option. the BID-PRI field of the BID option.
Binding Identifier registrations and deregistrations indirectly Binding Identifier registrations and deregistrations indirectly
affect the MN's flow binding entries. The home agent MUST update the affect the MN's flow binding entries. The home agent MUST update the
flow binding entries table accordingly as BIDs are added or removed ( flow binding entries table accordingly as BIDs are added or removed (
[RFC5648]). For example, as discussed in Section 4.3, if all of the as per [RFC5648]). For example, as discussed in Section 4.3, if all
BIDs associated with a given flow binding entry are removed (i.e., of the BIDs associated with a given flow binding entry are removed
become invalid) the entry MUST be marked as inactive. While if any (i.e., become invalid) the entry MUST be marked as inactive. While
of the invalid BIDs associated with an inactive flow binding entry if any of the invalid BIDs associated with an inactive flow binding
are registered (i.e., become valid), the entry MUST be marked as entry are registered (i.e., become valid), the entry MUST be marked
active. as active.
5.3.2. Handling Flow Identification Mobility Options 5.3.2. Handling Flow Identification Mobility Options
When the home agent receives a binding update which includes at least When the home agent receives a binding update which includes at least
one flow identification mobility option, it first performs the one flow identification mobility option, it first performs the
operation described in section 10.3.1 of RFC3775, followed by the operation described in section 10.3.1 of RFC3775, followed by the
operations defined in Section 5.3.1 of this document. operations defined in Section 5.3.1 of this document.
Home agents that do not support this specification will ignore the Home agents that do not support this specification will ignore the
flow identification mobility options and all their sub-options, flow identification mobility options and all their sub-options,
skipping to change at page 26, line 5 skipping to change at page 24, line 28
If all FID fields have different values the flow identification If all FID fields have different values the flow identification
mobility options can be processed further and in any order, as mobility options can be processed further and in any order, as
defined by the following subsections. defined by the following subsections.
5.3.2.1. Handling new FIDs 5.3.2.1. Handling new FIDs
If the FID field of the flow identification mobility option is not If the FID field of the flow identification mobility option is not
already present in the list of flow binding entries for this mobile already present in the list of flow binding entries for this mobile
node, then this is a request for a new entry. node, then this is a request for a new entry.
If the flow identification mobility option does not include a traffic If the flow identification mobility option does not include a
selector sub-option, the home agent MUST reject this request by traffic selector sub-option, the home agent MUST reject this
copying the flow identification mobility option in the BA, and request by copying the flow identification mobility option in the
setting the Status field to the value defined in Figure 2 for "Flow BA, and setting the Status field to the value defined in Figure 2
identification option malformed". for "Flow identification option malformed".
If the flow identification option does include a traffic selector
sub-option, but the format indicated in the TS Format field is not
supported, the home agent MUST reject this request by copying the
flow identification mobility option in the BA, and setting the Status
field to the value defined in Figure 2 for "Traffic Selector format
not supported".
Then the home agent MUST check the Action field in combination with
the Binding Reference sub-option if present.
- if the Action indicates 'Discard',
Any binding reference sub-options that might be present SHOULD be
ignored.
The home agent SHOULD add a new entry in the mobile node's list of If the flow identification option does include a traffic selector
flow binding entries, as defined below. sub-option, but the format indicated in the TS Format field is not
supported, the home agent MUST reject this request by copying the
flow identification mobility option in the BA, and setting the
Status field to the value defined in Figure 2 for "Traffic
Selector format not supported".
- if the Action indicates 'Forward", Then the home agent MUST check the Binding Reference sub-option.
If the Binding reference sub-option is not included, the home If the Binding reference sub-option is not included, the home
agent MUST reject this request by copying the flow identification agent MUST reject this request by copying the flow identification
mobility option in the BA, and setting the Status field to the mobility option in the BA, and setting the Status field to the
value defined for "Flow identification mobility option malformed" value defined for "Flow identification mobility option malformed"
in Section 4.2. in Section 4.2.
If the binding reference sub-option is present and includes one or If the binding reference sub-option is present and includes one or
more BIDs that are not present in the binding cache of the mobile more BIDs that are not present in the binding cache of the mobile
node the home agent MUST reject this request by copying the flow node the home agent MUST reject this request by copying the flow
skipping to change at page 27, line 9 skipping to change at page 25, line 22
When the home agent decides to add an entry in the mobile node's list When the home agent decides to add an entry in the mobile node's list
of flow binding entries, as discussed above, it MUST do it according of flow binding entries, as discussed above, it MUST do it according
to the following rules: The entry MUST be placed according to the to the following rules: The entry MUST be placed according to the
order indicated by the FID-PRI field of the flow identification order indicated by the FID-PRI field of the flow identification
mobility option and it MUST include: mobility option and it MUST include:
the FID as a key to the entry the FID as a key to the entry
The traffic selector included in the corresponding sub-option The traffic selector included in the corresponding sub-option
the action indicated in the Action field the BIDs indicated in the binding reference sub-option
the BIDs, depending on action field, indicated in the binding
reference sub-option
the entry MUST be marked as Active, as shown in Section 4.3 the entry MUST be marked as Active, as shown in Section 4.3
5.3.2.2. Handling known FIDs 5.3.2.2. Handling known FIDs
If the FID field of the flow identification mobility option is If the FID field of the flow identification mobility option is
already present in the list of flow binding entries for this mobile already present in the list of flow binding entries for this mobile
node, then this is a request to update the existing entry. node, then this is a request to update the existing entry.
The flow binding modification is essentially a process where The flow binding modification is essentially a process where
parameters associated with an existing flow binding entry are parameters associated with an existing flow binding entry are
replaced by the parameters included in a flow identification mobility replaced by the parameters included in a flow identification mobility
option with the same FID as the existing entry. option with the same FID as the existing entry.
The home agent MUST: The home agent MUST change the priority of the entry according to the
FID-PRI field of the flow identification mobility option.
Change the priority of the entry according to the FID-PRI field of
the flow identification mobility option.
Change the action associated with the entry according to the
Action field of the flow identification mobility option.
Since this flow identification mobility option is designed to update Since this flow identification mobility option is designed to update
an existing entry it may or may not include a traffic selector sub- an existing entry it may or may not include a traffic selector sub-
option. option. Specifically:
If a traffic selector sub-option is not included in the flow if a traffic selector sub-option is not included in the flow
identification mobility option, then the traffic selector already identification mobility option, then the traffic selector already
associated with entry MUST be maintained, associated with entry MUST be maintained,
otherwise the traffic selector in the entry MUST be replaced by otherwise the traffic selector in the entry MUST be replaced by
the traffic selector in the sub-option. the traffic selector in the sub-option.
Like Section 5.3.2.1, if the Action field in the flow identification Since this flow identification mobility option is designed to update
mobility option is set to 'Discard' if a binding reference sub-option an existing entry, it may or may not include a binding reference sub-
is included in the option, it SHOULD be ignored; and any BIDs option. Specifically:
associated with the existing flow binding entry SHOULD be removed.
Unlike Section 5.3.2.1, however, if the Action field in the flow
identification mobility option is set to 'Forward', and since this
flow identification mobility option is designed to update an existing
entry, it may or may not include a binding reference sub-option.
If a binding reference sub-option is not included in the flow if a binding reference sub-option is not included in the flow
identification mobility option, then the BIDs already associated identification mobility option, then the BIDs already associated
with entry MUST be maintained, with entry MUST be maintained,
otherwise the BIDs in the entry MUST be replaced by the BIDs in otherwise the BIDs in the entry MUST be replaced by the BIDs in
the sub-option. the sub-option.
5.3.3. Handling Flow Summary Mobility Option 5.3.3. Handling Flow Summary Mobility Option
When the home agent receives a binding update which includes a flow When the home agent receives a binding update which includes flow
summary mobility option, it first performs the operation described in summary mobility options, it first performs the operation described
section 10.3.1 of RFC3775. Binding update messages including more so far in Section 5.3.
than one flow summary mobility option MUST be rejected.
An [RFC3775] de-registration binding update (with a zero lifetime)
would result in deleting all bindings, including all flow bindings
regardless of the presence of the flow summary mobility option. A
binding update (with a zero lifetime) would result in deleting all
bindings, including all flow bindings regardless of the presence of
the flow summary mobility option. A specific binding de-
registration, however, as defined in [RFC5648] (with lifetime of zero
and one or mobe Binding Identifier mobility options identifying
specific BIDs)does not remove all the bindings for the MN and thus it
SHOULD include a Flow Summary Mobility Option to maintain the flow
bindings that need to be preserved.
If the value of any of the FID fields included in the flow summary If the value of any of the FID fields included in a flow summary
mobility option is not present in the list of flow binding entries mobility option is not present in the list of flow binding entries
for this mobile node, the home agent MUST reject this flow binding for this mobile node, the home agent MUST reject this flow binding
refresh by including a flow identification mobility option in the BA refresh by including a flow identification mobility option in the BA
for each FID that is not found, and by setting the FID field to the for each FID that is not found, and by setting the FID field to the
value of the FID that is not found and the Status field to the value value of the FID that is not found and the Status field to the value
defined for "FID not found" in Section 4.2. defined for "FID not found" in Section 4.2.
If the value of the FID field is present in the mobile nodes list of If the value of the FID field is present in the mobile nodes list of
flow binding entries the, home agent SHOULD refresh the flow binding flow binding entries the, home agent SHOULD refresh the flow binding
entry identified by the FID without changing any of the other entry identified by the FID without changing any of the other
parameters associated with it. parameters associated with it.
If a given FID is included more than once in the same or different
flow summary mobility options in the same binding update message, the
duplicates can be simply ignored.
Note that, an [RFC3775] de-registration binding update (with a zero
lifetime) would result in deleting all bindings, including all flow
bindings regardless of the presence of flow summary mobility options.
A binding update (with a zero lifetime) would result in deleting all
bindings, including all flow bindings regardless of the presence of
flow summary mobility options. A specific binding de-registration,
however, as defined in [RFC5648] (with lifetime of zero and one or
more Binding Identifier mobility options identifying specific BIDs)
does not remove all the bindings for the MN and thus it SHOULD
include flow summary mobility options to maintain the flow bindings
that need to be preserved.
5.3.4. Flow Binding Removals 5.3.4. Flow Binding Removals
Removal of flow bindings is performed implicitly by omission of a Removal of flow bindings is performed implicitly by omission of a
given FID from a binding update. given FID from a binding update.
When a valid binding update is received, any registered FIDs that are When a valid binding update is received, any registered FIDs that are
not explicitly referred to in a flow identification mobility option not explicitly referred to in a flow identification mobility option
or in a flow summary mobility option, in the same binding update, or in a flow summary mobility option, in the same binding update,
MUST be removed from the list of flow binding entries for the mobile MUST be removed from the list of flow binding entries for the mobile
node. node.
skipping to change at page 29, line 40 skipping to change at page 27, line 47
codes also defined in Section 4.2. Section 5.3.2 identifies a number codes also defined in Section 4.2. Section 5.3.2 identifies a number
of cases where specific error codes should be used. of cases where specific error codes should be used.
Home agents that support this specification MAY refuse to maintain Home agents that support this specification MAY refuse to maintain
flow bindings by setting the status field of any flow identification flow bindings by setting the status field of any flow identification
mobility options to the value defined for "Administratively mobility options to the value defined for "Administratively
prohibited" in Section 4.2, or by just ignoring all the flow binding prohibited" in Section 4.2, or by just ignoring all the flow binding
options. options.
Note that BID options and their Status field are handled as defined Note that BID options and their Status field are handled as defined
in [RFC5648]. in [RFC5648]. The BID-PRI field in a BID option included in the
binding acknowledgement is copied from the the BID-PRI field of the
corresponding BID option in the binding request.
5.3.6. Packet Processing 5.3.6. Packet Processing
This section defines packet processing rules according to this This section defines packet processing rules according to this
specification. This specification does not change any of the packet specification. This specification does not change any of the packet
interception rules defined in [RFC3775], and [RFC5555]. These rules interception rules defined in [RFC3775], and [RFC5555]. These rules
apply to HAs, MAPs, and CNs, as part of the routing process for any apply to HAs, MAPs, and CNs, as part of the routing process for any
packet with destination address set to a valid home address of the packet with destination address set to a valid home address of the
mobile node. For nodes other than CNs this also applies to packets mobile node. For nodes other than CNs this also applies to packets
with destination address set to an address under any of the with destination address set to an address under any of the
registered prefixes. These rules apply equally to IPv6 packets as registered prefixes. These rules apply equally to IPv6 packets as
well as to IPv4 packets as per [RFC5555]. well as to IPv4 packets as per [RFC5555].
Before a packet is forwarded to the mobile node it MUST be matched Before a packet is forwarded to the mobile node it MUST be matched
against the ordered list of flow bindings stored in the list of flow against the ordered list of flow bindings stored in the list of flow
binding entries for this mobile node (see Section 4.3). A match is binding entries for this mobile node (see Section 4.3). A match is
attempted with the traffic selector included in the first line attempted with the traffic selector included in the first line
(highest order) of the table. If the packet matches the traffic (highest order) of the table. The first entry that creates a match
selector, the action defined by the action parameter of the table defines how the packet is routed. When a packet matches the traffic
SHOULD be performed. selector of a given entry, a copy of the packet is forwarded to each
of the care-of addresses associated with the BIDs indicated in the
- if the Action indicates 'Discard', the packet is silently same line of the table.
discarded
- if the Action indicates 'Forward", a copy of the packet is
forwarded to each of the care-of addresses associated with the
BIDs indicated in the same line of the table.
If the action indicated in one of the entries in the list of flow If any of the BIDs indicated does not correspond to a valid care-of
bindings is 'Discard' then, no BIDs need to be indicated in the same address, e.g., the BID was deregistered then, that BID has no effect
entry since the packet is not forwarded. If, however, the action on the traffic. In other words, packets matching the flow binding
indicated in an entry of the list of flow bindings is 'Forward", the are forwarded to the remaining BIDs, pointing to registered care-of
entry should indicate one or more valid BIDs. For 'Forward' if any
of the BIDs indicated does not correspond to a valid care-of address,
e.g., the BID was deregistered then that BID has no effect on the
traffic. In other words, packets matching the flow binding are
forwarded to the remaining BIDs, pointing to registered care-of
addresses. If none of the BIDs pointed to in a flow binding entry is addresses. If none of the BIDs pointed to in a flow binding entry is
valid then the entry is considered to be inactive (as defined in valid then the entry is considered to be inactive (as defined in
Section 4.3) and is skipped. In other words packets should not be Section 4.3) and is skipped. In other words packets should not be
matched against that entry. matched against that entry.
If a packet does not match any of the active flow binding entries for If a packet does not match any of the active flow binding entries for
the given MN, the packet SHOULD be forwarded to the care-of address the given MN, the packet SHOULD be forwarded to the highest order
associated with the BID with the highest BID-PRI. care-of address i.e., the one associated with the BID with the lowest
BID-PRI.
If a packet is fragmented, only the first fragment contains all IP If a packet is fragmented, only the first fragment contains all IP
and transport layer headers, while subsequent fragments only contain and transport layer headers, while subsequent fragments only contain
an IP header without transport layer headers. For this reason it is an IP header without transport layer headers. For this reason it is
possible that subsequent fragments do not match the same traffic possible that subsequent fragments do not match the same traffic
selector as the initial fragment of such a packet. Unless specific selector as the initial fragment of such a packet. Unless specific
measures are taken the likely outcome is that the initial fragment is measures are taken the likely outcome is that the initial fragment is
routed as the MN intended while subsequent fragments are routed routed as the MN intended while subsequent fragments are routed
differently, and probably based on the default flow binding. HAs, differently, and probably based on the default flow binding. HAs,
MAPs, and CNs SHOULD take care to forward all fragments of a given MAPs, and CNs SHOULD take care to forward all fragments of a given
skipping to change at page 32, line 20 skipping to change at page 30, line 20
Implementations SHOULD take care to minimize fragmentation by forming Implementations SHOULD take care to minimize fragmentation by forming
binding updates that are shorter than what the path MTU allows binding updates that are shorter than what the path MTU allows
whenever possible. whenever possible.
This specification offers a number of mechanisms for reducing the This specification offers a number of mechanisms for reducing the
size of binding updates. The operations defined in this size of binding updates. The operations defined in this
specification that require the most verbose options are those specification that require the most verbose options are those
registering new BIDs Section 4.1 and identifying new flows registering new BIDs Section 4.1 and identifying new flows
Section 4.2.1.4. Implementations are encouradged to keep binding Section 4.2.1.4. Implementations are encouradged to keep binding
updates to sizes below than that of the path's MTU by making full use updates to sizes below than that of the path's MTU by making full use
of BID Reference Section 4.2.1.3 and FID Summary Section 4.2.2 sub- of BID reference Section 4.2.1.3 sub-option and flow summary
options, which allows them to refer to already registered care-of Section 4.2.2 option, which allows them to refer to already
addresses and flows, while registering new ones in subsequent binding registered care-of addresses and flow bindings, while registering new
update messages. ones in subsequent binding update messages.
7. Security considerations 7. Security considerations
This draft introduces a new option that adds more granularity to the This draft introduces a new option that adds more granularity to the
binding update and acknowledgement messages defined in [RFC3775], binding update and acknowledgement messages defined in [RFC3775],
[RFC5555], and [RFC3963], so it inherits the security considerations [RFC5555], and [RFC3963], so it inherits the security considerations
discussed in these documents. The new option allows the mobile node discussed in these documents. The new option allows the mobile node
to associate some flows to one interface and other flows to another to associate some flows to one interface and other flows to another
interface. Since the flow identification mobility option is part of interface. Since the flow identification mobility option is part of
the mobility header, it uses the same security as the Binding Update, the mobility header, it uses the same security as the Binding Update,
skipping to change at page 34, line 18 skipping to change at page 32, line 18
existing namespaces as well as the creation of some new namespaces. existing namespaces as well as the creation of some new namespaces.
1) New Mobility Options [RFC3775]: This registry is available from 1) New Mobility Options [RFC3775]: This registry is available from
http://www.iana.org under "Mobile IPv6 parameters". The following http://www.iana.org under "Mobile IPv6 parameters". The following
type numbers need to be assigned for: type numbers need to be assigned for:
Flow Identification Mobility Option, define in Section 4.2 Flow Identification Mobility Option, define in Section 4.2
Flow Summary Mobility Option, defined in Section 4.2.2 Flow Summary Mobility Option, defined in Section 4.2.2
2) New "Flow Identification Mobility Option Action codes" 2) New "Flow Identification Mobility Option Status codes"
namespace needs to be created. The following 'Action' codes are
defined in this specification, in Section 4.2:
0 Reserved
1 Discard
2 Forward
3-254 unassigned and available for allocation based on
Standards Action or IESG Approval as per [RFC5226]
255 reserved for experimental use. A single value should be
sufficient for experimenting with a different flow
identifiction format.
3) New "Flow Identification Mobility Option Status codes"
namespace needs to be created. The following 'Status' codes are namespace needs to be created. The following 'Status' codes are
defined in this specification, in Section 4.2: defined in this specification, in Section 4.2:
0 Flow binding successful 0 Flow binding successful
1-127 unassigned and available for success codes to be 1-127 unassigned and available for success codes to be
allocated via STD action allocated via Standards Action or IESG Approval as per
[RFC5226]
128 Administratively prohibited 128 Administratively prohibited
129 Flow binding rejected, reason unspecified 129 Flow binding rejected, reason unspecified
130 Flow identification mobility option malformed 130 Flow identification mobility option malformed
131 BID not found 131 BID not found
132 FID not found 132 FID not found
133 Traffic selector format not supported 133 Traffic selector format not supported
134 Discard function not supported 134-250 unassigned and available for reject codes to be
135 Forward function not supported
136-250 unassigned and available for reject codes to be
allocated via Standards Action or IESG Approval as per allocated via Standards Action or IESG Approval as per
[RFC5226] [RFC5226]
251-255 reserved for experimental use. This small number of 251-255 reserved for experimental use. This small number of
status codes should be sufficient for experiments with status codes should be sufficient for experiments with
currently unforeseen error conditions. currently unforeseen error conditions.
4) New "Flow Identification Sub-Options" namespace for the Flow 4) New "Flow Identification Sub-Options" namespace for the Flow
Identification Mobility Option. The sub-option space is defined Identification Mobility Option. The sub-option space is defined
in Figure 3. The following Sub-option Type values are defined in in Figure 3. The following Sub-option Type values are defined in
skipping to change at page 39, line 9 skipping to change at page 36, line 9
Castelluccia, D. Craig, K. ElMalki, K. Georgios, , C. Goerg, C. Kaas- Castelluccia, D. Craig, K. ElMalki, K. Georgios, , C. Goerg, C. Kaas-
Petersen, J. Laganier, T. Noel, F.-N. Pavlidou, V. Park, P. Stupar. Petersen, J. Laganier, T. Noel, F.-N. Pavlidou, V. Park, P. Stupar.
Also, Gabor Fekete for the analysis that led to the inclusion of the Also, Gabor Fekete for the analysis that led to the inclusion of the
BIDRef sub-option, and Henrik Levkowetz for suggesting support for BIDRef sub-option, and Henrik Levkowetz for suggesting support for
other ways of describing flows. other ways of describing flows.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-mext-binary-ts]
Tsirtsis, G., Giaretta, G., Soliman, H., and N. Montavont,
"Traffic Selectors for Flow Bindings",
draft-ietf-mext-binary-ts-04 (work in progress),
February 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P.
Thubert, "Network Mobility (NEMO) Basic Support Protocol", Thubert, "Network Mobility (NEMO) Basic Support Protocol",
RFC 3963, January 2005. RFC 3963, January 2005.
skipping to change at page 39, line 32 skipping to change at page 36, line 38
[RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and [RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", RFC 5555, June 2009. Routers", RFC 5555, June 2009.
[RFC5648] Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T., [RFC5648] Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T.,
and K. Nagami, "Multiple Care-of Addresses Registration", and K. Nagami, "Multiple Care-of Addresses Registration",
RFC 5648, October 2009. RFC 5648, October 2009.
11.2. Informative References 11.2. Informative References
[I-D.ietf-mext-binary-ts]
Tsirtsis, G., Giaretta, G., Soliman, H., and N. Montavont,
"Traffic Selectors for Flow Bindings",
draft-ietf-mext-binary-ts-04 (work in progress),
February 2010.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
McManus, "Requirements for Traffic Engineering Over MPLS", McManus, "Requirements for Traffic Engineering Over MPLS",
RFC 2702, September 1999. RFC 2702, September 1999.
[RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005. RFC 4303, December 2005.
 End of changes. 61 change blocks. 
313 lines changed or deleted 186 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/