draft-ietf-mext-binary-ts-03.txt   draft-ietf-mext-binary-ts-04.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: August 13, 2010 H. Soliman Expires: August 30, 2010 H. Soliman
Elevate Technologies Elevate Technologies
N. Montavont N. Montavont
IT/TB IT/TB
February 9, 2010 February 26, 2010
Traffic Selectors for Flow Bindings Traffic Selectors for Flow Bindings
draft-ietf-mext-binary-ts-03.txt draft-ietf-mext-binary-ts-04.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 August 13, 2010. This Internet-Draft will expire on August 30, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 19 skipping to change at page 6, line 19
|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 SPI | | (E)Start IPSEC SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (F)End 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
skipping to change at page 7, line 25 skipping to change at page 7, line 25
(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 IPSEC SPI - Security Parameter Index
This field identifies the first 32-bit SPI value, from the range This field identifies the first 32-bit IPSEC SPI value, from the
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 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 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 IPSEC SPI field. This field
NOT be included unless the Start SPI field is included. When this MUST NOT be included unless the Start IPSEC SPI field is included.
field is included the receiver will match all of the SPI values When this field is included the receiver will match all of the SPI
between fields (E) and (F), inclusive of (E) and (F). 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/assignments/port-numbers)
(H)End Source Port (H)End Source Port
skipping to change at page 10, line 33 skipping to change at page 10, line 33
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ (D)End Destination Address + + (D)End Destination Address +
| | | |
+ + + +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (E)Start SPI | | (E)Start IPSEC SPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (F)End 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 DS | (N)End DS | (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
skipping to change at page 11, line 43 skipping to change at page 11, line 43
(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 IPSEC SPI - Security Parameter Index
This field identifies the first 32-bit SPI value, from the range This field identifies the first 32-bit IPSEC SPI value, from the
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 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 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 IPSEC SPI field. This field
NOT be included unless the Start SPI field is included. When this MUST NOT be included unless the Start IPSEC SPI field is included.
field is included the receiver will match all of the SPI values When this field is included the receiver will match all of the SPI
between fields (E) and (F), inclusive of (E) and (F). 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 24-bit long. For the According to [RFC2460] the flow label is 24-bit 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 8-bits of "0" before inserting it prefix the flow label value with 8-bits of "0" before inserting it
in this field. The receiver SHOULD ignore the first 8-bits of in this field. The receiver SHOULD ignore the first 8-bits of
skipping to change at page 13, line 19 skipping to change at page 13, line 19
(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 TC - Traffic Class
This field identifies the first differential services value, from This field identifies the first traffic class value, from the
the range of differential services values to be matched, on data range of traffic class values to be matched, on data packets sent
packets sent from a corresponding node to the mobile node as seen from a corresponding node to the mobile node as seen by the home
by the home agent. Note that this field is called Type of Service agent. This field is equivalent to the Start DS field in the IPv4
field in [RFC0791]. [RFC3260] then clarified that the field has traffic selector in Figure 1. As per [RFC3260], the field is
been redefined as 6 bits DS field and 2 bits reserved, later defined as 6 bits DS field and 2 bits reserved, later claimed by
claimed by Explicit Congestion Notification (ECN) [RFC3168]. For Explicit Congestion Notification (ECN) [RFC3168]. For the purpose
the purpose of this specification the DS field is 8 bits long, of this specification the TC field is 8 bits long, were the 6 most
were the 6 most significant bits indicating the DS field to be significant bits indicating the DS field to be matched and the 2
matched and the 2 least significant bits MUST be set to 0 by the least significant bits MUST be set to 0 by the sender and ignored
sender and ignored by the receiver. by the receiver.
(N)End DS - Differential Services (N)End TC - Traffic Class
If more than one contiguous DS values need to be matched then this If more than one contiguous TC 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 TC field. This field MUST NOT be
included unless the Start DS field is included. When this field included unless the Start TC 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 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.
skipping to change at page 18, line 12 skipping to change at page 18, line 12
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] [I-D.ietf-mext-flow-binding]
Soliman, H., Tsirtsis, G., Montavont, N., Giaretta, G., Soliman, H., Tsirtsis, G., Montavont, N., Giaretta, G.,
and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and NEMO and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and NEMO
Basic Support", draft-ietf-mext-flow-binding-04 (work in Basic Support", draft-ietf-mext-flow-binding-05 (work in
progress), November 2009. progress), February 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.
skipping to change at page 19, line 10 skipping to change at page 19, line 10
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@gmail.com Email: tsirtsis@qualcomm.com
Gerardo Giarreta Gerardo Giarreta
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
 End of changes. 24 change blocks. 
44 lines changed or deleted 44 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/