draft-ietf-mext-flow-binding-02.txt   draft-ietf-mext-flow-binding-03.txt 
IETF MEXT Working Group H. Soliman IETF MEXT Working Group H. Soliman
Internet-Draft Elevate Technologies Internet-Draft Elevate Technologies
Intended status: Standards Track G. Tsirtsis Intended status: Standards Track G. Tsirtsis
Expires: October 30, 2009 Qualcomm Expires: January 14, 2010 Qualcomm
N. Montavont N. Montavont
IT/TB IT/TB
G. Giaretta G. Giaretta
Qualcomm Qualcomm
K. Kuladinithi K. Kuladinithi
University of Bremen University of Bremen
April 28, 2009 July 13, 2009
Flow Bindings in Mobile IPv6 and Nemo Basic Support Flow Bindings in Mobile IPv6 and NEMO Basic Support
draft-ietf-mext-flow-binding-02.txt draft-ietf-mext-flow-binding-03.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 30, 2009. This Internet-Draft will expire on January 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
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 their peers to direct downlink allow multihomed nodes to instruct home agents and other Mobile IPv6
flows to specific addresses. entities to direct inbound flows to specific addresses.
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. Binding Reference Sub-option . . . . . . . . . . . . . 11 4.2.1. Binding Reference Sub-option . . . . . . . . . . . . . 11
4.2.2. Flow Description Sub-option . . . . . . . . . . . . . 12 4.2.2. Flow Description Sub-option . . . . . . . . . . . . . 12
4.3. Flow Identification Summary Mobility Option . . . . . . . 13 4.3. Flow Identification Summary Mobility Option . . . . . . . 12
4.4. Flow Bindings entries list and its relationship to 4.4. Flow Bindings entries list and its relationship to
Binding Cache . . . . . . . . . . . . . . . . . . . . . . 14 Binding Cache . . . . . . . . . . . . . . . . . . . . . . 13
5. Protocol operations . . . . . . . . . . . . . . . . . . . . . 17 5. Protocol operations . . . . . . . . . . . . . . . . . . . . . 16
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.1. Preferred Care-of address . . . . . . . . . . . . . . 17 5.1.1. Preferred Care-of address . . . . . . . . . . . . . . 16
5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 17 5.2. Mobile Node Considerations . . . . . . . . . . . . . . . . 16
5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 18 5.2.1. Sending BU with BID Options . . . . . . . . . . . . . 17
5.2.2. Sending BU with Flow Identification Options . . . . . 18 5.2.2. Sending BU with Flow Identification Options . . . . . 17
5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 20 5.2.3. Sending BU with a Flow Summary Option . . . . . . . . 19
5.2.4. Removing flow bindings . . . . . . . . . . . . . . . . 21 5.2.4. Removing flow bindings . . . . . . . . . . . . . . . . 19
5.2.5. Receiving Binding Acknowledgements . . . . . . . . . . 21 5.2.5. Receiving Binding Acknowledgements . . . . . . . . . . 20
5.2.6. Return Routability Procedure . . . . . . . . . . . . . 21 5.2.6. Return Routability Procedure . . . . . . . . . . . . . 20
5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 22 5.3. HA, MAP, and CN Considerations . . . . . . . . . . . . . . 21
5.3.1. Receiving BU with BID Options . . . . . . . . . . . . 22 5.3.1. Receiving BU with BID Options . . . . . . . . . . . . 21
5.3.2. Receiving BU with Flow Identification Options . . . . 23 5.3.2. Receiving BU with Flow Identification Options . . . . 21
5.3.3. Receiving BU with Flow Summary Option . . . . . . . . 25 5.3.3. Receiving BU with Flow Summary Option . . . . . . . . 24
5.3.4. Handling flow binding Removals . . . . . . . . . . . . 26 5.3.4. Handling flow binding Removals . . . . . . . . . . . . 24
5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 26 5.3.5. Sending Binding Acknowledgements . . . . . . . . . . . 25
5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 27 5.3.6. Packet Processing . . . . . . . . . . . . . . . . . . 25
6. Security considerations . . . . . . . . . . . . . . . . . . . 28 6. Security considerations . . . . . . . . . . . . . . . . . . . 27
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.1. Normative References . . . . . . . . . . . . . . . . . . . 32 10.1. Normative References . . . . . . . . . . . . . . . . . . . 31
10.2. Informative References . . . . . . . . . . . . . . . . . . 32 10.2. Informative References . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
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 [I-D.ietf-mext-nemo-v4traversal] and Mobile IPv6 [RFC3775], DSMIPv6 [I-D.ietf-mext-nemo-v4traversal] and
Nemo Basic Support [RFC3963] allow a mobile node / mobile router to NEMO Basic Support [RFC3963] allow a mobile node / mobile router to
manage its mobility using the binding update message, which binds one manage its mobility using the binding update message, which binds one
care-of address to one home address. The binding update message can care-of address to one home address. The binding update message can
be sent to the home agent. In Mobile IPv6, the binding update can be sent to the home agent. In Mobile IPv6, the binding update can
also be sent to correspondent node or to a mobility anchor point (see also be sent to correspondent node or to a mobility anchor point (see
[RFC5380]). The semantics of the binding update are limited to [RFC5380]). The semantics of the binding update are limited to
care-of address changes. That is, [RFC3775], care-of address changes. That is, [RFC3775],
[I-D.ietf-mext-nemo-v4traversal], and [RFC3963] do not allow a mobile [I-D.ietf-mext-nemo-v4traversal], and [RFC3963] do not allow a mobile
node / mobile router to bind more than one address to the home node / mobile router to bind more than one address to the home
address. In [I-D.ietf-monami6-multiplecoa] Mobile IPv6 and Nemo address. In [I-D.ietf-monami6-multiplecoa] Mobile IPv6 and NEMO
Basic Support are extended to allow the binding of more than one Basic Support are extended to allow the binding of more than one
care-of address to a home address. This specification further care-of address to a home address. This specification further
extends Mobile IPv6, DSMIPv6, and Nemo Basic Support to allow it to extends Mobile IPv6, DSMIPv6, and NEMO Basic Support to allow it to
specify policies associated with each binding. A policy can contain specify policies associated with each binding. A policy can contain
a request for a special treatment of a particular IPv4 or IPv6 flow, a request for a special treatment of a particular IPv4 or IPv6 flow,
which is viewed as a group of packets matching a flow descriptor. which is viewed as a group of packets matching a flow descriptor.
Hence, this specification allows a mobile node / mobile router to Hence, this specification allows a mobile node / mobile router to
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 anchor point. directly with correspondent node and mobility anchor point.
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
skipping to change at page 6, line 5 skipping to change at page 6, line 5
care-of address. Requesting the flow binding can be decided based on care-of address. Requesting the flow binding can be decided based on
local policies within the mobile node / mobile router and based on local policies within the mobile node / mobile router and based on
the link characteristics and the types of applications running at the the link characteristics and the types of applications running at the
time. Such policies are outside the scope of this document. time. Such policies are outside the scope of this document.
It should be noted that the flow identification option can be It should be noted that the flow identification option can be
associated with any binding update, whether it is sent to a home associated with any binding update, whether it is sent to a home
agent, correspondent node (in the case of Mobile IPv6), or mobility agent, correspondent node (in the case of Mobile IPv6), or mobility
anchor point (in the case of Hierarchical Mobile IPv6). anchor point (in the case of Hierarchical Mobile IPv6).
Note that per-packet load balancing may have negative impacts on TCP
congestion avoidance mechanisms as it is desirable to maintain order
between packets belonging to the same TCP connection. This behaviour
is specified in [RFC2702]. Other negative impacts are also
foreseen for other types of real time connections due to the
potential variations in RTT between packets. Moreover, per-packet
load-balancing will negatively affect traffic with ant-replay
protection mechanisms. Hence, per-packet load balancing is not
currently supported in this extension.
In the rest of the document, the term "mobile node" is used to In the rest of the document, the term "mobile node" is used to
designate either a mobile node as defined in [RFC3775] or a mobile designate either a mobile node as defined in [RFC3775] or a mobile
router as defined in [RFC3963] unless stated otherwise. router as defined in [RFC3963] unless stated otherwise.
3. Terminology 3. Terminology
Terms used in this document are defined in [RFC3753] and [RFC4885]. Terms used in this document are defined in [RFC3753] and [RFC4885].
The following terms are also used in this document: The following terms are also used in this document:
Flow: A flow is identified as a set of data packets that are Flow: A flow is identified as a set of data packets that are
exchanged between two nodes and match a given flow description exchanged between two nodes and match a given flow description
Flow Description: A set of instructions that describes a flow. Flow Description: Information that identifies one or more IP
packets. The identification can use the source address,
destination port, protocol number, DSCP value, or other
information from the packet with predefined values.
Flow Identifier: Identifier of a flow binding. Flow Identifier: An unsigned integer.
Flow binding: An entry in the list of flow binding associated with Flow binding: A triplet consisting of a flow identifier, a flow
a given mobile node. descriptor, and an action. An IP packet that matches the triplet
will be processed according to the action.
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.
4.1. Definition Update for Binding Identifier Mobility Option 4.1. Definition Update for Binding Identifier Mobility Option
This specification updates the definition of the Binding Identifier This specification updates the definition of the Binding Identifier
Mobility option defined in [I-D.ietf-monami6-multiplecoa], as Mobility option defined in [I-D.ietf-monami6-multiplecoa], as
skipping to change at page 8, line 32 skipping to change at page 8, line 32
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
+ + + +
: IPv4 or IPv6 care-of address (CoA) : : IPv4 or IPv6 care-of address (CoA) :
+ + + +
+---------------------------------------------------------------+ +---------------------------------------------------------------+
Figure 1: The Binding Identifier Mobility option Figure 1: The Binding Identifier Mobility option
BID-PRI BID-PRI
This is a 7-bit field placing each BID to a relative priority This is a 7-bit unsigned integer placing each BID to a relative
with other registered BIDs. Value "0" is reserved for priority with other registered BIDs. Value "0" is reserved. A
implementation of [I-D.ietf-monami6-multiplecoa] that do not lower number in this field indicates higher priority, while
support this specification. A higher number in this field BIDs with the same BID-PRI value have equal priority. This is
indicates lower priority, while BIDs with the same BID-PRI consistent with current practice in packet classifiers.
value have equal priority.
4.2. Flow Identification Mobility Option 4.2. Flow Identification Mobility Option
The Flow identification mobility option is included in the binding The Flow identification mobility option is included in the binding
update and acknowledgement messages. This option contains update and acknowledgement messages. This option contains
information that allows the receiver of a binding update to install information that allows the receiver of a binding update to install
policies on a traffic flow and route it to a given care-of address. policies on a traffic flow and route it to a given care-of address.
Multiple options may exist within the same binding update message. Multiple options may exist within the same binding update message.
The alignment requirement for this option is 4n.
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 | PRO | Status | | FID-PRI | Action | Rsvd | Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: The flow identification mobility option Figure 2: The flow identification mobility option
Option Type Option Type
TBD TBD
Option Len Option Len
Length of option, including any sub-options, in 8-octet units Length of option, including any sub-options, in 8-octet units
FID FID
The Flow Identifier field is an 8-bit unsigned integer that The Flow Identifier field is an 16-bit unsigned integer that
includes the identifier for the flow binding. This field is includes the identifier for the flow binding. This field is
used to refer to an existing binding or to create a new used to refer to an existing binding or to create a new
binding. The value of this field is set by the mobile node. binding. The value of this field is set by the mobile node.
FID = 0 is reserved and MUST NOT be used.
FID-PRI FID-PRI
This is an 8-bit priority field to indicate the priority of a This is an unsigned 8-bit priority field to indicate the
particular option. This field is needed in cases where two priority of a particular option. This field is needed in cases
different flow descriptions in two different options overlap. where two different flow descriptions in two different options
The priority field decides which policy should be in those overlap. The priority field decides which policy should be in
cases. A lower number in this field indicates a higher those cases. A lower number in this field indicates a higher
priority. priority.
Action Action
This field specifies the action that needs to be taken by the This field specifies the action that needs to be taken by the
receiver of the binding update containing the flow receiver of the binding update containing the flow
identification option. The details of these requests are identification option. The details of these requests are
discussed below. discussed below.
Rsvd Rsvd
This field is unused. It MUST be initialized to zero by the This field is unused. It MUST be set to zero by the sender and
sender and MUST be ignored by the receiver. MUST be ignored by the receiver.
PRO
This is a 4-bit field that describes the required processing
for the option. This field may indicate a request for adding,
deleting, modifying or refreshing the option. The details of
these requests are discussed below.
Status Status
This field indicates the success or failure of the flow binding This field indicates the success or failure of the flow binding
operation for the particular flow in the option. This field is operation for the particular flow in the option. This field is
not relevant to the binding update message as a whole or to not relevant to the binding update message as a whole or to
other flow identification options. Values from 0 to 127 other flow identification options. Values from 0 to 127
indicate success. Values of 128 and higher indicate failure. indicate success. Values of 128 and higher indicate failure.
This field is only relevant when included in the Binding 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. update message.
The following values are reserved for the PRO field in this option:
0 Add a flow binding
1 Modify a flow binding
The following values are reserved for the Action field in this The following values are reserved for the Action field in this
option: option:
1 Forward. This value indicates a request to forward a flow to 1 Discard. This value indicates a request to discard all packets
the address indicated in the Binding Reference sub-option. A
single BID MUST be associated with this Action.
2 Discard. This value indicates a request to discard all packets
in the flow described by the option. No BIDs are associated with in the flow described by the option. No BIDs are associated with
this Action. this Action.
3 n-cast. This value indicates a request to replicate the flow to 2 n-cast. This value indicates a request to send the flow to one
several addresses indicated in the Binding Reference sub-option. or more addresses indicated in the Binding Reference sub-option.
One or more BIDs MUST be associated with this Action. 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. Care should be taken when
the n-cast action is used as some transport layers may not be able
to handle packet duplication and this can affect their
performance.
The following values are reserved for the status field within the The following values are reserved for the status field within the
flow identification option: flow identification option:
0 Flow binding successful. 0 Flow binding successful.
128 Flow binding rejected, reason unspecified. 128 Flow binding rejected, reason unspecified.
129 Flow identification option poorly formed. 129 Flow identification option malformed.
130 Administratively prohibited. 130 Administratively prohibited.
135 FID already in use 135 FID already in use
136 FID not found 136 FID not found
137 FD-Type not supported. 137 FD-Type not supported.
138 Discard function not supported. 138 Discard function not supported.
139 N-cast function not supported. 139 N-cast function not supported.
It should be noted that per-packet load balancing may have negative
impacts on TCP congestion avoidance mechanisms as it is desirable to
maintain order between packets belonging to the same TCP connection.
This behaviour is specified in RFC2702 [RFC2702]. Other negative
impacts are also foreseen for other types of real time connections
due to the potential variations in RTT between packets. Hence per-
packet load balancing is not currently supported in this extension.
A number of sub-options can follow the option defined in this A number of sub-options can follow the option defined in this
section. These are defined below. section. These are defined below.
4.2.1. Binding Reference Sub-option 4.2.1. Binding Reference Sub-option
This section introduces the Binding Reference sub-option, which may This section introduces the Binding Reference sub-option, which may
be included in the Flow identification option. The Binding Reference be included in the Flow identification option. The Binding Reference
sub-option includes one or more BIDs defined in MCoA sub-option includes one or more BIDs defined in MCoA
[I-D.ietf-monami6-multiplecoa]. When this sub-option is included in [I-D.ietf-monami6-multiplecoa]. When this sub-option is included in
the Flow identification option it associates the flow described with the Flow identification option it associates the flow described with
one or more registered BIDs. one or more registered BIDs.
The binding identifier option, defined in When binding a flow using this sub-option, the binding identifier
[I-D.ietf-monami6-multiplecoa], registering a given BID which is then option, defined in [I-D.ietf-monami6-multiplecoa], MUST be defined in
indicated in the Binding Reference sub-option, MUST be either defined either the same or an earlier BU. The Binding Reference sub-option
in the same or earlier BU from the one including the binding is shown below.
reference sub-option. The Binding Reference sub-option is shown
below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-opt Type | Sub-Opt Len | BID | |Sub-opt Type | Sub-Opt Len | BID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BID ........ | BID ........
+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-
Figure 3: The Binding Reference sub-option Figure 3: The Binding Reference sub-option
skipping to change at page 13, line 18 skipping to change at page 12, line 43
Sub-opt Type field. Flow description is out of scope of this Sub-opt Type field. Flow description is out of scope of this
document. document.
The following values are reserved for the sub-option Type values are The following values are reserved for the sub-option Type values are
defined for Flow Description: defined for Flow Description:
17-32 reserved for Flow Description formats. 17-32 reserved for Flow Description formats.
4.3. Flow Identification Summary Mobility Option 4.3. Flow Identification Summary Mobility Option
TBD The Flow Identification Summary Mobility option includes one or more
flow identifiers (FIDs) for the purpose of refresing their state
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 5: The Flow Identification Summary Option Figure 5: The Flow Identification Summary Option
Option Type Option Type
Indicates the Sub-option type. For the Binding Reference sub- TBD
option, this field MUST be set to 1.
Option Length Option Length
Indicates the sub-option length in octets. This field includes Length of option, including any sub-options, in 8-octet units
the entire length of the sub-option including the Sub-opt Type
and Sub-opt-Len fields.
FID FID
A registered FID. One or more FID fields can be included in A registered FID. One or more FID fields can be included in
this option. Since each FID is 2 bytes long, the value of the this option. Since each FID is 2 bytes long, the value of the
Option Len field indicates the number of FIDs present. Number Option Len field indicates the number of FIDs present.
of FIDs = (Sub-opt Len-2)/2.
4.4. Flow Bindings entries list and its relationship to Binding Cache 4.4. Flow Bindings entries list and its relationship to Binding Cache
The conceptual mobile IPv6 binding cache was defined in [RFC3775] to The conceptual mobile IPv6 binding cache was defined in [RFC3775] to
identify the mobile IP state maintained by the mobile node, home identify the mobile IP state maintained by the mobile node, home
agent, and corresponding node. The binding cache includes, between agent, and corresponding node. The binding cache includes, between
others, the mobile node's home address, the registered care-of others, the mobile node's home address, the registered care-of
address, and the lifetime of the binding. The binding cache was then address, and the lifetime of the binding. The binding cache was then
extended by [I-D.ietf-monami6-multiplecoa] to include more than one extended by [I-D.ietf-monami6-multiplecoa] to include more than one
care-of addresses and to associate each of them with a Binding care-of addresses and to associate each of them with a Binding
Identifier (BID). Identifier (BID).
This specification does not change modify the mobile IPv6 binding This specification does not modify the mobile IPv6 binding cache any
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 binding. Flow binding an entry for each of the registered flow binding. Flow binding
entries can point to an entry in the binding cache by means of the entries can point to an entry in the binding cache by means of the
BID. Each flow binding entry include the following parameters : BID. Each flow binding entry include the following parameters :
* FID (Flow Identifier): For a given mobile node, identified by * FID (Flow Identifier): For a given mobile node, identified by
its primary home address, the FID MUST uniquely identify an its primary home address, the FID MUST uniquely identify an
entry, i.e. a unique flow binding. Each mobile node can only entry, i.e. a unique flow binding. Each mobile node can only
have a single entry identified by a given FID at any one time. have a single entry identified by a given FID at any one time.
Different mobile nodes can use the same FID number space. Different mobile nodes can use the same FID number space.
* A Flow Descriptor: Included in a Flow Description sub-option. * A Flow Descriptor: Included in a Flow Description sub-option.
* BID(s): The list of BIDs associated with the entry as defined * BID(s): The list of BIDs associated with the entry as defined
by the Binding Reference sub-option included in the FID option by the Binding Reference sub-option included in the FID option
that created it. that created it.
* Action: The action associated with a given entry as defined by * Action: The action associated with a given entry as defined by
the PRO field of the FID option that created it the Action field of the FID option that created it
* Active/Inactive flag: This flag indicates whether the entry is * Active/Inactive flag: This flag indicates whether the entry is
active or inactive. active or inactive.
* FID-PRI: This field indicates the priority of the flow and is
used to break the tie between overlapping flows.
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 corresponding binding cache. An entry in the flow bindings list, the corresponding 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.
The BIDs included in a given entry point to a corresponding entry in A valid BID is required to make the entry "active". If all of the
the binding cache for the purpose of identifying a care-of address. BIDs pointed to by a given entry are not valid BIDs in the binding
cache, the flow binding entry becomes "inactive", in other words it
Depending on the Action parameter in a given entry a valid BID is does not affect data traffic. Note that if the action parameter in
required to make the entry "active". If all of the BIDs pointed to an entry indicates "n-cast" then the entry becomes inactive only if
by a given entry are not valid BIDs in the binding cache, the flow none of the BIDs is valid. If only some of the BIDs are valid, the
binding entry becomes "inactive", in other words it does not affect invalid BIDs are simply ignored.
data traffic. Note that if the action parameter in an entry
indicates "n-cast" then the entry becomes inactive only if none of
the BIDs is valid. If only some of the BIDs are 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 corresponding the mobile node as well as in mobility agents and corresponding
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 bindings As an example the following represents an ordered flow bindings
entries table for a mobile node that has registered three care-of entries table for a mobile node that has registered multiple care-of
addresses and three flow bindings. addresses and flow bindings.
FID-PRI FID Flow Description BIDs Action A/I FID-PRI FID Flow Description BIDs Action A/I
------- --- ---------------- ---- ------- ------ ------- --- ---------------- ---- ------- ------
10 4 TCP 2 Forward Active 10 4 TCP 2 Forward Active
20 3 srcAddr=IPx N/A Discard Active 20 3 srcAddr=IPx N/A Discard Active
30 2 srcAddr=IPy 4 Forward Inactive 30 2 srcAddr=IPy 4 Forward Inactive
40 5 UDP 1,3 N-Cast Active 40 5 UDP 1,3 N-Cast Active
Ordered Flow Binding Entries Ordered Flow Binding Entries
skipping to change at page 17, line 51 skipping to change at page 16, line 51
The ordered list of BIDs is used to determine how to forward a packet The ordered list of BIDs is used to determine how to forward a packet
to a given mobile node when the packet does not match any of the flow to a given mobile node when the packet does not match any of the flow
binding entries defined in Section 4.4. A packet that does not match binding entries defined in Section 4.4. A packet that does not match
any of the flow binding entries SHOULD be forwarded to the care-of any of the flow binding entries SHOULD be forwarded to the care-of
address identified by the BID with the highest priority i.e., lowest address identified by the BID with the highest priority i.e., lowest
BID-PRI value. BID-PRI value.
5.2. Mobile Node Considerations 5.2. Mobile Node Considerations
This specification allows the mobile node to maintain several This specification allows the mobile node to maintain several
bindings in its home agent and to direct packets to different care-of bindings with its home agent, MAP and correspondent nodes and to
addresses according to flow bindings. This section details the direct packets to different care-of addresses according to flow
mobile node operations necessary to implement this specification. bindings. This section details the mobile node operations necessary
to implement this specification.
The home agent list of flow bindings is manipulated by the mobile The home agent list of flow bindings is manipulated by the mobile
node, via flow identification and flow summary options included in node, via flow identification and flow summary options included in
binding update messages. Each flow binding update can add, modify, binding update messages. Each flow binding update can add, modify,
refresh, or delete a given binding. More than one flow refresh, or delete a given binding. More than one flow
identification options MAY be included in the same binding update but identification options MAY be included in the same binding update but
each of them MUST include a different FID. In other words, two flow each of them MUST include a different FID. In other words, two flow
identification options in the same message can not be about the same identification options in the same message can not be about the same
flow binding. flow binding.
skipping to change at page 19, line 7 skipping to change at page 18, line 8
must be logically registered by this binding update, or must have must be logically registered by this binding update, or must have
already been registered by the receiver of the binding update in an already been registered by the receiver of the binding update in an
earlier binding update , as defined in Section 5.2.1. earlier binding update , as defined in Section 5.2.1.
The flow identification option MUST include a unique Flow Identifier The flow identification option MUST include a unique Flow Identifier
in the FID field. The FID needs only be unique for the receiver of 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 FID can be the binding update and for the same sender, i.e. the same FID can be
used across different receivers of the binding update, for the same used across different receivers of the binding update, for the same
sender. sender.
The FID-PRI field is set to the desired priority of the FID, The FID-PRI field is set to the desired unique priority of the
defining the order of the binding to be added in the list of flow FID, defining the order of the binding to be added in the list of
binding entries as defined in Section 4.4. flow binding entries as defined in Section 4.4.
The Action field is set to one of the defined action codes (see The Action field is set to one of the defined action codes (see
Section 4.2). Section 4.2).
The PRO field MUST indicate an Add operation.
The Status filed is set to zero in all binding update messages. The Status filed is set to zero in all binding update messages.
The mobile node MUST include exactly one Flow Description sub-option The mobile node MUST include exactly one Flow Description sub-option
(see Section 4.2.2) describing the flow associated with the new (see Section 4.2.2) describing the flow associated with the new
binding. binding.
The mobile node MAY also include exactly one BID Reference sub-option The mobile node MAY also include exactly one BID Reference sub-option
(see Section 4.2.1) to associate the flow binding with a given set of (see Section 4.2.1) to associate the flow binding with a given set of
BIDs and corresponding CoAs. Depending on the Action field of the BIDs and corresponding CoAs. Depending on the Action field of the
Flow Binding Identifier option, the following rules MUST be followed Flow Binding Identifier option, the following rules MUST be followed
with respect to the Binding Reference sub-option: with respect to the Binding Reference sub-option:
- if the Action indicates 'Forward', a single Binding Reference
sub-option with a single BID MUST be included. This BID MUST be
associated with a single care-of address.
- if the Action indicates 'Discard', the Binding Reference sub- - if the Action indicates 'Discard', the Binding Reference sub-
option SHOULD NOT be included. If it is included it will be option SHOULD NOT be included. If it is included it will be
ignored by the receiver. ignored by the receiver.
- if the Action indicates 'n-cast', a single Binding Reference - if the Action indicates 'n-cast', a single Binding Reference
sub-option with one or more BIDs MUST be included. sub-option with one or more BIDs MUST be included.
5.2.2.2. Modifying flow bindings 5.2.2.2. Modifying flow bindings
Flow binding modification is essentially a process where an existing Flow binding modification is essentially a process where an existing
skipping to change at page 20, line 5 skipping to change at page 18, line 48
new flow binding (included in the option) is added, and given the new flow binding (included in the option) is added, and given the
same FID as the flow that was removed. With this procedure the same FID as the flow that was removed. With this procedure the
mobile node can change the action, the priority, the BID, or the flow mobile node can change the action, the priority, the BID, or the flow
description associated with a flow binding. description 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 PRO field MUST be set to 1, indicating a request to modify the The FID-PRI and Action fields MUST be set to the unique desired
binding. value to be implemented with this modification.
The FID-PRI and Action fields MUST be set to the desired values to
be implemented with this modification.
The Status field is set to zero since this option is in a binding The Status field is set to zero since this option is in a binding
update. update.
The mobile node MAY include exactly one Flow Description sub-option The mobile node MAY include exactly one Flow Description sub-option
(see Section 4.2.2) describing the modified flow to be associated (see Section 4.2.2) describing the modified flow to be associated
with the binding. with the binding.
The mobile node MAY also include exactly one BID Reference sub-option The mobile node MAY also include exactly one BID Reference sub-option
(see Section 4.2.1) to associate the existing binding with a new set (see Section 4.2.1) to associate the existing binding with a new set
skipping to change at page 20, line 47 skipping to change at page 19, line 41
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.3. MUST include one or more FID fields as indicated in Section 4.3.
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.
Any flow bindings (active or inactive) that are not included in a Any flow bindings (active or inactive) that are not included 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.4, MUST also be refreshed, or binding entries (see Section 4.4), 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
Removal of flow binging entries is performed implicitly by omission Removal of flow binging entries is performed implicitly by omission
of a given FID from a binding update. of a given FID from a binding update.
To remove a flow binding the MN simply sends a binding update that To remove a flow binding the MN simply sends a binding update that
includes flow identification and flow summary options for all the includes flow identification and flow summary options for all the
skipping to change at page 21, line 42 skipping to change at page 20, line 33
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 to
the transmission of a binding update MUST determine if the Binding the transmission of a binding update MUST determine if the Binding
Acknowledgement contains a copy of every flow identification options Acknowledgement contains a copy of every flow identification options
included in the binding update. A Binding Acknowledgement without included in the binding update. A Binding Acknowledgement without
flow identification option(s), in response to a Binding Update with flow identification option(s), in response to a Binding Update with
flow identification option, would indicate inability (or flow identification option, would indicate inability (or
unwillingness) on behalf of the source node to support the extensions unwillingness) on behalf of the source node to support the extensions
presented in this document. presented in this document.
If a received Binding Acknowledgement contains a copy of of each flow If a received Binding Acknowledgement contains a copy of each flow
identification option that was sent within the binding update, the identification option that was sent within the binding update, the
status field of each flow identification option indicates the status status field of each flow identification option indicates the status
of the flow binding on the distant node. of the flow binding on the distant node.
5.2.6. Return Routability Procedure 5.2.6. 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. the mobile node and the correspondent node.
This procedure is not affected by the extensions defined in this This procedure is not affected by the extensions defined in this
document. However, since a binding update message is secured with document. However, since a binding update message is secured with
the key generated based on the home address and care-of address test, the key generated based on the home address and care-of address test,
a mobile node MUST NOT bind a flow to a care-of address whose keygen a mobile node MUST NOT bind a flow to a care-of address whose keygen
token (see RFC3775 [RFC3775]) was not used to generate the key for token (see RFC3775 [RFC3775]) was not used to generate the key for
securing the Binding Update. This limitation prohibits the sender securing the Binding Update. This limitation prohibits the sender
from requesting the n-cast action before having registered each from requesting the n-cast action for multiple addresses before
care-of address one by one. having registered each care-of address one by one.
5.3. HA, MAP, and CN Considerations 5.3. HA, MAP, and CN Considerations
This specification allows the home agents, mobility anchor points, This specification allows the home agents, mobility anchor points,
and corresponding nodes to maintain several bindings for a given home and corresponding nodes to maintain several bindings for a given home
address and to direct packets to different care-of addresses address and to direct packets to different care-of addresses
according to flow bindings. This section details the home agent according to flow bindings. This section details the home agent
operations necessary to implement this specification. These operations necessary to implement this specification. These
operations are identical for MAPs and CNs unless otherwise stated. operations are identical for MAPs and CNs unless otherwise stated.
skipping to change at page 23, line 29 skipping to change at page 22, line 19
If more than one flow identification option in the same BU, has the If more than one flow identification option in the same BU, has the
same value in the FID field, all the flow identification options MUST same value in the FID field, all the flow identification options MUST
be rejected. be rejected.
If all FID fields have different values the flow identification If all FID fields have different values the flow identification
options can be processed further and in any order, as defined by the options can be processed further and in any order, as defined by the
following subsections. following subsections.
5.3.2.1. Handling Flow Binding Add Requests 5.3.2.1. Handling Flow Binding Add Requests
If the PRO field of the flow identification option is set to 'Add',
it indicates a flow binding add request.
If the FID field of the flow identification option is already present If the FID field of the flow identification option is already present
in the list of flow binding entries for this mobile node, the home in the list of flow binding entries for this mobile node, the home
agent MUST reject this flow binding add request by copying the flow agent MUST reject this flow binding add request by copying the flow
identification option in the BA, and setting the Status field to 135 identification option in the BA, and setting the Status field to 135
(FID already in use). (FID already in use).
If the flow identification option does not include a flow description If the flow identification option does not include a flow description
sub-option, the home agent MUST again reject this request by copying sub-option, the home agent MUST again reject this request by copying
the flow identification option in the BA, and setting the Status the flow identification option in the BA, and setting the Status
field to 129 (Flow identification option poorly formed). field to 129 (Flow identification option malformed).
If the flow identification option does include a flow description If the flow identification option does include a flow description
sub-option, but the flow description type is not supported, the home sub-option, but the flow description type is not supported, the home
agent MUST also reject this request by copying the flow agent MUST also reject this request by copying the flow
identification option in the BA, and setting the Status field to 137 identification option in the BA, and setting the Status field to 137
(FD-Type not supported). (FD-Type not supported).
If the FID value is new the home agent MUST check the Action field in If the FID value is new the home agent MUST check the Action field in
combination with the Binding Reference sub-option if present. combination with the Binding Reference sub-option if present.
skipping to change at page 24, line 4 skipping to change at page 22, line 40
If the flow identification option does include a flow description If the flow identification option does include a flow description
sub-option, but the flow description type is not supported, the home sub-option, but the flow description type is not supported, the home
agent MUST also reject this request by copying the flow agent MUST also reject this request by copying the flow
identification option in the BA, and setting the Status field to 137 identification option in the BA, and setting the Status field to 137
(FD-Type not supported). (FD-Type not supported).
If the FID value is new the home agent MUST check the Action field in If the FID value is new the home agent MUST check the Action field in
combination with the Binding Reference sub-option if present. combination with the Binding Reference sub-option if present.
- if the Action indicates 'Forward' - if the Action indicates 'Forward'
If the Binding reference sub-option is not included or if it is If the Binding reference sub-option is not included or if it is
included but it contains more than a single BID, the home agent included but it contains more than a single BID, the home agent
MUST reject this flow binding add request by copying the flow MUST reject this flow binding add request by copying the flow
identification option in the BA, and setting the Status field to identification option in the BA, and setting the Status field to
129 (Flow identification option poorly formed). 129 (Flow identification option malformed).
If the Binding Reference sub-option is present and includes a If the Binding Reference sub-option is present and includes a
single BID, but the BID is not present in the binding cache of the single BID, but the BID is not present in the binding cache of the
mobile node the home agent MUST reject this flow binding add mobile node the home agent MUST reject this flow binding add
request by copying the flow identification option in the BA, and request by copying the flow identification option in the BA, and
setting the Status field to TBD (BID not known). setting the Status field to TBD (BID not known).
If the Binding Reference sub-option is present and includes a If the Binding Reference sub-option is present and includes a
single BID, and the BID exists in the mobile node's binding cache, single BID, and the BID exists in the mobile node's binding cache,
the home agent SHOULD add a new entry in the mobile node's list of the home agent SHOULD add a new entry in the mobile node's list of
skipping to change at page 24, line 34 skipping to change at page 23, line 23
ignored. ignored.
The home agent SHOULD add a new entry in the mobile node's list of The home agent SHOULD add a new entry in the mobile node's list of
flow binding entries, as defined below. flow binding entries, as defined below.
- if the Action indicates 'n-cast', - if the Action indicates 'n-cast',
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 flow binding add request by copying the agent MUST reject this flow binding add request by copying the
flow identification option in the BA, and setting the Status field flow identification option in the BA, and setting the Status field
to 129 (Flow identification option poorly formed). to 129 (Flow identification option malformed).
If the Binding Reference sub-option is present and includes BIDs If the Binding Reference sub-option is present and includes one or
that are not present in the binding cache of the mobile node the more BIDs that are not present in the binding cache of the mobile
home agent MUST reject this flow binding add request by copying node the home agent MUST reject this flow binding add request by
the flow identification option in the BA, and setting the Status copying the flow identification option in the BA, and setting the
field to TBD (BID not known). Status field to TBD (BID not known).
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, and the BIDs exist in the mobile node's binding cache, more BIDs, and the BIDs exist in the mobile node's binding cache,
the home agent SHOULD add a new entry in the mobile node's list of the home agent SHOULD add a new entry in the mobile node's list of
flow binding entries, as defined below. flow binding entries, as defined below.
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
skipping to change at page 25, line 17 skipping to change at page 24, line 7
The flow description included in the corresponding sub-option The flow description included in the corresponding sub-option
the action indicated in the Action field the action indicated in the Action field
the BIDs indicated in the binding reference sub-option the BIDs indicated in the binding reference sub-option
the entry MUST be marked as Active, as shown in Section 4.4 the entry MUST be marked as Active, as shown in Section 4.4
5.3.2.2. Handling flow binding Modification Requests 5.3.2.2. Handling flow binding Modification Requests
If the PRO field of the flow identification option is set to The flow binding modification is essentially a process where an
'Modify', it indicates a flow binding modification request.
Note that flow binding modification is essentially a process where an
existing flow binding is removed from the list of flow binding existing flow binding is removed from the list of flow binding
entries and a new flow binding (included in the option) is added, and entries and a new flow binding (included in the option) is added, and
given the same FID as the flow that was removed. given the same FID as the flow that was removed.
If the value of the FID field of the flow identification option is If the value of the FID field of the flow identification option is
not present in the binding cache entries for this mobile node, the not present in the binding cache entries for this mobile node, the
home agent MUST reject this flow binding modify request by copying home agent MUST reject this flow binding modify request by copying
the flow identification option in the BA, and setting the Status the flow identification option in the BA, and setting the Status
field to 135 (FID not found). field to 135 (FID not found).
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 first remove the flow flow binding entries, the home agent SHOULD first remove the flow
binding entry identified by the FID. The home agent then SHOULD binding entry identified by the FID. The home agent SHOULD then
processes this flow identification option as defined in processes this flow identification option as defined in
Section 5.3.2.1. Section 5.3.2.1.
5.3.3. Receiving BU with Flow Summary Option 5.3.3. Receiving BU with Flow Summary Option
When the home agent receives a binding update which includes a Flow When the home agent receives a binding update which includes a Flow
Summary option, it first performs the operation described in section Summary option, it first performs the operation described in section
10.3.1 of RFC3775. Binding update messages including more than one 10.3.1 of RFC3775. Binding update messages including more than one
flow summary option MUST be rejected. flow summary option MUST be rejected. A de-registration binding
update (with a zero lifetime) would result in deleting all bindings
Home agents that do not support this specification will ignore the regardless of the presence of the Flow summary option.
flow summary option, having no effect on the operation of the rest of
the protocol.
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 the flow summary
option is not present in the list of flow binding entries for this option is not present in the list of flow binding entries for this
mobile node, the home agent MUST reject this flow binding modify mobile node, the home agent MUST reject this flow binding refresh by
request by including a flow identification option in the BA, and including a flow identification option in the BA, and setting the FID
setting the FID field in the value of the FID that is not found and field in the value of the FID that is not found and the Status field
the Status field to 135 (FID not found). to 135 (FID not found).
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
slow binding entries the, home agent SHOULD refresh the binding entry slow binding entries the, home agent SHOULD refresh the binding entry
identified by the FID without changing any of the other parameters identified by the FID without changing any of the other parameters
associated with it. associated with it.
5.3.4. Handling flow binding Removals 5.3.4. Handling 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.
skipping to change at page 27, line 26 skipping to change at page 26, line 8
IPv4 packets when [I-D.ietf-mext-nemo-v4traversal]. IPv4 packets when [I-D.ietf-mext-nemo-v4traversal].
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.4). A match is binding entries for this mobile node (see Section 4.4). A match is
attempted with the flow description included in the first line attempted with the flow description included in the first line
(highest order) of the table. If the packet matches the flow (highest order) of the table. If the packet matches the flow
description, the action defined by the action parameter of the table description, the action defined by the action parameter of the table
SHOULD be performed. SHOULD be performed.
- if the Action indicates 'Forward' the packet is forwarded to the
care-of address indicated by the BID parameter in the same line of
the table.
- if the Action indicates 'Discard', the packet is silently - if the Action indicates 'Discard', the packet is silently
discarded discarded
- if the Action indicates 'n-cast', a copy of the packet is - if the Action indicates 'n-cast', a copy of the packet is
forwarded to each of the care-of addresses associated with the forwarded to each of the care-of addresses associated with the
BIDs indicated in the same line of the table. BIDs indicated in the same line of the table.
If the action indicated in one of the entries in the list of flow If the action indicated in one of the entries in the list of flow
bindings is "Discard" then, no BIDs needs to be indicated in the same bindings is "Discard" then, no BIDs needs to be indicated in the same
entry since the packet is not forwarded. If, however, the action entry since the packet is not forwarded. If, however, the action
indicated in an entry of the list of flow bindings is "forward" or indicated in an entry of the list of flow bindings is "n-cast", the
"n-cast", the entry must indicated a BID. For "n-cast" if any of the entry must indicated a BID. For "n-cast" if any of the BIDs
BIDs indicated does not correspond to a valid care-of address, e.g., indicated does not correspond to a valid care-of address, e.g., the
the BID was deregistered then that BID has no effect on the traffic. BID was deregistered then that BID has no effect on the traffic. In
In other words, packets matching the flow binding are n-casted to the other words, packets matching the flow binding are n-casted to the
other BIDs, pointing to registered care-of addresses. If none of the other BIDs, pointing to registered care-of addresses. If none of the
BIDs pointed to in a flow binding entry is valid then the entry is BIDs pointed to in a flow binding entry is valid then the entry is
considered to be inactive (as defined in Section 4.4) and is skipped. considered to be inactive (as defined in Section 4.4) and is skipped.
In other words packets should not be matched against that entry. In other words packets should not be matched against that entry.
6. Security considerations 6. 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 message. The new option allows the mobile node to binding update message. The new option allows the mobile node to
associate some flows to one interface and other flows to another associate some flows to one interface and other flows to another
skipping to change at page 31, line 9 skipping to change at page 30, line 9
We would like to explicitly acknowledge the following person who co- We would like to explicitly acknowledge the following person who co-
authored one of the documents used as source material for this authored one of the documents used as source material for this
document. document.
Nikolaus A. Fikouras, niko@comnets.uni-bremen.de Nikolaus A. Fikouras, niko@comnets.uni-bremen.de
9. Acknowledgements 9. Acknowledgements
We would also like to acknowledge the following people in We would also like to acknowledge the following people in
alphabetical order: C. Castelluccia, K. ElMalki, K. Georgios, , C. alphabetical order: C. Castelluccia, K. ElMalki, K. Georgios, , C.
Goerg, T. Noel, F.-N. Pavlidou, V. Park. Gabor Fekete for the Goerg, C. Kaas-Petersen, T. Noel, F.-N. Pavlidou, V. Park. Gabor
analysis that led to the inclusion of the BIDRef sub-option. Henrik Fekete for the analysis that led to the inclusion of the BIDRef sub-
Levkowetz for suggesting support for other ways of describing flows. option. Henrik Levkowetz for suggesting support for other ways of
describing flows.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-mext-nemo-v4traversal] [I-D.ietf-mext-nemo-v4traversal]
Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", draft-ietf-mext-nemo-v4traversal-10 (work in Routers", draft-ietf-mext-nemo-v4traversal-10 (work in
progress), April 2009. progress), April 2009.
 End of changes. 57 change blocks. 
175 lines changed or deleted 145 lines changed or added

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