idnits 2.17.1 draft-polk-sip-rph-new-namespaces-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5 on line 569. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 546. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 553. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 559. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1, updated by RFC 4748 (on line 40), which is fine, but *also* found old RFC 3978, Section 5.4, paragraph 1 text on line 575. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 12 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCXXXX' is mentioned on line 302, but not defined Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIP Working Group James Polk 3 Internet-Draft Cisco Systems 4 Expires: January 9th, 2008 5 Intended Status: Standards Track 6 Updates RFC 4412 (if published) 8 New Session Initiation Protocol Resource-Priority Header 9 Namespaces for the Defense Information Systems Agency 10 draft-polk-sip-rph-new-namespaces-01 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of 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 25 months and may be updated, replaced, or obsoleted by other documents 26 at any time. It is inappropriate to use Internet-Drafts as 27 reference material or to cite them other than as "work in 28 progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on January 9th, 2008. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2007). 42 Abstract 44 This document creates additional Session Initiation Protocol 45 Resource-Priority header namespaces, to be IANA registered. This 46 document intends to update RFC 4412, as a Proposed Standard document 47 if published by the RFC-Editor. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1 Conventions used in this document . . . . . . . . . . . . 3 53 2. Creating an Implied RPH Namespace Delimiter . . . . . . . . . 3 54 2.1 One-Part or Two-Part Namespaces Do Not Change Anything . . 3 55 3. New RPH Namespaces Created . . . . . . . . . . . . . . . . . 4 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 57 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 58 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 59 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 60 7.1 Normative References . . . . . . . . . . . . . . . . . . 11 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . 11 62 Intellectual Property and Copyright Statements . . . . . . . 12 64 1. Introduction 66 The US Defense Information Systems Agency (DISA) is rolling out 67 their Session Initiation Protocol (SIP) based architecture at this 68 time. This network will require more Resource-Priority header (RPH) 69 namespaces than were defined, and IANA registered, in RFC 4412 70 [RFC4412]. The purpose of this document is to define these 71 additional namespaces. Each will be RFC 4412 defined preemption 72 based in nature, and will have the same 5 priority-values. However, 73 the need for additional namespaces is due to DISA's plan to have 74 multiple divisions within their network, which will limit the 75 ability of one of these divisions from preempting sessions 76 identified as being from another namespace division. A simple 77 example of this is within the DSN network, their may be a specific 78 namespace assigned to the US Army, one to the US Navy, one to the US 79 Air Force, and one to the US Marines. Each of these namespaces will 80 need to be identified as being part of the DSN network, so each 81 namespace will start with "dsn", such as 83 dsn-usarmy.priority-value 85 while another namespace within the dsn network is 87 dsn-usmarines.priority-value 89 and so on for the Navy and Air Force. 91 A unique application of these different namespaces is that they will 92 be able to gain preferential treatment only to SIP messages, and by 93 extension - the sessions established with like namespaces, but not 94 other messages/sessions with different namespaces. This is a local 95 policy decision that RFC 4412 considers to be fundamental. 97 In other words, messages with a namespace of dsn-usarmy may only 98 have their RPH priority-values compared for preferential treatment 99 to other dsn-usarmy namespaces, and not any other namespaces, unless 100 two or more (complete) namespaces are considered to be equivalent, 101 as defined in section 8 of RFC 4412 [RFC4412]. 103 This is all a matter of local policy. However, this policy is a 104 known requirement from DISA to support moving forward. 106 1.1 Conventions used in this document 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 109 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 110 "OPTIONAL" in this document are to be interpreted as described 111 in [RFC2119]. 113 2. Creating an Implied RPH Namespace Delimiter 115 As shown in section 1 of this document, the common ASCII character 116 separating one namespace from another is the '-' dash character. 117 The beginning 3 characters of each namespace created within this 118 document is "dsn". This document does not officially split the RPH 119 namespace into 3 parts, but RECOMMENDS another creating an IANA 120 registered RPH namespace, or one that is not IANA registered, avoid 121 the use of the '-' dash character unless they wish to have some 122 implementations process this character as a delimiter because 123 namespace parts. The DISA network, the original reason for the 124 creation of the SIP Resource-Priority header, intends to use this 125 character in this fashion. 127 2.1 One-Part or Two-Part Namespaces Do Not Change Anything 129 The fact that there is a '-' dash character does not change the fact 130 that everything on the left side of the '.' character is either the 131 same or different. This means this document does not create a 132 2-part namespace, and by extension, a 3-part Resource-Priority 133 header value. The simple fact that anything has changed on the left 134 side of the '.' character means there is a new namespace to process, 135 regardless of whether this difference is on the right or left side 136 of a '-' dash character within what RFC 4412 defines as the 137 namespace field within the RPH. 139 That said, code in a SIP entity can look for the '-' dash character 140 to identify a virtual delimiter to be used however that 141 implementation wants. This is also viewed as an effective visual 142 delimiter for anyone looking at the RPH namespace to see which 143 subgroup within a primary domain the namespace belongs to (or 144 within). 146 The purpose of the characters on the left side of the '-' dash 147 character in the RPH namespace is not binding, but is generally 148 understood to be the domain identifier part of the namespace. 150 Equally, the purpose of the characters on the right side of the '-' 151 dash character in the RPH namespace is also not binding, but is 152 generally understood to be the sub-domain identifier. Looking at 153 the namespaces shown in section 1 of this document, DISA is defining 154 all of these new namespaces to be within the "dsn" domain (the first 155 part of all the namespaces here), of which all users within the US 156 Army will communicate within. All the users within the US Navy, US 157 Air Force and US Marines also will only communicate within the "dsn" 158 domain. Thus the subdomain for these 4 groups are "usarmy", 159 "usnavy", "usairforce", and "usmarines". This scenario creates four 160 new RPH namespaces: 162 dsn-usarmy 163 dsn-usnavy 164 dsn-usairforce 165 dsn-usmarines 167 that can be viewed as being part of the same network-ID ("dsn") and 168 different subdomains, called a precedence-domain, which are 169 separated by a '-' dash character. The '-' dash character is part of 170 the overall single namespace of each. 172 If any one (or more) character(s) in a namespace is different, it is 173 to be considered a different namespace. For example, "dsn-usarmy" 174 is a different namespace than "dsn-usarmy1", which is different than 175 "dsn-usarmy2". The fact that the differences between these 176 namespaces are on the right side of the '-' dash character means 177 SIP, through RFC 4412, interprets the difference to be a namespace 178 difference. Hence, a 417 (Unknown Namespace) is the appropriate 179 response to a Resource-Priority header with an unrecognized 180 namespace. The same is true for a comparison between these 181 namespaces: "dsn-usarmy" and "dsn2-usarmy". 183 3. New RPH Namespaces Created 185 The following 50 SIP Resource Priority header namespaces are created 186 by this document: 188 dsn-000000 dsn-000010 dsn-000020 dsn-000030 189 dsn-000001 dsn-000011 dsn-000021 dsn-000031 190 dsn-000002 dsn-000012 dsn-000022 191 dsn-000003 dsn-000013 dsn-000023 192 dsn-000004 dsn-000014 dsn-000024 193 dsn-000005 dsn-000015 dsn-000025 194 dsn-000006 dsn-000016 dsn-000026 195 dsn-000007 dsn-000017 dsn-000027 196 dsn-000008 dsn-000018 dsn-000028 197 dsn-000009 dsn-000019 dsn-000029 198 dsn-00000A dsn-00001A dsn-00002A 199 dsn-00000B dsn-00001B dsn-00002B 200 dsn-00000C dsn-00001C dsn-00002C 201 dsn-00000D dsn-00001D dsn-00002D 202 dsn-00000E dsn-00001E dsn-00002E 203 dsn-00000F dsn-00001F dsn-00002F 205 Each namespace listed above will have the same 5 priority-levels: 207 .0 (lowest priority) 208 .2 209 .4 210 .6 211 .8 (highest priority) 213 As stated earlier, one namespace will not be considered for 214 preferential treatment over another namespace unless local policy 215 has configured a SIP entity processing two messages (each with 216 different namespaces) as being equivalent (see section 8 of RFC 4412 217 [RFC4412] for this detailed). 219 The reality of this is, a message (or a call) with this RPH field 220 of: 222 dsn-000001.8 224 for example, will not have any preferential treatment over a 225 message, for example, with this RPH field: 227 dsn-000010.0 229 This is currently the policy within DISA. 231 As stated in Section 9 of RFC 4412 [RFC4412], an IANA registered 232 namespace SHOULD NOT change the number, and MUST NOT change the 233 relative priority order, of its assigned priority-values. 235 4. IANA Considerations 237 Abiding by the rules established within RFC 4412 [RFC4412], this is 238 a Standards-Track document registering new SIP Resource-Priority 239 header namespaces, and their associated priority-values and intended 240 algorithms. 242 4.1 IANA Resource-Priority Namespace Registration 244 Within the "Resource-Priority Namespaces" registry in the 245 sip-parameters section of IANA, the following table lists the new 246 RPH namespaces registered by this document (NOTE: RFCXXXX is to be 247 replaced by this document's RFC number if this document is published 248 by the RFC-Editor): 250 Intended New warn- New resp. 251 Namespace Levels Algorithm code code Reference 252 ---------- ------ ------------ --------- --------- --------- 253 dsn-000000 5 preemption no no [RFCXXXX] 254 dsn-000001 5 preemption no no [RFCXXXX] 255 dsn-000002 5 preemption no no [RFCXXXX] 256 dsn-000003 5 preemption no no [RFCXXXX] 257 dsn-000004 5 preemption no no [RFCXXXX] 258 dsn-000005 5 preemption no no [RFCXXXX] 259 dsn-000006 5 preemption no no [RFCXXXX] 260 dsn-000007 5 preemption no no [RFCXXXX] 261 dsn-000008 5 preemption no no [RFCXXXX] 262 dsn-000009 5 preemption no no [RFCXXXX] 263 dsn-00000A 5 preemption no no [RFCXXXX] 264 dsn-00000B 5 preemption no no [RFCXXXX] 265 dsn-00000C 5 preemption no no [RFCXXXX] 266 dsn-00000D 5 preemption no no [RFCXXXX] 267 dsn-00000E 5 preemption no no [RFCXXXX] 268 dsn-00000F 5 preemption no no [RFCXXXX] 269 dsn-000010 5 preemption no no [RFCXXXX] 270 dsn-000011 5 preemption no no [RFCXXXX] 271 dsn-000012 5 preemption no no [RFCXXXX] 272 dsn-000013 5 preemption no no [RFCXXXX] 273 dsn-000014 5 preemption no no [RFCXXXX] 274 dsn-000015 5 preemption no no [RFCXXXX] 275 dsn-000016 5 preemption no no [RFCXXXX] 276 dsn-000017 5 preemption no no [RFCXXXX] 277 dsn-000018 5 preemption no no [RFCXXXX] 278 dsn-000019 5 preemption no no [RFCXXXX] 279 dsn-00001A 5 preemption no no [RFCXXXX] 280 dsn-00001B 5 preemption no no [RFCXXXX] 281 dsn-00001C 5 preemption no no [RFCXXXX] 282 dsn-00001D 5 preemption no no [RFCXXXX] 283 dsn-00001E 5 preemption no no [RFCXXXX] 284 dsn-00001F 5 preemption no no [RFCXXXX] 285 dsn-000020 5 preemption no no [RFCXXXX] 286 dsn-000021 5 preemption no no [RFCXXXX] 287 dsn-000022 5 preemption no no [RFCXXXX] 288 dsn-000023 5 preemption no no [RFCXXXX] 289 dsn-000024 5 preemption no no [RFCXXXX] 290 dsn-000025 5 preemption no no [RFCXXXX] 291 dsn-000026 5 preemption no no [RFCXXXX] 292 dsn-000027 5 preemption no no [RFCXXXX] 293 dsn-000028 5 preemption no no [RFCXXXX] 294 dsn-000029 5 preemption no no [RFCXXXX] 295 dsn-00002A 5 preemption no no [RFCXXXX] 296 dsn-00002B 5 preemption no no [RFCXXXX] 297 dsn-00002C 5 preemption no no [RFCXXXX] 298 dsn-00002D 5 preemption no no [RFCXXXX] 299 dsn-00002E 5 preemption no no [RFCXXXX] 300 dsn-00002F 5 preemption no no [RFCXXXX] 301 dsn-000030 5 preemption no no [RFCXXXX] 302 dsn-000031 5 preemption no no [RFCXXXX] 304 4.2 IANA Priority-Value Registrations 306 Within the "Resource-Priority Priority-values" registry in the sip- 307 parameters section of IANA, the list of priority-values for each of 308 the newly created RPH namespaces from section 4.1 of this document, 309 prioritized least to greatest, is registered by the following: 311 Namespace: dsn-000000 312 Reference: RFCXXXX (this document) 313 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 315 Namespace: dsn-000001 316 Reference: RFCXXXX (this document) 317 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 319 Namespace: dsn-000002 320 Reference: RFCXXXX (this document) 321 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 323 Namespace: dsn-000003 324 Reference: RFCXXXX (this document) 325 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 327 Namespace: dsn-000004 328 Reference: RFCXXXX (this document) 329 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 331 Namespace: dsn-000005 332 Reference: RFCXXXX (this document) 333 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 335 Namespace: dsn-000006 336 Reference: RFCXXXX (this document) 337 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 339 Namespace: dsn-000007 340 Reference: RFCXXXX (this document) 341 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 343 Namespace: dsn-000008 344 Reference: RFCXXXX (this document) 345 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 347 Namespace: dsn-000009 348 Reference: RFCXXXX (this document) 349 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 350 Namespace: dsn-00000A 351 Reference: RFCXXXX (this document) 352 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 354 Namespace: dsn-00000B 355 Reference: RFCXXXX (this document) 356 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 358 Namespace: dsn-00000C 359 Reference: RFCXXXX (this document) 360 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 362 Namespace: dsn-00000D 363 Reference: RFCXXXX (this document) 364 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 366 Namespace: dsn-00000E 367 Reference: RFCXXXX (this document) 368 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 370 Namespace: dsn-00000F 371 Reference: RFCXXXX (this document) 372 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 374 Namespace: dsn-000010 375 Reference: RFCXXXX (this document) 376 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 378 Namespace: dsn-000011 379 Reference: RFCXXXX (this document) 380 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 382 Namespace: dsn-000012 383 Reference: RFCXXXX (this document) 384 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 386 Namespace: dsn-000013 387 Reference: RFCXXXX (this document) 388 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 390 Namespace: dsn-000014 391 Reference: RFCXXXX (this document) 392 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 394 Namespace: dsn-000015 395 Reference: RFCXXXX (this document) 396 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 398 Namespace: dsn-000016 399 Reference: RFCXXXX (this document) 400 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 401 Namespace: dsn-000017 402 Reference: RFCXXXX (this document) 403 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 405 Namespace: dsn-000018 406 Reference: RFCXXXX (this document) 407 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 409 Namespace: dsn-000019 410 Reference: RFCXXXX (this document) 411 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 413 Namespace: dsn-00001A 414 Reference: RFCXXXX (this document) 415 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 417 Namespace: dsn-00001B 418 Reference: RFCXXXX (this document) 419 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 421 Namespace: dsn-00001C 422 Reference: RFCXXXX (this document) 423 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 425 Namespace: dsn-00001D 426 Reference: RFCXXXX (this document) 427 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 429 Namespace: dsn-00001E 430 Reference: RFCXXXX (this document) 431 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 433 Namespace: dsn-00001F 434 Reference: RFCXXXX (this document) 435 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 437 Namespace: dsn-000020 438 Reference: RFCXXXX (this document) 439 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 441 Namespace: dsn-000021 442 Reference: RFCXXXX (this document) 443 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 445 Namespace: dsn-000022 446 Reference: RFCXXXX (this document) 447 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 449 Namespace: dsn-000023 450 Reference: RFCXXXX (this document) 451 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 452 Namespace: dsn-000024 453 Reference: RFCXXXX (this document) 454 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 456 Namespace: dsn-000025 457 Reference: RFCXXXX (this document) 458 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 460 Namespace: dsn-000026 461 Reference: RFCXXXX (this document) 462 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 464 Namespace: dsn-000027 465 Reference: RFCXXXX (this document) 466 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 468 Namespace: dsn-000028 469 Reference: RFCXXXX (this document) 470 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 472 Namespace: dsn-000029 473 Reference: RFCXXXX (this document) 474 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 476 Namespace: dsn-00002A 477 Reference: RFCXXXX (this document) 478 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 480 Namespace: dsn-00002B 481 Reference: RFCXXXX (this document) 482 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 484 Namespace: dsn-00002C 485 Reference: RFCXXXX (this document) 486 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 488 Namespace: dsn-00002D 489 Reference: RFCXXXX (this document) 490 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 492 Namespace: dsn-00002E 493 Reference: RFCXXXX (this document) 494 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 496 Namespace: dsn-00002F 497 Reference: RFCXXXX (this document) 498 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 500 Namespace: dsn-000030 501 Reference: RFCXXXX (this document) 502 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 503 Namespace: dsn-000031 504 Reference: RFCXXXX (this document) 505 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 507 5. Security Considerations 509 This document has the same Security Considerations as RFC 4412. 511 6. Acknowledgements 513 To Jeff Hewett for his helpful guidance in this effort. 515 7. References 517 7.1 Normative References 519 [RFC4412] Schulzrinne, H., Polk, J., "Communications Resource 520 Priority for the Session Initiation Protocol (SIP)", RFC 521 4411, Feb 2006 523 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 524 Requirement Levels", RFC 2119, March 1997 526 Author's Address 528 James M. Polk 529 3913 Treemont Circle 530 Colleyville, Texas 76034 531 USA 533 Phone: +1-817-271-3552 534 Fax: none 535 Email: jmpolk@cisco.com 537 Intellectual Property Statement 539 The IETF takes no position regarding the validity or scope of any 540 Intellectual Property Rights or other rights that might be claimed 541 to pertain to the implementation or use of the technology described 542 in this document or the extent to which any license under such 543 rights might or might not be available; nor does it represent that 544 it has made any independent effort to identify any such rights. 545 Information on the procedures with respect to rights in RFC 546 documents can be found in BCP 78 and BCP 79. 548 Copies of IPR disclosures made to the IETF Secretariat and any 549 assurances of licenses to be made available, or the result of an 550 attempt made to obtain a general license or permission for the use 551 of such proprietary rights by implementers or users of this 552 specification can be obtained from the IETF on-line IPR repository 553 at http://www.ietf.org/ipr. 555 The IETF invites any interested party to bring to its attention any 556 copyrights, patents or patent applications, or other proprietary 557 rights that may cover technology that may be required to implement 558 this standard. Please address the information to the IETF at 559 ietf-ipr@ietf.org. 561 Disclaimer of Validity 563 This document and the information contained herein are provided on 564 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 565 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 566 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 567 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 568 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 569 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 571 Copyright Statement 573 Copyright (C) The Internet Society (2007). This document is subject 574 to the rights, licenses and restrictions contained in BCP 78, and 575 except as set forth therein, the authors retain all their rights. 577 Acknowledgment 579 Funding for the RFC Editor function is provided by the IETF 580 Administrative Support Activity (IASA).