idnits 2.17.1 draft-ietf-sip-rph-new-namespaces-00.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 467. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 478. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 485. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 491. 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 10 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 213, 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: April 16th, 2008 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-00 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 April 16th, 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 . . . . . . . . . . . . 2 49 2. New RPH Namespaces Created . . . . . . . . . . . . . . . . . 2 50 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 51 3.1 IANA Resource-Priority Namespace Registration . . . . . . . 4 52 3.2 IANA Priority-Value Registrations . . . . . . . . . . . . 5 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 55 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 56 6.1 Normative References . . . . . . . . . . . . . . . . . . 9 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . 9 58 Intellectual Property and Copyright Statements . . . . . . . 9 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 preemption 68 based in nature, and will have the same 5 priority-values. 70 One aspect within DISA's network will be to allow a session or call 71 to only preempt another call established with the same 72 Resource-Priority header namespace, but no other namespace. 74 In other words, messages with a namespace of dsn-X may only 75 have their RPH priority-values compared for preferential treatment 76 to other dsn-X namespaces, and not any other namespaces, unless 77 two or more (complete) namespaces are considered to be equivalent, 78 as defined in section 8 of RFC 4412 [RFC4412]. 80 This is all a matter of local policy. However, this policy is a 81 known requirement from DISA to support moving forward. 83 1.1 Conventions used in this document 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 86 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 87 "OPTIONAL" in this document are to be interpreted as described 88 in [RFC2119]. 90 2. New RPH Namespaces Created 92 The following 50 SIP Resource Priority header namespaces are created 93 by this document: 95 dsn-000000 dsn-000010 dsn-000020 dsn-000030 96 dsn-000001 dsn-000011 dsn-000021 dsn-000031 97 dsn-000002 dsn-000012 dsn-000022 98 dsn-000003 dsn-000013 dsn-000023 99 dsn-000004 dsn-000014 dsn-000024 100 dsn-000005 dsn-000015 dsn-000025 101 dsn-000006 dsn-000016 dsn-000026 102 dsn-000007 dsn-000017 dsn-000027 103 dsn-000008 dsn-000018 dsn-000028 104 dsn-000009 dsn-000019 dsn-000029 105 dsn-00000A dsn-00001A dsn-00002A 106 dsn-00000B dsn-00001B dsn-00002B 107 dsn-00000C dsn-00001C dsn-00002C 108 dsn-00000D dsn-00001D dsn-00002D 109 dsn-00000E dsn-00001E dsn-00002E 110 dsn-00000F dsn-00001F dsn-00002F 112 Each namespace listed above will have the same 5 priority-levels: 114 .0 (lowest priority) 115 .2 116 .4 117 .6 118 .8 (highest priority) 120 A namespace from the above list will not be considered for 121 preferential treatment over another namespace unless local policy 122 has configured a SIP entity processing two messages (each with 123 different namespaces) as being equivalent (see section 8 of RFC 4412 124 [RFC4412] for this detailed). 126 The reality of this is, a message (or a call) with the following 127 Resource-Priority header value: 129 dsn-000001.8 131 for example, will not have any preferential treatment over a 132 message, for example, with this Resource-Priority header value: 134 dsn-000010.0 136 because they are two difference namespaces. 138 The dash '-' character is just like any other character, and is not 139 to be considered a delimiter in any official way within any 140 namespace here. This MAY change in future efforts. 142 As stated in Section 9 of RFC 4412 [RFC4412], an IANA registered 143 namespace SHOULD NOT change the number, and MUST NOT change the 144 relative priority order, of its assigned priority-values. 146 3. IANA Considerations 148 Abiding by the rules established within RFC 4412 [RFC4412], this is 149 a Standards-Track document registering new SIP Resource-Priority 150 header namespaces, and their associated priority-values and intended 151 algorithms. 153 3.1 IANA Resource-Priority Namespace Registration 155 Within the "Resource-Priority Namespaces" registry in the 156 sip-parameters section of IANA, the following table lists the new 157 RPH namespaces registered by this document (NOTE: 'RFCXXXX' is to be 158 replaced by this document's RFC number if this document is published 159 by the RFC-Editor): 161 Intended New warn- New resp. 162 Namespace Levels Algorithm code code Reference 163 ---------- ------ ------------ --------- --------- --------- 164 dsn-000000 5 preemption no no [RFCXXXX] 165 dsn-000001 5 preemption no no [RFCXXXX] 166 dsn-000002 5 preemption no no [RFCXXXX] 167 dsn-000003 5 preemption no no [RFCXXXX] 168 dsn-000004 5 preemption no no [RFCXXXX] 169 dsn-000005 5 preemption no no [RFCXXXX] 170 dsn-000006 5 preemption no no [RFCXXXX] 171 dsn-000007 5 preemption no no [RFCXXXX] 172 dsn-000008 5 preemption no no [RFCXXXX] 173 dsn-000009 5 preemption no no [RFCXXXX] 174 dsn-00000A 5 preemption no no [RFCXXXX] 175 dsn-00000B 5 preemption no no [RFCXXXX] 176 dsn-00000C 5 preemption no no [RFCXXXX] 177 dsn-00000D 5 preemption no no [RFCXXXX] 178 dsn-00000E 5 preemption no no [RFCXXXX] 179 dsn-00000F 5 preemption no no [RFCXXXX] 180 dsn-000010 5 preemption no no [RFCXXXX] 181 dsn-000011 5 preemption no no [RFCXXXX] 182 dsn-000012 5 preemption no no [RFCXXXX] 183 dsn-000013 5 preemption no no [RFCXXXX] 184 dsn-000014 5 preemption no no [RFCXXXX] 185 dsn-000015 5 preemption no no [RFCXXXX] 186 dsn-000016 5 preemption no no [RFCXXXX] 187 dsn-000017 5 preemption no no [RFCXXXX] 188 dsn-000018 5 preemption no no [RFCXXXX] 189 dsn-000019 5 preemption no no [RFCXXXX] 190 dsn-00001A 5 preemption no no [RFCXXXX] 191 dsn-00001B 5 preemption no no [RFCXXXX] 192 dsn-00001C 5 preemption no no [RFCXXXX] 193 dsn-00001D 5 preemption no no [RFCXXXX] 194 dsn-00001E 5 preemption no no [RFCXXXX] 195 dsn-00001F 5 preemption no no [RFCXXXX] 196 dsn-000020 5 preemption no no [RFCXXXX] 197 dsn-000021 5 preemption no no [RFCXXXX] 198 dsn-000022 5 preemption no no [RFCXXXX] 199 dsn-000023 5 preemption no no [RFCXXXX] 200 dsn-000024 5 preemption no no [RFCXXXX] 201 dsn-000025 5 preemption no no [RFCXXXX] 202 dsn-000026 5 preemption no no [RFCXXXX] 203 dsn-000027 5 preemption no no [RFCXXXX] 204 dsn-000028 5 preemption no no [RFCXXXX] 205 dsn-000029 5 preemption no no [RFCXXXX] 206 dsn-00002A 5 preemption no no [RFCXXXX] 207 dsn-00002B 5 preemption no no [RFCXXXX] 208 dsn-00002C 5 preemption no no [RFCXXXX] 209 dsn-00002D 5 preemption no no [RFCXXXX] 210 dsn-00002E 5 preemption no no [RFCXXXX] 211 dsn-00002F 5 preemption no no [RFCXXXX] 212 dsn-000030 5 preemption no no [RFCXXXX] 213 dsn-000031 5 preemption no no [RFCXXXX] 215 3.2 IANA Priority-Value Registrations 217 Within the "Resource-Priority Priority-values" registry in the sip- 218 parameters section of IANA, the list of priority-values for each of 219 the newly created RPH namespaces from section 4.1 of this document, 220 prioritized least to greatest, is registered by the following: 222 Namespace: dsn-000000 223 Reference: RFCXXXX (this document) 224 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 226 Namespace: dsn-000001 227 Reference: RFCXXXX (this document) 228 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 230 Namespace: dsn-000002 231 Reference: RFCXXXX (this document) 232 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 234 Namespace: dsn-000003 235 Reference: RFCXXXX (this document) 236 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 238 Namespace: dsn-000004 239 Reference: RFCXXXX (this document) 240 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 242 Namespace: dsn-000005 243 Reference: RFCXXXX (this document) 244 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 246 Namespace: dsn-000006 247 Reference: RFCXXXX (this document) 248 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 250 Namespace: dsn-000007 251 Reference: RFCXXXX (this document) 252 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 254 Namespace: dsn-000008 255 Reference: RFCXXXX (this document) 256 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 258 Namespace: dsn-000009 259 Reference: RFCXXXX (this document) 260 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 262 Namespace: dsn-00000A 263 Reference: RFCXXXX (this document) 264 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 266 Namespace: dsn-00000B 267 Reference: RFCXXXX (this document) 268 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 270 Namespace: dsn-00000C 271 Reference: RFCXXXX (this document) 272 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 274 Namespace: dsn-00000D 275 Reference: RFCXXXX (this document) 276 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 278 Namespace: dsn-00000E 279 Reference: RFCXXXX (this document) 280 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 282 Namespace: dsn-00000F 283 Reference: RFCXXXX (this document) 284 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 286 Namespace: dsn-000010 287 Reference: RFCXXXX (this document) 288 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 290 Namespace: dsn-000011 291 Reference: RFCXXXX (this document) 292 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 294 Namespace: dsn-000012 295 Reference: RFCXXXX (this document) 296 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 298 Namespace: dsn-000013 299 Reference: RFCXXXX (this document) 300 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 302 Namespace: dsn-000014 303 Reference: RFCXXXX (this document) 304 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 306 Namespace: dsn-000015 307 Reference: RFCXXXX (this document) 308 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 310 Namespace: dsn-000016 311 Reference: RFCXXXX (this document) 312 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 314 Namespace: dsn-000017 315 Reference: RFCXXXX (this document) 316 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 318 Namespace: dsn-000018 319 Reference: RFCXXXX (this document) 320 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 322 Namespace: dsn-000019 323 Reference: RFCXXXX (this document) 324 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 326 Namespace: dsn-00001A 327 Reference: RFCXXXX (this document) 328 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 330 Namespace: dsn-00001B 331 Reference: RFCXXXX (this document) 332 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 334 Namespace: dsn-00001C 335 Reference: RFCXXXX (this document) 336 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 338 Namespace: dsn-00001D 339 Reference: RFCXXXX (this document) 340 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 342 Namespace: dsn-00001E 343 Reference: RFCXXXX (this document) 344 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 346 Namespace: dsn-00001F 347 Reference: RFCXXXX (this document) 348 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 350 Namespace: dsn-000020 351 Reference: RFCXXXX (this document) 352 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 354 Namespace: dsn-000021 355 Reference: RFCXXXX (this document) 356 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 358 Namespace: dsn-000022 359 Reference: RFCXXXX (this document) 360 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 362 Namespace: dsn-000023 363 Reference: RFCXXXX (this document) 364 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 366 Namespace: dsn-000024 367 Reference: RFCXXXX (this document) 368 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 370 Namespace: dsn-000025 371 Reference: RFCXXXX (this document) 372 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 374 Namespace: dsn-000026 375 Reference: RFCXXXX (this document) 376 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 378 Namespace: dsn-000027 379 Reference: RFCXXXX (this document) 380 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 382 Namespace: dsn-000028 383 Reference: RFCXXXX (this document) 384 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 386 Namespace: dsn-000029 387 Reference: RFCXXXX (this document) 388 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 390 Namespace: dsn-00002A 391 Reference: RFCXXXX (this document) 392 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 394 Namespace: dsn-00002B 395 Reference: RFCXXXX (this document) 396 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 398 Namespace: dsn-00002C 399 Reference: RFCXXXX (this document) 400 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 402 Namespace: dsn-00002D 403 Reference: RFCXXXX (this document) 404 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 406 Namespace: dsn-00002E 407 Reference: RFCXXXX (this document) 408 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 410 Namespace: dsn-00002F 411 Reference: RFCXXXX (this document) 412 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 414 Namespace: dsn-000030 415 Reference: RFCXXXX (this document) 416 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 418 Namespace: dsn-000031 419 Reference: RFCXXXX (this document) 420 Priority-Values (least to greatest): "0", "2", "4", "6", "8" 422 4. Security Considerations 424 This document has the same Security Considerations as RFC 4412. 426 5. Acknowledgements 428 To Jeff Hewett for his helpful guidance in this effort. 430 6. References 432 6.1 Normative References 434 [RFC4412] Schulzrinne, H., Polk, J., "Communications Resource 435 Priority for the Session Initiation Protocol (SIP)", RFC 436 4411, Feb 2006 438 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 439 Requirement Levels", RFC 2119, March 1997 441 Author's Address 443 James Polk 444 3913 Treemont Circle 445 Colleyville, Texas 76034 446 USA 448 Phone: +1-817-271-3552 449 Fax: none 450 Email: jmpolk@cisco.com 452 Full Copyright Statement 454 Copyright (C) The IETF Trust (2007). 456 This document is subject to the rights, licenses and restrictions 457 contained in BCP 78, and except as set forth therein, the authors 458 retain all their rights. 460 This document and the information contained herein are provided on 461 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 462 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 463 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 464 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 465 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 466 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 467 FOR A PARTICULAR PURPOSE. 469 Intellectual Property 471 The IETF takes no position regarding the validity or scope of any 472 Intellectual Property Rights or other rights that might be claimed 473 to pertain to the implementation or use of the technology described 474 in this document or the extent to which any license under such 475 rights might or might not be available; nor does it represent that 476 it has made any independent effort to identify any such rights. 477 Information on the procedures with respect to rights in RFC 478 documents can be found in BCP 78 and BCP 79. 480 Copies of IPR disclosures made to the IETF Secretariat and any 481 assurances of licenses to be made available, or the result of an 482 attempt made to obtain a general license or permission for the use 483 of such proprietary rights by implementers or users of this 484 specification can be obtained from the IETF on-line IPR repository 485 at http://www.ietf.org/ipr. 487 The IETF invites any interested party to bring to its attention any 488 copyrights, patents or patent applications, or other proprietary 489 rights that may cover technology that may be required to implement 490 this standard. Please address the information to the IETF at 491 ietf-ipr@ietf.org. 493 Acknowledgment 495 Funding for the RFC Editor function is provided by the IETF 496 Administrative Support Activity (IASA).