draft-ietf-mext-binary-ts-00.txt   draft-ietf-mext-binary-ts-01.txt 
Network Working Group G. Tsirtsis Network Working Group G. Tsirtsis
Internet-Draft G. Giarreta Internet-Draft G. Giarreta
Intended status: Standards Track Qualcomm Intended status: Standards Track Qualcomm
Expires: January 30, 2010 H. Soliman Expires: May 13, 2010 H. Soliman
Elevate Technologies Elevate Technologies
N. Montavont N. Montavont
IT/TB IT/TB
July 29, 2009 November 9, 2009
Binary Traffic Selectors for FB Traffic Selectors for Flow Bindings
draft-ietf-mext-binary-ts-00.txt draft-ietf-mext-binary-ts-01.txt
Abstract
This document defines binary formats for IPv4 and IPv6 traffic
selectors to be used in conjuction with flow bindings for Mobile
IPv6.
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 36 skipping to change at page 1, line 42
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 January 30, 2010. This Internet-Draft will expire on May 13, 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
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This document defines binary format for IPv4 and IPv6 traffic described in the BSD License.
selectors to be used in conjuction with flow bindings for Mobile
IPv6.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 5 3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 5
3.1. IPv4 binary traffic selector . . . . . . . . . . . . . . . 5 3.1. IPv4 binary traffic selector . . . . . . . . . . . . . . . 5
3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 7 3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 8
4. Flow Identification Status codes . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
7. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 7.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15 7.2. Informative References . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
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
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 [I-D.ietf-mext-flow-binding].
The binary traffic selector sub-options defined here, allow efficient The binary traffic selector sub-options defined here, allow efficient
identification of flow(s) based on well known fields in IPv4, IPv6, identification of flow(s) based on well known fields in IPv4
and transport layer headers. [RFC0791], IPv6 [RFC2460], and transport layer headers like TCP
[RFC0793] and UDP [RFC0768].
3. Traffic Selector Sub-Options 3. Traffic Selector Sub-Options
[I-D.ietf-mext-flow-binding] defines the format for the traffic [I-D.ietf-mext-flow-binding] defines the format for the traffic
selector sub-option. selector sub-option.
The following values of the sub-option Type field, are reserved in The following values of the TS Format field, are defined in this
this specification for binary traffic selectors specification for binary traffic selectors.
TS Format:
TBD IPv4 binary traffic selector TBD IPv4 binary traffic selector
TBD IPv6 binary traffic selector TBD IPv6 binary traffic selector
3.1. IPv4 binary traffic selector 3.1. IPv4 binary traffic selector
If the Type field of the traffic selector sub-option indicates "IPv4 If the TS Format field of the traffic selector sub-option indicates
binary traffic selector", then the traffic selector is formatted as "IPv4 binary traffic selector", then the traffic selector is
follows: formatted as 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|B|C|D|E|F|G|H|I|K|L| Resvd | (A)DS | (B)Protocol | |Sub-opt Type | Sub-Opt Len | TS Format | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (C)Source Address | |A|B|C|D|E|F|G|H|I|J|K|L|M|N| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (D)Destination Address | | (A)Start Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|(E)S. PrefLeng |(F)D. PrefLeng | (G)Source port - Low | | (B)End Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (H)Source port - High | (I)Dst port - Low | | (C)Start Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (K)Dst port - High | (L)SPI | | (D)End Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (L)SPI | | (E)Start SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (F)End SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (G)Start Source port | (H)End Source port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (I)Start Destination port | (J)End Destination port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (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-L) 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)DS - Differential Services (A)Start Source Address
The Differential Services (DS) field in the data packet as seen by This field identifies the first source address, from the range of
the home agent. Note that this is called Type of Service field in 32-bit IPv4 addresses to be matched, on data packets as seen by
[RFC0791]. [RFC3260] then clarified that the field has been the home agent. In other words this is one of the addresses of
redefined as 6 bits DS field and 2 bits reserved, later claimed by the correspondent node.
Explicit Congestion Notification (ECN) [RFC3168]. For the purpose
of this specification the DS field is 8bit long, were the 6 most
significant bits indicating the DS field to be matched and the 2
list significant bits MUST be set to 0 by the sender and ignored
by the receiver.
(B)Protocol (B)End Source Address
An 8-bit unsigned integer representing the value of the transport If more than one contiguous source addresses need to be mached
protocol number associated with the port numbers in data packets. 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
field MUST NOT be included unless the Start Source Address field
is included. When this field is included the receiver will match
all of the addresses between fields (A) and (B), inclusive of (A)
and (B).
(C)Source Address (C)Start Destination Address
This field identifies the source address of data packets as seen This field identifies the first destination address, from the
by the home agent that is, the 32-bit IPv4 address of the range of 32-bit IPv4 addresses to be matched, on data packets as
correspondent node. seen by the home agent. In other words this is one of the
registered addresses of the mobile node.
(D)Destination Address (D)End Destination Address
This field identifies the destination address of data packets as If more than one contiguous destination addresses need to be
seen by the home agent. When included this field must one of the mached then this field can be used to indicate the end value of a
registered home addresses of the mobile node. It is a 32-bit IPv4 range starting from the value of the Start Destination Address
address. field. This field MUST NOT be included unless the Start
Destination Address field is included. When this field is
included the receiver will match all of the addresses between
fields (C) and (D), inclusive of (C) and (D).
(E)Source Prefix Length (E)Start SPI - Security Parameter Index
This field includes the prefix length for the source address. This field identifies the first 32-bit SPI value, from the range
This field can only be included if the Source Address field is of SPI values to be matched, on data packets as seen by the home
agent. This field is defined in [RFC4303]
(F)End SPI - Security Parameter Index
If more than one contiguous SPI values need to be mached then this
field can be used to indicate the end value of a range starting
from the value of the Start SPI field. This field MUST NOT be
included unless the Start SPI field is included. When this field
is included the receiver will match all of the SPI values between
fields (E) and (F), inclusive of (E) and (F).
(G)Start Source Port
This field identifies the first 16-bit source port number, from
the range of port numbers to be matched, on data packets as seen
by the home agent.
(H)End Source Port
If more than one contiguous source port numbers need to be mached
then this field can be used to indicate the end value of a range
starting from the value of the Start Source Port field. This
field MUST NOT be included unless the Start Source Port field is
included. When this field is included the receiver will match all included. When this field is included the receiver will match all
of the addresses in the subnet identified by this field. of the port numbers between fields (G) and (H), inclusive of (G)
and (H).
(F)Destination Prefix Length (I)Start Destination Port
This field includes the prefix length for the destination address. This field identifies the first 16-bit destination port number,
If The Destination Address field is included then it refers to from the range of port numbers to be matched, on data packets as
that field. When this field is included the receiver will match seen by the home agent.
all of the addresses in the subnet identified by this field.
(G)Source Port - Low (J)End Destination Port
This field identifies the lowest source port number within a range If more than one contiguous destination port numbers need to be
of port numbers that will be used in data packets, as seen by the mached then this field can be used to indicate the end value of a
home agent. range starting from the value of the Start Destination Port field.
This field MUST NOT be included unless the Start Destination Port
field is included. When this field is included the receiver will
match all of the port numbers between fields (I) and (K),
inclusive of (I) and (J).
(H)Source Port - High (K)Start DS - Differential Services
This field identifies the highest source port number within a
range of port numbers that will be used in data packets, as seen
by the home agent. This field MUST NOT be included if the Source
Port - Low field is not includede. If a single port is indicated
then this field MUST NOT be included. When it is included it MUST
be set to the value larger than that of Source Port - Low field.
(I)Destination Port - Low This field identifies the first differential services value, from
the range of differential services values to be matched, on data
packets as seen by the home agent. Note that this field is called
Type of Service field in [RFC0791]. [RFC3260] then clarified that
the field has been redefined as 6 bits DS field and 2 bits
reserved, later claimed by Explicit Congestion Notification (ECN)
[RFC3168]. For the purpose of this specification the DS field is
8bit long, were the 6 most significant bits indicating the DS
field to be matched and the 2 list significant bits MUST be set to
0 by the sender and ignored by the receiver.
This field identifies the lowest destination port number within a (L)End DS - Differential Services
range of port numbers that will be used in data packets as seen by
the home agent.
(K)Destination Port - High If more than one contiguous DS values need to be mached then this
field can be used to indicate the end value of a range starting
from the value of the Start DS field. This field MUST NOT be
included unless the Start DS field is included. When this field
is included the receiver will match all of the values between
fields (K) and (L), inclusive of (K) and (L).
This field identifies the highest destination port number within a (M)Start Protocol
range of port numbers that will be used in data packets, as seen
by the home agent. This field MUST NOT be included if the
Destination Port - Low field is not includede. If a single port
is indicated then this field MUST NOT be included. When it is
included it MUST be set to the value larger than that of
Destination Port - Low field.
(L)SPI - Security Parameter Index This field identifies the first 8-bit protocol value, from the
range of protocol values to be matched, on data packets as seen by
the home agent.
The SPI field in the data packet as seen by the home agent. (N)End Protocol
Resved If more than one contiguous protocol values need to be mached 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
MUST NOT be included unless the Start Protocol field is included.
When this field is included the receiver will match all of the
values between fields (M) and (N), inclusive of (M) and (N).
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 Type field of the traffic selector sub-option indicates "IPv6 If the TS Format field of the traffic selector sub-option indicates
binary traffic selector", then the traffic selector is formatted as "IPv6 binary traffic selector", then the traffic selector is
follows: formatted as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|B|C|D|E|F|G|H|I|K|L|M| Resvd | (A)DS | (B)Protocol | |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 |
+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ (C)Source Address + + +
| | | |
+ + + (A)Start Source Address +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +
| | | |
+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ (D)Destination Address + + +
| | | |
+ + + (B)End Source Address +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +
|(E)S. PrefLeng |(F)D. PrefLeng | (G)Source port - Low | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (H)Source port - High | (I)Dst port - Low | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +
| (K)Dst port - High | (L)SPI | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + (C)Start Destination Address +
| (L)SPI | (M)Flow Label | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +
| (M)Flow Label | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ (D)End Destination Address +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (E)Start SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (F)End SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (G)Start Flow Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (H)End Flow Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (I)Start Source port | (J)End Source port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (K)Start Destination port | (L)End Destination port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (M)Start DS | (N)End DS | (O)Start NH | (P) End NH |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: IPv6 binary traffic selector Figure 2: IPv6 binary traffic selector
Flags (A-M) 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) DS - Differential Services (A)Start Source Address
The Differential Services (DS) field in the data packet as seen by This field identifies the first source address, from the range of
the home agent. Note that this is called Traffic Class field in 128-bit IPv6 addresses to be matched, on data packets as seen by
[RFC2460]. [RFC3260] then clarified that the field has been the home agent. In other words this is one of the addresses of
redefined as 6 bits DS field and 2 bits reserved, later claimed by the correspondent node.
Explicit Congestion Notification (ECN) in [RFC3168]. For the
purpose of this specification the DS field is 8bit long, were the
6 most significant bits indicating the DS field to be matched and
the 2 list significant bits MUST be set to 0 by the sender and
ignored by the receiver.
(B)Protocol (B)End Source Address
An 8-bit unsigned integer representing value of the transport If more than one contiguous source addresses need to be mached
protocol number associated with the port numbers in data packets. 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
field MUST NOT be included unless the Start Source Address field
is included. When this field is included the receiver will match
all of the addresses between fields (A) and (B), inclusive of (A)
and (B).
(C)Source Address (C)Start Destination Address
This field identifies the source address of data packets as seen This field identifies the first destination address, from the
by the home agent. That is, the address of the correspondent node range of 128-bit IPv6 addresses to be matched, on data packets as
and it is a 128-bit IPv6 address. seen by the home agent. In other words this is one of the
registered addresses of the mobile node.
(D)Destination Address (D)End Destination Address
This field identifies the destination address of the data packet If more than one contiguous destination addresses need to be
as seen by the home agent. When included this field must be set mached then this field can be used to indicate the end value of a
to either one of the registered home addresses of the mobile node range starting from the value of the Start Destination Address
or to an address that falls under one of the mobile's home network field. This field MUST NOT be included unless the Start
prefixes. The value of this fild is 128-bit IPv6 address. Destination Address field is included. When this field is
included the receiver will match all of the addresses between
fields (C) and (D), inclusive of (C) and (D).
(E)Source Prefix Length (E)Start SPI - Security Parameter Index
This field includes the prefix for the source address. This field This field identifies the first 32-bit SPI value, from the range
MUST NOT be included if the Source Address field is not included. of SPI values to be matched, on data packets as seen by the home
When this field is included the receiver will match all of the agent.
addresses in the subnet identified by this field.
(F)Destination Prefix Length (F)End SPI - Security Parameter Index
This field includes the prefix for the destination address. This If more than one contiguous SPI values need to be mached then this
field MUST NOT be included if the Source Address field is not field can be used to indicate the end value of a range starting
from the value of the Start SPI field. This field MUST NOT be
included unless the Start SPI field is included. When this field
is included the receiver will match all of the SPI values between
fields (E) and (F), inclusive of (E) and (F).
(G)Start Flow Label
This field identifies the first flow label value, from the range
of flow label values to be matched, on data packets as seen by the
home agent. According to [RFC2460] the flow label is 24-bit long.
For the purpose of this specification the sender of this options
MUST prefix flow label values with 8-bits of "0" before inserting
it in this field. The receive SHOULD ignore the first 8-bits of
this field.
(H)End Flow Label
If more than one contiguous flow label values need to be mached
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
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 all
of the addresses in the subnet identified by this field. of the flow label values between fields (G) and (H), inclusive of
(G) and (H).
(G)Source Port - Low (I)Start Source Port
This field identifies the lowest source port number within a range This field identifies the first 16-bit source port number, from
of port numbers that will be used in data packets, as seen by the the range of port numbers to be matched, on data packets as seen
home agent. by the home agent.
(H)Source Port - High (J)End Source Port
This field identifies the highest source port number within a If more than one contiguous source port numbers need to be mached
range of port numbers that will be used in data packets, as seen then this field can be used to indicate the end value of a range
by the home agent. This field MUST NOT be included if the Source starting from the value of the Start Source Port field. This
Port - Low field is not includede. If a single port is indicated field MUST NOT be included unless the Start Source Port field is
then this field MUST NOT be included. When it is included it MUST included. When this field is included the receiver will match all
be set to the value larger than that of Source Port - Low field. of the port numbers between fields (I) and (J), inclusive of (I)
and (J).
(I)Destination Port - Low (K)Start Destination Port
This field identifies the lowest destination port number within a This field identifies the first 16-bit destination port number,
range of port numbers that will be used in data packets as seen by from the range of port numbers to be matched, on data packets as
the home agent. seen by the home agent.
(K)Destination Port - High (L)End Destination Port
If more than one contiguous destination port numbers need to be
mached then this field can be used to indicate the end value of a
range starting from the value of the Start Destination Port field.
This field MUST NOT be included unless the Start Destination Port
field is included. When this field is included the receiver will
match all of the port numbers between fields (K) and (L),
inclusive of (K) and (L).
This field identifies the highest destination port number within a (M)Start DS - Differential Services
range of port numbers that will be used in data packets, as seen
by the home agent. This field MUST NOT be included if the
Destination Port - Low field is not includede. If a single port
is indicated then this field MUST NOT be included. When it is
included it MUST be set to the value larger than that of
Destination Port - Low field.
(L)SPI - Security Parameter Index This field identifies the first differential services value, from
the range of differential services values to be matched, on data
packets as seen by the home agent. Note that this field is called
Type of Service field in [RFC0791]. [RFC3260] then clarified that
the field has been redefined as 6 bits DS field and 2 bits
reserved, later claimed by Explicit Congestion Notification (ECN)
[RFC3168]. For the purpose of this specification the DS field is
8bit long, were the 6 most significant bits indicating the DS
field to be matched and the 2 list significant bits MUST be set to
0 by the sender and ignored by the receiver.
The SPI field in the data packet as seen by the home agent. (N)End DS - Differential Services
(M)Flow Label If more than one contiguous DS values need to be mached then this
field can be used to indicate the end value of a range starting
from the value of the Start DS field. This field MUST NOT be
included unless the Start DS field is included. When this field
is included the receiver will match all of the values between
fields (M) and (N), inclusive of (M) and (N).
The Flow Label field in the data packet as seen by the home agent. (O)Start NH - Next Header
Resved This field identifies the first 8-bit next header value, from the
range of next header values to be matched, on data packets as seen
by the home agent.
Reserved for future use. (P)End NH - Next Header
4. Flow Identification Status codes If more than one contiguous next header values need to be mached
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
NOT be included unless the Start next header field is included.
When this field is included the receiver will match all of the
values between fields (O) and (P), inclusive of (O) and (P).
TBD Reserved
Reserved for future use. These bits MUST be set to zero by the
sender and ignored by the receiver.
5. Security Considerations 4. Security Considerations
This draft defines the format of traffic selector sub-options defined This draft defines the format of traffic selector sub-options defined
in the flow bindings [I-D.ietf-mext-flow-binding]. The authors have in the flow bindings [I-D.ietf-mext-flow-binding]. The authors have
not identified any security concenrs pertaining to this draft beyond not identified any security concenrs pertaining to this draft beyond
what is already identified in [I-D.ietf-mext-flow-binding]. what is already identified in [I-D.ietf-mext-flow-binding].
6. IANA Considerations 5. IANA Considerations
TBD 1) New TS format values from the "Traffic Selector Format" namespace
for the Traffic Selector sub-option defined in
[I-D.ietf-mext-flow-binding]. Values are requested for the
following:
7. Aknowledgements IPv4 Binary Traffic Selector
TBD IPv6 Binary Traffic Selector
8. References 6. Aknowledgements
8.1. Normative References The authors would like to thank Patrick Stupar and Julien Laganier
for their contributions to this document.
7. References
7.1. Normative References
[I-D.ietf-mext-flow-binding] [I-D.ietf-mext-flow-binding]
Soliman, H., Montavont, N., and K. Kuladinithi, "Flow Soliman, H., Montavont, N., and K. Kuladinithi, "Flow
Bindings in Mobile IPv6 and NEMO Basic Support", Bindings in Mobile IPv6 and NEMO Basic Support",
draft-ietf-mext-flow-binding-03 (work in progress), draft-ietf-mext-flow-binding-03 (work in progress),
July 2009. July 2009.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
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,
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
8.2. Informative References [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005.
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@gmail.com Email: tsirtsis@gmail.com
 End of changes. 76 change blocks. 
213 lines changed or deleted 353 lines changed or added

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