draft-ietf-mext-binary-ts-02.txt   draft-ietf-mext-binary-ts-03.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: June 19, 2010 H. Soliman Expires: August 13, 2010 H. Soliman
Elevate Technologies Elevate Technologies
N. Montavont N. Montavont
IT/TB IT/TB
December 16, 2009 February 9, 2010
Traffic Selectors for Flow Bindings Traffic Selectors for Flow Bindings
draft-ietf-mext-binary-ts-02.txt draft-ietf-mext-binary-ts-03.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 to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
skipping to change at page 1, line 42 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 June 19, 2010. This Internet-Draft will expire on August 13, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
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 BSD License. described in the BSD License.
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 . . . . . . . . . . . . . . . 9 3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 6. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . . 17 7.1. Normative References . . . . . . . . . . . . . . . . . . . 18
7.2. Informative References . . . . . . . . . . . . . . . . . . 17 7.2. Informative References . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
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
skipping to change at page 5, line 31 skipping to change at page 5, line 31
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, N is sett n if K, L, M, N 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| 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 |
skipping to change at page 6, line 40 skipping to change at page 6, line 40
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 as seen by 32-bit IPv4 addresses to be matched, on data packets sent from a
the home agent. In other words this is one of the addresses of corresponding node to the mobile node as seen by the home agent.
the correspondent node. In other words this is one of the addresses of the correspondent
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 as range of 32-bit IPv4 addresses to be matched, on data packets sent
seen by the home agent. In other words this is one of the from a corresponding node to the mobile node as seen by the home
registered home addresses of the mobile node. agent. In other words this is one of the registered home
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 a
range starting from the value of the Start Destination Address 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 SPI - Security Parameter Index (E)Start SPI - Security Parameter Index
This field identifies the first 32-bit SPI value, from the range This field identifies the first 32-bit SPI value, from the range
of SPI values to be matched, on data packets as seen by the home of SPI values to be matched, on data packets sent from a
agent. This field is defined in [RFC4303]. corresponding node to the mobile node as seen by the home agent.
This field is defined in [RFC4303].
(F)End SPI - Security Parameter Index (F)End SPI - Security Parameter Index
If more than one contiguous SPI values need to be matched then If more than one contiguous SPI values need 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 SPI field. This field MUST starting from the value of the Start SPI field. This field MUST
NOT be included unless the Start SPI field is included. When this NOT be included unless the Start SPI field is included. When this
field is included the receiver will match all of the SPI values field is included the receiver will match all of the SPI values
between fields (E) and (F), inclusive of (E) and (F). 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 as seen the range of port numbers to be matched, on data packets sent from
by the home agent. This is from the range of port numbers defined a corresponding node to the mobile node as seen by the home agent.
by IANA (http://www.iana.org/assignments/port-numbers) This is from the range of port numbers defined by IANA
(http://www.iana.org/assignments/port-numbers)
(H)End Source Port (H)End Source Port
If more than one contiguous source port numbers need to be matched 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 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 starting from the value of the Start Source Port field. This
field MUST NOT be included unless the Start Source Port field is 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 port numbers between fields (G) and (H), inclusive of (G) of the port numbers between fields (G) and (H), inclusive of (G)
and (H). and (H).
(I)Start Destination Port (I)Start Destination Port
skipping to change at page 8, line 10 skipping to change at page 8, line 15
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 Port field. This starting from the value of the Start Source Port field. This
field MUST NOT be included unless the Start Source Port field is 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 port numbers between fields (G) and (H), inclusive of (G) of the port numbers between fields (G) and (H), inclusive of (G)
and (H). 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 as from the range of port numbers to be matched, on data packets sent
seen by the home agent. from a corresponding node to the mobile node as seen by the home
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 numbers need 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 a
range starting from the value of the Start Destination Port field. range starting from the value of the Start Destination Port field.
This field MUST NOT be included unless the Start Destination Port This field MUST NOT be included unless the Start Destination Port
field is included. When this field is included the receiver will field is included. When this field is included the receiver will
match all of the port numbers between fields (I) and (J), match all of the port numbers between fields (I) and (J),
inclusive of (I) 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 as seen by the home agent. Note that this field is called packets sent from a corresponding node to the mobile node as seen
Type of Service field in [RFC0791]. [RFC3260] then clarified that by the home agent. Note that this field is called Type of Service
the field has been redefined as 6 bits DS field and 2 bits field in [RFC0791]. [RFC3260] then clarified that the field has
reserved, later claimed by Explicit Congestion Notification (ECN) been redefined as 6 bits DS field and 2 bits reserved, later
[RFC3168]. For the purpose of this specification the DS field is claimed by Explicit Congestion Notification (ECN) [RFC3168]. For
8 bits long, were the 6 most significant bits indicating the DS the purpose of this specification the DS field is 8 bits long,
field to be matched and the 2 least significant bits MUST be set were the 6 most significant bits indicating the DS field to be
to 0 by the sender and ignored by the receiver. matched and the 2 least significant bits MUST be set to 0 by the
sender and ignored by the receiver.
(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 values need to be matched then this
field can be used to indicate the end value of a range starting 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 from the value of the Start DS field. This field MUST NOT be
included unless the Start DS field is included. When this field included unless the Start DS field is included. When this field
is included, it MUST be coded the same way as defined for (K). is included, it MUST be coded the same way as defined for (K).
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 (K) and (L), inclusive of (K) and (L). 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 as seen by range of protocol values to be matched, on data packets sent from
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 values need 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).
skipping to change at page 10, line 45 skipping to change at page 11, line 4
| (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 DS | (N)End DS | (O)Start NH | (P) End NH | | (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-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 as seen by 128-bit IPv6 addresses to be matched, on data packets sent from a
the home agent. In other words this is one of the addresses of corresponding node to the mobile node as seen by the home agent.
the correspondent node. In other words this is one of the addresses of the correspondent
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 as range of 128-bit IPv6 addresses to be matched, on data packets
seen by the home agent. In other words this is one of the sent from a corresponding node to the mobile node as seen by the
registered home addresses of the mobile node. home agent. In other words this is one of the registered home
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 a
range starting from the value of the Start Destination Address 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 SPI - Security Parameter Index (E)Start SPI - Security Parameter Index
This field identifies the first 32-bit SPI value, from the range This field identifies the first 32-bit SPI value, from the range
of SPI values to be matched, on data packets as seen by the home of SPI values to be matched, on data packets sent from a
agent. This field is defined in [RFC4303]. corresponding node to the mobile node as seen by the home agent.
This field is defined in [RFC4303].
(F)End SPI - Security Parameter Index (F)End SPI - Security Parameter Index
If more than one contiguous SPI values need to be matched then If more than one contiguous SPI values need 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 SPI field. This field MUST starting from the value of the Start SPI field. This field MUST
NOT be included unless the Start SPI field is included. When this NOT be included unless the Start SPI field is included. When this
field is included the receiver will match all of the SPI values field is included the receiver will match all of the SPI values
between fields (E) and (F), inclusive of (E) and (F). 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 as seen by the of flow label values to be matched, on data packets sent from a
home agent. According to [RFC2460] the flow label is 24-bit long. corresponding node to the mobile node as seen by the home agent.
For the purpose of this specification the sender of this option According to [RFC2460] the flow label is 24-bit long. For the
MUST prefix the flow label value with 8-bits of "0" before purpose of this specification the sender of this option MUST
inserting it in this field. The receiver SHOULD ignore the first prefix the flow label value with 8-bits of "0" before inserting it
8-bits of this field. in this field. The receiver SHOULD ignore the first 8-bits of
this field.
(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 values need 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 all
of the flow label values between fields (G) and (H), inclusive of of the flow label values between fields (G) and (H), inclusive of
(G) and (H). (G) and (H).
(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 as seen the range of port numbers to be matched, on data packets sent from
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 numbers need 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 Port field. This starting from the value of the Start Source Port field. This
field MUST NOT be included unless the Start Source Port field is 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 port numbers between fields (I) and (J), inclusive of (I) of the port numbers between fields (I) and (J), inclusive of (I)
and (J). and (J).
skipping to change at page 12, line 39 skipping to change at page 13, line 4
If more than one contiguous source port numbers need to be matched 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 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 starting from the value of the Start Source Port field. This
field MUST NOT be included unless the Start Source Port field is 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 port numbers between fields (I) and (J), inclusive of (I) of the port numbers between fields (I) and (J), inclusive of (I)
and (J). 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 as from the range of port numbers to be matched, on data packets sent
seen by the home agent. from a corresponding node to the mobile node as seen by the home
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 numbers need 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 a
range starting from the value of the Start Destination Port field. range starting from the value of the Start Destination Port field.
This field MUST NOT be included unless the Start Destination Port This field MUST NOT be included unless the Start Destination Port
field is included. When this field is included the receiver will field is included. When this field is included the receiver will
match all of the port numbers between fields (K) and (L), match all of the port numbers between fields (K) and (L),
inclusive of (K) and (L). inclusive of (K) and (L).
(M)Start DS - Differential Services (M)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 as seen by the home agent. Note that this field is called packets sent from a corresponding node to the mobile node as seen
Type of Service field in [RFC0791]. [RFC3260] then clarified that by the home agent. Note that this field is called Type of Service
the field has been redefined as 6 bits DS field and 2 bits field in [RFC0791]. [RFC3260] then clarified that the field has
reserved, later claimed by Explicit Congestion Notification (ECN) been redefined as 6 bits DS field and 2 bits reserved, later
[RFC3168]. For the purpose of this specification the DS field is claimed by Explicit Congestion Notification (ECN) [RFC3168]. For
8 bits long, were the 6 most significant bits indicating the DS the purpose of this specification the DS field is 8 bits long,
field to be matched and the 2 least significant bits MUST be set were the 6 most significant bits indicating the DS field to be
to 0 by the sender and ignored by the receiver. matched and the 2 least significant bits MUST be set to 0 by the
sender and ignored by the receiver.
(N)End DS - Differential Services (N)End DS - Differential Services
If more than one contiguous DS values need to be matched then this If more than one contiguous DS values need to be matched then this
field can be used to indicate the end value of a range starting 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 from the value of the Start DS field. This field MUST NOT be
included unless the Start DS field is included. When this field included unless the Start DS field is included. When this field
is included, it MUST be coded the same way as defined for (M). is included, it MUST be coded the same way as defined for (M).
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).
(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 as seen range of next header values to be matched, on data packets sent
by the home agent. from a corresponding node to the mobile node as seen by the home
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 values need 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
 End of changes. 29 change blocks. 
69 lines changed or deleted 79 lines changed or added

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