idnits 2.17.1 draft-ietf-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 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 552. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 563. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 570. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 576. 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 IETF Trust Copyright Line does not match the current year == Unrecognized Status in 'Intended Status: Standards Track (as PS)', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 248, but not defined Summary: 1 error (**), 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: May 17th, 2008 November 17th, 2007 5 Intended Status: Standards Track (as PS) 7 IANA Registration of New Session Initiation Protocol (SIP) 8 Resource-Priority Header Namespaces 9 draft-ietf-sip-rph-new-namespaces-01.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other documents 25 at any time. It is inappropriate to use Internet-Drafts as 26 reference material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on May 17th, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 This document creates additional Session Initiation Protocol 43 Resource-Priority header namespaces, to be IANA registered. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 48 1.1 Conventions used in this document . . . . . . . . . . . . 3 49 2. New RPH Namespaces Created . . . . . . . . . . . . . . . . . 3 50 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 51 3.1 IANA Resource-Priority Namespace Registration . . . . . . . 5 52 3.2 IANA Priority-Value Registrations . . . . . . . . . . . . 6 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 55 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 56 6.1 Normative References . . . . . . . . . . . . . . . . . . 11 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . 11 58 Intellectual Property and Copyright Statements . . . . . . . 11 60 1. Introduction 62 The US Defense Information Systems Agency (DISA) is rolling out 63 their Session Initiation Protocol (SIP) based architecture at this 64 time. This network will require more Resource-Priority header (RPH) 65 namespaces than were defined, and IANA registered, in RFC 4412 66 [RFC4412]. The purpose of this document is to define these 67 additional namespaces. Each will be RFC 4412 defined as preemption 68 based in nature, and will have the same 9 priority-values. 70 DISA has a requirement to be able to assign different RPH namespaces 71 to different units of differing sizes throughout their networks. 72 Examples of this may be 74 - each branch of service (army, navy, air force, marines, coast 75 guard) 77 - some departments within the government (Homeland Security, 78 Commerce, Treasury) 80 - plus have temporary assignments to individual units of varying 81 sizes 83 These temporary assignments might be combinations of smaller units 84 involving several branches of service operating as one unit (say, 85 one task force, which is separate than the branch of service), or a 86 single commando unit requiring special treatment for a short period 87 of time, making it appear separate from the branch of service they 88 are from. 90 Providing DISA with a pool of namespaces for fine grained RPH 91 assignment(s) allows them the flexibility they need for their 92 mission requirements. One can imagine due to their sheer size and 93 separation of purpose, they can easily utilize a significant number 94 of namespaces within their networks. This is the reason for the 95 assignment of so many new namespaces, which seems to deviate from 96 guidance in RFC 4412 to have a few namespaces as possible. 98 This document makes no changes to SIP, just adds IANA registered RPH 99 namespaces for its use. 101 1.1 Conventions used in this document 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 104 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 105 "OPTIONAL" in this document are to be interpreted as described 106 in [RFC2119]. 108 2. New RPH Namespaces Created 110 The following 50 SIP Resource Priority header namespaces are created 111 by this document: 113 dsn-000000 dsn-000010 dsn-000020 dsn-000030 114 dsn-000001 dsn-000011 dsn-000021 dsn-000031 115 dsn-000002 dsn-000012 dsn-000022 116 dsn-000003 dsn-000013 dsn-000023 117 dsn-000004 dsn-000014 dsn-000024 118 dsn-000005 dsn-000015 dsn-000025 119 dsn-000006 dsn-000016 dsn-000026 120 dsn-000007 dsn-000017 dsn-000027 121 dsn-000008 dsn-000018 dsn-000028 122 dsn-000009 dsn-000019 dsn-000029 123 dsn-00000A dsn-00001A dsn-00002A 124 dsn-00000B dsn-00001B dsn-00002B 125 dsn-00000C dsn-00001C dsn-00002C 126 dsn-00000D dsn-00001D dsn-00002D 127 dsn-00000E dsn-00001E dsn-00002E 128 dsn-00000F dsn-00001F dsn-00002F 130 Each namespace listed above is wholly different, unless one or more 131 sets of namespaces are aggregated according to the rules of section 132 8, within RFC 4412. 134 These aggregates of two or more namespaces, that are to be 135 considered equivalent during treatment, can be a set of any IANA 136 registered RPH namespaces, not just adjacent namespaces. 138 Each namespace listed above will have the same 9 priority-levels: 140 .0 (lowest priority) 141 .1 142 .2 143 .3 144 .4 145 .5 146 .6 147 .7 148 .8 149 .9 (highest priority) 151 According to the rules established in RFC 4412 [RFC4412], 152 priority-values have a relative order for preferential treatment, 153 unless one or more consecutive groups of priority-values are to be 154 considered equivalent (i.e., first-received, first treated). 156 Thus, a message (or a call) with the following Resource-Priority 157 header value: 159 dsn-000001.8 161 for example, MUST NOT ever receive preferential treatment over a 162 message, for example, with this Resource-Priority header value: 164 dsn-000010.0 166 because they are two difference namespaces, unless the namespaces 168 dsn-000001 and dsn-000010 170 are configured as equivalent namespaces (according to section 8 of 171 RFC 4412). 173 The dash '-' character is just like any other character, and is not 174 to be considered a delimiter in any official way within any 175 namespace here. This MAY change in future efforts. 177 As stated in Section 9 of RFC 4412 [RFC4412], an IANA registered 178 namespace SHOULD NOT change the number, and MUST NOT change the 179 relative priority order, of its assigned priority-values. 181 3. IANA Considerations 183 Abiding by the rules established within RFC 4412 [RFC4412], this is 184 a Standards-Track document registering new SIP Resource-Priority 185 header namespaces, and their associated priority-values and intended 186 algorithms. 188 3.1 IANA Resource-Priority Namespace Registration 190 Within the "Resource-Priority Namespaces" registry in the 191 sip-parameters section of IANA, the following table lists the new 192 RPH namespaces registered by this document (NOTE: 'RFCXXXX' is to be 193 replaced by this document's RFC number if this document is published 194 by the RFC-Editor): 196 Intended New warn- New resp. 197 Namespace Levels Algorithm code code Reference 198 ---------- ------ ------------ --------- --------- --------- 199 dsn-000000 10 preemption no no [RFCXXXX] 200 dsn-000001 10 preemption no no [RFCXXXX] 201 dsn-000002 10 preemption no no [RFCXXXX] 202 dsn-000003 10 preemption no no [RFCXXXX] 203 dsn-000004 10 preemption no no [RFCXXXX] 204 dsn-000005 10 preemption no no [RFCXXXX] 205 dsn-000006 10 preemption no no [RFCXXXX] 206 dsn-000007 10 preemption no no [RFCXXXX] 207 dsn-000008 10 preemption no no [RFCXXXX] 208 dsn-000009 10 preemption no no [RFCXXXX] 209 dsn-00000A 10 preemption no no [RFCXXXX] 210 dsn-00000B 10 preemption no no [RFCXXXX] 211 dsn-00000C 10 preemption no no [RFCXXXX] 212 dsn-00000D 10 preemption no no [RFCXXXX] 213 dsn-00000E 10 preemption no no [RFCXXXX] 214 dsn-00000F 10 preemption no no [RFCXXXX] 215 dsn-000010 10 preemption no no [RFCXXXX] 216 dsn-000011 10 preemption no no [RFCXXXX] 217 dsn-000012 10 preemption no no [RFCXXXX] 218 dsn-000013 10 preemption no no [RFCXXXX] 219 dsn-000014 10 preemption no no [RFCXXXX] 220 dsn-000015 10 preemption no no [RFCXXXX] 221 dsn-000016 10 preemption no no [RFCXXXX] 222 dsn-000017 10 preemption no no [RFCXXXX] 223 dsn-000018 10 preemption no no [RFCXXXX] 224 dsn-000019 10 preemption no no [RFCXXXX] 225 dsn-00001A 10 preemption no no [RFCXXXX] 226 dsn-00001B 10 preemption no no [RFCXXXX] 227 dsn-00001C 10 preemption no no [RFCXXXX] 228 dsn-00001D 10 preemption no no [RFCXXXX] 229 dsn-00001E 10 preemption no no [RFCXXXX] 230 dsn-00001F 10 preemption no no [RFCXXXX] 231 dsn-000020 10 preemption no no [RFCXXXX] 232 dsn-000021 10 preemption no no [RFCXXXX] 233 dsn-000022 10 preemption no no [RFCXXXX] 234 dsn-000023 10 preemption no no [RFCXXXX] 235 dsn-000024 10 preemption no no [RFCXXXX] 236 dsn-000025 10 preemption no no [RFCXXXX] 237 dsn-000026 10 preemption no no [RFCXXXX] 238 dsn-000027 10 preemption no no [RFCXXXX] 239 dsn-000028 10 preemption no no [RFCXXXX] 240 dsn-000029 10 preemption no no [RFCXXXX] 241 dsn-00002A 10 preemption no no [RFCXXXX] 242 dsn-00002B 10 preemption no no [RFCXXXX] 243 dsn-00002C 10 preemption no no [RFCXXXX] 244 dsn-00002D 10 preemption no no [RFCXXXX] 245 dsn-00002E 10 preemption no no [RFCXXXX] 246 dsn-00002F 10 preemption no no [RFCXXXX] 247 dsn-000030 10 preemption no no [RFCXXXX] 248 dsn-000031 10 preemption no no [RFCXXXX] 250 3.2 IANA Priority-Value Registrations 252 Within the "Resource-Priority Priority-values" registry in the sip- 253 parameters section of IANA, the list of priority-values for each of 254 the newly created RPH namespaces from section 4.1 of this document, 255 prioritized least to greatest, is registered by the following: 257 Namespace: dsn-000000 258 Reference: RFCXXXX (this document) 259 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 260 "6", "7", "8", "9" 262 Namespace: dsn-000001 263 Reference: RFCXXXX (this document) 264 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 265 "6", "7", "8", "9" 267 Namespace: dsn-000002 268 Reference: RFCXXXX (this document) 269 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 270 "6", "7", "8", "9" 272 Namespace: dsn-000003 273 Reference: RFCXXXX (this document) 274 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 275 "6", "7", "8", "9" 277 Namespace: dsn-000004 278 Reference: RFCXXXX (this document) 279 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 280 "6", "7", "8", "9" 282 Namespace: dsn-000005 283 Reference: RFCXXXX (this document) 284 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 285 "6", "7", "8", "9" 287 Namespace: dsn-000006 288 Reference: RFCXXXX (this document) 289 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 290 "6", "7", "8", "9" 291 Namespace: dsn-000007 292 Reference: RFCXXXX (this document) 293 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 294 "6", "7", "8", "9" 296 Namespace: dsn-000008 297 Reference: RFCXXXX (this document) 298 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 299 "6", "7", "8", "9" 301 Namespace: dsn-000009 302 Reference: RFCXXXX (this document) 303 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 304 "6", "7", "8", "9" 306 Namespace: dsn-00000A 307 Reference: RFCXXXX (this document) 308 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 309 "6", "7", "8", "9" 311 Namespace: dsn-00000B 312 Reference: RFCXXXX (this document) 313 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 314 "6", "7", "8", "9" 316 Namespace: dsn-00000C 317 Reference: RFCXXXX (this document) 318 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 319 "6", "7", "8", "9" 321 Namespace: dsn-00000D 322 Reference: RFCXXXX (this document) 323 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 324 "6", "7", "8", "9" 326 Namespace: dsn-00000E 327 Reference: RFCXXXX (this document) 328 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 329 "6", "7", "8", "9" 331 Namespace: dsn-00000F 332 Reference: RFCXXXX (this document) 333 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 334 "6", "7", "8", "9" 336 Namespace: dsn-000010 337 Reference: RFCXXXX (this document) 338 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 339 "6", "7", "8", "9" 341 Namespace: dsn-000011 342 Reference: RFCXXXX (this document) 343 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 344 "6", "7", "8", "9" 346 Namespace: dsn-000012 347 Reference: RFCXXXX (this document) 348 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 349 "6", "7", "8", "9" 351 Namespace: dsn-000013 352 Reference: RFCXXXX (this document) 353 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 354 "6", "7", "8", "9" 356 Namespace: dsn-000014 357 Reference: RFCXXXX (this document) 358 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 359 "6", "7", "8", "9" 361 Namespace: dsn-000015 362 Reference: RFCXXXX (this document) 363 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 364 "6", "7", "8", "9" 366 Namespace: dsn-000016 367 Reference: RFCXXXX (this document) 368 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 369 "6", "7", "8", "9" 371 Namespace: dsn-000017 372 Reference: RFCXXXX (this document) 373 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 374 "6", "7", "8", "9" 376 Namespace: dsn-000018 377 Reference: RFCXXXX (this document) 378 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 379 "6", "7", "8", "9" 381 Namespace: dsn-000019 382 Reference: RFCXXXX (this document) 383 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 384 "6", "7", "8", "9" 386 Namespace: dsn-00001A 387 Reference: RFCXXXX (this document) 388 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 389 "6", "7", "8", "9" 391 Namespace: dsn-00001B 392 Reference: RFCXXXX (this document) 393 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 394 "6", "7", "8", "9" 395 Namespace: dsn-00001C 396 Reference: RFCXXXX (this document) 397 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 398 "6", "7", "8", "9" 400 Namespace: dsn-00001D 401 Reference: RFCXXXX (this document) 402 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 403 "6", "7", "8", "9" 405 Namespace: dsn-00001E 406 Reference: RFCXXXX (this document) 407 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 408 "6", "7", "8", "9" 410 Namespace: dsn-00001F 411 Reference: RFCXXXX (this document) 412 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 413 "6", "7", "8", "9" 415 Namespace: dsn-000020 416 Reference: RFCXXXX (this document) 417 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 418 "6", "7", "8", "9" 420 Namespace: dsn-000021 421 Reference: RFCXXXX (this document) 422 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 423 "6", "7", "8", "9" 425 Namespace: dsn-000022 426 Reference: RFCXXXX (this document) 427 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 428 "6", "7", "8", "9" 430 Namespace: dsn-000023 431 Reference: RFCXXXX (this document) 432 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 433 "6", "7", "8", "9" 435 Namespace: dsn-000024 436 Reference: RFCXXXX (this document) 437 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 438 "6", "7", "8", "9" 440 Namespace: dsn-000025 441 Reference: RFCXXXX (this document) 442 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 443 "6", "7", "8", "9" 445 Namespace: dsn-000026 446 Reference: RFCXXXX (this document) 447 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 448 "6", "7", "8", "9" 450 Namespace: dsn-000027 451 Reference: RFCXXXX (this document) 452 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 453 "6", "7", "8", "9" 455 Namespace: dsn-000028 456 Reference: RFCXXXX (this document) 457 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 458 "6", "7", "8", "9" 460 Namespace: dsn-000029 461 Reference: RFCXXXX (this document) 462 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 463 "6", "7", "8", "9" 465 Namespace: dsn-00002A 466 Reference: RFCXXXX (this document) 467 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 468 "6", "7", "8", "9" 470 Namespace: dsn-00002B 471 Reference: RFCXXXX (this document) 472 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 473 "6", "7", "8", "9" 475 Namespace: dsn-00002C 476 Reference: RFCXXXX (this document) 477 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 478 "6", "7", "8", "9" 480 Namespace: dsn-00002D 481 Reference: RFCXXXX (this document) 482 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 483 "6", "7", "8", "9" 485 Namespace: dsn-00002E 486 Reference: RFCXXXX (this document) 487 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 488 "6", "7", "8", "9" 490 Namespace: dsn-00002F 491 Reference: RFCXXXX (this document) 492 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 493 "6", "7", "8", "9" 495 Namespace: dsn-000030 496 Reference: RFCXXXX (this document) 497 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 498 "6", "7", "8", "9" 500 Namespace: dsn-000031 501 Reference: RFCXXXX (this document) 502 Priority-Values (least to greatest): "0", "1", "2", "3", "4", "5", 503 "6", "7", "8", "9" 505 4. Security Considerations 507 This document has the same Security Considerations as RFC 4412. 509 5. Acknowledgements 511 To Jeff Hewett for his helpful guidance in this effort. Thanks to 512 Janet Gunn, John Rosenberg, Joel Halpern and Henning Schulzrinne for 513 their comments. 515 6. References 517 6.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 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 Full Copyright Statement 539 Copyright (C) The IETF Trust (2007). 541 This document is subject to the rights, licenses and restrictions 542 contained in BCP 78, and except as set forth therein, the authors 543 retain all their rights. 545 This document and the information contained herein are provided on 546 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 547 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 548 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 549 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 550 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 551 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 552 FOR A PARTICULAR PURPOSE. 554 Intellectual Property 556 The IETF takes no position regarding the validity or scope of any 557 Intellectual Property Rights or other rights that might be claimed 558 to pertain to the implementation or use of the technology described 559 in this document or the extent to which any license under such 560 rights might or might not be available; nor does it represent that 561 it has made any independent effort to identify any such rights. 562 Information on the procedures with respect to rights in RFC 563 documents can be found in BCP 78 and BCP 79. 565 Copies of IPR disclosures made to the IETF Secretariat and any 566 assurances of licenses to be made available, or the result of an 567 attempt made to obtain a general license or permission for the use 568 of such proprietary rights by implementers or users of this 569 specification can be obtained from the IETF on-line IPR repository 570 at http://www.ietf.org/ipr. 572 The IETF invites any interested party to bring to its attention any 573 copyrights, patents or patent applications, or other proprietary 574 rights that may cover technology that may be required to implement 575 this standard. Please address the information to the IETF at 576 ietf-ipr@ietf.org. 578 Acknowledgment 580 Funding for the RFC Editor function is provided by the IETF 581 Administrative Support Activity (IASA).