idnits 2.17.1 draft-ietf-mext-binary-ts-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 (October 5, 2010) is 4951 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-10 ** Obsolete normative reference: RFC 793 (Obsoleted by RFC 9293) ** 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: April 8, 2011 H. Soliman 6 Elevate Technologies 7 N. Montavont 8 IT/TB 9 October 5, 2010 11 Traffic Selectors for Flow Bindings 12 draft-ietf-mext-binary-ts-05.txt 14 Abstract 16 This document defines binary formats for IPv4 and IPv6 traffic 17 selectors to be used in conjunction with flow bindings for Mobile 18 IPv6. 20 Status of this Memo 22 This Internet-Draft is submitted 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). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 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 This Internet-Draft will expire on April 8, 2011. 37 Copyright Notice 39 Copyright (c) 2010 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 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 55 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3. Traffic Selector Sub-Options . . . . . . . . . . . . . . . . . 5 57 3.1. IPv4 binary traffic selector . . . . . . . . . . . . . . . 5 58 3.2. IPv6 binary traffic selector . . . . . . . . . . . . . . . 9 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 61 6. Aknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 18 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 18 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 67 1. Requirements notation 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 71 document are to be interpreted as described in [RFC2119]. 73 2. Introduction 75 This document defines binary formats for IPv4 and IPv6 Traffic 76 Selector sub-options as defined in [I-D.ietf-mext-flow-binding]. 78 The binary traffic selector format defined here, allows for efficient 79 identification of flow(s) based on well known fields in IPv4 80 [RFC0791], IPv6 [RFC2460], and transport layer headers like TCP 81 [RFC0793] and UDP [RFC0768]. 83 3. Traffic Selector Sub-Options 85 [I-D.ietf-mext-flow-binding] defines the format for the traffic 86 selector sub-option. 88 The following values of the TS Format field, are defined in this 89 specification for binary traffic selectors. 91 TS Format: 93 1 IPv4 binary traffic selector 95 2 IPv6 binary traffic selector 97 3.1. IPv4 binary traffic selector 99 If the TS Format field of the traffic selector sub-option indicates 100 "IPv4 binary traffic selector", then the traffic selector is 101 formatted as shown below. 103 The alignment requirement for this sub-option is: 105 4n if A, B, C, D, E, or F is set 107 2n if G, H, I, or J is set 109 n if K, L, M, or N is set 110 0 1 2 3 111 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 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 |Sub-opt Type | Sub-Opt Len | TS Format | Reserved | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 |A|B|C|D|E|F|G|H|I|J|K|L|M|N| Reserved | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | (A)Start Source Address | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | (B)End Source Address | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | (C)Start Destination Address | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | (D)End Destination Address | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | (E)Start IPsec SPI | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | (F)End IPsec SPI | 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | (G)Start Source port | (H)End Source port | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | (I)Start Destination port | (J)End Destination port | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | (K)Start DS | (L)End DS |(M)Start Prot. | (N) End Prot. | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 Figure 1: IPv4 binary traffic selector 138 Flags (A-N) 140 Each flag indicates whether the corresponding field is present in 141 the message 143 (A)Start Source Address 145 This field identifies the first source address, from the range of 146 32-bit IPv4 addresses to be matched, on data packets sent from a 147 corresponding node to the mobile node as seen by the home agent. 148 In other words this is one of the addresses of the correspondent 149 node. 151 (B)End Source Address 153 If more than one contiguous source address needs to be matched 154 then this field can be used to indicate the end value of a range 155 starting from the value of the Start Source Address field. This 156 field MUST NOT be included unless the Start Source Address field 157 is included. When this field is included the receiver will match 158 all of the addresses between fields (A) and (B), inclusive of (A) 159 and (B). 161 (C)Start Destination Address 163 This field identifies the first destination address, from the 164 range of 32-bit IPv4 addresses to be matched, on data packets sent 165 from a corresponding node to the mobile node as seen by the home 166 agent. In other words this is one of the registered home 167 addresses of the mobile node. 169 (D)End Destination Address 171 If more than one contiguous destination address needs to be 172 matched then this field can be used to indicate the end value of a 173 range starting from the value of the Start Destination Address 174 field. This field MUST NOT be included unless the Start 175 Destination Address field is included. When this field is 176 included the receiver will match all of the addresses between 177 fields (C) and (D), inclusive of (C) and (D). 179 (E)Start IPsec SPI - Security Parameter Index 181 This field identifies the first 32-bit IPsec SPI value, from the 182 range of SPI values to be matched, on data packets sent from a 183 corresponding node to the mobile node as seen by the home agent. 184 This field is defined in [RFC4303]. 186 (F)End IPsec SPI - Security Parameter Index 188 If more than one contiguous SPI values need to be matched then 189 this field can be used to indicate the end value of a range 190 starting from the value of the Start IPsec SPI field. This field 191 MUST NOT be included unless the Start IPsec SPI field is included. 192 When this field is included the receiver will match all of the SPI 193 values between fields (E) and (F), inclusive of (E) and (F). 195 (G)Start Source Port 197 This field identifies the first 16-bit source port number, from 198 the range of port numbers to be matched, on data packets sent from 199 a corresponding node to the mobile node as seen by the home agent. 200 This is from the range of port numbers defined by IANA 201 (http://www.iana.org/assignments/port-numbers) 203 (H)End Source Port 204 If more than one contiguous source port numbers need to be matched 205 then this field can be used to indicate the end value of a range 206 starting from the value of the Start Source Port field. This 207 field MUST NOT be included unless the Start Source Port field is 208 included. When this field is included the receiver will match all 209 of the port numbers between fields (G) and (H), inclusive of (G) 210 and (H). 212 (I)Start Destination Port 214 This field identifies the first 16-bit destination port number, 215 from the range of port numbers to be matched, on data packets sent 216 from a corresponding node to the mobile node as seen by the home 217 agent. 219 (J)End Destination Port 221 If more than one contiguous destination port numbers need to be 222 matched then this field can be used to indicate the end value of a 223 range starting from the value of the Start Destination Port field. 224 This field MUST NOT be included unless the Start Destination Port 225 field is included. When this field is included the receiver will 226 match all of the port numbers between fields (I) and (J), 227 inclusive of (I) and (J). 229 (K)Start DS - Differential Services 231 This field identifies the first differential services value, from 232 the range of differential services values to be matched, on data 233 packets sent from a corresponding node to the mobile node as seen 234 by the home agent. Note that this field is called Type of Service 235 field in [RFC0791]. [RFC3260] then clarified that the field has 236 been redefined as 6 bits DS field and 2 bits reserved, later 237 claimed by Explicit Congestion Notification (ECN) [RFC3168]. For 238 the purpose of this specification the (K)Start DS field is 8 bits 239 long, were the 6 most significant bits indicating the DS field to 240 be matched and the 2 least significant bit's value MUST be ignored 241 in any comparision. 243 (L)End DS - Differential Services 245 If more than one contiguous DS values need to be matched then this 246 field can be used to indicate the end value of a range starting 247 from the value of the Start DS field. This field MUST NOT be 248 included unless the Start DS field is included. When this field 249 is included, it MUST be coded the same way as defined for (K). 250 When this field is included the receiver will match all of the 251 values between fields (K) and (L), inclusive of (K) and (L). 253 (M)Start Protocol 255 This field identifies the first 8-bit protocol value, from the 256 range of protocol values to be matched, on data packets sent from 257 a corresponding node to the mobile node as seen by the home agent. 259 (N)End Protocol 261 If more than one contiguous protocol values need to be matched 262 then this field can be used to indicate the end value of a range 263 starting from the value of the Start Protocol field. This field 264 MUST NOT be included unless the Start Protocol field is included. 265 When this field is included the receiver will match all of the 266 values between fields (M) and (N), inclusive of (M) and (N). 268 Reserved 270 Reserved for future use. These bits MUST be set to zero by the 271 sender and ignored by the receiver. 273 3.2. IPv6 binary traffic selector 275 If the TS Format field of the traffic selector sub-option indicates 276 "IPv6 binary traffic selector", then the traffic selector is 277 formatted as follows: 279 The alignment requirement for this sub-option is: 281 8n if A, B, C, or D is set 283 4n if E, F, G, or H is set 285 2n if I, J, K, or L is set 287 n if M, N, O, or P is set 289 0 1 2 3 290 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 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 |Sub-opt Type | Sub-Opt Len | TS Format | Reserved | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P| Reserved | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | | 297 + + 298 | | 299 + (A)Start Source Address + 300 | | 301 + + 302 | | 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | | 305 + + 306 | | 307 + (B)End Source Address + 308 | | 309 + + 310 | | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | | 313 + + 314 | | 315 + (C)Start Destination Address + 316 | | 317 + + 318 | | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | | 321 + + 322 | | 323 + (D)End Destination Address + 324 | | 325 + + 326 | | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | (E)Start IPsec SPI | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | (F)End IPsec SPI | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | (G)Start Flow Label | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | (H)End Flow Label | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | (I)Start Source port | (J)End Source port | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | (K)Start Destination port | (L)End Destination port | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | (M)Start TC | (N)End TC | (O)Start NH | (P) End NH | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 Figure 2: IPv6 binary traffic selector 345 Flags (A-P) 346 Each flag indicates whether the corresponding field is present in 347 the message 349 (A)Start Source Address 351 This field identifies the first source address, from the range of 352 128-bit IPv6 addresses to be matched, on data packets sent from a 353 corresponding node to the mobile node as seen by the home agent. 354 In other words this is one of the addresses of the correspondent 355 node. 357 (B)End Source Address 359 If more than one contiguous source address needs to be matched 360 then this field can be used to indicate the end value of a range 361 starting from the value of the Start Source Address field. This 362 field MUST NOT be included unless the Start Source Address field 363 is included. When this field is included the receiver will match 364 all of the addresses between fields (A) and (B), inclusive of (A) 365 and (B). 367 (C)Start Destination Address 369 This field identifies the first destination address, from the 370 range of 128-bit IPv6 addresses to be matched, on data packets 371 sent from a corresponding node to the mobile node as seen by the 372 home agent. In other words this is one of the registered home 373 addresses of the mobile node. 375 (D)End Destination Address 377 If more than one contiguous destination address needs to be 378 matched then this field can be used to indicate the end value of a 379 range starting from the value of the Start Destination Address 380 field. This field MUST NOT be included unless the Start 381 Destination Address field is included. When this field is 382 included the receiver will match all of the addresses between 383 fields (C) and (D), inclusive of (C) and (D). 385 (E)Start IPsec SPI - Security Parameter Index 387 This field identifies the first 32-bit IPsec SPI value, from the 388 range of SPI values to be matched, on data packets sent from a 389 corresponding node to the mobile node as seen by the home agent. 390 This field is defined in [RFC4303]. 392 (F)End IPsec SPI - Security Parameter Index 393 If more than one contiguous SPI values need to be matched then 394 this field can be used to indicate the end value of a range 395 starting from the value of the Start IPsec SPI field. This field 396 MUST NOT be included unless the Start IPsec SPI field is included. 397 When this field is included the receiver will match all of the SPI 398 values between fields (E) and (F), inclusive of (E) and (F). 400 (G)Start Flow Label 402 This field identifies the first flow label value, from the range 403 of flow label values to be matched, on data packets sent from a 404 corresponding node to the mobile node as seen by the home agent. 405 According to [RFC2460] the flow label is 20-bits long. For the 406 purpose of this specification the sender of this option MUST 407 prefix the flow label value with 12-bits of "0" before inserting 408 it in the (G)Start Flow Label field. The receiver SHOULD ignore 409 the first 12-bits of this field before using it for comparisons 410 with flow labels in packets. 412 (H)End Flow Label 414 If more than one contiguous flow label values need to be matched 415 then this field can be used to indicate the end value of a range 416 starting from the value of the Start Flow Label field. This field 417 MUST NOT be included unless the Start Flow Label field is 418 included. When this field is included the receiver will match all 419 of the flow label values between fields (G) and (H), inclusive of 420 (G) and (H). When this field is included, it MUST be coded the 421 same way as defined for (G). 423 (I)Start Source Port 425 This field identifies the first 16-bit source port number, from 426 the range of port numbers to be matched, on data packets sent from 427 a corresponding node to the mobile node as seen by the home agent. 429 (J)End Source Port 431 If more than one contiguous source port numbers need to be matched 432 then this field can be used to indicate the end value of a range 433 starting from the value of the Start Source Port field. This 434 field MUST NOT be included unless the Start Source Port field is 435 included. When this field is included the receiver will match all 436 of the port numbers between fields (I) and (J), inclusive of (I) 437 and (J). 439 (K)Start Destination Port 440 This field identifies the first 16-bit destination port number, 441 from the range of port numbers to be matched, on data packets sent 442 from a corresponding node to the mobile node as seen by the home 443 agent. 445 (L)End Destination Port 447 If more than one contiguous destination port numbers need to be 448 matched then this field can be used to indicate the end value of a 449 range starting from the value of the Start Destination Port field. 450 This field MUST NOT be included unless the Start Destination Port 451 field is included. When this field is included the receiver will 452 match all of the port numbers between fields (K) and (L), 453 inclusive of (K) and (L). 455 (M)Start TC - Traffic Class 457 This field identifies the first traffic class value, from the 458 range of traffic class values to be matched, on data packets sent 459 from a corresponding node to the mobile node as seen by the home 460 agent. This field is equivalent to the Start DS field in the IPv4 461 traffic selector in Figure 1. As per [RFC3260], the field is 462 defined as 6 bits DS field and 2 bits reserved, later claimed by 463 Explicit Congestion Notification (ECN) [RFC3168]. For the purpose 464 of this specification the (M)Start TC field is 8 bits long, where 465 the 6 most significant bits indicating the DS field to be matched 466 and the 2 least significant bit's value MUST be 468 (N)End TC - Traffic Class 470 If more than one contiguous TC values need to be matched then this 471 field can be used to indicate the end value of a range starting 472 from the value of the Start TC field. This field MUST NOT be 473 included unless the Start TC field is included. When this field 474 is included, it MUST be coded the same way as defined for (M). 475 When this field is included the receiver will match all of the 476 values between fields (M) and (N), inclusive of (M) and (N). 478 (O)Start NH - Next Header 480 This field identifies the first 8-bit next header value, from the 481 range of next header values to be matched, on data packets sent 482 from a corresponding node to the mobile node as seen by the home 483 agent. 485 (P)End NH - Next Header 486 If more than one contiguous next header values need to be matched 487 then this field can be used to indicate the end value of a range 488 starting from the value of the Start NH field. This field MUST 489 NOT be included unless the Start next header field is included. 490 When this field is included the receiver will match all of the 491 values between fields (O) and (P), inclusive of (O) and (P). 493 Reserved 495 Reserved for future use. These bits MUST be set to zero by the 496 sender and ignored by the receiver. 498 4. Security Considerations 500 This draft defines the format of the traffic selector field of a sub- 501 option defined for flow bindings [I-D.ietf-mext-flow-binding]. The 502 authors have not identified any security concerns pertaining to this 503 draft beyond what is already identified in 504 [I-D.ietf-mext-flow-binding]. 506 5. IANA Considerations 508 1) New TS format values from the "Traffic Selector Format" namespace 509 for the Traffic Selector sub-option defined in 510 [I-D.ietf-mext-flow-binding]. The following values are requested: 512 1 IPv4 Binary Traffic Selector 514 2 IPv6 Binary Traffic Selector 516 6. Aknowledgements 518 The authors would like to thank Patrick Stupar and Julien Laganier 519 for their contributions to this document. We would also like to 520 thank Benjamin Lim, Dave Craig, Patrick Stupar, and Basavaraj Patil 521 for their reviews and comments. 523 7. References 525 7.1. Normative References 527 [I-D.ietf-mext-flow-binding] 528 Tsirtsis, G., Soliman, H., Montavont, N., Giaretta, G., 529 and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and NEMO 530 Basic Support", draft-ietf-mext-flow-binding-10 (work in 531 progress), September 2010. 533 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 534 August 1980. 536 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 537 September 1981. 539 [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, 540 RFC 793, September 1981. 542 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 543 Requirement Levels", BCP 14, RFC 2119, March 1997. 545 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 546 (IPv6) Specification", RFC 2460, December 1998. 548 [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition 549 of Explicit Congestion Notification (ECN) to IP", 550 RFC 3168, September 2001. 552 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 553 RFC 4303, December 2005. 555 7.2. Informative References 557 [RFC3260] Grossman, D., "New Terminology and Clarifications for 558 Diffserv", RFC 3260, April 2002. 560 Authors' Addresses 562 George Tsirtsis 563 Qualcomm 565 Email: tsirtsis@qualcomm.com 567 Gerardo Giarreta 568 Qualcomm 570 Email: gerardog@qualcomm.com 572 Hesham Soliman 573 Elevate Technologies 575 Email: hesham@elevatemobile.com 577 Nicolas Montavont 578 Institut Telecom / Telecom Bretagne 579 2, rue de la chataigneraie 580 Cesson Sevigne 35576 581 France 583 Phone: (+33) 2 99 12 70 23 584 Email: nicolas.montavont@telecom-bretagne.eu 585 URI: http://www.rennes.enst-bretagne.fr/~nmontavo//