The Session Description Protocol (SDP) 'trafficclass' Attribute
draft-ietf-mmusic-traffic-class-for-sdp-03

The information below is for an old version of the document
Document Type Active Internet-Draft (mmusic WG)
Last updated 2013-02-28 (latest revision 2013-02-18)
Replaces draft-polk-mmusic-traffic-class-for-sdp
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Ari Keränen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network WG                                                   James Polk
Internet-Draft                                           Subha Dhesikan
Expires: August 18, 2013                                     Paul Jones
Intended Status: Standards Track (PS)                     Cisco Systems
                                                           Feb 18, 2013

    The Session Description Protocol (SDP) 'trafficclass' Attribute
               draft-ietf-mmusic-traffic-class-for-sdp-03

Abstract

   This document proposes a new Session Description Protocol (SDP) 
   attribute to identify the traffic class a session is requesting
   in its offer/answer exchange.  

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six 
   months and may be updated, replaced, or obsoleted by other documents
   at any time.  It is inappropriate to use Internet-Drafts as 
   reference material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 18, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with 
   respect to this document.  Code Components extracted from this 
   document must include Simplified BSD License text as described in 
   Section 4.e of the Trust Legal Provisions and are provided without 
   warranty as described in the Simplified BSD License.

Polk, et al.              Expires Aug 18, 2013                 [Page 1]
Internet-Draft         SDP trafficclass Attribute              Feb 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Traffic Class Framework and Component Definitions . . . . . .  5
   3.  Traffic Class Attribute Definition  . . . . . . . . . . . . .  6
       3.1 Categories within the SDP Traffic Class Label . . . . . .  8
       3.2 Applications within the SDP Traffic Class Label . . . . .  9
       3.3 Adjectives within the SDP Traffic Class Label . . . . . .  9
       3.3.1 Qualified Adjectives  . . . . . . . . . . . . . . . . .  9
   4.  Matching Categories with Applications and Adjectives  . . . . 11
       4.1 Conversational Category Traffic Class . . . . . . . . . . 11
       4.2 Multimedia-Conferencing Category Traffic Class  . . . . . 12
       4.3 Realtime-Interactive Category Traffic Class . . . . . . . 14
       4.4 Multimedia-Streaming Category Traffic Class . . . . . . . 15
       4.5 Broadcast Category Traffic Class  . . . . . . . . . . . . 17
   5.  Offer/Answer Behavior . . . . . . . . . . . . . . . . . . . . 18
       5.1 Offer Behavior  . . . . . . . . . . . . . . . . . . . . . 18
       5.2 Answer Behavior . . . . . . . . . . . . . . . . . . . . . 19
   6.  Security considerations . . . . . . . . . . . . . . . . . . . 20
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . . 20
   8.  Acknowledgments   . . . . . . . . . . . . . . . . . . . . . . 23
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 24
       9.1.  Normative References  . . . . . . . . . . . . . . . . . 24
       9.2.  Informative References  . . . . . . . . . . . . . . . . 24
       Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . 25
       Appendix  . . . . . . . . . . . . . . . . . . . . . . . . . . 25

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

1.  Introduction

   The Session Description Protocol (SDP) [RFC4566] provides a means 
   for an offerer to describe the specifics of a session to an 
   answerer, and for the answerer to respond back with its session 
   specifics to the offerer.  These session specifics include offering 
   the codec or codecs to choose from, the specific IP address and port
   number the offerer wants to receive the RTP stream(s) on/at, the 
   particulars about the codecs the offerer wants considered or 
   mandated, and so on.  

   There are many facets within SDP to determine the Real-time 
   Transport Protocol (RTP) [RFC3550] details for the session 
   establishment between one or more endpoints, but identifying how the
Show full document text