idnits 2.17.1 draft-ietf-tsvwg-rsvp-app-id-vv-profiles-01.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: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 15 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document updates RFC2872, but the abstract doesn't seem to directly say this. It does mention RFC2872 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2872, updated by this document, for RFC5378 checks: 1999-10-28) -- 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.) -- The document date (September 19, 2013) is 3866 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) == Missing Reference: 'RFC 2119' is mentioned on line 80, but not defined == Missing Reference: 'RFC2752' is mentioned on line 141, but not defined ** Obsolete undefined reference: RFC 2752 (Obsoleted by RFC 3182) == Unused Reference: 'RFC2119' is defined on line 632, but no explicit reference was found in the text == Unused Reference: 'RFC2474' is defined on line 640, but no explicit reference was found in the text == Unused Reference: 'RFC2750' is defined on line 644, but no explicit reference was found in the text == Unused Reference: 'RFC3182' is defined on line 654, but no explicit reference was found in the text == Unused Reference: 'RFC4594' is defined on line 667, but no explicit reference was found in the text -- Duplicate reference: RFC2205, mentioned in 'RFC2205', was also mentioned in 'RFC2119'. ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Possible downref: Non-RFC (?) normative reference: ref. 'ID-TRAF-CLASS' Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network WG James Polk 3 Internet-Draft Subha Dhesikan 4 Expires: March 19, 2014 Cisco Systems 5 Intended Status: Standards Track September 19, 2013 6 Updates: RFC 2872 (if accepted) 8 Resource Reservation Protocol (RSVP) Application-ID 9 Profiles for Voice and Video Streams 10 draft-ietf-tsvwg-rsvp-app-id-vv-profiles-01 12 Abstract 14 RFC 2872 defines an Resource Reservation Protocol (RSVP) object for 15 application identifiers. This document uses that App-ID and gives 16 implementers specific guidelines for differing voice and video 17 stream identifications to nodes along a reservation path, creating 18 specific profiles for voice and video session identification. 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 31 months and may be updated, replaced, or obsoleted by other documents 32 at any time. It is inappropriate to use Internet-Drafts as 33 reference material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on March 19, 2014. 37 Copyright Notice 39 Copyright (c) 2013 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 47 respect to this document. Code Components extracted from this 48 document must include Simplified BSD License text as described in 49 Section 4.e of the Trust Legal Provisions and are provided without 50 warranty as described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Application-ID Template . . . . . . . . . . . . . . . . . . . 3 56 3. The Voice and Video Application-ID Profiles . . . . . . . . . 4 57 3.1 The Broadcast video Profile . . . . . . . . . . . . . . . 4 58 3.2 The Real-time Interactive Profile . . . . . . . . . . . . 5 59 3.3 The Multimedia Conferencing Profile . . . . . . . . . . . 5 60 3.4 The Multimedia Streaming Profile . . . . . . . . . . . . 6 61 3.5 The Conversational Profile . . . . . . . . . . . . . . . 6 62 4. Security considerations . . . . . . . . . . . . . . . . . . . 7 63 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 7 64 5.1 Application Profiles . . . . . . . . . . . . . . . . . . 7 65 5.1.1 Broadcast Profiles IANA Registry . . . . . . . . . . . 8 66 5.1.2 Realtime-Interactive Profiles IANA Registry . . . . . . 8 67 5.1.3 Multimedia-Conferencing Profiles IANA Registry . . . . 9 68 5.1.4 Multimedia-Streaming Profiles IANA Registry . . . . . . 10 69 5.1.5 Conversational Profiles IANA Registry . . . . . . . . . 10 70 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 12 71 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 72 7.1. Normative References . . . . . . . . . . . . . . . . . 12 73 7.2. Informative References . . . . . . . . . . . . . . . . 13 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 13 75 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . 14 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in RFC 2119 [RFC 2119]. 81 1. Introduction 83 RFC 2872 [RFC2872] describes the usage of policy elements for 84 providing application information in Resource Reservation Protocol 85 (RSVP) signaling [RFC2205]. The intention of providing this 86 information is to enable application-based policy control. However, 87 RFC 2872 does not enumerate any application profiles. The absence 88 of explicit, uniform profiles leads to incompatible handling of 89 these values and misapplied policies. An application profile used by 90 a sender might not be understood by the intermediaries or receiver 91 in a different domain. Therefore, there is a need to enumerate 92 application profiles that are universally understood and applied for 93 correct policy control. 95 Call control between endpoints has the ability to bind or associate 96 many attributes to a reservation. One new attribute is currently 97 being defined so as to establish the type of traffic contained in 98 that reservation. This is accomplished via assigning a traffic label 99 to the call (or session or flow) [ID-TRAF-CLASS]. 101 This document takes the application traffic classes from 102 [ID-TRAF-CLASS] and places those strings in the APP-ID object 103 defined in RFC 2872. Thus, the intermediary devices (e.g., routers) 104 processing the RSVP message can learn the identified profile within 105 the Application-ID policy element for a particular reservation, and 106 possibly be configured with the profile(s) to understand them 107 correctly, thus performing the correct admission control. 109 Another goal of this document is to the ability to signal an 110 application profile which can then be translated into a DSCP value 111 as per the choice of each domain. While the DCLASS object [RFC2996] 112 allows the transfer of DSCP value in an RSVP message, that RFC does 113 not allow the flexibility of having different domains choosing the 114 DSCP value for the traffic classes that they maintain. 116 How these labels indicate the appropriate Differentiated Services 117 Codepoint (DSCP) is out of scope for this document. 119 This document will break out each application type and propose how 120 the values in application-id template should be populated for 121 uniformity and interoperability. 123 2. Application ID Template 125 The template from RFC 2872 is as follows: 127 0 1 2 3 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | PE Length (8) | P-type = AUTH_APP | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | Attribute Length | A-type = | Sub-type = | 132 | | POLICY_LOCATOR| ASCII_DN | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Application name as ASCII string | 135 | (e.g. SAP.EXE) | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 In line with how this policy element is constructed in RFC 2872, the 139 A-type will remain "POLICY_LOCATOR". 141 The P-type field is first created in [RFC2752]. This document 142 uses the existing P-type "AUTH_APP" for application traffic class. 144 The first Sub-type will be mandatory for every profile within this 145 document, and will be "ASCII_DN". No other Sub-types are defined by 146 any profile within this document, but MAY be included by individual 147 implementations - and MUST be ignored if not understood by receiving 148 implementations along the reservation path. 150 RFC 2872 states the #1 sub-element from RFC 2872 as the "identifier 151 that uniquely identifies the application vendor", which is optional 152 to include. This document modifies this vendor limitation so that 153 the identifier need only be unique - and not limited to an 154 application vendor (identifier). For example, this specification now 155 allows an RFC that defines an industry recognizable term or string 156 to be a valid identifier. For example, a term or string taken from 157 another IETF document, such as "conversational" or "avconf" from 158 [ID-TRAF-CLASS]. This sub-element is still optional to include. 160 The following subsections will define the values within the above 161 template into specific profiles for voice and video identification. 163 3. The Voice and Video Application-ID Profiles 165 This section contains the elements of the Application ID policy 166 object which is used to signal the application classes defined in 167 [ID-TRAF-CLASS]. 169 3.1 The Broadcast Profiles 171 Broadcast profiles are for minimally buffered one-way streaming 172 flows, such as video surveillance, or Internet based concerts or 173 non-VOD TV broadcasts such as live sporting events. 175 This document creates Broadcast profiles for 177 - Broadcast IPTV for audio and video 178 - Broadcast Live-events for audio and video 179 - Broadcast Surveillance for audio and video 181 Here is an example profile for identifying Broadcast 182 Video-Surveillance 184 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 185 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 186 APP=broadcast.video.surveillance, VER=" 188 [Editor's Note: "rfcXXXX" will be replaced with the RFC number 189 assigned to the [ID-TRAF-CLASS] reference. This 190 'note' should be removed during the RFC-Editor 191 review process.] 193 Where the Globally Unique Identifier (GUID) indicates the documented 194 reference that created this well-known string [ID-TRAF-CLASS], the 195 APP is the profile name with no spaces, and the "VER=" is included, 196 but has no value at this time. 198 3.2 The Realtime Interactive Profiles 200 Realtime Interactive profiles are for on-line gaming, and both 201 remote and virtual avconf applications, in which the timing is 202 particularly important towards the feedback to uses of these 203 applications. This traffic type will generally not be UDP based, 204 with minimal tolerance to RTT delays. 206 This document creates Realtime Interactive profiles for 208 - Realtime-Interactive Gaming 209 - Realtime-Interactive Remote-Desktop 210 - Realtime-Interactive Virtualized-Desktop 212 Here is the profile for identifying Realtime-Interactive Gaming 214 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 215 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 216 APP=realtime-interactive.gaming, VER=" 218 Where the Globally Unique Identifier (GUID) indicates the documented 219 reference that created this well-known string [ID-TRAF-CLASS], the 220 APP is the profile name with no spaces, and the "VER=" is included, 221 but has no value, but MAY if versioning becomes important. 223 3.3 The Multimedia Conferencing Profiles 225 There will be Multimedia Conferencing profiles for presentation 226 data, application sharing and whiteboarding, where these 227 applications will most often be associated with a larger 228 Conversational (audio and/or audio/video) conference. Timing is 229 important, but some minimal delays are acceptable, unlike the case 230 for Realtime-Interactive traffic. 232 This document creates Multimedia-Conferencing profiles for 234 - Multimedia-Conferencing presentation-data 235 - Multimedia-Conferencing presentation-video 236 - Multimedia-Conferencing presentation-audio 237 - Multimedia-Conferencing application-sharing 238 - Multimedia-Conferencing whiteboarding 240 Here is the profile for identifying Multimedia-Conferencing 241 Application-sharing 243 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 244 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 245 APP=multimedia-conferencing.application-sharing, VER=" 247 Where the Globally Unique Identifier (GUID) indicates the RFC 248 reference that created this well-known string [ID-TRAF-CLASS], the 249 APP is the profile name with no spaces, and the "VER=" is included, 250 but has no value, but MAY if versioning becomes important. 252 3.4 The Multimedia Streaming Profiles 254 Multimedia Streaming profiles are for more significantly buffered 255 one-way streaming flows than Broadcast profiles. These include... 257 This document creates Multimedia Streaming profiles for 259 - Multimedia-Streaming multiplex 260 - Multimedia-Streaming webcast 262 Here is the profile for identifying Multimedia Streaming 263 webcast 265 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 266 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 267 APP=multimedia-streaming.webcast, VER=" 269 Where the Globally Unique Identifier (GUID) indicates the documented 270 reference that created this well-known string [ID-TRAF-CLASS], the 271 APP is the profile name with no spaces, and the "VER=" is included, 272 but has no value, but MAY if versioning becomes important. 274 3.5 The Conversational Profiles 276 Conversational category is for realtime bidirectional 277 communications, such as voice or video, and is the most numerous due 278 to the choices of application with or without adjectives. The number 279 of profiles is then doubled because there needs to be one for 280 unadmitted and one for admitted. The IANA section lists all that 281 are currently proposed for registration at this time, therefore 282 there will not be an exhaustive list provided in this section. 284 This document creates Conversational profiles for 286 - Conversational Audio 287 - Conversational Audio Admitted 288 - Conversational Video 289 - Conversational Video Admitted 290 - Conversational Audio Avconf 291 - Conversational Audio Avconf Admitted 292 - Conversational Video Avconf 293 - Conversational Video Avconf Admitted 294 - Conversational Audio Immersive 295 - Conversational Audio Immersive Admitted 296 - Conversational Video Immersive 297 - Conversational Video Immersive Admitted 299 Here is an example profile for identifying Conversational Audio: 301 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 302 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 303 APP=conversational.audio, VER=" 305 Where the Globally Unique Identifier (GUID) indicates the documented 306 reference that created this well-known string [ID-TRAF-CLASS], the 307 APP is the profile name with no spaces, and the "VER=" is included, 308 but has no value, but MAY if versioning becomes important. 310 4. Security considerations 312 The security considerations section within RFC 2872 sufficiently 313 covers this document, with one possible exception - someone using 314 the wrong template values (e.g., claiming a reservation is 315 Multimedia Streaming when it is in fact Real-time Interactive). 316 Given that each traffic flow is within separate reservations, and 317 RSVP does not have the ability to police the type of traffic within 318 any reservation, solving for this appears to be administratively 319 handled at best. This is not meant to be a 'punt', but there really 320 is nothing this template creates that is going to make things any 321 harder for anyone (that we know of now). 323 5. IANA considerations 325 5.1 Application Profiles 327 This document requests IANA create a new registry for the 328 application identification classes similar to the following table 329 within the Resource Reservation Protocol (RSVP) Parameters registry: 331 Registry Name: RSVP APP-ID Profiles 332 Reference: [this document] 333 Registration procedures: Standards Track document [RFC5226] 335 [Editor's Note: "rfcXXXX" will be replaced with the RFC number 336 assigned to the [ID-TRAF-CLASS] reference. This 337 'note' should be removed during the RFC-Editor 338 review process.] 340 5.1.1 Broadcast Profiles IANA Registry 342 Broadcast Audio IPTV Profile 343 P-type = AUTH_APP 344 A-type = POLICY_LOCATOR 345 Sub-type = ASCII_DN 346 Conformant policy locator = 347 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 348 APP=broadcast.audio.iptv, VER=" 349 Reference: [this document] 351 Broadcast Video IPTV Profile 352 P-type = AUTH_APP 353 A-type = POLICY_LOCATOR 354 Sub-type = ASCII_DN 355 Conformant policy locator = 356 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 357 APP=broadcast.video.iptv, VER=" 358 Reference: [this document] 360 Broadcast Audio Live-events Profile 361 P-type = AUTH_APP 362 A-type = POLICY_LOCATOR 363 Sub-type = ASCII_DN 364 Conformant policy locator = 365 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 366 APP=broadcast.audio.live-events, VER=" 367 Reference: [this document] 369 Broadcast Video Live-events Profile 370 P-type = AUTH_APP 371 A-type = POLICY_LOCATOR 372 Sub-type = ASCII_DN 373 Conformant policy locator = 374 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 375 APP=broadcast.video.live-events, VER=" 376 Reference: [this document] 378 Broadcast Audio-Surveillance Profile 379 P-type = AUTH_APP 380 A-type = POLICY_LOCATOR 381 Sub-type = ASCII_DN 382 Conformant policy locator = 383 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 384 APP=broadcast.audio.surveillance, VER=" 385 Reference: [this document] 387 Broadcast Video-Surveillance Profile 388 P-type = AUTH_APP 389 A-type = POLICY_LOCATOR 390 Sub-type = ASCII_DN 391 Conformant policy locator = 392 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 393 APP=broadcast.video.surveillance, VER=" 394 Reference: [this document] 396 5.1.2 Realtime-Interactive Profiles IANA Registry 398 Realtime-Interactive Gaming Profile 399 P-type = AUTH_APP 400 A-type = POLICY_LOCATOR 401 Sub-type = ASCII_DN 402 Conformant policy locator = 403 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 404 APP= realtime-interactive.gaming, VER=" 405 Reference: [this document] 407 Real-time Interactive Remote-Desktop Profile 408 P-type = AUTH_APP 409 A-type = POLICY_LOCATOR 410 Sub-type = ASCII_DN 411 Conformant policy locator = 412 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 413 APP=realtime-interactive.remote-desktop, VER=" 414 Reference: [this document] 416 Real-time Interactive Virtualized-Desktop Profile 417 P-type = AUTH_APP 418 A-type = POLICY_LOCATOR 419 Sub-type = ASCII_DN 420 Conformant policy locator = 421 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 422 APP=realtime-interactive. 423 remote-desktop.virtual, VER=" 424 Reference: [this document] 426 Real-time Interactive Telemetry Profile 427 P-type = AUTH_APP 428 A-type = POLICY_LOCATOR 429 Sub-type = ASCII_DN 430 Conformant policy locator = 431 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 432 APP=realtime-interactive.telemetry, VER=" 433 Reference: [this document] 435 5.1.3 Multimedia-Conferencing Profiles IANA Registry 437 Multimedia-Conferencing Presentation-Data Profile 438 P-type = AUTH_APP 439 A-type = POLICY_LOCATOR 440 Sub-type = ASCII_DN 441 Conformant policy locator = 442 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 443 APP= multimedia-conferencing.presentation-data, 444 VER=" 445 Reference: [this document] 447 Multimedia-Conferencing Presentation-Video Profile 448 P-type = AUTH_APP 449 A-type = POLICY_LOCATOR 450 Sub-type = ASCII_DN 451 Conformant policy locator = 452 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 453 APP= multimedia-conferencing.presentation-video, 454 VER=" 455 Reference: [this document] 457 Multimedia-Conferencing Presentation-Audio Profile 458 P-type = AUTH_APP 459 A-type = POLICY_LOCATOR 460 Sub-type = ASCII_DN 461 Conformant policy locator = 462 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 463 APP= multimedia-conferencing.presentation-audio, 464 VER=" 465 Reference: [this document] 467 Multimedia-Conferencing Application-Sharing Profile 468 P-type = AUTH_APP 469 A-type = POLICY_LOCATOR 470 Sub-type = ASCII_DN 471 Conformant policy locator = 472 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 473 APP= multimedia-conferencing.application-sharing, 474 VER=" 475 Reference: [this document] 477 Multimedia-Conferencing Whiteboarding Profile 478 P-type = AUTH_APP 479 A-type = POLICY_LOCATOR 480 Sub-type = ASCII_DN 481 Conformant policy locator = 482 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 483 APP= multimedia-conferencing.whiteboarding, VER=" 484 Reference: [this document] 486 5.1.4 Multimedia-Streaming Profiles IANA Registry 488 Multimedia-Streaming Multiplex Profile 489 P-type = AUTH_APP 490 A-type = POLICY_LOCATOR 491 Sub-type = ASCII_DN 492 Conformant policy locator = 493 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 494 APP=multimedia-streaming.multiplex, VER=" 495 Reference: [this document] 497 Multimedia-Streaming Webcast Profile 498 P-type = AUTH_APP 499 A-type = POLICY_LOCATOR 500 Sub-type = ASCII_DN 501 Conformant policy locator = 502 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 503 APP=multimedia-streaming.webcast, VER=" 505 Reference: [this document] 507 5.1.5 Conversational Profiles IANA Registry 509 Conversational Audio Profile 510 P-type = AUTH_APP 511 A-type = POLICY_LOCATOR 512 Sub-type = ASCII_DN 513 Conformant policy locator = 514 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 515 APP=conversational.audio, VER=" 516 Reference: [this document] 518 Conversational Audio Admitted Profile 519 P-type = AUTH_APP 520 A-type = POLICY_LOCATOR 521 Sub-type = ASCII_DN 522 Conformant policy locator = 523 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 524 APP=conversational.audio.aq:admitted, VER=" 525 Reference: [this document] 527 Conversational Video Profile 528 P-type = AUTH_APP 529 A-type = POLICY_LOCATOR 530 Sub-type = ASCII_DN 531 Conformant policy locator = 532 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 533 APP=conversational.video, VER=" 534 Reference: [this document] 536 Conversational Video Admitted Profile 537 P-type = AUTH_APP 538 A-type = POLICY_LOCATOR 539 Sub-type = ASCII_DN 540 Conformant policy locator = 541 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 542 APP=conversational.video.aq:admitted, VER=" 543 Reference: [this document] 545 Conversational Audio Avconf Profile 546 P-type = AUTH_APP 547 A-type = POLICY_LOCATOR 548 Sub-type = ASCII_DN 549 Conformant policy locator = 550 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 551 APP=conversational.audio.avconf, VER=" 552 Reference: [this document] 554 Conversational Audio Avconf Admitted Profile 555 P-type = AUTH_APP 557 A-type = POLICY_LOCATOR 558 Sub-type = ASCII_DN 559 Conformant policy locator = 560 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 561 APP=conversational.audio.avconf.aq:admitted, 562 VER=" 563 Reference: [this document] 565 Conversational Video Avconf Profile 566 P-type = AUTH_APP 567 A-type = POLICY_LOCATOR 568 Sub-type = ASCII_DN 569 Conformant policy locator = 570 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 571 APP=conversational.video.avconf, VER=" 572 Reference: [this document] 574 Conversational Video Avconf Admitted Profile 575 P-type = AUTH_APP 576 A-type = POLICY_LOCATOR 577 Sub-type = ASCII_DN 578 Conformant policy locator = 579 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 580 APP=conversational.video.avconf.aq:admitted, 581 VER=" 582 Reference: [this document] 584 Conversational Audio Immersive Profile 585 P-type = AUTH_APP 586 A-type = POLICY_LOCATOR 587 Sub-type = ASCII_DN 588 Conformant policy locator = 589 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 590 APP=conversational.audio.immersive, VER=" 591 Reference: [this document] 593 Conversational Audio Immersive Admitted Profile 594 P-type = AUTH_APP 595 A-type = POLICY_LOCATOR 596 Sub-type = ASCII_DN 597 Conformant policy locator = 598 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 599 APP=conversational.audio.immersive.aq:admitted, 600 VER=" 601 Reference: [this document] 603 Conversational Video Immersive Profile 604 P-type = AUTH_APP 605 A-type = POLICY_LOCATOR 606 Sub-type = ASCII_DN 607 Conformant policy locator = 608 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 609 APP=conversational.video.immersive, VER=" 610 Reference: [this document] 612 Conversational Video Immersive Admitted Profile 613 P-type = AUTH_APP 614 A-type = POLICY_LOCATOR 615 Sub-type = ASCII_DN 616 Conformant policy locator = 617 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 618 APP=conversational.video.immersive.aq:admitted, 619 VER=" 620 Reference: [this document] 622 6. Acknowledgments 624 To Francois Le Faucheur, Paul Jones, Ken Carlberg, Georgios 625 Karagiannis and Glen Lavers for their helpful comments, document 626 reviews and encouragement. 628 7. References 630 7.1. Normative References 632 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 633 Requirement Levels", RFC 2119, March 1997 634 Functional Specification", RFC 2205, September 1997 636 [RFC2205] R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, S. Jamin, 637 "Resource ReSerVation Protocol (RSVP) -- Version 1 638 Functional Specification", RFC 2205, September 1997 640 [RFC2474] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the 641 Differentiated Services Field (DS Field) in the IPv4 and 642 IPv6 Headers ", RFC 2474, December 1998 644 [RFC2750] S. Herzog, "RSVP Extensions for Policy Control", RFC 2750, 645 January 2000 647 [RFC2872] Y. Bernet, R. Pabbati, "Application and Sub Application 648 Identity Policy Element for Use with RSVP", RFC 2872, 649 June 2000 651 [RFC2996] Y. Bernet, "Format of the RSVP DCLASS Object", RFC 2996, 652 November 2000 654 [RFC3182] S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. 655 Herzog, R. Hess, "Identity Representation for RSVP", 656 RFC 3182, October 2001 658 [RFC5226] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 659 Considerations Section in RFCs", RFC 5226, May 2008 661 [ID-TRAF-CLASS] J. Polk, S. Dhesikan, P. Jones, "The Session 662 Description Protocol (SDP) 'trafficclass' Attribute", 663 work in progress, Feb 2013 665 7.2. Informative References 667 [RFC4594] J. Babiarz, K. Chan, F Baker, "Configuration Guidelines for 668 Diffserv Service Classes", RFC 4594, August 2006 670 Authors' Addresses 672 James Polk 673 3913 Treemont Circle 674 Colleyville, Texas, USA 675 +1.817.271.3552 677 mailto: jmpolk@cisco.com 679 Subha Dhesikan 680 170 W Tasman St 681 San Jose, CA, USA 682 +1.408-902-3351 684 mailto: sdhesika@cisco.com 686 Appendix - Changes to ID 688 [Editor's Note: this appendix should be removed in the RFC-Editor's 689 process.] 691 A.1 - Changes from WG version -00 to WG version -01 693 The following changes were made in this version: 695 - corrected nits 697 - globally replaced GUID link from the MMUSIC Trafficclass ID to the 698 future RFC of that document. 700 - added profiles for presentation-video and presentation-audio 702 A.2 - Changes from Individual -04 to WG version -00 704 The following changes were made in this version: 706 - changed P-Type from APP_TC back to AUTH_APP, which is already 707 defined. 709 - fixed nits and inconsistencies 711 A.3 - Changes from Individual -03 to -04 713 The following changes were made in this version: 715 - clarified security considerations section to mean RSVP cannot 716 police the type of traffic within a reservation to know if a 717 traffic flow should be using a different profile, as defined in 718 this document. 720 - changed existing informative language regarding "... other 721 Sub-types ..." from 'can' to normative 'MAY'. 722 - editorial changes to clear up minor mistakes 724 A.4 - Changes from Individual -02 to -03 726 The following changes were made in this version: 728 - Added [ID-TRAF-CLASS] as a reference 730 - Changed to a new format of the profile string. 732 - Added many new profiles based on the new format into each parent 733 category of Section 3. 735 - changed the GUID to refer to draft-ietf-mmusic-traffic-class-for- 736 sdp-03.txt 738 - changed 'desktop' adjective to 'avconf' to keep in alignment with 739 [ID-TRAF-CLASS] 741 - Have a complete IANA Registry proposal for each application-ID 742 discussed in this draft. 744 - General text clean-up of the draft.