draft-ietf-mext-binary-ts-05.txt   rfc6088.txt 
Network Working Group G. Tsirtsis Internet Engineering Task Force (IETF) G. Tsirtsis
Internet-Draft G. Giarreta Request for Comments: 6088 G. Giaretta
Intended status: Standards Track Qualcomm Category: Standards Track Qualcomm
Expires: April 8, 2011 H. Soliman ISSN: 2070-1721 H. Soliman
Elevate Technologies Elevate Technologies
N. Montavont N. Montavont
IT/TB IT/TB
October 5, 2010 January 2011
Traffic Selectors for Flow Bindings Traffic Selectors for Flow Bindings
draft-ietf-mext-binary-ts-05.txt
Abstract Abstract
This document defines binary formats for IPv4 and IPv6 traffic This document defines binary formats for IPv4 and IPv6 traffic
selectors to be used in conjunction with flow bindings for Mobile selectors to be used in conjunction with flow bindings for Mobile
IPv6. IPv6.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on April 8, 2011. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6088.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 2
3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 5 3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 2
3.1. IPv4 binary traffic selector . . . . . . . . . . . . . . . 5 3.1. IPv4 Binary Traffic Selector . . . . . . . . . . . . . . . 2
3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 9 3.2. IPv6 Binary Traffic Selector . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . . 18 7.1. Normative References . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . . 18 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction 1. Introduction
This document defines binary formats for IPv4 and IPv6 Traffic This document defines binary formats for IPv4 and IPv6 traffic
Selector sub-options as defined in [I-D.ietf-mext-flow-binding]. selector sub-options, as defined in [RFC6089].
The binary traffic selector format defined here, allows for efficient The binary traffic selector format defined here, allows for efficient
identification of flow(s) based on well known fields in IPv4 identification of flow(s) based on well-known fields in IPv4
[RFC0791], IPv6 [RFC2460], and transport layer headers like TCP [RFC0791], IPv6 [RFC2460], and transport layer headers like TCP
[RFC0793] and UDP [RFC0768]. [RFC0793] and UDP [RFC0768].
2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Traffic Selector Sub-Options 3. Traffic Selector Sub-Options
[I-D.ietf-mext-flow-binding] defines the format for the traffic [RFC6089] defines the format for the traffic selector sub-option.
selector sub-option.
The following values of the TS Format field, are defined in this The following values of the TS Format field are defined in this
specification for binary traffic selectors. specification for binary traffic selectors.
TS Format: TS Format:
1 IPv4 binary traffic selector 1 IPv4 binary traffic selector
2 IPv6 binary traffic selector 2 IPv6 binary traffic selector
3.1. IPv4 binary traffic selector 3.1. IPv4 Binary Traffic Selector
If the TS Format field of the traffic selector sub-option indicates If the TS Format field of the traffic selector sub-option indicates
"IPv4 binary traffic selector", then the traffic selector is "IPv4 binary traffic selector", then the traffic selector is
formatted as shown below. formatted as shown below.
The alignment requirement for this sub-option is: The alignment requirement for this sub-option is:
4n if A, B, C, D, E, or F is set 4n if A, B, C, D, E, or F is set
2n if G, H, I, or J is set 2n if G, H, I, or J is set
n if K, L, M, or N is set n if K, L, M, or N is set
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 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 | TS Format | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Sub-opt Type | Sub-Opt Len | TS Format | Reserved |
|A|B|C|D|E|F|G|H|I|J|K|L|M|N| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |A|B|C|D|E|F|G|H|I|J|K|L|M|N| Reserved |
| (A)Start Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (A)Start Source Address |
| (B)End Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (B)End Source Address |
| (C)Start Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (C)Start Destination Address |
| (D)End Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (D)End Destination Address |
| (E)Start IPsec SPI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (E)Start IPsec SPI |
| (F)End IPsec SPI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (F)End IPsec SPI |
| (G)Start Source port | (H)End Source port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (G)Start Source port | (H)End Source port |
| (I)Start Destination port | (J)End Destination port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (I)Start Destination port | (J)End Destination port |
| (K)Start DS | (L)End DS |(M)Start Prot. | (N) End Prot. | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | (K)Start DS | (L)End DS |(M)Start Prot. | (N) End Prot. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: IPv4 binary traffic selector Figure 1: IPv4 binary traffic selector
Flags (A-N) Flags (A-N)
Each flag indicates whether the corresponding field is present in Each flag indicates whether the corresponding field is present in
the message the message.
(A)Start Source Address (A)Start Source Address
This field identifies the first source address, from the range of This field identifies the first source address, from the range of
32-bit IPv4 addresses to be matched, on data packets sent from a 32-bit IPv4 addresses to be matched, on data packets sent from a
corresponding node to the mobile node as seen by the home agent. corresponding node to the mobile node as seen by the home agent.
In other words this is one of the addresses of the correspondent In other words, this is one of the addresses of the correspondent
node. node.
(B)End Source Address (B)End Source Address
If more than one contiguous source address needs to be matched If more than one contiguous source address needs to be matched,
then this field can be used to indicate the end value of a range then this field can be used to indicate the end value of a range
starting from the value of the Start Source Address field. This starting from the value of the Start Source Address field. This
field MUST NOT be included unless the Start Source Address field field MUST NOT be included unless the Start Source Address field
is included. When this field is included the receiver will match is included. When this field is included, the receiver will match
all of the addresses between fields (A) and (B), inclusive of (A) all of the addresses between fields (A) and (B), inclusive of (A)
and (B). and (B).
(C)Start Destination Address (C)Start Destination Address
This field identifies the first destination address, from the This field identifies the first destination address, from the
range of 32-bit IPv4 addresses to be matched, on data packets sent range of 32-bit IPv4 addresses to be matched, on data packets sent
from a corresponding node to the mobile node as seen by the home from a corresponding node to the mobile node as seen by the home
agent. In other words this is one of the registered home agent. In other words, this is one of the registered home
addresses of the mobile node. addresses of the mobile node.
(D)End Destination Address (D)End Destination Address
If more than one contiguous destination address needs to be If more than one contiguous destination address needs to be
matched then this field can be used to indicate the end value of a matched, then this field can be used to indicate the end value of
range starting from the value of the Start Destination Address a range starting from the value of the Start Destination Address
field. This field MUST NOT be included unless the Start field. This field MUST NOT be included unless the Start
Destination Address field is included. When this field is Destination Address field is included. When this field is
included the receiver will match all of the addresses between included, the receiver will match all of the addresses between
fields (C) and (D), inclusive of (C) and (D). fields (C) and (D), inclusive of (C) and (D).
(E)Start IPsec SPI - Security Parameter Index (E)Start IPsec SPI - Security Parameter Index
This field identifies the first 32-bit IPsec SPI value, from the This field identifies the first 32-bit IPsec SPI value, from the
range of SPI values to be matched, on data packets sent from a range of SPI values to be matched, on data packets sent from a
corresponding node to the mobile node as seen by the home agent. corresponding node to the mobile node as seen by the home agent.
This field is defined in [RFC4303]. This field is defined in [RFC4303].
(F)End IPsec SPI - Security Parameter Index (F)End IPsec SPI - Security Parameter Index
If more than one contiguous SPI values need to be matched then If more than one contiguous SPI value needs to be matched, then
this field can be used to indicate the end value of a range this field can be used to indicate the end value of a range
starting from the value of the Start IPsec SPI field. This field starting from the value of the Start IPsec SPI field. This field
MUST NOT be included unless the Start IPsec SPI field is included. MUST NOT be included unless the Start IPsec SPI field is included.
When this field is included the receiver will match all of the SPI When this field is included, the receiver will match all of the
values between fields (E) and (F), inclusive of (E) and (F). SPI values between fields (E) and (F), inclusive of (E) and (F).
(G)Start Source Port (G)Start Source Port
This field identifies the first 16-bit source port number, from This field identifies the first 16-bit source port number, from
the range of port numbers to be matched, on data packets sent from the range of port numbers to be matched, on data packets sent from
a corresponding node to the mobile node as seen by the home agent. a corresponding node to the mobile node as seen by the home agent.
This is from the range of port numbers defined by IANA This is from the range of port numbers defined by IANA
(http://www.iana.org/assignments/port-numbers) (http://www.iana.org).
(H)End Source Port (H)End Source Port
If more than one contiguous source port numbers need to be matched
then this field can be used to indicate the end value of a range If more than one contiguous source port number needs to be
starting from the value of the Start Source Port field. This matched, then this field can be used to indicate the end value of
field MUST NOT be included unless the Start Source Port field is a range starting from the value of the Start Source Port field.
included. When this field is included the receiver will match all This field MUST NOT be included unless the Start Source Port field
of the port numbers between fields (G) and (H), inclusive of (G) is included. When this field is included, the receiver will match
and (H). all of the port numbers between fields (G) and (H), inclusive of
(G) and (H).
(I)Start Destination Port (I)Start Destination Port
This field identifies the first 16-bit destination port number, This field identifies the first 16-bit destination port number,
from the range of port numbers to be matched, on data packets sent from the range of port numbers to be matched, on data packets sent
from a corresponding node to the mobile node as seen by the home from a corresponding node to the mobile node as seen by the home
agent. agent.
(J)End Destination Port (J)End Destination Port
If more than one contiguous destination port numbers need to be If more than one contiguous destination port number needs to be
matched then this field can be used to indicate the end value of a matched, then this field can be used to indicate the end value of
range starting from the value of the Start Destination Port field. a range starting from the value of the Start Destination Port
This field MUST NOT be included unless the Start Destination Port field. This field MUST NOT be included unless the Start
field is included. When this field is included the receiver will Destination Port field is included. When this field is included,
match all of the port numbers between fields (I) and (J), the receiver will match all of the port numbers between fields (I)
inclusive of (I) and (J). and (J), inclusive of (I) and (J).
(K)Start DS - Differential Services (K)Start DS - Differential Services
This field identifies the first differential services value, from This field identifies the first differential services value, from
the range of differential services values to be matched, on data the range of differential services values to be matched, on data
packets sent from a corresponding node to the mobile node as seen packets sent from a corresponding node to the mobile node as seen
by the home agent. Note that this field is called Type of Service by the home agent. Note that this field is called a "Type of
field in [RFC0791]. [RFC3260] then clarified that the field has Service field" in [RFC0791]. [RFC3260] then clarified that the
been redefined as 6 bits DS field and 2 bits reserved, later field has been redefined as a 6-bit DS field with 2 bits reserved,
claimed by Explicit Congestion Notification (ECN) [RFC3168]. For later claimed by Explicit Congestion Notification (ECN) [RFC3168].
the purpose of this specification the (K)Start DS field is 8 bits For the purpose of this specification, the (K)Start DS field is 8
long, were the 6 most significant bits indicating the DS field to bits long, where the 6 most significant bits indicate the DS field
be matched and the 2 least significant bit's value MUST be ignored to be matched and the 2 least significant bits' values MUST be
in any comparision. ignored in any comparison.
(L)End DS - Differential Services (L)End DS - Differential Services
If more than one contiguous DS values need to be matched then this If more than one contiguous DS value needs to be matched, then
field can be used to indicate the end value of a range starting this field can be used to indicate the end value of a range
from the value of the Start DS field. This field MUST NOT be starting from the value of the Start DS field. This field MUST
included unless the Start DS field is included. When this field NOT be included unless the Start DS field is included. When this
is included, it MUST be coded the same way as defined for (K). field is included, it MUST be coded the same way as defined for
When this field is included the receiver will match all of the (K). When this field is included, the receiver will match all of
values between fields (K) and (L), inclusive of (K) and (L). the values between fields (K) and (L), inclusive of (K) and (L).
(M)Start Protocol (M)Start Protocol
This field identifies the first 8-bit protocol value, from the This field identifies the first 8-bit protocol value, from the
range of protocol values to be matched, on data packets sent from range of protocol values to be matched, on data packets sent from
a corresponding node to the mobile node as seen by the home agent. a corresponding node to the mobile node as seen by the home agent.
(N)End Protocol (N)End Protocol
If more than one contiguous protocol values need to be matched If more than one contiguous protocol value needs to be matched,
then this field can be used to indicate the end value of a range then this field can be used to indicate the end value of a range
starting from the value of the Start Protocol field. This field starting from the value of the Start Protocol field. This field
MUST NOT be included unless the Start Protocol field is included. MUST NOT be included unless the Start Protocol field is included.
When this field is included the receiver will match all of the When this field is included, the receiver will match all of the
values between fields (M) and (N), inclusive of (M) and (N). values between fields (M) and (N), inclusive of (M) and (N).
Reserved Reserved
Reserved for future use. These bits MUST be set to zero by the Reserved for future use. These bits MUST be set to zero by the
sender and ignored by the receiver. sender and ignored by the receiver.
3.2. IPv6 binary traffic selector 3.2. IPv6 Binary Traffic Selector
If the TS Format field of the traffic selector sub-option indicates If the TS Format field of the traffic selector sub-option indicates
"IPv6 binary traffic selector", then the traffic selector is "IPv6 binary traffic selector", then the traffic selector is
formatted as follows: formatted as follows:
The alignment requirement for this sub-option is: The alignment requirement for this sub-option is:
8n if A, B, C, or D is set 8n if A, B, C, or D is set
4n if E, F, G, or H is set 4n if E, F, G, or H is set
2n if I, J, K, or L is set 2n if I, J, K, or L is set
n if M, N, O, or P is set n if M, N, O, or P is set
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 | TS Format | Reserved | |Sub-opt Type | Sub-Opt Len | TS Format | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| Reserved | |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ (A)Start Source Address + + (A)Start Source Address +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ (B)End Source Address + + (B)End Source Address +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ (C)Start Destination Address + + (C)Start Destination Address +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ (D)End Destination Address + + (D)End Destination Address +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (E)Start IPsec SPI | | (E)Start IPsec SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (F)End IPsec SPI | | (F)End IPsec SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (G)Start Flow Label | | (G)Start Flow Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (H)End Flow Label | | (H)End Flow Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (I)Start Source port | (J)End Source port | | (I)Start Source port | (J)End Source port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (K)Start Destination port | (L)End Destination port | | (K)Start Destination port | (L)End Destination port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (M)Start TC | (N)End TC | (O)Start NH | (P) End NH | | (M)Start TC | (N)End TC | (O)Start NH | (P) End NH |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: IPv6 binary traffic selector Figure 2: IPv6 binary traffic selector
Flags (A-P) Flags (A-P)
Each flag indicates whether the corresponding field is present in Each flag indicates whether the corresponding field is present in
the message the message
(A)Start Source Address (A)Start Source Address
This field identifies the first source address, from the range of This field identifies the first source address, from the range of
128-bit IPv6 addresses to be matched, on data packets sent from a 128-bit IPv6 addresses to be matched, on data packets sent from a
corresponding node to the mobile node as seen by the home agent. corresponding node to the mobile node as seen by the home agent.
In other words this is one of the addresses of the correspondent In other words, this is one of the addresses of the correspondent
node. node.
(B)End Source Address (B)End Source Address
If more than one contiguous source address needs to be matched If more than one contiguous source address needs to be matched,
then this field can be used to indicate the end value of a range then this field can be used to indicate the end value of a range
starting from the value of the Start Source Address field. This starting from the value of the Start Source Address field. This
field MUST NOT be included unless the Start Source Address field field MUST NOT be included unless the Start Source Address field
is included. When this field is included the receiver will match is included. When this field is included, the receiver will match
all of the addresses between fields (A) and (B), inclusive of (A) all of the addresses between fields (A) and (B), inclusive of (A)
and (B). and (B).
(C)Start Destination Address (C)Start Destination Address
This field identifies the first destination address, from the This field identifies the first destination address, from the
range of 128-bit IPv6 addresses to be matched, on data packets range of 128-bit IPv6 addresses to be matched, on data packets
sent from a corresponding node to the mobile node as seen by the sent from a corresponding node to the mobile node as seen by the
home agent. In other words this is one of the registered home home agent. In other words, this is one of the registered home
addresses of the mobile node. addresses of the mobile node.
(D)End Destination Address (D)End Destination Address
If more than one contiguous destination address needs to be If more than one contiguous destination address needs to be
matched then this field can be used to indicate the end value of a matched, then this field can be used to indicate the end value of
range starting from the value of the Start Destination Address a range starting from the value of the Start Destination Address
field. This field MUST NOT be included unless the Start field. This field MUST NOT be included unless the Start
Destination Address field is included. When this field is Destination Address field is included. When this field is
included the receiver will match all of the addresses between included, the receiver will match all of the addresses between
fields (C) and (D), inclusive of (C) and (D). fields (C) and (D), inclusive of (C) and (D).
(E)Start IPsec SPI - Security Parameter Index (E)Start IPsec SPI - Security Parameter Index
This field identifies the first 32-bit IPsec SPI value, from the This field identifies the first 32-bit IPsec SPI value, from the
range of SPI values to be matched, on data packets sent from a range of SPI values to be matched, on data packets sent from a
corresponding node to the mobile node as seen by the home agent. corresponding node to the mobile node as seen by the home agent.
This field is defined in [RFC4303]. This field is defined in [RFC4303].
(F)End IPsec SPI - Security Parameter Index (F)End IPsec SPI - Security Parameter Index
If more than one contiguous SPI values need to be matched then
If more than one contiguous SPI value needs to be matched, then
this field can be used to indicate the end value of a range this field can be used to indicate the end value of a range
starting from the value of the Start IPsec SPI field. This field starting from the value of the Start IPsec SPI field. This field
MUST NOT be included unless the Start IPsec SPI field is included. MUST NOT be included unless the Start IPsec SPI field is included.
When this field is included the receiver will match all of the SPI When this field is included, the receiver will match all of the
values between fields (E) and (F), inclusive of (E) and (F). SPI values between fields (E) and (F), inclusive of (E) and (F).
(G)Start Flow Label (G)Start Flow Label
This field identifies the first flow label value, from the range This field identifies the first flow label value, from the range
of flow label values to be matched, on data packets sent from a of flow label values to be matched, on data packets sent from a
corresponding node to the mobile node as seen by the home agent. corresponding node to the mobile node as seen by the home agent.
According to [RFC2460] the flow label is 20-bits long. For the According to [RFC2460], the flow label is 24 bits long. For the
purpose of this specification the sender of this option MUST purpose of this specification, the sender of this option MUST
prefix the flow label value with 12-bits of "0" before inserting prefix the flow label value with 8 bits of "0" before inserting it
it in the (G)Start Flow Label field. The receiver SHOULD ignore in the (G)Start Flow Label field. The receiver SHOULD ignore the
the first 12-bits of this field before using it for comparisons first 8 bits of this field before using it in comparisons with
with flow labels in packets. flow labels in packets.
(H)End Flow Label (H)End Flow Label
If more than one contiguous flow label values need to be matched If more than one contiguous flow label value needs to be matched,
then this field can be used to indicate the end value of a range then this field can be used to indicate the end value of a range
starting from the value of the Start Flow Label field. This field starting from the value of the Start Flow Label field. This field
MUST NOT be included unless the Start Flow Label field is MUST NOT be included unless the Start Flow Label field is
included. When this field is included the receiver will match all included. When this field is included, the receiver will match
of the flow label values between fields (G) and (H), inclusive of all of the flow label values between fields (G) and (H), inclusive
(G) and (H). When this field is included, it MUST be coded the of (G) and (H). When this field is included, it MUST be coded the
same way as defined for (G). same way as defined for (G).
(I)Start Source Port (I)Start Source Port
This field identifies the first 16-bit source port number, from This field identifies the first 16-bit source port number, from
the range of port numbers to be matched, on data packets sent from the range of port numbers to be matched, on data packets sent from
a corresponding node to the mobile node as seen by the home agent. a corresponding node to the mobile node as seen by the home agent.
(J)End Source Port (J)End Source Port
If more than one contiguous source port numbers need to be matched If more than one contiguous source port number needs to be
then this field can be used to indicate the end value of a range matched, then this field can be used to indicate the end value of
starting from the value of the Start Source Port field. This a range starting from the value of the Start Source Port field.
field MUST NOT be included unless the Start Source Port field is This field MUST NOT be included unless the Start Source Port field
included. When this field is included the receiver will match all is included. When this field is included, the receiver will match
of the port numbers between fields (I) and (J), inclusive of (I) all of the port numbers between fields (I) and (J), inclusive of
and (J). (I) and (J).
(K)Start Destination Port (K)Start Destination Port
This field identifies the first 16-bit destination port number, This field identifies the first 16-bit destination port number,
from the range of port numbers to be matched, on data packets sent from the range of port numbers to be matched, on data packets sent
from a corresponding node to the mobile node as seen by the home from a corresponding node to the mobile node as seen by the home
agent. agent.
(L)End Destination Port (L)End Destination Port
If more than one contiguous destination port numbers need to be If more than one contiguous destination port number needs to be
matched then this field can be used to indicate the end value of a matched, then this field can be used to indicate the end value of
range starting from the value of the Start Destination Port field. a range starting from the value of the Start Destination Port
This field MUST NOT be included unless the Start Destination Port field. This field MUST NOT be included unless the Start
field is included. When this field is included the receiver will Destination Port field is included. When this field is included,
match all of the port numbers between fields (K) and (L), the receiver will match all of the port numbers between fields (K)
inclusive of (K) and (L). and (L), inclusive of (K) and (L).
(M)Start TC - Traffic Class (M)Start TC - Traffic Class
This field identifies the first traffic class value, from the This field identifies the first traffic class value, from the
range of traffic class values to be matched, on data packets sent range of traffic class values to be matched, on data packets sent
from a corresponding node to the mobile node as seen by the home from a corresponding node to the mobile node as seen by the home
agent. This field is equivalent to the Start DS field in the IPv4 agent. This field is equivalent to the Start DS field in the IPv4
traffic selector in Figure 1. As per [RFC3260], the field is traffic selector in Figure 1. As per [RFC3260], the field is
defined as 6 bits DS field and 2 bits reserved, later claimed by defined as a 6-bit DS field with 2 bits reserved, later claimed by
Explicit Congestion Notification (ECN) [RFC3168]. For the purpose Explicit Congestion Notification (ECN) [RFC3168]. For the purpose
of this specification the (M)Start TC field is 8 bits long, where of this specification, the (M)Start TC field is 8 bits long, where
the 6 most significant bits indicating the DS field to be matched the 6 most significant bits indicate the DS field to be matched
and the 2 least significant bit's value MUST be and the 2 least significant bits' values MUST be ignored in any
comparison.
(N)End TC - Traffic Class (N)End TC - Traffic Class
If more than one contiguous TC values need to be matched then this If more than one contiguous TC value needs to be matched, then
field can be used to indicate the end value of a range starting this field can be used to indicate the end value of a range
from the value of the Start TC field. This field MUST NOT be starting from the value of the Start TC field. This field MUST
included unless the Start TC field is included. When this field NOT be included unless the Start TC field is included. When this
is included, it MUST be coded the same way as defined for (M). field is included, it MUST be coded the same way as defined for
When this field is included the receiver will match all of the (M). When this field is included, the receiver will match all of
values between fields (M) and (N), inclusive of (M) and (N). the values between fields (M) and (N), inclusive of (M) and (N).
(O)Start NH - Next Header (O)Start NH - Next Header
This field identifies the first 8-bit next header value, from the This field identifies the first 8-bit next header value, from the
range of next header values to be matched, on data packets sent range of next header values to be matched, on data packets sent
from a corresponding node to the mobile node as seen by the home from a corresponding node to the mobile node as seen by the home
agent. agent.
(P)End NH - Next Header (P)End NH - Next Header
If more than one contiguous next header values need to be matched
If more than one contiguous next header value needs to be matched,
then this field can be used to indicate the end value of a range then this field can be used to indicate the end value of a range
starting from the value of the Start NH field. This field MUST starting from the value of the Start NH field. This field MUST
NOT be included unless the Start next header field is included. NOT be included unless the Start next header field is included.
When this field is included the receiver will match all of the When this field is included, the receiver will match all of the
values between fields (O) and (P), inclusive of (O) and (P). values between fields (O) and (P), inclusive of (O) and (P).
Reserved Reserved
Reserved for future use. These bits MUST be set to zero by the Reserved for future use. These bits MUST be set to zero by the
sender and ignored by the receiver. sender and ignored by the receiver.
4. Security Considerations 4. Security Considerations
This draft defines the format of the traffic selector field of a sub- This document defines the format of the traffic selector field of a
option defined for flow bindings [I-D.ietf-mext-flow-binding]. The sub-option defined for flow bindings [RFC6089]. The authors have not
authors have not identified any security concerns pertaining to this identified any security concerns pertaining to this document beyond
draft beyond what is already identified in what is already identified in [RFC6089].
[I-D.ietf-mext-flow-binding].
5. IANA Considerations 5. IANA Considerations
1) New TS format values from the "Traffic Selector Format" namespace The following new TS format values have been assigned from the
for the Traffic Selector sub-option defined in "Traffic Selector Format" namespace for the traffic selector sub-
[I-D.ietf-mext-flow-binding]. The following values are requested: option defined in [RFC6089].
1 IPv4 Binary Traffic Selector 1 IPv4 Binary Traffic Selector
2 IPv6 Binary Traffic Selector 2 IPv6 Binary Traffic Selector
6. Aknowledgements 6. Acknowledgements
The authors would like to thank Patrick Stupar and Julien Laganier The authors would like to thank Patrick Stupar and Julien Laganier
for their contributions to this document. We would also like to for their contributions to this document. We would also like to
thank Benjamin Lim, Dave Craig, Patrick Stupar, and Basavaraj Patil thank Benjamin Lim, Dave Craig, Patrick Stupar, and Basavaraj Patil
for their reviews and comments. for their reviews and comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-mext-flow-binding]
Tsirtsis, G., Soliman, H., Montavont, N., Giaretta, G.,
and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and NEMO
Basic Support", draft-ietf-mext-flow-binding-10 (work in
progress), September 2010.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, September 1981. RFC 793, September 1981.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 18, line 37 skipping to change at page 12, line 31
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
of Explicit Congestion Notification (ECN) to IP", of Explicit Congestion Notification (ECN) to IP",
RFC 3168, September 2001. RFC 3168, September 2001.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005. RFC 4303, December 2005.
[RFC6089] Tsirtsis, G., Soliman, H., Montavont, N., Giaretta, G.,
and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and
Network Mobility (NEMO) Basic Support", RFC 6089,
January 2011.
7.2. Informative References 7.2. Informative References
[RFC3260] Grossman, D., "New Terminology and Clarifications for [RFC3260] Grossman, D., "New Terminology and Clarifications for
Diffserv", RFC 3260, April 2002. Diffserv", RFC 3260, April 2002.
Authors' Addresses Authors' Addresses
George Tsirtsis George Tsirtsis
Qualcomm Qualcomm
Email: tsirtsis@qualcomm.com EMail: tsirtsis@qualcomm.com
Gerardo Giarreta Gerardo Giaretta
Qualcomm Qualcomm
Email: gerardog@qualcomm.com EMail: gerardog@qualcomm.com
Hesham Soliman Hesham Soliman
Elevate Technologies Elevate Technologies
Email: hesham@elevatemobile.com EMail: hesham@elevatemobile.com
Nicolas Montavont Nicolas Montavont
Institut Telecom / Telecom Bretagne Institut Telecom / Telecom Bretagne
2, rue de la chataigneraie 2, rue de la chataigneraie
Cesson Sevigne 35576 Cesson Sevigne 35576
France France
Phone: (+33) 2 99 12 70 23 Phone: (+33) 2 99 12 70 23
Email: nicolas.montavont@telecom-bretagne.eu EMail: nicolas.montavont@telecom-bretagne.eu
URI: http://www.rennes.enst-bretagne.fr/~nmontavo// URI: http://www.rennes.enst-bretagne.fr/~nmontavo//
 End of changes. 65 change blocks. 
235 lines changed or deleted 234 lines changed or added

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