idnits 2.17.1 draft-ietf-mext-binary-ts-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (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 (November 9, 2009) is 5283 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 793 (Obsoleted by RFC 9293) ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) Summary: 3 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: May 13, 2010 H. Soliman 6 Elevate Technologies 7 N. Montavont 8 IT/TB 9 November 9, 2009 11 Traffic Selectors for Flow Bindings 12 draft-ietf-mext-binary-ts-01.txt 14 Abstract 16 This document defines binary formats for IPv4 and IPv6 traffic 17 selectors to be used in conjuction with flow bindings for Mobile 18 IPv6. 20 Status of this Memo 22 This Internet-Draft is submitted to IETF in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on May 13, 2010. 43 Copyright Notice 45 Copyright (c) 2009 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the BSD License. 58 Table of Contents 60 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 61 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 5 63 3.1. IPv4 binary traffic selector . . . . . . . . . . . . . . . 5 64 3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 8 65 4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 67 6. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 69 7.1. Normative References . . . . . . . . . . . . . . . . . . . 17 70 7.2. Informative References . . . . . . . . . . . . . . . . . . 17 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 73 1. Requirements notation 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 77 document are to be interpreted as described in [RFC2119]. 79 2. Introduction 81 This document defines binary formats for IPv4 and IPv6 Traffic 82 Selector sub-options as defined in [I-D.ietf-mext-flow-binding]. 84 The binary traffic selector sub-options defined here, allow efficient 85 identification of flow(s) based on well known fields in IPv4 86 [RFC0791], IPv6 [RFC2460], and transport layer headers like TCP 87 [RFC0793] and UDP [RFC0768]. 89 3. Traffic Selector Sub-Options 91 [I-D.ietf-mext-flow-binding] defines the format for the traffic 92 selector sub-option. 94 The following values of the TS Format field, are defined in this 95 specification for binary traffic selectors. 97 TS Format: 99 TBD IPv4 binary traffic selector 101 TBD IPv6 binary traffic selector 103 3.1. IPv4 binary traffic selector 105 If the TS Format field of the traffic selector sub-option indicates 106 "IPv4 binary traffic selector", then the traffic selector is 107 formatted as shown below. 109 0 1 2 3 110 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 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 |Sub-opt Type | Sub-Opt Len | TS Format | Reserved | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 |A|B|C|D|E|F|G|H|I|J|K|L|M|N| Reserved | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | (A)Start Source Address | 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | (B)End Source Address | 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 | (C)Start Destination Address | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | (D)End Destination Address | 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 124 | (E)Start SPI | 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 | (F)End SPI | 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | (G)Start Source port | (H)End Source port | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | (I)Start Destination port | (J)End Destination port | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | (K)Start DS | (L)End DS |(M)Start Prot. | (N) End Prot. | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 Figure 1: IPv4 binary traffic selector 137 Flags (A-N) 139 Each flag indicates whether the corresponding field is present in 140 the message 142 (A)Start Source Address 144 This field identifies the first source address, from the range of 145 32-bit IPv4 addresses to be matched, on data packets as seen by 146 the home agent. In other words this is one of the addresses of 147 the correspondent node. 149 (B)End Source Address 151 If more than one contiguous source addresses need to be mached 152 then this field can be used to indicate the end value of a range 153 starting from the value of the Start Source Address field. This 154 field MUST NOT be included unless the Start Source Address field 155 is included. When this field is included the receiver will match 156 all of the addresses between fields (A) and (B), inclusive of (A) 157 and (B). 159 (C)Start Destination Address 161 This field identifies the first destination address, from the 162 range of 32-bit IPv4 addresses to be matched, on data packets as 163 seen by the home agent. In other words this is one of the 164 registered addresses of the mobile node. 166 (D)End Destination Address 168 If more than one contiguous destination addresses need to be 169 mached then this field can be used to indicate the end value of a 170 range starting from the value of the Start Destination Address 171 field. This field MUST NOT be included unless the Start 172 Destination Address field is included. When this field is 173 included the receiver will match all of the addresses between 174 fields (C) and (D), inclusive of (C) and (D). 176 (E)Start SPI - Security Parameter Index 178 This field identifies the first 32-bit SPI value, from the range 179 of SPI values to be matched, on data packets as seen by the home 180 agent. This field is defined in [RFC4303] 182 (F)End SPI - Security Parameter Index 183 If more than one contiguous SPI values need to be mached then this 184 field can be used to indicate the end value of a range starting 185 from the value of the Start SPI field. This field MUST NOT be 186 included unless the Start SPI field is included. When this field 187 is included the receiver will match all of the SPI values between 188 fields (E) and (F), inclusive of (E) and (F). 190 (G)Start Source Port 192 This field identifies the first 16-bit source port number, from 193 the range of port numbers to be matched, on data packets as seen 194 by the home agent. 196 (H)End Source Port 198 If more than one contiguous source port numbers need to be mached 199 then this field can be used to indicate the end value of a range 200 starting from the value of the Start Source Port field. This 201 field MUST NOT be included unless the Start Source Port field is 202 included. When this field is included the receiver will match all 203 of the port numbers between fields (G) and (H), inclusive of (G) 204 and (H). 206 (I)Start Destination Port 208 This field identifies the first 16-bit destination port number, 209 from the range of port numbers to be matched, on data packets as 210 seen by the home agent. 212 (J)End Destination Port 214 If more than one contiguous destination port numbers need to be 215 mached then this field can be used to indicate the end value of a 216 range starting from the value of the Start Destination Port field. 217 This field MUST NOT be included unless the Start Destination Port 218 field is included. When this field is included the receiver will 219 match all of the port numbers between fields (I) and (K), 220 inclusive of (I) and (J). 222 (K)Start DS - Differential Services 224 This field identifies the first differential services value, from 225 the range of differential services values to be matched, on data 226 packets as seen by the home agent. Note that this field is called 227 Type of Service field in [RFC0791]. [RFC3260] then clarified that 228 the field has been redefined as 6 bits DS field and 2 bits 229 reserved, later claimed by Explicit Congestion Notification (ECN) 230 [RFC3168]. For the purpose of this specification the DS field is 231 8bit long, were the 6 most significant bits indicating the DS 232 field to be matched and the 2 list significant bits MUST be set to 233 0 by the sender and ignored by the receiver. 235 (L)End DS - Differential Services 237 If more than one contiguous DS values need to be mached then this 238 field can be used to indicate the end value of a range starting 239 from the value of the Start DS field. This field MUST NOT be 240 included unless the Start DS field is included. When this field 241 is included the receiver will match all of the values between 242 fields (K) and (L), inclusive of (K) and (L). 244 (M)Start Protocol 246 This field identifies the first 8-bit protocol value, from the 247 range of protocol values to be matched, on data packets as seen by 248 the home agent. 250 (N)End Protocol 252 If more than one contiguous protocol values need to be mached then 253 this field can be used to indicate the end value of a range 254 starting from the value of the Start Protocol field. This field 255 MUST NOT be included unless the Start Protocol field is included. 256 When this field is included the receiver will match all of the 257 values between fields (M) and (N), inclusive of (M) and (N). 259 Reserved 261 Reserved for future use. These bits MUST be set to zero by the 262 sender and ignored by the receiver. 264 3.2. IPv6 binary traffic selector 266 If the TS Format field of the traffic selector sub-option indicates 267 "IPv6 binary traffic selector", then the traffic selector is 268 formatted as follows: 270 0 1 2 3 271 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 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 |Sub-opt Type | Sub-Opt Len | TS Format | Reserved | 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| Reserved | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | | 278 + + 279 | | 280 + (A)Start Source Address + 281 | | 282 + + 283 | | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | | 286 + + 287 | | 288 + (B)End Source Address + 289 | | 290 + + 291 | | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 | | 294 + + 295 | | 296 + (C)Start Destination Address + 297 | | 298 + + 299 | | 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 | | 302 + + 303 | | 304 + (D)End Destination Address + 305 | | 306 + + 307 | | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 | (E)Start SPI | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | (F)End SPI | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 | (G)Start Flow Label | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | (H)End Flow Label | 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 | (I)Start Source port | (J)End Source port | 318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 | (K)Start Destination port | (L)End Destination port | 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | (M)Start DS | (N)End DS | (O)Start NH | (P) End NH | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 Figure 2: IPv6 binary traffic selector 326 Flags (A-P) 327 Each flag indicates whether the corresponding field is present in 328 the message 330 (A)Start Source Address 332 This field identifies the first source address, from the range of 333 128-bit IPv6 addresses to be matched, on data packets as seen by 334 the home agent. In other words this is one of the addresses of 335 the correspondent node. 337 (B)End Source Address 339 If more than one contiguous source addresses need to be mached 340 then this field can be used to indicate the end value of a range 341 starting from the value of the Start Source Address field. This 342 field MUST NOT be included unless the Start Source Address field 343 is included. When this field is included the receiver will match 344 all of the addresses between fields (A) and (B), inclusive of (A) 345 and (B). 347 (C)Start Destination Address 349 This field identifies the first destination address, from the 350 range of 128-bit IPv6 addresses to be matched, on data packets as 351 seen by the home agent. In other words this is one of the 352 registered addresses of the mobile node. 354 (D)End Destination Address 356 If more than one contiguous destination addresses need to be 357 mached then this field can be used to indicate the end value of a 358 range starting from the value of the Start Destination Address 359 field. This field MUST NOT be included unless the Start 360 Destination Address field is included. When this field is 361 included the receiver will match all of the addresses between 362 fields (C) and (D), inclusive of (C) and (D). 364 (E)Start SPI - Security Parameter Index 366 This field identifies the first 32-bit SPI value, from the range 367 of SPI values to be matched, on data packets as seen by the home 368 agent. 370 (F)End SPI - Security Parameter Index 372 If more than one contiguous SPI values need to be mached then this 373 field can be used to indicate the end value of a range starting 374 from the value of the Start SPI field. This field MUST NOT be 375 included unless the Start SPI field is included. When this field 376 is included the receiver will match all of the SPI values between 377 fields (E) and (F), inclusive of (E) and (F). 379 (G)Start Flow Label 381 This field identifies the first flow label value, from the range 382 of flow label values to be matched, on data packets as seen by the 383 home agent. According to [RFC2460] the flow label is 24-bit long. 384 For the purpose of this specification the sender of this options 385 MUST prefix flow label values with 8-bits of "0" before inserting 386 it in this field. The receive SHOULD ignore the first 8-bits of 387 this field. 389 (H)End Flow Label 391 If more than one contiguous flow label values need to be mached 392 then this field can be used to indicate the end value of a range 393 starting from the value of the Start Flow Label field. This field 394 MUST NOT be included unless the Start Flow Label field is 395 included. When this field is included the receiver will match all 396 of the flow label values between fields (G) and (H), inclusive of 397 (G) and (H). 399 (I)Start Source Port 401 This field identifies the first 16-bit source port number, from 402 the range of port numbers to be matched, on data packets as seen 403 by the home agent. 405 (J)End Source Port 407 If more than one contiguous source port numbers need to be mached 408 then this field can be used to indicate the end value of a range 409 starting from the value of the Start Source Port field. This 410 field MUST NOT be included unless the Start Source Port field is 411 included. When this field is included the receiver will match all 412 of the port numbers between fields (I) and (J), inclusive of (I) 413 and (J). 415 (K)Start Destination Port 417 This field identifies the first 16-bit destination port number, 418 from the range of port numbers to be matched, on data packets as 419 seen by the home agent. 421 (L)End Destination Port 422 If more than one contiguous destination port numbers need to be 423 mached then this field can be used to indicate the end value of a 424 range starting from the value of the Start Destination Port field. 425 This field MUST NOT be included unless the Start Destination Port 426 field is included. When this field is included the receiver will 427 match all of the port numbers between fields (K) and (L), 428 inclusive of (K) and (L). 430 (M)Start DS - Differential Services 432 This field identifies the first differential services value, from 433 the range of differential services values to be matched, on data 434 packets as seen by the home agent. Note that this field is called 435 Type of Service field in [RFC0791]. [RFC3260] then clarified that 436 the field has been redefined as 6 bits DS field and 2 bits 437 reserved, later claimed by Explicit Congestion Notification (ECN) 438 [RFC3168]. For the purpose of this specification the DS field is 439 8bit long, were the 6 most significant bits indicating the DS 440 field to be matched and the 2 list significant bits MUST be set to 441 0 by the sender and ignored by the receiver. 443 (N)End DS - Differential Services 445 If more than one contiguous DS values need to be mached then this 446 field can be used to indicate the end value of a range starting 447 from the value of the Start DS field. This field MUST NOT be 448 included unless the Start DS field is included. When this field 449 is included the receiver will match all of the values between 450 fields (M) and (N), inclusive of (M) and (N). 452 (O)Start NH - Next Header 454 This field identifies the first 8-bit next header value, from the 455 range of next header values to be matched, on data packets as seen 456 by the home agent. 458 (P)End NH - Next Header 460 If more than one contiguous next header values need to be mached 461 then this field can be used to indicate the end value of a range 462 starting from the value of the Start NH field. This field MUST 463 NOT be included unless the Start next header field is included. 464 When this field is included the receiver will match all of the 465 values between fields (O) and (P), inclusive of (O) and (P). 467 Reserved 468 Reserved for future use. These bits MUST be set to zero by the 469 sender and ignored by the receiver. 471 4. Security Considerations 473 This draft defines the format of traffic selector sub-options defined 474 in the flow bindings [I-D.ietf-mext-flow-binding]. The authors have 475 not identified any security concenrs pertaining to this draft beyond 476 what is already identified in [I-D.ietf-mext-flow-binding]. 478 5. IANA Considerations 480 1) New TS format values from the "Traffic Selector Format" namespace 481 for the Traffic Selector sub-option defined in 482 [I-D.ietf-mext-flow-binding]. Values are requested for the 483 following: 485 IPv4 Binary Traffic Selector 487 IPv6 Binary Traffic Selector 489 6. Aknowledgements 491 The authors would like to thank Patrick Stupar and Julien Laganier 492 for their contributions to this document. 494 7. References 496 7.1. Normative References 498 [I-D.ietf-mext-flow-binding] 499 Soliman, H., Montavont, N., and K. Kuladinithi, "Flow 500 Bindings in Mobile IPv6 and NEMO Basic Support", 501 draft-ietf-mext-flow-binding-03 (work in progress), 502 July 2009. 504 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 505 August 1980. 507 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 508 September 1981. 510 [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, 511 RFC 793, September 1981. 513 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 514 Requirement Levels", BCP 14, RFC 2119, March 1997. 516 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 517 (IPv6) Specification", RFC 2460, December 1998. 519 [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition 520 of Explicit Congestion Notification (ECN) to IP", 521 RFC 3168, September 2001. 523 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 524 RFC 4303, December 2005. 526 7.2. Informative References 528 [RFC3260] Grossman, D., "New Terminology and Clarifications for 529 Diffserv", RFC 3260, April 2002. 531 Authors' Addresses 533 George Tsirtsis 534 Qualcomm 536 Email: tsirtsis@gmail.com 538 Gerardo Giarreta 539 Qualcomm 541 Email: gerardog@qualcomm.com 543 Hesham Soliman 544 Elevate Technologies 546 Email: hesham@elevatemobile.com 548 Nicolas Montavont 549 Institut Telecom / Telecom Bretagne 550 2, rue de la chataigneraie 551 Cesson Sevigne 35576 552 France 554 Phone: (+33) 2 99 12 70 23 555 Email: nicolas.montavont@telecom-bretagne.eu 556 URI: http://www.rennes.enst-bretagne.fr/~nmontavo//