draft-ietf-mmusic-traffic-class-for-sdp-00.txt   draft-ietf-mmusic-traffic-class-for-sdp-01.txt 
Network WG James Polk Network WG James Polk
Internet-Draft Subha Dhesikan Internet-Draft Subha Dhesikan
Expires: April 24, 2012 Paul Jones Expires: Sept 12, 2012 Paul Jones
Intended Status: Standards Track (PS) Cisco Systems Intended Status: Standards Track (PS) Cisco Systems
October 24, 2011 March 12, 2012
The Session Description Protocol (SDP) 'trafficclass' Attribute The Session Description Protocol (SDP) 'trafficclass' Attribute
draft-ietf-mmusic-traffic-class-for-sdp-00 draft-ietf-mmusic-traffic-class-for-sdp-01
Abstract Abstract
This document proposes a new Session Description Protocol (SDP) This document proposes a new Session Description Protocol (SDP)
attribute to identify the traffic class a session is requesting attribute to identify the traffic class a session is requesting
in its offer/answer exchange. in its offer/answer exchange.
Legal
This documents and the information contained therein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted in full conformance with the
the provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on September 12, 2012.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Traffic Class Framework and String Definitions . . . . . . . 5 2. Traffic Class Framework and String Definitions . . . . . . . 5
3. Traffic Class Attribute Definition . . . . . . . . . . . . . 11 3. Traffic Class Attribute Definition . . . . . . . . . . . . . 11
4. Offer/Answer Behavior . . . . . . . . . . . . . . . . . . . . 14 4. Offer/Answer Behavior . . . . . . . . . . . . . . . . . . . . 15
4.1 Offer Behavior . . . . . . . . . . . . . . . . . . . . . 14 4.1 Offer Behavior . . . . . . . . . . . . . . . . . . . . . 15
4.2 Answer Behavior . . . . . . . . . . . . . . . . . . . . . 14 4.2 Answer Behavior . . . . . . . . . . . . . . . . . . . . . 15
5. Security considerations . . . . . . . . . . . . . . . . . . . 16 5. Security considerations . . . . . . . . . . . . . . . . . . . 16
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 17
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 18 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 20
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1. Introduction 1. Introduction
The Session Description Protocol (SDP) [RFC4566] provides a means The Session Description Protocol (SDP) [RFC4566] provides a means
for an offerer to describe the specifics of a session to an for an offerer to describe the specifics of a session to an
answerer, and for the answerer to respond back with its session answerer, and for the answerer to respond back with its session
skipping to change at page 3, line 37 skipping to change at page 3, line 37
of session the RTP is, including the ability to provide call of session the RTP is, including the ability to provide call
admission control based on the type of traffic in the network. admission control based on the type of traffic in the network.
- allow network monitoring/management of traffic types realtime and - allow network monitoring/management of traffic types realtime and
after-the-fact analysis. after-the-fact analysis.
Some network operators want the ability to guarantee certain traffic Some network operators want the ability to guarantee certain traffic
gets a minimum amount of network bandwidth per link or through a gets a minimum amount of network bandwidth per link or through a
series of links that perhaps makes up a network such as a campus or series of links that perhaps makes up a network such as a campus or
WAN, or a backbone. For example, a call center voice application WAN, or a backbone. For example, a call center voice application
gets at least 20% of a link as a minimum bandwidth. gets at least 20% of a link as a minimum bandwidth allocation.
Some network operators want the ability to allow certain users or Some network operators want the ability to allow certain users or
devices access to greater bandwidth during non-busy hours, than devices access to greater bandwidth during non-busy hours, than
during busy hours of the day. For example, all desktop video to during busy hours of the day. For example, all desktop video to
operate at 1080p during non-peak times, but curtail a similar operate at 1080p during non-peak times, but curtail a similar
session between the same users or devices to 720p or 360p during session between the same users or devices to 720p or 360p during
peak hours. This case is not as clear as accepting or denying peak hours. Another example would be to reduce the frames per
similar sessions during different times of the day, but tuning the second (fps) rate, say from 30fps to 15fps. This case is not as
access to the bandwidth based on the type of session. In other clear as accepting or denying similar sessions during different
words, tune down the bandwidth for desktop video during peak hours times of the day, but tuning the access to the bandwidth based on
to allow a 3-screen telepresense session that would otherwise look the type of session. In other words, tune down the bandwidth for
like the same type of traffic (RTP, and more granular, video). desktop video during peak hours to allow a 3-screen telepresense
session that would otherwise look like the same type of traffic
(RTP, and more granular, video).
RFC 4594 established a guideline for classifying the various flows RFC 4594 established a guideline for classifying the various flows
in the network and the Differentiated Services Codepoints (DSCP) in the network and the Differentiated Services Codepoints (DSCP)
that apply to many traffic types (table 3 of [RFC4594]), including that apply to many traffic types (table 3 of [RFC4594]), including
RTP based voice and video traffic sessions. The RFC also defines the RTP based voice and video traffic sessions. The RFC also defines the
per hop network behavior that is strongly encouraged for each of per hop network behavior that is strongly encouraged for each of
these application traffic types based on the traffic characteristics these application traffic types based on the traffic characteristics
and tolerances to delay, loss and jitter within each traffic class. and tolerances to delay, loss and jitter within each traffic class.
Video was broken down into 4 categories in that RFC, and voice into Video was broken down into 4 categories in that RFC, and voice into
skipping to change at page 4, line 42 skipping to change at page 4, line 44
between enterprise networks will likely have to take advantage of between enterprise networks will likely have to take advantage of
MPLS. MPLS.
Within a network core, where only MPLS is used, Diffserv typically Within a network core, where only MPLS is used, Diffserv typically
does not apply. That said, Diffserv can be used to identify which does not apply. That said, Diffserv can be used to identify which
traffic goes into which MPLS tunnels [RFC4124]. traffic goes into which MPLS tunnels [RFC4124].
Labeling realtime traffic types using a layer 4 protocol would Labeling realtime traffic types using a layer 4 protocol would
likely mean RSVP [RFC2205] or NSIS [RFC4080]. RSVP has an likely mean RSVP [RFC2205] or NSIS [RFC4080]. RSVP has an
Application Identifier (app-ID) defined in [RFC2872] that provides a Application Identifier (app-ID) defined in [RFC2872] that provides a
means for carrying a traffic class label along the data path. An means for carrying a traffic class label along the media path. An
advantage with this mechanism is for the label to inform each domain advantage with this mechanism is for the label to inform each domain
along the media path what type of traffic this traffic flow is, and along the media path what type of traffic this traffic flow is, and
allow each domain to adjust the appropriate DSCP (set by each domain allow each domain to adjust the appropriate DSCP (set by each domain
for use within that domain). Meaning, if a DSCP is set by an for use within that domain). Meaning, if a DSCP is set by an
endpoint or a router in the first domain and gets reset by a SP, the endpoint or a router in the first domain and gets reset by a SP, the
far end domain will be able to reset the DSCP to the intended far end domain will be able to reset the DSCP to the intended
traffic class. There is a proposed extension to RSVP which creates traffic class. There is a proposed extension to RSVP which creates
individual profiles for what goes into each app-ID field to describe individual profiles for what goes into each app-ID field to describe
these traffic classes [ID-RSVP-PROF], which will take advantage of these traffic classes [ID-RSVP-PROF], which will take advantage of
what is described in this document. what is described in this document.
skipping to change at page 5, line 45 skipping to change at page 5, line 48
new SDP attribute "trafficclass". Section 4 discusses the offerer new SDP attribute "trafficclass". Section 4 discusses the offerer
and answerer behavior when generating or receiving this attribute. and answerer behavior when generating or receiving this attribute.
2. Traffic Class Framework and String Definitions 2. Traffic Class Framework and String Definitions
The framework of the traffic class attribute will have at least two The framework of the traffic class attribute will have at least two
parts, allowing for several more to be included. The intention is to parts, allowing for several more to be included. The intention is to
have a parent class (e.g., Conversational) that merely serves as the have a parent class (e.g., Conversational) that merely serves as the
anchor point for an application component that when paired together, anchor point for an application component that when paired together,
form the highest level traffic class. An adjective component form the highest level traffic class. An adjective component
provides further granularity for the application. provides further granularity for the application. There can be more
than one adjective within a traffic class label to further refine
the uniqueness of a traffic class being described.
The traffic class label will have the following structure, The traffic class label will have the following structure,
parent.application(.adjective)(.adjective)(.admitted/non-admitted) parent.application(.adjective)(.adjective)
[Editor's Note: the above is not exactly the ABNF to be used. [Editor's Note: the above is not exactly the ABNF to be used.
The order is right. The parent and application The order is right. The parent and application
MUST appear (each only once) and zero or more MUST appear (each only once) and zero or more
adjectives can appear.] adjectives can appear.]
Where Where
1) the 1st component is the human understandable category; 1) the 1st component is the human understandable category;
2) the 2nd component is the application; 2) the 2nd component is the application;
3) an optional 3rd component or series of components are 3) an optional 3rd component or series of components are
adjective(s) used to further refine the application component; adjective(s) used to further refine the application component;
and and
4) an optional 4th component is to classify this flow as a CAC
admitted or non-admitted traffic flow. The default is
non-admitted, whether present or not.
The construction of the traffic class label for Telepresence video The construction of the traffic class label for Telepresence video
would follow the form like this: would follow the minimum form of:
Conversational.video.immersive Conversational.video.immersive
where there might be one or more adjective after '.immersive'.
There is no traffic class or DSCP value associated with just There is no traffic class or DSCP value associated with just
"Conversational". There is a traffic class associated with "Conversational". There is a traffic class associated with
"Conversational.video", creating a differentiation between it and a "Conversational.video", creating a differentiation between it and a
"Conversational.video.immersive" traffic class, which would have "Conversational.video.immersive" traffic class, which would have
DSCP associated with the latter traffic class, depending on local DSCP associated with the latter traffic class, depending on local
policy. Each parent component is defined below, as are several of policy. Each parent component is defined below, as are several of
application and adjective strings. application and adjective strings.
[Editor's Note: We're not yet sure how much of what's below will be [Editor's Note: We're not yet sure how much of what's below will be
proposed for IANA registration, but the 5 parent proposed for IANA registration, but the 5 parent
skipping to change at page 7, line 8 skipping to change at page 7, line 11
o Text o Text
o application-sharing o application-sharing
o Presentation-data o Presentation-data
o Whiteboarding o Whiteboarding
o Web (conference) chat/instant messaging o Web (conference) chat/instant messaging
o Gaming o Gaming
o Virtual-desktop (interactive) o Virtual-desktop (interactive)
o Remote-desktop o Remote-desktop
o Telemetry (e.g., NORAD missile control) o Telemetry (e.g., NORAD missile control)
o Multiplex (i.e., combined streams) o Multiplex (i.e., combined streams)
o (something to cover theater quality Netflix movies)
o (something to cover YouTube)
o Webcast o Webcast
o IPTV o IPTV
o Live-events (though not the buffered ones) o Live-events (though not the buffered ones)
o surveillance o surveillance
The following adjective components of the traffic class attribute The following adjective components of the traffic class attribute
are as follows: are as follows:
o Immersive o Immersive
o Desktop-video o avconf
o Realtime-Text o Realtime-Text
o web o web
Each of the above 3 lists will be defined in the following Each of the above 3 lists will be defined in the following
subsections. subsections.
2.1 Conversational Parent Traffic Class 2.1 Conversational Parent Traffic Class
The Conversational traffic class is best suited for applications The Conversational traffic class is best suited for applications
that require very low delay variation and generally intended to that require very low delay variation and generally intended to
enable real-time, bi-directional person-to-person or enable real-time, bi-directional person-to-person or
multi-directional via an MTP communication, such as the following multi-directional via an MTP communication, such as the following
application components: application components:
o Audio (voice) o Audio (voice)**
o Video o Video**
o Text (i.e., real-time text required by deaf users) o Text (i.e., real-time text required by deaf users)
With adjective substrings to the above (which may or may not get **The above applications will also be used within Multimedia
IANA registered) Streaming and Broadcast
With adjective substrings to the above
Immersive (TP) - An interactive audio-visual communications Immersive (TP) - An interactive audio-visual communications
experience between remote locations, where the users enjoy a experience between remote locations, where the users enjoy a
strong sense of realism and presence between all participants strong sense of realism and presence between all participants
by optimizing a variety of attributes such as audio and video by optimizing a variety of attributes such as audio and video
quality, eye contact, body language, spatial audio, quality, eye contact, body language, spatial audio,
coordinated environments and natural image size. coordinated environments and natural image size.
Desktop-video - An interactive audio-visual communication Desktop-video - An interactive audio-visual communication
experience that is not immersive in nature, though can have a experience that is not immersive in nature, though can have a
skipping to change at page 8, line 15 skipping to change at page 8, line 17
Realtime-Text (RTT) - a term for real-time transmission of text in Realtime-Text (RTT) - a term for real-time transmission of text in
a character-by-character fashion for use in conversational a character-by-character fashion for use in conversational
services, often as a text equivalent to voice-based services, often as a text equivalent to voice-based
conversational services. Conversational text is defined in the conversational services. Conversational text is defined in the
ITU-T Framework for multimedia services, Recommendation F.700 ITU-T Framework for multimedia services, Recommendation F.700
[RFC5194]. [RFC5194].
Web - for realtime aspects of web conferencing; mutually exclusive Web - for realtime aspects of web conferencing; mutually exclusive
of both Immersive and Desktop video experiences of both Immersive and Desktop video experiences
**The above substrings might also be used within Multimedia +--------------------------------------------------------------------+
Conferencing**
+--------------------------------------------------------------------+
|Traffic Class | | Tolerance to | |Traffic Class | | Tolerance to |
--------------------------------------------------------------------+
| Name | Traffic Characteristics | Loss |Delay |Jitter| | Name | Traffic Characteristics | Loss |Delay |Jitter|
|===============+===============================+======+======+======| |===============+===============================+======+======+======|
| | High priority, typically | Very | Very | Very | | | High priority, typically | Very | Very | Very |
|Conversational | small packets (large video | Low | Low | Low | |Conversational | small packets (large video | Low | Low | Low |
| | frames produce large packets),| | | | | | frames produce large packets),| | | |
| | generally sustained high | | | | | | generally sustained high | | | |
| | packet rate, low inter-packet | | | | | | packet rate, low inter-packet | | | |
| | transmission interval, | | | | | | transmission interval, | | | |
| | usually UDP framed in (S)RTP | | | | | | usually UDP framed in (S)RTP | | | |
+---------------+-------------------------------+------+------+------+ +---------------+-------------------------------+------+------+------+
Figure 1. Conversational Traffic Characteristics
2.2 Multimedia-Conferencing Parent Traffic Class 2.2 Multimedia-Conferencing Parent Traffic Class
Multimedia-Conferencing traffic class is best suited for Multimedia-Conferencing traffic class is best suited for
applications that are generally intended for communication between applications that are generally intended for communication between
human users, but are less demanding in terms of delay, packet loss, human users, but are less demanding in terms of delay, packet loss,
and jitter than what Conversational applications require. These and jitter than what Conversational applications require. These
applications require low to medium delay and may have the ability to applications require low to medium delay and may have the ability to
change encoding rate (rate adaptive) or transmit data at varying change encoding rate (rate adaptive) or transmit data at varying
rates, such as the following application components: rates, such as the following application component:
o application-sharing (that webex does or protocols like T.128) - o application-sharing (that webex does or protocols like T.128) -
An application that shares the output of one or more running An application that shares the output of one or more running
applications or the desktop on a host. This can utilize applications or the desktop on a host. This can utilize
vector graphics, raster graphics or video. vector graphics, raster graphics or video.
o Presentation-data - can be a series of still images or motion o Presentation-data - can be a series of still images or motion
video. video.
o Whiteboarding - an application enabling the exchange of graphical o Whiteboarding - an application enabling the exchange of graphical
skipping to change at page 9, line 16 skipping to change at page 9, line 19
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
|Traffic Class | | Tolerance to | |Traffic Class | | Tolerance to |
| Name | Traffic Characteristics | Loss |Delay |Jitter| | Name | Traffic Characteristics | Loss |Delay |Jitter|
|===============+===============================+======+======+======| |===============+===============================+======+======+======|
| Multimedia | Variable size packets, | Low | Low | Low | | Multimedia | Variable size packets, | Low | Low | Low |
| Conferencing | Variable transmit interval, | - | - | - | | Conferencing | Variable transmit interval, | - | - | - |
| | rate adaptive, reacts to |Medium|Medium|Medium| | | rate adaptive, reacts to |Medium|Medium|Medium|
| | loss, usually TCP-based | | | | | | loss, usually TCP-based | | | |
+---------------+-------------------------------+------+------+------+ +---------------+-------------------------------+------+------+------+
Figure 2. Multimedia Conferencing Traffic Characteristics
2.3 Realtime-Interactive Parent Traffic Class 2.3 Realtime-Interactive Parent Traffic Class
Realtime-Interactive traffic class is intended for interactive Realtime-Interactive traffic class is intended for interactive
variable rate inelastic applications that require low jitter and variable rate inelastic applications that require low jitter and
loss and very low delay, such as the following application loss and very low delay, such as the following application
components: components:
o Gaming - interactive player video games with other users on other o Gaming - interactive player video games with other users on other
hosts (e.g., Doom) hosts (e.g., Doom)
o Virtual desktop (interactive) - similar to an X-windows station, o Virtualized desktop (interactive) - similar to an X-windows
has no local hard drive, or is operating an application with no station, has no local hard drive, or is operating an
local storage application with nolocal storage
o Remote Desktop - controlling a remote node with local peripherals o Remote Desktop - controlling a remote node with local peripherals
(i.e., monitor, keyboard and mouse) (i.e., monitor, keyboard and mouse)
o Telemetry - a communication that allows remote measurement and o Telemetry - a communication that allows remote measurement and
reporting of information (e.g., post launch missile status or reporting of information (e.g., post launch missile status or
energy monitoring) energy monitoring)
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
|Traffic Class | | Tolerance to | |Traffic Class | | Tolerance to |
| Name | Traffic Characteristics | Loss |Delay |Jitter| | Name | Traffic Characteristics | Loss |Delay |Jitter|
|===============+===============================+======+======+======| |===============+===============================+======+======+======|
| Realtime | Inelastic, mostly variable | Low | Very | Low | | Realtime | Inelastic, mostly variable | Low | Very | Low |
| Interactive | rate, rate increases with | | Low | | | Interactive | rate, rate increases with | | Low | |
| | user activity | | | | | | user activity | | | |
+---------------+-------------------------------+------+------+------+ +---------------+-------------------------------+------+------+------+
2.4 Multimedia-Streaming Parent Traffic Class Figure 3. Realtime Interactive Traffic Characteristics
2.4 Multimedia-Streaming Parent Traffic Class
Multimedia-Streaming traffic class is best suited for variable rate Multimedia-Streaming traffic class is best suited for variable rate
elastic streaming media applications where a human is waiting for elastic streaming media applications where a human is waiting for
output and where the application has the capability to react to output and where the application has the capability to react to
packet loss by reducing its transmission rate, such as the following packet loss by reducing its transmission rate, such as the following
application components: application components:
o Audio o Audio
o Video o Video
o Multiplex (i.e., combined streams) o Multiplex (i.e., combined a/v streams)
With adjective substrings to the above (which may or may not get With adjective substrings to the above (which may or may not get
IANA registered) IANA registered)
(something to cover theater quality Netflix movies)
(something to cover YouTube)
Webcast Webcast
The primary difference from the Multimedia-streaming parent class The primary difference from the Multimedia-streaming parent class
and the Broadcast parent class is about the length of time for and the Broadcast parent class is about the length of time for
buffering. Buffered streaming audio and/or video (e.g., Netflix or buffering. Buffered streaming audio and/or video which are initiated
previously-recorded videos on web sites like CNN, ESPN or from an by SDP, and not HTTP. Buffering here can be from many seconds to
internal corporate server). Buffering here can be from seconds to hours, and is typically at the destination end (as opposed to
hours (as opposed to Broadcast buffering which is minimal). The Broadcast buffering which is minimal at the destination). The
buffering aspect is what differentiates this parent class from the buffering aspect is what differentiates this parent class from the
Broadcast class (which has minimal or no buffering). Broadcast class (which has minimal or no buffering).
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
|Traffic Class | | Tolerance to | |Traffic Class | | Tolerance to |
| Name | Traffic Characteristics | Loss |Delay |Jitter| | Name | Traffic Characteristics | Loss |Delay |Jitter|
|===============+===============================+======+======+======| |===============+===============================+======+======+======|
| Multimedia | Variable size packets, |Low - |Medium| High | | Multimedia | Variable size packets, |Low - |Medium| High |
| Streaming | elastic with variable rate |Medium|- High| | | Streaming | elastic with variable rate |Medium|- High| |
| | | | | | | | | | | |
+---------------+-------------------------------+------+------+------+ +---------------+-------------------------------+------+------+------+
Figure 4. Multimedia Streaming Traffic Characteristics
2.5 Broadcast Parent Traffic Class 2.5 Broadcast Parent Traffic Class
Broadcast traffic class is best suited for inelastic streaming media Broadcast traffic class is best suited for inelastic streaming media
applications that may be of constant or variable rate, requiring low Applications, which might have a 'wardrobe malfunction' delay at or
jitter and very low packet loss, such as the following application near the source but not typically at the destination, that may be of
components: constant or variable rate, requiring low jitter and very low packet
loss, such as the following application components:
o Audio
o Video
o Multiplex (i.e., combined a/v streams)
With adjective substrings to the above:
o IPTV o IPTV
o Live events (though not the buffered ones) o Live events (non-buffered)
o Video surveillance o Video surveillance - one way video from a camera (e.g., observing
a parking lot or building exit), typically enabled for
long periods of time, usually stored at the destination.
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
|Traffic Class | | Tolerance to | |Traffic Class | | Tolerance to |
| Name | Traffic Characteristics | Loss |Delay |Jitter| | Name | Traffic Characteristics | Loss |Delay |Jitter|
|===============+===============================+======+======+======| |===============+===============================+======+======+======|
| Broadcast | Constant and variable rate, | Very |Low - |Low - | | Broadcast | Constant and variable rate, | Very |Low - |Low - |
| | inelastic, generally | Low |Medium|Medium| | | inelastic, generally | Low |Medium|Medium|
| | non-bursty flows, generally | | | | | | non-bursty flows, generally | | | |
| | sustained high packet rate, | | | | | | sustained high packet rate, | | | |
| | low inter-packet transmission | | | | | | low inter-packet transmission | | | |
| | interval, usually UDP framed | | | | | | interval, usually UDP framed | | | |
| | in (S)RTP | | | | | | in (S)RTP | | | |
+---------------+-------------------------------+------+------+------+ +---------------+-------------------------------+------+------+------+
Figure 5. Broadcast Traffic Characteristics
3. SDP Attribute Definition 3. SDP Attribute Definition
This document proposes the 'trafficclass' session and media-level This document proposes the 'trafficclass' session and media-level
SDP [RFC4566] attribute. The following is the Augmented SDP [RFC4566] attribute. The following is the Augmented
Backus-Naur Form (ABNF) [RFC5234] syntax for this attribute, which Backus-Naur Form (ABNF) [RFC5234] syntax for this attribute, which
is based on the SDP [RFC4566] grammar: is based on the SDP [RFC4566] grammar:
attribute =/ traffic-classification attribute =/ traffic-classification
traffic-classification = "trafficclass" ":" [SP] parent-class traffic-classification = "trafficclass" ":" [SP] parent-class
"." app-type *( app-param ) "." app-type *( adj-param )
parent-class = "Broadcast" / parent-class = "Broadcast" /
"Realtime-Interactive" / "Realtime-Interactive" /
"Multimedia-Conferencing" / "Multimedia-Conferencing" /
"Multimedia-Streaming" / "Multimedia-Streaming" /
"Conversational" / "Conversational" /
extension-mech extension-mech
extension-mech = token extension-mech = token
app-type = "audio" / "video" / "text" / app-type = "audio" / "video" / "text" /
"application-sharing" / "application-sharing" /
"presentation-data" / "presentation-data" / "whiteboarding" /
"whiteboarding" / "webchat/IM" / "webchat/IM" / "gaming" /
"gaming" / "virtual-desktop" / "virtual-desktop" / "remote-desktop" /
"remote-desktop" / "telemetry"/ "telemetry"/ "multiplex" / "webcast" /
"multiplex" / "Netflix" / "youtube" / "IPTV" / "live-events" /
"webcast" / "IPTV" / "live-events" / "surveillance" / extension-mech
"surveillance"
app-param = "." adjective / "." cac-class adj-param = "." unqualified-adjective /
"." qualified-adjective
adjective = "immersive" / "desktop-video" / unqualified-adjective = "immersive" / "avconf" /
"Realtime-Text" /"web" / "Realtime-Text" /"web" /
generic-param ; from RFC3261 generic-param ; from RFC3261
cac-class = "admitted" / "non-admitted" qualified-adjective = qual-category ":" q-adjective
qual-category = "aq" / extension-mech
q-adjective = "admitted" / "non-admitted" / "none" /
generic-param ; from RFC3261
The attribute is named "trafficclass", for traffic classification, The attribute is named "trafficclass", for traffic classification,
identifying which one of the five traffic classes applies to the identifying which one of the five traffic classes applies to the
media stream. There MUST NOT be more than one trafficclass attribute media stream. There MUST NOT be more than one trafficclass attribute
per media line. Confusion would result in where more than one exists per media line. Confusion would result in where more than one exists
per m= line. per m= line.
The parent classes in this document are an augmented version of the The parent classes in this document are an augmented version of the
application labels introduced by table 3 of RFC 4595 (which will be application labels introduced by table 3 of RFC 4595 (which will be
rewritten based on the updated labels and treatments expected for rewritten based on the updated labels and treatments expected for
skipping to change at page 12, line 31 skipping to change at page 12, line 48
+-------------------------+------------------------------+ +-------------------------+------------------------------+
| Realtime-Interactive | Realtime-Interactive | | Realtime-Interactive | Realtime-Interactive |
+-------------------------+------------------------------+ +-------------------------+------------------------------+
| Multimedia-Conferencing | Multimedia-Conferencing | | Multimedia-Conferencing | Multimedia-Conferencing |
+-------------------------+------------------------------+ +-------------------------+------------------------------+
| Multimedia-Streaming | Multimedia-Streaming | | Multimedia-Streaming | Multimedia-Streaming |
+-------------------------+------------------------------+ +-------------------------+------------------------------+
| Telephony | Conversational | | Telephony | Conversational |
+-------------------------+------------------------------+ +-------------------------+------------------------------+
Table 6. Label Changes from RFC 4594 Figure 6. Label Changes from RFC 4594
As is evident from the changes above, from left to right, two labels As is evident from the changes above, from left to right, two labels
are different and each of the meanings are different in this are different and each of the meanings are different in this
document relative to how RFC 4594 defined them. These differences document relative to how RFC 4594 defined them. These differences
are articulated in Section 2 of this document. are articulated in Section 2 of this document.
A parent class is a human understandable categorization, and MUST A parent class is a human understandable categorization, and MUST
NOT be the only part of the traffic class label present in the NOT be the only part of the traffic class label present in the
attribute. The parent class string MUST always be paired with an attribute. The parent class string MUST always be paired with an
application type, with a "." as the string separator. application type, with a "." as the component separator.
The application types (app-type) define the application of a The application types (app-type) define the application of a
particular traffic flow. The application types are listed both in particular traffic flow. The application types are listed both in
the ABNF and defined in Section 2 of this document. Not every the ABNF and defined in Section 2 of this document. Not every
combination parent class is paired with application types, at least combination parent class is paired with application types, at least
as defined in this document. Section 2.1 through 2.5 list many of as defined in this document. Section 2.1 through 2.5 list many of
the expected combinations. the expected combinations.
For additional application type granularity, adjective strings can For additional application type granularity, adjective components
be added (also listed in Section 2). One or more adjectives can be can be added (also listed in Section 2). One or more adjectives can
within the same traffic class attribute. It is also permitted to be within the same traffic class attribute. It is also permitted to
include one or more non-IANA registered adjective label, but these include one or more non-IANA registered adjective component, but
MUST be prefaced by the additional delimiter "_", creating a these MUST be prefaced by the additional delimiter "_", creating a
possibility such as possibility such as
parent-class.application-type.adjective._non-standard-adjective parent-class.application-type.adjective._non-standard-adjective
^^^^ ^^^^
See the underscore See the underscore
For example, this is valid: For example, this is valid:
m=audio 50000 RTP/AVP 112 m=video 50000 RTP/AVP 112
a=trafficclass Conversational.video.immersive._foo._bar a=trafficclass Conversational.video.immersive._foo._bar
where both "foo" and "bar" are not IANA registered adjectives, but where both "foo" and "bar" are not IANA registered adjectives, but
"immersive" is IANA registered. However, including non-registered "immersive" is IANA registered. However, including non-registered
adjectives without the "_" delimiter are not valid, such as the adjectives without the "_" delimiter are not valid, such as the
following: following:
m=audio 50000 RTP/AVP 112 m=video 50000 RTP/AVP 112
a=trafficclass Conversational.video.immersive.foo.bar a=trafficclass Conversational.video.immersive.foo.bar
There is no limit to the number of adjectives allowed, without There is no limit to the number of adjectives allowed, without
regard for whether they are registered or not. These non-registered regard for whether they are registered or not. These non-registered
adjectives can be vendor generated, or merely considered to be adjectives can be vendor generated, or merely considered to be
proprietary in nature. proprietary in nature.
It is important to note that the order of components matters, but It is important to note that the order of component types matter,
only for the components. In other words, the parent class component but not the order of the adjective components. There might be local
MUST be before the application component, which MUST be before the significance to the ordering though. In other words, the parent
adjective component, which MUST be before the cac-class component. class component MUST be before the application component, which MUST
If there are no adjective components, the cac-class component is be before the adjective component.
immediately after the application component.
If there is more than one adjective component describing a traffic Some algorithm such as alphabetizing the list and matching the
class, the order of the adjectives MUST NOT matter. Some algorithm understood strings SHOULD be used.
such as alphabetizing the list and matching the understood strings
SHOULD be used.
In addition to, or as an alternative to one or more adjectives, a Adjectives can be either unqualified or qualified. Qualified
cac-class value MAY be present indicating whether or not a session adjectives have a designation it is qualified and a ":" separating
has had call admission control applied to it. The following two the string component into two parts. We define this qualifying
values are created by this document for the cac-class value: designation to have the form of a two or three letter qualifier, in
which the last letter is always "q" (i.e., for "qualified").
- admitted We are proposing in this document to have a single qualified
- nonadmitted adjective indicating whether this trafficclass has had or will have
capacity-admission applied to it. Here we define the admission
qualifier ("aq") with three possible values for this adjective:
admitted, non-admitted and none, that will have the form
The default cac-class value for any trafficclass attribute is aq:admitted|non-admitted|none
nonadmitted, even if not present. There MUST NOT be more than one
cac-class sub-string per m=line.
Any application, adjective or cac-class string component within this Like all adjectives, it is OPTIONAL to include this adjective in any
attribute that is not understood MUST be ignored, leaving all that trafficclass attribute, and has the following meanings:
is understood to be processed. Ignored string components SHOULD NOT
be deleted, as a downstream entity could understand the component(s) - admitted - capacity admission mechanisms or protocols are to be or
and use it/them. were used for the full amount of bandwidth in relation
to this m= line.
- non-admitted - capacity admission mechanisms or protocols were
attempted but failed in relation to this m= line. This
does not mean the flow described by this m= line
failed. It just failed to attain the capacity admission
mechanism or protocol necessary for a predictable
quality of service, and is likely to continue with only
a class of service marking or best effort.
- none - no capacity admission mechanisms or protocols are or
were attempted in relation to this m= line.
The default for any flow generated from an m= line not having a
trafficclass adjective of 'aq:admitted' or 'aq:non-admitted' MUST be
the equivalent of 'aq:none', whether or not it is present.
Any parent class, application, or adjective string component within
this attribute that is not understood MUST be ignored, leaving all
that is understood to be processed. Ignored string components SHOULD
NOT be deleted, as a downstream entity could understand the
component(s) and use it/them.
Not understanding the parent class string SHOULD mean that this Not understanding the parent class string SHOULD mean that this
attribute is ignored. attribute is ignored.
The following is an example of media level description with a The following is an example of media level description with a
'trafficclass' attribute: 'trafficclass' attribute:
m=audio 50000 RTP/AVP 112 m=video 50000 RTP/AVP 112
a=trafficclass conversational.video.immersive.admitted a=trafficclass conversational.video.immersive.aq:admitted
The above indicates a multiscreen telepresence session that has had The above indicates a telepresence session that has had capacity
call admission control applied to the media flow. admission process applied to its media flow.
4. Offer/Answer Behavior 4. Offer/Answer Behavior
Through the inclusion of the 'trafficclass' attribute, an Through the inclusion of the 'trafficclass' attribute, an
offer/answer exchange identifies the application type for use by offer/answer exchange identifies the application type for use by
endpoints within a session. Policy elements can use this attribute endpoints within a session. Policy elements can use this attribute
to determine the acceptability and/or treatment of that session to determine the acceptability and/or treatment of that session
through lower layers. One specific use-case is for setting of the through lower layers. One specific use-case is for setting of the
DSCP specific for that application type (say a Broadcast instead DSCP specific for that application type (say a Broadcast instead
of a conversational video), decided on a per domain basis - of a Conversational video), decided on a per domain basis -
instead of exclusively by the offering domain. instead of exclusively by the offering domain.
4.1 Offer Behavior 4.1 Offer Behavior
Offerers include the 'trafficclass' attribute with a single well Offerers include the 'trafficclass' attribute with a single string
string comprised of two or more components (from the list in Section comprised of two or more components (from the list in Section 2) to
2) to obtain configurable and predictable classification between the obtain configurable and predictable classification between the
answerer and the offerer. The offerer can also include a private set answerer and the offerer. The offerer can also include a private set
of components, or a combination of IANA registered and private of components, or a combination of IANA registered and private
components within a single domain (e.g., enterprise networks). components within a single domain (e.g., enterprise networks).
Offerers of this 'trafficclass' attribute MUST NOT change the label Offerers of this 'trafficclass' attribute MUST NOT change the label
in transit (e.g., wrt to B2BUAs). SBCs at domain boundaries can in transit (e.g., wrt to B2BUAs). Session Border Controllers (SBC)
change this attribute through local policy. at domain boundaries can change this attribute through local policy.
Offers containing a 'trafficclass' label not understood are ignored Offers containing a 'trafficclass' label not understood are ignored
by default (i.e., as if there was no 'trafficclass' attribute in the by default (i.e., as if there was no 'trafficclass' attribute in the
offer). offer).
4.2 Answer Behavior 4.2 Answer Behavior
Upon receiving an offer containing a 'trafficclass' attribute, if Upon receiving an offer containing a 'trafficclass' attribute, if
the offer is accepted, the answerer will use this attribute to the offer is accepted, the answerer will use this attribute to
classify the session or media (level) traffic accordingly towards classify the session or media (level) traffic accordingly towards
skipping to change at page 15, line 19 skipping to change at page 16, line 5
If not, the attribute SHOULD be ignored. If not, the attribute SHOULD be ignored.
If yes, it checks the application component. If yes, it checks the application component.
2 - does the answerer understand the application component? 2 - does the answerer understand the application component?
If not, the answerer needs to check if it has a local policy to If not, the answerer needs to check if it has a local policy to
proceed without an application component. The default for this proceed without an application component. The default for this
situation is as if the parent component was not understand, situation is as if the parent component was not understand,
i.e., the attribute SHOULD be ignored. the attribute SHOULD be ignored.
If yes, it checks there are any other component present in this If yes, it checks to see if there are any other components
attribute to start its classification. present in this attribute to start its classification.
3 - does the answerer understand the adjective component or 3 - does the answerer understand the adjective component or
components if any are present? components if any are present?
If not present, see if there is a cac-class component, and If not present, process and match the trafficclass label value
before processing classification. as is.
If yes, determine if there are more than one. Alphabetize all of
the adjective components and match the traffic classification.
4 - does the answerer understand the cac-class component if present?
If not, consider the media flow for this m= line to be
nonadmitted.
If yes, classify whether this component is CAC admitted or If yes, determine if there is more than one. Search for each
nonadmitted. that is understood. Any adjectives not understood are to be
ignored, as if they are not present.
The answerer will answer the offer with its own 'trafficclass' The answerer will answer the offer with its own 'trafficclass'
attribute, which will likely be the same value, although this is not attribute, which will likely be the same value, although this is not
mandatory (at this time). mandatory (at this time). The Offerer will process the received
answer just as the answerer processed the offer. In other words, the
processing steps and rules are identical for each end.
The answerer should expect to receive RTP packets marked as The answerer should expect to receive RTP packets marked as
indicated by its 'trafficclass' attribute in the answer itself. indicated by its 'trafficclass' attribute in the answer itself.
An Answer MAY have a 'trafficclass' attribute when one was not in An Answer MAY have a 'trafficclass' attribute when one was not in
the offer. This will at least aid the local domain, and perhaps the offer. This will at least aid the local domain, and perhaps
each domain the session transits, to categorize the application type each domain the session transits, to categorize the application type
of this RTP session. of this RTP session.
Answerers that are middleboxes can use the 'trafficclass' attribute Answerers that are middleboxes can use the 'trafficclass' attribute
skipping to change at page 16, line 15 skipping to change at page 16, line 47
which DSCP an RTP stream is assigned within a domain, if the which DSCP an RTP stream is assigned within a domain, if the
answerer were an inbound SBC to a domain. answerer were an inbound SBC to a domain.
5. Security considerations 5. Security considerations
RFC 5897 [RFC5897] discusses many of the pitfalls of service RFC 5897 [RFC5897] discusses many of the pitfalls of service
classification, which is similar enough to this idea of traffic classification, which is similar enough to this idea of traffic
classification to apply here as well. That document highly classification to apply here as well. That document highly
recommends the user not being able to set any classification. recommends the user not being able to set any classification.
Barring a hack within an endpoint (i.e., to intentionally Barring a hack within an endpoint (i.e., to intentionally
mis-classifying (i.e., lying) about which classification an RTP misclassifying (i.e., lying) about which classification an RTP
stream is), this document's solution makes the classification part stream is), this document's solution makes the classification part
of the signaling between endpoints, which is recommended by RFC of the signaling between endpoints, which is recommended by RFC
5897. 5897.
6. IANA considerations 6. IANA considerations
6.1 Registration of the SDP 'trafficclass' Attribute 6.1 Registration of the SDP 'trafficclass' Attribute
This document requests IANA to register the following SDP att-field This document requests IANA to register the following SDP att-field
under the Session Description Protocol (SDP) Parameters registry: under the Session Description Protocol (SDP) Parameters registry:
skipping to change at page 17, line 33 skipping to change at page 18, line 17
Registry Name: "trafficclass" Attribute Application Type Values Registry Name: "trafficclass" Attribute Application Type Values
Reference: [this document] Reference: [this document]
Registration Procedures: Specification Required Registration Procedures: Specification Required
Application Values Reference Application Values Reference
------------------ --------- ------------------ ---------
Audio [this document] Audio [this document]
Video [this document] Video [this document]
Text [this document] Text [this document]
application-sharing [this document] Application-sharing [this document]
Presentation-data [this document] Presentation-data [this document]
Whiteboarding [this document] Whiteboarding [this document]
Webchat/instant messaging [this document] Webchat/instant messaging [this document]
Gaming [this document] Gaming [this document]
Virtual-desktop [this document] Virtualized-desktop [this document]
Remote-desktop [this document] Remote-desktop [this document]
Telemetry [this document] Telemetry [this document]
Multiplex [this document] Multiplex [this document]
Netflix* [this document]
YouTube* [this document]
Webcast [this document] Webcast [this document]
IPTV [this document] IPTV [this document]
Live-event [this document] Live-event [this document]
surveillance [this document] surveillance [this document]
[Editor's Note: these are placeholders until a more generic string 6.4 The Traffic Classification Unqualified Adjective Registration
can be agreed to by the WG]
6.4 The Traffic Classification Adjective Registration
This document requests IANA to create a new registry for the This document requests IANA to create a new registry for the
traffic application classes similar to the following table traffic unqualified adjective values similar to the following table
within the Session Description Protocol (SDP) Parameters registry: within the Session Description Protocol (SDP) Parameters registry:
Registry Name: "trafficclass" Attribute Adjective Values Registry Name: "trafficclass" Attribute Unqualified Adjective Values
Reference: [this document] Reference: [this document]
Registration Procedures: Specification Required Registration Procedures: Specification Required
Application Values Reference Application Values Reference
------------------ --------- ------------------ ---------
Immersive [this document] Immersive [this document]
Desktop-video [this document] Desktop-video [this document]
Realtime-Text [this document] Realtime-Text [this document]
web [this document] web [this document]
6.5 The Traffic Classification Attribute Call Admission Control Class 6.5 The Traffic Classification Attribute Qualified Adjective Values
Registration Registration
This document requests IANA to create a new registry for the This document requests IANA to create a new registry Qualified
Call Admission Control Class similar to the following table within Adjective Values similar to the following table within the Session
the Session Description Protocol (SDP) Parameters registry: Description Protocol (SDP) Parameters registry:
Registry Name: "trafficclass" SDP Call Admission Control Class Registry Name: "trafficclass" Attribute Qualified Adjective Values
(cac-class) Attribute Values
Reference: [this document] Reference: [this document]
Registration Procedures: Specification Required Registration Procedures: Specification Required
Attribute Values Reference Qualification Category Attribute Values Reference
---------------- --------- ---------------------- ---------------- ---------
Admitted [this document] AQ Admitted [this document]
Non-admitted [this document] AQ Non-admitted [this document]
AQ None [this document]
7. Acknowledgments 7. Acknowledgments
To Dave Oran, Toerless Eckert, Henry Chen, David Benham, David To Dave Oran, Toerless Eckert, Henry Chen, David Benham, David
Benham, Mo Zanty, Michael Ramalho, Glen Lavers, Charles Ganzhorn, Benham, Mo Zanty, Michael Ramalho, Glen Lavers, Charles Ganzhorn,
and Greg Edwards for their comments and suggestions. and Greg Edwards for their comments and suggestions.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997 Requirement Levels", RFC 2119, March 1997
[RFC4566] M. Handley, V. Jacobson, C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003.
[RFC5865] F. Baker, J. Polk, M. Dolly, "A Differentiated Services Code
Point (DSCP) for Capacity-Admitted Traffic", RFC 5865,
May 2010
[RFC2474] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the
Differentiated Services Field (DS Field) in the IPv4 and
IPv6 Headers ", RFC 2474, December 1998
[RFC2205] R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, S. Jamin, [RFC2205] R. Braden, Ed., L. Zhang, S. Berson, S. Herzog, S. Jamin,
"Resource ReSerVation Protocol (RSVP) -- Version 1 "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997 Functional Specification", RFC 2205, September 1997
[RFC4080] R. Hancock, G. Karagiannis, J. Loughney, S. Van den Bosch, [RFC2474] K. Nichols, S. Blake, F. Baker, D. Black, "Definition of the
"Next Steps in Signaling (NSIS): Framework", RFC 4080, June Differentiated Services Field (DS Field) in the IPv4 and
2005 IPv6 Headers ", RFC 2474, December 1998
[RFC2872] Y. Bernet, R. Pabbati, "Application and Sub Application [RFC2872] Y. Bernet, R. Pabbati, "Application and Sub Application
Identity Policy Element for Use with RSVP", RFC 2872, Identity Policy Element for Use with RSVP", RFC 2872,
June 2000 June 2000
[RFC5897] J. Rosenberg, "Identification of Communications Services in [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
the Session Initiation Protocol (SIP)", RFC 5897, June 2010 Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003.
[RFC4080] R. Hancock, G. Karagiannis, J. Loughney, S. Van den Bosch,
"Next Steps in Signaling (NSIS): Framework", RFC 4080, June
2005
[RFC4124] F. Le Faucheur, Ed., " Protocol Extensions for Support of [RFC4124] F. Le Faucheur, Ed., " Protocol Extensions for Support of
Diffserv-aware MPLS Traffic Engineering ", RFC 4124, Diffserv-aware MPLS Traffic Engineering ", RFC 4124,
June 2005 June 2005
[RFC4566] M. Handley, V. Jacobson, C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5865] F. Baker, J. Polk, M. Dolly, "A Differentiated Services Code
Point (DSCP) for Capacity-Admitted Traffic", RFC 5865,
May 2010
[RFC5897] J. Rosenberg, "Identification of Communications Services in
the Session Initiation Protocol (SIP)", RFC 5897, June 2010
8.2. Informative References 8.2. Informative References
[RFC4594] J. Babiarz, K. Chan, F Baker, "Configuration Guidelines for [RFC4594] J. Babiarz, K. Chan, F Baker, "Configuration Guidelines for
Diffserv Service Classes", RFC 4594, August 2006 Diffserv Service Classes", RFC 4594, August 2006
[ID-RSVP-PROF] J. Polk, S. Dhesikan, "Resource Reservation Protocol [ID-RSVP-PROF] J. Polk, S. Dhesikan, "Resource Reservation Protocol
(RSVP) Application-ID Profiles for Voice and Video Streams", (RSVP) Application-ID Profiles for Voice and Video Streams",
work in progress, Mar 2011 work in progress, Mar 2011
Author's Addresses Author's Addresses
skipping to change at line 962 skipping to change at page 20, line 44
Subha Dhesikan Subha Dhesikan
170 W Tasman St 170 W Tasman St
San Jose, CA, USA San Jose, CA, USA
+1.408-902-3351 +1.408-902-3351
mailto: sdhesika@cisco.com mailto: sdhesika@cisco.com
Paul E. Jones Paul E. Jones
mailto: paulej@packetizer.com mailto: paulej@packetizer.com
Appendix - Changes from Previous Versions
A.1 From -00 to -01
These are the following changes made between the WG -00 version and
the -01 version:
- removed the non-SDP applications Netflix and VOD
- switched the adjective 'desktop' to 'avconf'
- Labeled each of the figures.
- clarified the differences between Multimedia-Streaming and
Broadcast parent categories.
- defined Video surveillance
- added the concept of a 'qualified' adjective, and modified the
ABNF.
- deleted the idea of a 'cac-class' as a separate component, and
made the equivalent a qualified adjective.
- modified the answerer behavior because of the removal of the
'cac-class' component.
- created an IANA registry for qualified adjectives
- general clean-up of the doc.
Did *not* do the following in this version:
- add the ability to have more than one trafficclass attribute based
on the codec chosen, as feedback indicated this was a bad idea.
- no swap of the Multimedia-Conferencing parent category with the
offered Collaboration parent category, as doing this did not solve
any perceived problems.
- add more to the 'how does this get processed' portion of Section
3. That will come in the next revision.
 End of changes. 85 change blocks. 
191 lines changed or deleted 208 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/