draft-ietf-mext-binary-ts-04.txt   draft-ietf-mext-binary-ts-05.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 30, 2010 H. Soliman Expires: April 8, 2011 H. Soliman
Elevate Technologies Elevate Technologies
N. Montavont N. Montavont
IT/TB IT/TB
February 26, 2010 October 5, 2010
Traffic Selectors for Flow Bindings Traffic Selectors for Flow Bindings
draft-ietf-mext-binary-ts-04.txt 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 to IETF in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 This Internet-Draft will expire on April 8, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
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
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 Simplified 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 . . . . . . . . . . . . . . . . . . . 15 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
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 set n if K, L, M, or 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (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
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 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 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 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 SPI
values 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)
skipping to change at page 8, line 38 skipping to change at page 8, line 38
(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 Type of Service
field in [RFC0791]. [RFC3260] then clarified that the field has field in [RFC0791]. [RFC3260] then clarified that the field has
been redefined as 6 bits DS field and 2 bits reserved, later been redefined as 6 bits DS field and 2 bits reserved, later
claimed by Explicit Congestion Notification (ECN) [RFC3168]. For claimed by Explicit Congestion Notification (ECN) [RFC3168]. For
the purpose of this specification the DS field is 8 bits long, the purpose of this specification the (K)Start DS field is 8 bits
were the 6 most significant bits indicating the DS field to be long, were the 6 most significant bits indicating the DS field to
matched and the 2 least significant bits MUST be set to 0 by the be matched and the 2 least significant bit's value MUST be ignored
sender and ignored by the receiver. in any comparision.
(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).
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 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 |
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 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 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 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 SPI
values 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 20-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 8-bits of "0" before inserting it prefix the flow label value with 12-bits of "0" before inserting
in this field. The receiver SHOULD ignore the first 8-bits of it in the (G)Start Flow Label field. The receiver SHOULD ignore
this field. the first 12-bits of this field before using it for comparisons
with 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 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). When this field is included, it MUST be coded the
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 numbers need to be matched
skipping to change at page 13, line 28 skipping to change at page 13, line 28
(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 6 bits DS field and 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 TC field is 8 bits long, were the 6 most of this specification the (M)Start TC field is 8 bits long, where
significant bits indicating the DS field to be matched and the 2 the 6 most significant bits indicating the DS field to be matched
least significant bits MUST be set to 0 by the sender and ignored and the 2 least significant bit's value MUST be
by the receiver.
(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 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 TC field. This field MUST NOT be from the value of the Start TC field. This field MUST NOT be
included unless the Start TC 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).
skipping to change at page 18, line 10 skipping to change at page 18, line 10
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] [I-D.ietf-mext-flow-binding]
Soliman, H., Tsirtsis, G., Montavont, N., Giaretta, G., Tsirtsis, G., Soliman, H., 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-05 (work in Basic Support", draft-ietf-mext-flow-binding-10 (work in
progress), February 2010. 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.
 End of changes. 27 change blocks. 
46 lines changed or deleted 41 lines changed or added

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