idnits 2.17.1 draft-polk-tsvwg-rsvp-app-id-vv-profiles-04.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 16, 2012) is 4274 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 81, but not defined == Missing Reference: 'RFC2752' is mentioned on line 142, but not defined ** Obsolete undefined reference: RFC 2752 (Obsoleted by RFC 3182) == Missing Reference: 'TBD' is mentioned on line 326, but not defined == Unused Reference: 'RFC2119' is defined on line 636, but no explicit reference was found in the text == Unused Reference: 'RFC2474' is defined on line 644, but no explicit reference was found in the text == Unused Reference: 'RFC2750' is defined on line 648, but no explicit reference was found in the text == Unused Reference: 'RFC3182' is defined on line 658, but no explicit reference was found in the text == Unused Reference: 'RFC4594' is defined on line 671, 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 (~~), 11 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 16, 2013 Cisco Systems 5 Intended Status: Standards Track July 16, 2012 6 Updates: RFC 2872 (if accepted) 8 Resource Reservation Protocol (RSVP) Application-ID 9 Profiles for Voice and Video Streams 10 draft-polk-tsvwg-rsvp-app-id-vv-profiles-04 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 January 16, 2013. 37 Copyright Notice 39 Copyright (c) 2012 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 New RSVP Policy Element (P-Type) . . . . . . . . . . . . 7 65 5.2 Application Profiles . . . . . . . . . . . . . . . . . . 7 66 5.2.1 Broadcast Profiles IANA Registry . . . . . . . . . . . 8 67 5.2.2 Realtime-Interactive Profiles IANA Registry . . . . . . 8 68 5.2.3 Multimedia-Conferencing Profiles IANA Registry . . . . 9 69 5.2.4 Multimedia-Streaming Profiles IANA Registry . . . . . . 10 70 5.2.5 Conversational Profiles IANA Registry . . . . . . . . . 10 71 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 12 72 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 7.1. Normative References . . . . . . . . . . . . . . . . . 12 74 7.2. Informative References . . . . . . . . . . . . . . . . 13 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 13 76 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . 14 78 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 80 document are to be interpreted as described in RFC 2119 [RFC 2119]. 82 1. Introduction 84 RFC 2872 [RFC2872] describes the usage of policy elements for 85 providing application information in Resource Reservation Protocol 86 (RSVP) signaling [RFC2205]. The intention of providing this 87 information is to enable application-based policy control. However, 88 RFC 2872 does not enumerate any application profiles. The absence 89 of explicit, uniform profiles leads to incompatible handling of 90 these values and misapplied policies. An application profile used by 91 a sender might not be understood by the intermediaries or receiver 92 in a different domain. Therefore, there is a need to enumerate 93 application profiles that are universally understood and applied for 94 correct policy control. 96 Call control between endpoints has the ability to bind or associate 97 many attributes to a reservation. One new attribute currently being 98 defined is to establish the type of traffic contained that 99 reservation. This is accomplished via assigning a traffic label to 100 the call (or session or flow) [ID-TRAF-CLASS]. 102 This document takes the application traffic classes from 103 [ID-TRAF-CLASS] and places those strings in the APP-ID object 104 defined in RFC 2872. Thus, the intermediary devices (e.g., routers) 105 processing the RSVP message can learn the identified profile within 106 the Application-ID policy element for a particular reservation, and 107 possibly be configured with the profile(s) to understand them 108 correctly, thus performing the correct admission control. 110 Another goal of this document is to the ability to signal an 111 application profile which can then be translated into a DSCP value 112 as per the choice of each domain. While the DCLASS object [RFC2996] 113 allows the transfer of DSCP value in an RSVP message, it does not 114 allow the flexibility of having different domains choosing the DSCP 115 value for the traffic classes that that they maintain. 117 How these labels indicate the appropriate Differentiated Services 118 Codepoint (DSCP) is out of scope for this document. 120 This document will break out each application type and propose how 121 the values in application-id template should be populated for 122 uniformity and interoperability. 124 2. Application ID Template 126 The template from RFC 2872 is as follows: 128 0 1 2 3 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | PE Length (8) | P-type = AUTH_APP | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | Attribute Length | A-type = | Sub-type = | 133 | | POLICY_LOCATOR| ASCII_DN | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | Application name as ASCII string | 136 | (e.g. SAP.EXE) | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 In line with how this policy element is constructed in RFC 2872, the 140 A-type will remain "POLICY_LOCATOR". 142 The P-type field is first created in [RFC2752]. This document 143 creates the new P-type "APP_TC" for application traffic class, which 144 is more appropriately named for the purpose described in this 145 extension. 147 The first Sub-type will be mandatory for every profile within this 148 document, and will be "ASCII_DN". No other Sub-types are defined by 149 any profile within this document, but MAY be included by individual 150 implementations - and MUST be ignored if not understood by receiving 151 implementations along the reservation path. 153 RFC 2872 states the #1 sub-element from RFC 2872 as the "identifier 154 that uniquely identifies the application vendor", which is optional 155 to include. This document modifies this vendor limitation so that 156 the identifier need only be unique - and not limited to an 157 application vendor (identifier). For example, this specification now 158 allows an RFC that defines an industry recognizable term or string 159 to be a valid identifier. For example, a term or string taken from 160 another IETF document, such as "conversational" or "avconf" from 161 [ID-TRAF-CLASS]. This sub-element is still optional to include. 163 The following subsections will define the values within the above 164 template into specific profiles for voice and video identification. 166 3. The Voice and Video Application-ID Profiles 168 This section contains the elements of the Application ID policy 169 object which is used to signal the application classes defined in 170 [ID-TRAF-CLASS]. 172 3.1 The Broadcast Profiles 174 Broadcast profiles are for minimally buffered one-way streaming 175 flows, such as video surveillance, or Internet based concerts or 176 non-VOD TV broadcasts such as live sporting events. 178 There will be Broadcast profiles for 180 - Broadcast IPTV for audio and video 181 - Broadcast Live-events for audio and video 182 - Broadcast Surveillance for audio and video 184 Here is an example profile for identifying Broadcast 185 Video-Surveillance 187 APP_TC, POLICY_LOCATOR, ASCII_DN, 188 "GUID=http://www.ietf.org/internet-drafts/ 189 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 190 APP=broadcast.video.surveillance, VER=" 192 Where the Globally Unique Identifier (GUID) indicates the documented 193 reference that created this well known string [ID-TRAF-CLASS], the 194 APP is the profile name with no spaces, and the "VER=" is included, 195 but has no value at this time. 197 3.2 The Realtime Interactive Profiles 198 Realtime Interactive profiles are for on-line gaming, and both 199 remote and virtual avconf applications, in which the timing is 200 particularly important towards the feedback to uses of these 201 applications. This traffic type will generally not be UDP based, 202 with minimal tolerance to RTT delays. 204 There will be Realtime Interactive profiles for 206 - Realtime-Interactive Gaming 207 - Realtime-Interactive Remote-Desktop 208 - Realtime-Interactive Virtualized-Desktop 210 Here is the profile for identifying Realtime-Interactive Gaming 212 APP_TC, POLICY_LOCATOR, ASCII_DN, 213 "GUID=http://www.ietf.org/internet-drafts/ 214 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 215 APP=realtime-interactive.gaming, VER=" 217 Where the Globally Unique Identifier (GUID) indicates the documented 218 reference that created this well known string [ID-TRAF-CLASS], the 219 APP is the profile name with no spaces, and the "VER=" is included, 220 but has no value, but MAY if versioning becomes important. 222 3.3 The Multimedia Conferencing Profiles 224 There will be Multimedia Conferencing profiles for presentation 225 data, application sharing and whiteboarding, where these 226 applications will most often be associated with a larger 227 Conversational (audio and/or audio/video) conference. Timing is 228 important, but some minimal delays are acceptable, unlike the case 229 for Realtime-Interactive traffic. 231 - Multimedia-Conferencing presentation-data 232 - Multimedia-Conferencing application-sharing 233 - Multimedia-Conferencing whiteboarding 235 Here is the profile for identifying Multimedia-Conferencing 236 Application-sharing 238 APP_TC, POLICY_LOCATOR, ASCII_DN, 239 "GUID=http://www.ietf.org/internet-drafts/ 240 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 241 APP=multimedia-conferencing.application-sharing, VER=" 243 Where the Globally Unique Identifier (GUID) indicates the RFC 244 reference that created this well known string [ID-TRAF-CLASS], the 245 APP is the profile name with no spaces, and the "VER=" is included, 246 but has no value, but MAY if versioning becomes important. 248 3.4 The Multimedia Streaming Profiles 250 Multimedia Streaming profiles are for more significantly buffered 251 one-way streaming flows than Broadcast profiles. These include... 253 There will be Multimedia Streaming profiles for 255 - Multimedia-Streaming multiplex 256 - Multimedia-Streaming webcast 258 Here is the profile for identifying Multimedia Streaming 259 webcast 261 APP_TC, POLICY_LOCATOR, ASCII_DN, 262 "GUID=http://www.ietf.org/internet-drafts/ 263 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 264 APP=multimedia-streaming.webcast, VER=" 266 Where the Globally Unique Identifier (GUID) indicates the documented 267 reference that created this well known string [ID-TRAF-CLASS], the 268 APP is the profile name with no spaces, and the "VER=" is included, 269 but has no value, but MAY if versioning becomes important. 271 3.5 The Conversational Profiles 273 Conversational category is for realtime bidirectional 274 communications, such as voice or video, and is the most numerous due 275 to the choices of application with or without adjectives. The number 276 of profiles is then doubled because there needs to be one for 277 unadmitted and one for admitted. The IANA section lists all that 278 are currently proposed for registration at this time, therefore 279 there will not be an exhaustive list provided in this section. 281 There will be conversational profiles for 283 - Conversational Audio 284 - Conversational Audio Admitted 285 - Conversational Video 286 - Conversational Video Admitted 287 - Conversational Audio Avconf 288 - Conversational Audio Avconf Admitted 289 - Conversational Video Avconf 290 - Conversational Video Avconf Admitted 291 - Conversational Audio Immersive 292 - Conversational Audio Immersive Admitted 293 - Conversational Video Immersive 294 - Conversational Video Immersive Admitted 296 Here is an example profile for identifying Conversational Audio: 298 APP_TC, POLICY_LOCATOR, ASCII_DN, 299 "GUID=http://www.ietf.org/internet-drafts/ 300 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 301 APP=conversational.audio, VER=" 303 Where the Globally Unique Identifier (GUID) indicates the documented 304 reference that created this well known string [ID-TRAF-CLASS], the 305 APP is the profile name with no spaces, and the "VER=" is included, 306 but has no value, but MAY if versioning becomes important. 308 4. Security considerations 310 The security considerations section within RFC 2872 sufficiently 311 covers this document, with one possible exception - someone using 312 the wrong template values (e.g., claiming a reservation is 313 Multimedia Streaming when it is in fact Real-time Interactive). 314 Given that each traffic flow is within separate reservations, and 315 RSVP does not have the ability to police the type of traffic within 316 any reservation, solving for this appears to be administratively 317 handled at best. This is not meant to be a 'punt', but there really 318 is nothing this template creates that is going to make things any 319 harder for anyone (that we know of now). 321 5. IANA considerations 323 5.1 New RSVP Policy Element (P-Type) 325 In line with the convention created in RFC 3182, the following 326 P-Type is created in the RSVP Policy Element registry [TBD]: 328 4 APP_TC Traffic Class identification of applications 330 [Editor's note: Unfortunately, RFC 2750 specified the creation of 331 the "RSVP Policy Element" IANA registration, which 332 does not appear at the 333 http://www.iana.org/assignments/rsvp-parameters 334 page, therefore it appears this registry does not 335 yet exist. We will get with the chairs to work on 336 this.] 338 5.2 Application Profiles 340 This document requests IANA create a new registry for the 341 application identification classes similar to the following table 342 within the Resource Reservation Protocol (RSVP) Parameters registry: 344 Registry Name: RSVP APP-ID Profiles 345 Reference: [this document] 346 Registration procedures: Standards Track document [RFC5226] 348 5.2.1 Broadcast Profiles IANA Registry 350 Broadcast Audio IPTV Profile 351 P-type = APP_TC 352 A-type = POLICY_LOCATOR 353 Sub-type = ASCII_DN 354 Conformant policy locator = 355 "GUID=http://www.ietf.org/internet-drafts/ 356 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 357 APP=broadcast.audio.iptv, VER=" 358 Reference: [this document] 360 Broadcast Video IPTV Profile 361 P-type = APP_TC 362 A-type = POLICY_LOCATOR 363 Sub-type = ASCII_DN 364 Conformant policy locator = 365 "GUID=http://www.ietf.org/internet-drafts/ 366 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 367 APP=broadcast.video.iptv, VER=" 368 Reference: [this document] 370 Broadcast Audio Live-events Profile 371 P-type = APP_TC 372 A-type = POLICY_LOCATOR 373 Sub-type = ASCII_DN 374 Conformant policy locator = 375 "GUID=http://www.ietf.org/internet-drafts/ 376 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 377 APP=broadcast.audio.live-events, VER=" 378 Reference: [this document] 380 Broadcast Audio Live-events Profile 381 P-type = APP_TC 382 A-type = POLICY_LOCATOR 383 Sub-type = ASCII_DN 384 Conformant policy locator = 385 "GUID=http://www.ietf.org/internet-drafts/ 386 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 387 APP=broadcast.video.live-events, VER=" 388 Reference: [this document] 390 Broadcast Audio-Surveillance Profile 391 P-type = APP_TC 392 A-type = POLICY_LOCATOR 393 Sub-type = ASCII_DN 394 Conformant policy locator = 395 "GUID=http://www.ietf.org/internet-drafts/ 396 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 397 APP=broadcast.audio.surveillance, VER=" 399 Reference: [this document] 401 Broadcast Video-Surveillance Profile 402 P-type = APP_TC 403 A-type = POLICY_LOCATOR 404 Sub-type = ASCII_DN 405 Conformant policy locator = 406 "GUID=http://www.ietf.org/internet-drafts/ 407 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 408 APP=broadcast.video.surveillance, VER=" 409 Reference: [this document] 411 5.2.2 Realtime-Interactive Profiles IANA Registry 413 Realtime-Interactive Gaming Profile 414 P-type = APP_TC 415 A-type = POLICY_LOCATOR 416 Sub-type = ASCII_DN 417 Conformant policy locator = 418 "GUID=http://www.ietf.org/internet-drafts/ 419 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 420 APP= realtime-interactive.gaming, VER=" 421 Reference: [this document] 423 Real-time Interactive Remote-Desktop Profile 424 P-type = APP_TC 425 A-type = POLICY_LOCATOR 426 Sub-type = ASCII_DN 427 Conformant policy locator = 428 "GUID=http://www.ietf.org/internet-drafts/ 429 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 430 APP=realtime-interactive.remote-desktop, VER=" 431 Reference: [this document] 433 Real-time Interactive Virtualized-Desktop Profile 434 P-type = APP_TC 435 A-type = POLICY_LOCATOR 436 Sub-type = ASCII_DN 437 Conformant policy locator = 438 "GUID=http://www.ietf.org/internet-drafts/ 439 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 440 APP=realtime-interactive.virtualized-desktop, 441 VER=" 442 Reference: [this document] 444 5.2.3 Multimedia-Conferencing Profiles IANA Registry 446 Multimedia-Conferencing Presentation-Data Profile 447 P-type = APP_TC 448 A-type = POLICY_LOCATOR 449 Sub-type = ASCII_DN 450 Conformant policy locator = 451 "GUID=http://www.ietf.org/internet-drafts/ 452 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 453 APP= multimedia-conferencing.presentation-data, 454 VER=" 455 Reference: [this document] 457 Multimedia-Conferencing Application-Sharing Profile 458 P-type = APP_TC 459 A-type = POLICY_LOCATOR 460 Sub-type = ASCII_DN 461 Conformant policy locator = 462 "GUID=http://www.ietf.org/internet-drafts/ 463 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 464 APP= multimedia-conferencing.application-sharing, 465 VER=" 466 Reference: [this document] 468 Multimedia-Conferencing Whiteboarding Profile 469 P-type = APP_TC 470 A-type = POLICY_LOCATOR 471 Sub-type = ASCII_DN 472 Conformant policy locator = 473 "GUID=http://www.ietf.org/internet-drafts/ 474 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 475 APP= multimedia-conferencing.whiteboarding, VER=" 476 Reference: [this document] 478 5.2.4 Multimedia-Streaming Profiles IANA Registry 480 Multimedia-Streaming Multiplex Profile 481 P-type = APP_TC 482 A-type = POLICY_LOCATOR 483 Sub-type = ASCII_DN 484 Conformant policy locator = 485 "GUID=http://www.ietf.org/internet-drafts/ 486 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 487 APP=multimedia-streaming.multiplex, VER=" 488 Reference: [this document] 490 Multimedia-Streaming Webcast Profile 491 P-type = APP_TC 492 A-type = POLICY_LOCATOR 493 Sub-type = ASCII_DN 494 Conformant policy locator = 495 "GUID=http://www.ietf.org/internet-drafts/ 496 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 497 APP=multimedia-streaming.webcast, VER=" 498 Reference: [this document] 500 5.2.5 Conversational Profiles IANA Registry 502 Conversational Audio Profile 503 P-type = APP_TC 504 A-type = POLICY_LOCATOR 505 Sub-type = ASCII_DN 506 Conformant policy locator = 507 "GUID=http://www.ietf.org/internet-drafts/ 508 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 509 APP=conversational.audio, VER=" 510 Reference: [this document] 512 Conversational Audio Admitted Profile 513 P-type = APP_TC 514 A-type = POLICY_LOCATOR 515 Sub-type = ASCII_DN 516 Conformant policy locator = 517 "GUID=http://www.ietf.org/internet-drafts/ 518 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 519 APP=conversational.audio.aq:admitted, VER=" 520 Reference: [this document] 522 Conversational Video Profile 523 P-type = APP_TC 524 A-type = POLICY_LOCATOR 525 Sub-type = ASCII_DN 526 Conformant policy locator = 527 "GUID=http://www.ietf.org/internet-drafts/ 528 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 529 APP=conversational.video, VER=" 530 Reference: [this document] 532 Conversational Video Admitted Profile 533 P-type = APP_TC 534 A-type = POLICY_LOCATOR 535 Sub-type = ASCII_DN 536 Conformant policy locator = 537 "GUID=http://www.ietf.org/internet-drafts/ 538 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 539 APP=conversational.video.aq:admitted, VER=" 540 Reference: [this document] 542 Conversational Audio Avconf Profile 543 P-type = APP_TC 544 A-type = POLICY_LOCATOR 545 Sub-type = ASCII_DN 546 Conformant policy locator = 547 "GUID=http://www.ietf.org/internet-drafts/ 548 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 549 APP=conversational.audio.avconf, VER=" 550 Reference: [this document] 552 Conversational Audio Avconf Admitted Profile 553 P-type = APP_TC 554 A-type = POLICY_LOCATOR 555 Sub-type = ASCII_DN 556 Conformant policy locator = 557 "GUID=http://www.ietf.org/internet-drafts/ 558 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 559 APP=conversational.audio.avconf.aq:admitted, 560 VER=" 561 Reference: [this document] 563 Conversational Video Avconf Profile 564 P-type = APP_TC 565 A-type = POLICY_LOCATOR 566 Sub-type = ASCII_DN 567 Conformant policy locator = 568 "GUID=http://www.ietf.org/internet-drafts/ 569 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 570 APP=conversational.video.avconf, VER=" 571 Reference: [this document] 573 Conversational Video Avconf Admitted Profile 574 P-type = APP_TC 575 A-type = POLICY_LOCATOR 576 Sub-type = ASCII_DN 577 Conformant policy locator = 578 "GUID=http://www.ietf.org/internet-drafts/ 579 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 580 APP=conversational.video.avconf.aq:admitted, 581 VER=" 582 Reference: [this document] 584 Conversational Audio Immersive Profile 585 P-type = APP_TC 586 A-type = POLICY_LOCATOR 587 Sub-type = ASCII_DN 588 Conformant policy locator = 589 "GUID=http://www.ietf.org/internet-drafts/ 590 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 591 APP=conversational.audio.immersive, VER=" 592 Reference: [this document] 594 Conversational Audio Immersive Admitted Profile 595 P-type = APP_TC 596 A-type = POLICY_LOCATOR 597 Sub-type = ASCII_DN 598 Conformant policy locator = 599 "GUID=http://www.ietf.org/internet-drafts/ 600 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 601 APP=conversational.audio.immersive.aq:admitted, 602 VER=" 604 Reference: [this document] 606 Conversational Video Immersive Profile 607 P-type = APP_TC 608 A-type = POLICY_LOCATOR 609 Sub-type = ASCII_DN 610 Conformant policy locator = 611 "GUID=http://www.ietf.org/internet-drafts/ 612 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 613 APP=conversational.video.immersive, VER=" 614 Reference: [this document] 616 Conversational Video Immersive Admitted Profile 617 P-type = APP_TC 618 A-type = POLICY_LOCATOR 619 Sub-type = ASCII_DN 620 Conformant policy locator = 621 "GUID=http://www.ietf.org/internet-drafts/ 622 draft-ietf-mmusic-traffic-class-for-sdp-01.txt, 623 APP=conversational.video.immersive.aq:admitted, 624 VER=" 625 Reference: [this document] 627 7. Acknowledgments 629 To Francois Le Faucheur, Paul Jones and Glen Lavers for their 630 helpful comments and encouragement. 632 8. References 634 8.1. Normative References 636 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 637 Requirement Levels", RFC 2119, March 1997 638 Functional Specification", RFC 2205, September 1997 640 [RFC2205] R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, S. Jamin, 641 "Resource ReSerVation Protocol (RSVP) -- Version 1 642 Functional Specification", RFC 2205, September 1997 644 [RFC2474] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the 645 Differentiated Services Field (DS Field) in the IPv4 and 646 IPv6 Headers ", RFC 2474, December 1998 648 [RFC2750] S. Herzog, "RSVP Extensions for Policy Control", RFC 2750, 649 January 2000 651 [RFC2872] Y. Bernet, R. Pabbati, "Application and Sub Application 652 Identity Policy Element for Use with RSVP", RFC 2872, 653 June 2000 655 [RFC2996] Y. Bernet, "Format of the RSVP DCLASS Object", RFC 2996, 656 November 2000 658 [RFC3182] S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. 659 Herzog, R. Hess, "Identity Representation for RSVP", 660 RFC 3182, October 2001 662 [RFC5226] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 663 Considerations Section in RFCs", RFC 5226, May 2008 665 [ID-TRAF-CLASS] J. Polk, S. Dhesikan, P. Jones, " The Session 666 Description Protocol (SDP) 'trafficclass' Attribute ", 667 work in progress, Oct 2011 669 8.2. Informative References 671 [RFC4594] J. Babiarz, K. Chan, F Baker, "Configuration Guidelines for 672 Diffserv Service Classes", RFC 4594, August 2006 674 Authors' Addresses 676 James Polk 677 3913 Treemont Circle 678 Colleyville, Texas, USA 679 +1.817.271.3552 681 mailto: jmpolk@cisco.com 683 Subha Dhesikan 684 170 W Tasman St 685 San Jose, CA, USA 686 +1.408-902-3351 688 mailto: sdhesika@cisco.com 690 Appendix - Changes to ID 692 A.1 - Changes from Individual -03 to -04 694 The following changes were made in this version: 696 - clarified security considerations section to mean RSVP cannot 697 police the type of traffic within a reservation to know if a 698 traffic flow should be using a different profile, as defined in 699 this document. 701 - changed existing informative language regarding "... other 702 Sub-types ..." from 'can' to normative 'MAY'. 704 - editorial changes to clear up minor mistakes 706 A.2 - Changes from Individual -02 to -03 708 The following changes were made in this version: 710 - Added [ID-TRAF-CLASS] as a reference 712 - Changed to a new format of the profile string. 714 - Added many new profiles based on the new format into each parent 715 category of Section 3. 717 - changed the GUID to refer to draft-ietf-mmusic-traffic-class-for- 718 sdp-01.txt 720 - changed 'desktop' adjective to 'avconf' to keep in alignment with 721 draft-ietf-mmusic-traffic-class-for-sdp-01.txt 723 - Have a complete IANA Registry proposal for each application-ID 724 discussed in this draft. 726 - General text clean-up of the draft.