1 / 8

draft-polk-tsvwg-rsvp-app-id-vv-profiles-02

draft-polk-tsvwg-rsvp-app-id-vv-profiles-02. IETF80 (Prague) James Polk Subha Dhesikan. Scope of ID. Purpose – differentiate what traffic type is in each reservation Create registered profiles using RFC 2872 RSVP Application-ID Object for each real-time traffic class defined within RFC 4594.

cocheta-green
Download Presentation

draft-polk-tsvwg-rsvp-app-id-vv-profiles-02

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-polk-tsvwg-rsvp-app-id-vv-profiles-02 IETF80 (Prague) James Polk Subha Dhesikan

  2. Scope of ID • Purpose – differentiate what traffic type is in each reservation • Create registered profiles using RFC 2872 RSVP Application-ID Object for each real-time traffic class defined within RFC 4594

  3. RSVP APP-ID Object Template The template from RFC 2872 is as follows: 0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PE Length (8) | P-type = AUTH_APP | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Attribute Length | A-type = | Sub-type = | | | POLICY_LOCATOR| ASCII_DN | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Application policy locator attribute data in X.500 DN format | | (see below) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Creates a profile that includes the following pieces of information: “P-type = , A-type = , Sub-type = , GUID=, APP= , VER= “ Version-02 created a new P-Type unique to this called “APP-TC” for application traffic class

  4. Profiles Proposed The Broadcast video Profile APP-TC, POLICY_LOCATOR, ASCII_DN, "GUID=http://www.ietf.org/rfc/rfc4594.txt", APP=broadcast-video, VER=" The Real-time Interactive Profile APP-TC, POLICY_LOCATOR, ASCII_DN, "GUID=http://www.ietf.org/rfc/rfc4594.txt, APP=realtime-interactive, VER=" The Multimedia Conferencing Profile APP-TC, POLICY_LOCATOR, ASCII_DN, "GUID=http://www.ietf.org/rfc/rfc4594.txt, APP=multimedia-conferencing, VER="

  5. Profiles Proposed The Multimedia Streaming Profile APP-TC, POLICY_LOCATOR, ASCII_DN, "GUID=http://www.ietf.org/rfc/rfc4594.txt, APP=multimedia-streaming, VER=" The Telephony Profile (was “VOIP”) APP-TC, POLICY_LOCATOR, ASCII_DN, "GUID=http://www.ietf.org/rfc/rfc4594.txt, APP=Telephony, VER=" The CAC-Admitted Voice Profile APP-TC, POLICY_LOCATOR, ASCII_DN, "GUID=http://www.ietf.org/rfc/rfc5865.txt, APP=cac-admitted-voice, VER="

  6. Fixed Open issues in this Version • The “VER=“ field will not be dropped • Made the change to a “GUID=“ value • i.e., "http://www.ietf.org/rfc/rfc4594.txt" instead of "RFC4594“ • Created a new P-type • APP-TC = Application Traffic Class)

  7. delimiter Proprietary delimiter New Open issues • MMUSIC WG wants to rename traffic class labels • They don’t like the 1-to-1 mapping to DSCPs • They want clear definitions of what traffic goes into each traffic class • This relates to the layer 7 traffic classification between SIP servers (i.e., a new attribute line per media codec) • draft-polk-mmusic-traffic-class-for-sdp-01 creates a label hierarchy like: Multimedia-conferencing.telepresence.immersive._foo._bar.admitted

  8. Next • Is this interesting enough to consider standardizing?

More Related