idnits 2.17.1 draft-ietf-mext-binary-ts-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 29, 2009) is 5383 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-11) exists of draft-ietf-mext-flow-binding-03 ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Tsirtsis 3 Internet-Draft G. Giarreta 4 Intended status: Standards Track Qualcomm 5 Expires: January 30, 2010 H. Soliman 6 Elevate Technologies 7 N. Montavont 8 IT/TB 9 July 29, 2009 11 Binary Traffic Selectors for FB 12 draft-ietf-mext-binary-ts-00.txt 14 Status of this Memo 16 This Internet-Draft is submitted to IETF in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on January 30, 2010. 37 Copyright Notice 39 Copyright (c) 2009 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents in effect on the date of 44 publication of this document (http://trustee.ietf.org/license-info). 45 Please review these documents carefully, as they describe your rights 46 and restrictions with respect to this document. 48 Abstract 50 This document defines binary format for IPv4 and IPv6 traffic 51 selectors to be used in conjuction with flow bindings for Mobile 52 IPv6. 54 Table of Contents 56 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 57 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 5 59 3.1. IPv4 binary traffic selector . . . . . . . . . . . . . . . 5 60 3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 7 61 4. Flow Identification Status codes . . . . . . . . . . . . . . . 11 62 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 64 7. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 65 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 66 8.1. Normative References . . . . . . . . . . . . . . . . . . . 15 67 8.2. Informative References . . . . . . . . . . . . . . . . . . 15 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 70 1. Requirements notation 72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 74 document are to be interpreted as described in [RFC2119]. 76 2. Introduction 78 This document defines binary formats for IPv4 and IPv6 Traffic 79 Selector sub-options as defined in [I-D.ietf-mext-flow-binding]. 81 The binary traffic selector sub-options defined here, allow efficient 82 identification of flow(s) based on well known fields in IPv4, IPv6, 83 and transport layer headers. 85 3. Traffic Selector Sub-Options 87 [I-D.ietf-mext-flow-binding] defines the format for the traffic 88 selector sub-option. 90 The following values of the sub-option Type field, are reserved in 91 this specification for binary traffic selectors 93 TBD IPv4 binary traffic selector 95 TBD IPv6 binary traffic selector 97 3.1. IPv4 binary traffic selector 99 If the Type field of the traffic selector sub-option indicates "IPv4 100 binary traffic selector", then the traffic selector is formatted as 101 follows: 103 0 1 2 3 104 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 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 |A|B|C|D|E|F|G|H|I|K|L| Resvd | (A)DS | (B)Protocol | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | (C)Source Address | 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | (D)Destination Address | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 |(E)S. PrefLeng |(F)D. PrefLeng | (G)Source port - Low | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 | (H)Source port - High | (I)Dst port - Low | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | (K)Dst port - High | (L)SPI | 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | (L)SPI | 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 Figure 1: IPv4 binary traffic selector 123 Flags (A-L) 125 Each flag indicates whether the corresponding field is present in 126 the message 128 (A)DS - Differential Services 130 The Differential Services (DS) field in the data packet as seen by 131 the home agent. Note that this is called Type of Service field in 132 [RFC0791]. [RFC3260] then clarified that the field has been 133 redefined as 6 bits DS field and 2 bits reserved, later claimed by 134 Explicit Congestion Notification (ECN) [RFC3168]. For the purpose 135 of this specification the DS field is 8bit long, were the 6 most 136 significant bits indicating the DS field to be matched and the 2 137 list significant bits MUST be set to 0 by the sender and ignored 138 by the receiver. 140 (B)Protocol 142 An 8-bit unsigned integer representing the value of the transport 143 protocol number associated with the port numbers in data packets. 145 (C)Source Address 147 This field identifies the source address of data packets as seen 148 by the home agent that is, the 32-bit IPv4 address of the 149 correspondent node. 151 (D)Destination Address 153 This field identifies the destination address of data packets as 154 seen by the home agent. When included this field must one of the 155 registered home addresses of the mobile node. It is a 32-bit IPv4 156 address. 158 (E)Source Prefix Length 160 This field includes the prefix length for the source address. 161 This field can only be included if the Source Address field is 162 included. When this field is included the receiver will match all 163 of the addresses in the subnet identified by this field. 165 (F)Destination Prefix Length 167 This field includes the prefix length for the destination address. 168 If The Destination Address field is included then it refers to 169 that field. When this field is included the receiver will match 170 all of the addresses in the subnet identified by this field. 172 (G)Source Port - Low 174 This field identifies the lowest source port number within a range 175 of port numbers that will be used in data packets, as seen by the 176 home agent. 178 (H)Source Port - High 179 This field identifies the highest source port number within a 180 range of port numbers that will be used in data packets, as seen 181 by the home agent. This field MUST NOT be included if the Source 182 Port - Low field is not includede. If a single port is indicated 183 then this field MUST NOT be included. When it is included it MUST 184 be set to the value larger than that of Source Port - Low field. 186 (I)Destination Port - Low 188 This field identifies the lowest destination port number within a 189 range of port numbers that will be used in data packets as seen by 190 the home agent. 192 (K)Destination Port - High 194 This field identifies the highest destination port number within a 195 range of port numbers that will be used in data packets, as seen 196 by the home agent. This field MUST NOT be included if the 197 Destination Port - Low field is not includede. If a single port 198 is indicated then this field MUST NOT be included. When it is 199 included it MUST be set to the value larger than that of 200 Destination Port - Low field. 202 (L)SPI - Security Parameter Index 204 The SPI field in the data packet as seen by the home agent. 206 Resved 208 Reserved for future use. These bits MUST be set to zero by the 209 sender and ignored by the receiver. 211 3.2. IPv6 binary traffic selector 213 If the Type field of the traffic selector sub-option indicates "IPv6 214 binary traffic selector", then the traffic selector is formatted as 215 follows: 217 0 1 2 3 218 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 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 |A|B|C|D|E|F|G|H|I|K|L|M| Resvd | (A)DS | (B)Protocol | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | | 223 + + 224 | | 225 + (C)Source Address + 226 | | 227 + + 228 | | 229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 230 | | 231 + + 232 | | 233 + (D)Destination Address + 234 | | 235 + + 236 | | 237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 238 |(E)S. PrefLeng |(F)D. PrefLeng | (G)Source port - Low | 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 | (H)Source port - High | (I)Dst port - Low | 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 | (K)Dst port - High | (L)SPI | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 | (L)SPI | (M)Flow Label | 245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 | (M)Flow Label | 247 +-+-+-+-+-+-+-+-+ 249 Figure 2: IPv6 binary traffic selector 251 Flags (A-M) 253 Each flag indicates whether the corresponding field is present in 254 the message 256 (A) DS - Differential Services 258 The Differential Services (DS) field in the data packet as seen by 259 the home agent. Note that this is called Traffic Class field in 260 [RFC2460]. [RFC3260] then clarified that the field has been 261 redefined as 6 bits DS field and 2 bits reserved, later claimed by 262 Explicit Congestion Notification (ECN) in [RFC3168]. For the 263 purpose of this specification the DS field is 8bit long, were the 264 6 most significant bits indicating the DS field to be matched and 265 the 2 list significant bits MUST be set to 0 by the sender and 266 ignored by the receiver. 268 (B)Protocol 270 An 8-bit unsigned integer representing value of the transport 271 protocol number associated with the port numbers in data packets. 273 (C)Source Address 275 This field identifies the source address of data packets as seen 276 by the home agent. That is, the address of the correspondent node 277 and it is a 128-bit IPv6 address. 279 (D)Destination Address 281 This field identifies the destination address of the data packet 282 as seen by the home agent. When included this field must be set 283 to either one of the registered home addresses of the mobile node 284 or to an address that falls under one of the mobile's home network 285 prefixes. The value of this fild is 128-bit IPv6 address. 287 (E)Source Prefix Length 289 This field includes the prefix for the source address. This field 290 MUST NOT be included if the Source Address field is not included. 291 When this field is included the receiver will match all of the 292 addresses in the subnet identified by this field. 294 (F)Destination Prefix Length 296 This field includes the prefix for the destination address. This 297 field MUST NOT be included if the Source Address field is not 298 included. When this field is included the receiver will match all 299 of the addresses in the subnet identified by this field. 301 (G)Source Port - Low 303 This field identifies the lowest source port number within a range 304 of port numbers that will be used in data packets, as seen by the 305 home agent. 307 (H)Source Port - High 309 This field identifies the highest source port number within a 310 range of port numbers that will be used in data packets, as seen 311 by the home agent. This field MUST NOT be included if the Source 312 Port - Low field is not includede. If a single port is indicated 313 then this field MUST NOT be included. When it is included it MUST 314 be set to the value larger than that of Source Port - Low field. 316 (I)Destination Port - Low 318 This field identifies the lowest destination port number within a 319 range of port numbers that will be used in data packets as seen by 320 the home agent. 322 (K)Destination Port - High 324 This field identifies the highest destination port number within a 325 range of port numbers that will be used in data packets, as seen 326 by the home agent. This field MUST NOT be included if the 327 Destination Port - Low field is not includede. If a single port 328 is indicated then this field MUST NOT be included. When it is 329 included it MUST be set to the value larger than that of 330 Destination Port - Low field. 332 (L)SPI - Security Parameter Index 334 The SPI field in the data packet as seen by the home agent. 336 (M)Flow Label 338 The Flow Label field in the data packet as seen by the home agent. 340 Resved 342 Reserved for future use. 344 4. Flow Identification Status codes 346 TBD 348 5. Security Considerations 350 This draft defines the format of traffic selector sub-options defined 351 in the flow bindings [I-D.ietf-mext-flow-binding]. The authors have 352 not identified any security concenrs pertaining to this draft beyond 353 what is already identified in [I-D.ietf-mext-flow-binding]. 355 6. IANA Considerations 357 TBD 359 7. Aknowledgements 361 TBD 363 8. References 365 8.1. Normative References 367 [I-D.ietf-mext-flow-binding] 368 Soliman, H., Montavont, N., and K. Kuladinithi, "Flow 369 Bindings in Mobile IPv6 and NEMO Basic Support", 370 draft-ietf-mext-flow-binding-03 (work in progress), 371 July 2009. 373 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 374 September 1981. 376 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 377 Requirement Levels", BCP 14, RFC 2119, March 1997. 379 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 380 (IPv6) Specification", RFC 2460, December 1998. 382 [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition 383 of Explicit Congestion Notification (ECN) to IP", 384 RFC 3168, September 2001. 386 8.2. Informative References 388 [RFC3260] Grossman, D., "New Terminology and Clarifications for 389 Diffserv", RFC 3260, April 2002. 391 Authors' Addresses 393 George Tsirtsis 394 Qualcomm 396 Email: tsirtsis@gmail.com 398 Gerardo Giarreta 399 Qualcomm 401 Email: gerardog@qualcomm.com 403 Hesham Soliman 404 Elevate Technologies 406 Email: hesham@elevatemobile.com 408 Nicolas Montavont 409 Institut Telecom / Telecom Bretagne 410 2, rue de la chataigneraie 411 Cesson Sevigne 35576 412 France 414 Phone: (+33) 2 99 12 70 23 415 Email: nicolas.montavont@telecom-bretagne.eu 416 URI: http://www.rennes.enst-bretagne.fr/~nmontavo//