idnits 2.17.1 draft-ietf-tsvwg-rsvp-app-id-vv-profiles-02.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 (July 4, 2014) is 3577 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 124, but not defined == Missing Reference: 'RFC2752' is mentioned on line 143, but not defined ** Obsolete undefined reference: RFC 2752 (Obsoleted by RFC 3182) == Unused Reference: 'RFC2119' is defined on line 634, but no explicit reference was found in the text == Unused Reference: 'RFC2474' is defined on line 642, but no explicit reference was found in the text == Unused Reference: 'RFC2750' is defined on line 646, but no explicit reference was found in the text == Unused Reference: 'RFC3182' is defined on line 656, but no explicit reference was found in the text == Unused Reference: 'RFC4594' is defined on line 669, 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: January 4, 2015 Cisco Systems 5 Intended Status: Standards Track July 4, 2014 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-02 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 July 4, 2014. 37 Copyright Notice 39 Copyright (c) 2014 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. RSVP 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 1. Introduction 79 RFC 2872 [RFC2872] describes the usage of policy elements for 80 providing application information in Resource Reservation Protocol 81 (RSVP) signaling [RFC2205]. The intention of providing this 82 information is to enable application-based policy control. However, 83 RFC 2872 does not enumerate any application profiles. The absence 84 of explicit, uniform profiles leads to incompatible handling of 85 these values and misapplied policies. An application profile used by 86 a sender might not be understood by the intermediaries or receiver 87 in a different domain. Therefore, there is a need to enumerate 88 application profiles that are universally understood and applied for 89 correct policy control. 91 Call control between endpoints has the ability to bind or associate 92 many attributes to a reservation. One new attribute is currently 93 being defined so as to establish the type of traffic contained in 94 that reservation. This is accomplished via assigning a traffic label 95 to the call (or session or flow) [ID-TRAF-CLASS]. 97 This document takes the application traffic classes from 98 [ID-TRAF-CLASS] and places those strings in the APP-ID object 99 defined in RFC 2872. Thus, the intermediary devices (e.g., routers) 100 processing the RSVP message can learn the identified profile within 101 the Application-ID policy element for a particular reservation, and 102 possibly be configured with the profile(s) to understand them 103 correctly, thus performing the correct admission control. 105 Another goal of this document is to the ability to signal an 106 application profile which can then be translated into a DSCP value 107 as per the choice of each domain. While the DCLASS object [RFC2996] 108 allows the transfer of DSCP value in an RSVP message, that RFC does 109 not allow the flexibility of having different domains choosing the 110 DSCP value for the traffic classes that they maintain. 112 How these labels indicate the appropriate Differentiated Services 113 Codepoint (DSCP) is out of scope for this document. 115 This document will break out each application type and propose how 116 the values in application-id template should be populated for 117 uniformity and interoperability. 119 1.1 Terminology 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC 2119]. 125 2. RSVP Application ID Template 127 The template from RFC 2872 is as follows: 129 0 1 2 3 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | PE Length (8) | P-type = AUTH_APP | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | Attribute Length | A-type = | Sub-type = | 134 | | POLICY_LOCATOR| ASCII_DN | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Application name as ASCII string | 137 | (e.g. SAP.EXE) | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 In line with how this policy element is constructed in RFC 2872, the 141 A-type will remain "POLICY_LOCATOR". 143 The P-type field is first created in [RFC2752]. This document 144 uses the existing P-type "AUTH_APP" for application traffic class. 146 The first Sub-type will be mandatory for every profile within this 147 document, and will be "ASCII_DN". No other Sub-types are defined by 148 any profile within this document, but MAY be included by individual 149 implementations - and MUST be ignored if not understood by receiving 150 implementations along the reservation path. 152 RFC 2872 states the #1 sub-element from RFC 2872 as the "identifier 153 that uniquely identifies the application vendor", which is optional 154 to include. This document modifies this vendor limitation so that 155 the identifier need only be unique - and not limited to an 156 application vendor (identifier). For example, this specification now 157 allows an RFC that defines an industry recognizable term or string 158 to be a valid identifier. For example, a term or string taken from 159 another IETF document, such as "conversational" or "avconf" from 160 [ID-TRAF-CLASS]. This sub-element is still optional to include. 162 The following subsections will define the values within the above 163 template into specific profiles for voice and video identification. 165 3. The Voice and Video Application-ID Profiles 167 This section contains the elements of the Application ID policy 168 object which is used to signal the application classes defined in 169 [ID-TRAF-CLASS]. 171 3.1 The Broadcast Profiles 173 Broadcast profiles are for minimally buffered one-way streaming 174 flows, such as video surveillance, or Internet based concerts or 175 non-VOD TV broadcasts such as live sporting events. 177 This document creates Broadcast profiles for 179 - Broadcast IPTV for audio and video 180 - Broadcast Live-events for audio and video 181 - Broadcast Surveillance for audio and video 183 Here is an example profile for identifying Broadcast 184 Video-Surveillance 186 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 187 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 188 APP=broadcast.video.surveillance, VER=" 190 [Editor's Note: "rfcXXXX" will be replaced with the RFC number 191 assigned to the [ID-TRAF-CLASS] reference. This 192 'note' should be removed during the RFC-Editor 193 review process.] 195 Where the Globally Unique Identifier (GUID) indicates the documented 196 reference that created this well-known string [ID-TRAF-CLASS], the 197 APP is the profile name with no spaces, and the "VER=" is included, 198 but has no value at this time. 200 3.2 The Realtime Interactive Profiles 202 Realtime Interactive profiles are for on-line gaming, and both 203 remote and virtual avconf applications, in which the timing is 204 particularly important towards the feedback to uses of these 205 applications. This traffic type will generally not be UDP based, 206 with minimal tolerance to RTT delays. 208 This document creates Realtime Interactive profiles for 210 - Realtime-Interactive Gaming 211 - Realtime-Interactive Remote-Desktop 212 - Realtime-Interactive Virtualized-Desktop 214 Here is the profile for identifying Realtime-Interactive Gaming 216 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 217 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 218 APP=realtime-interactive.gaming, VER=" 220 Where the Globally Unique Identifier (GUID) indicates the documented 221 reference that created this well-known string [ID-TRAF-CLASS], the 222 APP is the profile name with no spaces, and the "VER=" is included, 223 but has no value, but MAY if versioning becomes important. 225 3.3 The Multimedia Conferencing Profiles 227 There will be Multimedia Conferencing profiles for presentation 228 data, application sharing and whiteboarding, where these 229 applications will most often be associated with a larger 230 Conversational (audio and/or audio/video) conference. Timing is 231 important, but some minimal delays are acceptable, unlike the case 232 for Realtime-Interactive traffic. 234 This document creates Multimedia-Conferencing profiles for 236 - Multimedia-Conferencing presentation-data 237 - Multimedia-Conferencing presentation-video 238 - Multimedia-Conferencing presentation-audio 239 - Multimedia-Conferencing application-sharing 240 - Multimedia-Conferencing whiteboarding 242 Here is the profile for identifying Multimedia-Conferencing 243 Application-sharing 245 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 246 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 247 APP=multimedia-conferencing.application-sharing, VER=" 249 Where the Globally Unique Identifier (GUID) indicates the RFC 250 reference that created this well-known string [ID-TRAF-CLASS], the 251 APP is the profile name with no spaces, and the "VER=" is included, 252 but has no value, but MAY if versioning becomes important. 254 3.4 The Multimedia Streaming Profiles 256 Multimedia Streaming profiles are for more significantly buffered 257 one-way streaming flows than Broadcast profiles. These include... 259 This document creates Multimedia Streaming profiles for 261 - Multimedia-Streaming multiplex 262 - Multimedia-Streaming webcast 264 Here is the profile for identifying Multimedia Streaming 265 webcast 267 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 268 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 269 APP=multimedia-streaming.webcast, VER=" 271 Where the Globally Unique Identifier (GUID) indicates the documented 272 reference that created this well-known string [ID-TRAF-CLASS], the 273 APP is the profile name with no spaces, and the "VER=" is included, 274 but has no value, but MAY if versioning becomes important. 276 3.5 The Conversational Profiles 278 Conversational category is for realtime bidirectional 279 communications, such as voice or video, and is the most numerous due 280 to the choices of application with or without adjectives. The number 281 of profiles is then doubled because there needs to be one for 282 unadmitted and one for admitted. The IANA section lists all that 283 are currently proposed for registration at this time, therefore 284 there will not be an exhaustive list provided in this section. 286 This document creates Conversational profiles for 288 - Conversational Audio 289 - Conversational Audio Admitted 290 - Conversational Video 291 - Conversational Video Admitted 292 - Conversational Audio Avconf 293 - Conversational Audio Avconf Admitted 294 - Conversational Video Avconf 295 - Conversational Video Avconf Admitted 296 - Conversational Audio Immersive 297 - Conversational Audio Immersive Admitted 298 - Conversational Video Immersive 299 - Conversational Video Immersive Admitted 301 Here is an example profile for identifying Conversational Audio: 303 AUTH_APP, POLICY_LOCATOR, ASCII_DN, 304 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 305 APP=conversational.audio, VER=" 307 Where the Globally Unique Identifier (GUID) indicates the documented 308 reference that created this well-known string [ID-TRAF-CLASS], the 309 APP is the profile name with no spaces, and the "VER=" is included, 310 but has no value, but MAY if versioning becomes important. 312 4. Security considerations 314 The security considerations section within RFC 2872 sufficiently 315 covers this document, with one possible exception - someone using 316 the wrong template values (e.g., claiming a reservation is 317 Multimedia Streaming when it is in fact Real-time Interactive). 318 Given that each traffic flow is within separate reservations, and 319 RSVP does not have the ability to police the type of traffic within 320 any reservation, solving for this appears to be administratively 321 handled at best. This is not meant to be a 'punt', but there really 322 is nothing this template creates that is going to make things any 323 harder for anyone (that we know of now). 325 5. IANA considerations 327 5.1 Application Profiles 329 This document requests IANA create a new registry for the 330 application identification classes similar to the following table 331 within the Resource Reservation Protocol (RSVP) Parameters registry: 333 Registry Name: RSVP APP-ID Profiles 334 Reference: [this document] 335 Registration procedures: Standards Track document [RFC5226] 337 [Editor's Note: "rfcXXXX" will be replaced with the RFC number 338 assigned to the [ID-TRAF-CLASS] reference. This 339 'note' should be removed during the RFC-Editor 340 review process.] 342 5.1.1 Broadcast Profiles IANA Registry 344 Broadcast Audio IPTV Profile 345 P-type = AUTH_APP 346 A-type = POLICY_LOCATOR 347 Sub-type = ASCII_DN 348 Conformant policy locator = 349 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 350 APP=broadcast.audio.iptv, VER=" 351 Reference: [this document] 353 Broadcast Video IPTV Profile 354 P-type = AUTH_APP 355 A-type = POLICY_LOCATOR 356 Sub-type = ASCII_DN 357 Conformant policy locator = 358 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 359 APP=broadcast.video.iptv, VER=" 360 Reference: [this document] 362 Broadcast Audio Live-events Profile 363 P-type = AUTH_APP 364 A-type = POLICY_LOCATOR 365 Sub-type = ASCII_DN 366 Conformant policy locator = 367 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 368 APP=broadcast.audio.live-events, VER=" 369 Reference: [this document] 371 Broadcast Video Live-events Profile 372 P-type = AUTH_APP 373 A-type = POLICY_LOCATOR 374 Sub-type = ASCII_DN 375 Conformant policy locator = 376 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 377 APP=broadcast.video.live-events, VER=" 378 Reference: [this document] 380 Broadcast Audio-Surveillance Profile 381 P-type = AUTH_APP 382 A-type = POLICY_LOCATOR 383 Sub-type = ASCII_DN 384 Conformant policy locator = 385 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 386 APP=broadcast.audio.surveillance, VER=" 387 Reference: [this document] 389 Broadcast Video-Surveillance Profile 390 P-type = AUTH_APP 391 A-type = POLICY_LOCATOR 392 Sub-type = ASCII_DN 393 Conformant policy locator = 394 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 395 APP=broadcast.video.surveillance, VER=" 396 Reference: [this document] 398 5.1.2 Realtime-Interactive Profiles IANA Registry 400 Realtime-Interactive Gaming Profile 401 P-type = AUTH_APP 402 A-type = POLICY_LOCATOR 403 Sub-type = ASCII_DN 404 Conformant policy locator = 405 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 406 APP= realtime-interactive.gaming, VER=" 407 Reference: [this document] 409 Real-time Interactive Remote-Desktop Profile 410 P-type = AUTH_APP 411 A-type = POLICY_LOCATOR 412 Sub-type = ASCII_DN 413 Conformant policy locator = 414 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 415 APP=realtime-interactive.remote-desktop, VER=" 416 Reference: [this document] 418 Real-time Interactive Virtualized-Desktop Profile 419 P-type = AUTH_APP 420 A-type = POLICY_LOCATOR 421 Sub-type = ASCII_DN 422 Conformant policy locator = 423 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 424 APP=realtime-interactive. 425 remote-desktop.virtual, VER=" 426 Reference: [this document] 428 Real-time Interactive Telemetry Profile 429 P-type = AUTH_APP 430 A-type = POLICY_LOCATOR 431 Sub-type = ASCII_DN 432 Conformant policy locator = 433 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 434 APP=realtime-interactive.telemetry, VER=" 435 Reference: [this document] 437 5.1.3 Multimedia-Conferencing Profiles IANA Registry 439 Multimedia-Conferencing Presentation-Data Profile 440 P-type = AUTH_APP 441 A-type = POLICY_LOCATOR 442 Sub-type = ASCII_DN 443 Conformant policy locator = 444 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 445 APP= multimedia-conferencing.presentation-data, 446 VER=" 447 Reference: [this document] 449 Multimedia-Conferencing Presentation-Video Profile 450 P-type = AUTH_APP 451 A-type = POLICY_LOCATOR 452 Sub-type = ASCII_DN 453 Conformant policy locator = 454 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 455 APP= multimedia-conferencing.presentation-video, 456 VER=" 457 Reference: [this document] 459 Multimedia-Conferencing Presentation-Audio Profile 460 P-type = AUTH_APP 461 A-type = POLICY_LOCATOR 462 Sub-type = ASCII_DN 463 Conformant policy locator = 464 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 465 APP= multimedia-conferencing.presentation-audio, 466 VER=" 467 Reference: [this document] 469 Multimedia-Conferencing Application-Sharing Profile 470 P-type = AUTH_APP 471 A-type = POLICY_LOCATOR 472 Sub-type = ASCII_DN 473 Conformant policy locator = 474 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 475 APP= multimedia-conferencing.application-sharing, 476 VER=" 477 Reference: [this document] 479 Multimedia-Conferencing Whiteboarding Profile 480 P-type = AUTH_APP 481 A-type = POLICY_LOCATOR 482 Sub-type = ASCII_DN 483 Conformant policy locator = 484 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 485 APP= multimedia-conferencing.whiteboarding, VER=" 486 Reference: [this document] 488 5.1.4 Multimedia-Streaming Profiles IANA Registry 490 Multimedia-Streaming Multiplex Profile 491 P-type = AUTH_APP 492 A-type = POLICY_LOCATOR 493 Sub-type = ASCII_DN 494 Conformant policy locator = 495 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 496 APP=multimedia-streaming.multiplex, VER=" 497 Reference: [this document] 499 Multimedia-Streaming Webcast Profile 500 P-type = AUTH_APP 501 A-type = POLICY_LOCATOR 502 Sub-type = ASCII_DN 503 Conformant policy locator = 504 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 505 APP=multimedia-streaming.webcast, VER=" 507 Reference: [this document] 509 5.1.5 Conversational Profiles IANA Registry 511 Conversational Audio Profile 512 P-type = AUTH_APP 513 A-type = POLICY_LOCATOR 514 Sub-type = ASCII_DN 515 Conformant policy locator = 516 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 517 APP=conversational.audio, VER=" 518 Reference: [this document] 520 Conversational Audio Admitted Profile 521 P-type = AUTH_APP 522 A-type = POLICY_LOCATOR 523 Sub-type = ASCII_DN 524 Conformant policy locator = 525 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 526 APP=conversational.audio.aq:admitted, VER=" 527 Reference: [this document] 529 Conversational Video Profile 530 P-type = AUTH_APP 531 A-type = POLICY_LOCATOR 532 Sub-type = ASCII_DN 533 Conformant policy locator = 534 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 535 APP=conversational.video, VER=" 536 Reference: [this document] 538 Conversational Video Admitted Profile 539 P-type = AUTH_APP 540 A-type = POLICY_LOCATOR 541 Sub-type = ASCII_DN 542 Conformant policy locator = 543 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 544 APP=conversational.video.aq:admitted, VER=" 545 Reference: [this document] 547 Conversational Audio Avconf Profile 548 P-type = AUTH_APP 549 A-type = POLICY_LOCATOR 550 Sub-type = ASCII_DN 551 Conformant policy locator = 552 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 553 APP=conversational.audio.avconf, VER=" 554 Reference: [this document] 556 Conversational Audio Avconf Admitted Profile 557 P-type = AUTH_APP 559 A-type = POLICY_LOCATOR 560 Sub-type = ASCII_DN 561 Conformant policy locator = 562 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 563 APP=conversational.audio.avconf.aq:admitted, 564 VER=" 565 Reference: [this document] 567 Conversational Video Avconf Profile 568 P-type = AUTH_APP 569 A-type = POLICY_LOCATOR 570 Sub-type = ASCII_DN 571 Conformant policy locator = 572 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 573 APP=conversational.video.avconf, VER=" 574 Reference: [this document] 576 Conversational Video Avconf Admitted Profile 577 P-type = AUTH_APP 578 A-type = POLICY_LOCATOR 579 Sub-type = ASCII_DN 580 Conformant policy locator = 581 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 582 APP=conversational.video.avconf.aq:admitted, 583 VER=" 584 Reference: [this document] 586 Conversational Audio Immersive Profile 587 P-type = AUTH_APP 588 A-type = POLICY_LOCATOR 589 Sub-type = ASCII_DN 590 Conformant policy locator = 591 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 592 APP=conversational.audio.immersive, VER=" 593 Reference: [this document] 595 Conversational Audio Immersive Admitted Profile 596 P-type = AUTH_APP 597 A-type = POLICY_LOCATOR 598 Sub-type = ASCII_DN 599 Conformant policy locator = 600 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 601 APP=conversational.audio.immersive.aq:admitted, 602 VER=" 603 Reference: [this document] 605 Conversational Video Immersive Profile 606 P-type = AUTH_APP 607 A-type = POLICY_LOCATOR 608 Sub-type = ASCII_DN 609 Conformant policy locator = 610 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 611 APP=conversational.video.immersive, VER=" 612 Reference: [this document] 614 Conversational Video Immersive Admitted Profile 615 P-type = AUTH_APP 616 A-type = POLICY_LOCATOR 617 Sub-type = ASCII_DN 618 Conformant policy locator = 619 "GUID=http://www.rfc-editor.org/rfc/rfcXXXX.txt, 620 APP=conversational.video.immersive.aq:admitted, 621 VER=" 622 Reference: [this document] 624 6. Acknowledgments 626 To Francois Le Faucheur, Paul Jones, Ken Carlberg, Georgios 627 Karagiannis and Glen Lavers for their helpful comments, document 628 reviews and encouragement. 630 7. References 632 7.1. Normative References 634 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 635 Requirement Levels", RFC 2119, March 1997 636 Functional Specification", RFC 2205, September 1997 638 [RFC2205] R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, S. Jamin, 639 "Resource ReSerVation Protocol (RSVP) -- Version 1 640 Functional Specification", RFC 2205, September 1997 642 [RFC2474] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the 643 Differentiated Services Field (DS Field) in the IPv4 and 644 IPv6 Headers ", RFC 2474, December 1998 646 [RFC2750] S. Herzog, "RSVP Extensions for Policy Control", RFC 2750, 647 January 2000 649 [RFC2872] Y. Bernet, R. Pabbati, "Application and Sub Application 650 Identity Policy Element for Use with RSVP", RFC 2872, 651 June 2000 653 [RFC2996] Y. Bernet, "Format of the RSVP DCLASS Object", RFC 2996, 654 November 2000 656 [RFC3182] S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. 657 Herzog, R. Hess, "Identity Representation for RSVP", 658 RFC 3182, October 2001 660 [RFC5226] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 661 Considerations Section in RFCs", RFC 5226, May 2008 663 [ID-TRAF-CLASS] J. Polk, S. Dhesikan, P. Jones, "The Session 664 Description Protocol (SDP) 'trafficclass' Attribute", 665 work in progress, Feb 2013 667 7.2. Informative References 669 [RFC4594] J. Babiarz, K. Chan, F Baker, "Configuration Guidelines for 670 Diffserv Service Classes", RFC 4594, August 2006 672 Authors' Addresses 674 James Polk 675 3913 Treemont Circle 676 Colleyville, Texas, USA 677 +1.817.271.3552 679 mailto: jmpolk@cisco.com 681 Subha Dhesikan 682 170 W Tasman St 683 San Jose, CA, USA 684 +1.408-902-3351 686 mailto: sdhesika@cisco.com 688 Appendix - Changes to ID 690 [Editor's Note: this appendix should be removed in the RFC-Editor's 691 process.] 693 A.1 - Changes from WG version -00 to WG version -01 695 The following changes were made in this version: 697 - corrected nits 699 - globally replaced GUID link from the MMUSIC Trafficclass ID to the 700 future RFC of that document. 702 - added profiles for presentation-video and presentation-audio 704 A.2 - Changes from Individual -04 to WG version -00 706 The following changes were made in this version: 708 - changed P-Type from APP_TC back to AUTH_APP, which is already 709 defined. 711 - fixed nits and inconsistencies 713 A.3 - Changes from Individual -03 to -04 715 The following changes were made in this version: 717 - clarified security considerations section to mean RSVP cannot 718 police the type of traffic within a reservation to know if a 719 traffic flow should be using a different profile, as defined in 720 this document. 722 - changed existing informative language regarding "... other 723 Sub-types ..." from 'can' to normative 'MAY'. 724 - editorial changes to clear up minor mistakes 726 A.4 - Changes from Individual -02 to -03 728 The following changes were made in this version: 730 - Added [ID-TRAF-CLASS] as a reference 732 - Changed to a new format of the profile string. 734 - Added many new profiles based on the new format into each parent 735 category of Section 3. 737 - changed the GUID to refer to draft-ietf-mmusic-traffic-class-for- 738 sdp-03.txt 740 - changed 'desktop' adjective to 'avconf' to keep in alignment with 741 [ID-TRAF-CLASS] 743 - Have a complete IANA Registry proposal for each application-ID 744 discussed in this draft. 746 - General text clean-up of the draft.