The Session Description Protocol (SDP) Application Token Attribute
draft-even-mmusic-application-token-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-06-28
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MMUSIC WG                                                        R. Even
Internet-Draft                                       Huawei Technologies
Intended status: Informational                                 J. Lennox
Expires: December 30, 2013                                         Vidyo
                                                                   Q. Wu
                                                     Huawei Technologies
                                                           June 28, 2013

   The Session Description Protocol (SDP) Application Token Attribute
               draft-even-mmusic-application-token-00.txt

Abstract

   The RTP fixed header includes the payload type number and the SSRC
   values of the RTP stream.  RTP defines how you de-multiplex streams
   within an RTP session, but in some use cases applications need
   further identifiers in order to identify the application semantics
   associated with particular streams within the session.

   This document defines a mechanism to provide the mapping between the
   SSRCs of RTP streams and the application semantics by defining
   extensions to RTP and RTCP messages.

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 December 30, 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

Even, et al.            Expires December 30, 2013               [Page 1]
Internet-Draft            SDP application token                June 2013

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Proposal for an Application ID token  . . . . . . . . . . . .   4
     3.1.  RTCP SDES message . . . . . . . . . . . . . . . . . . . .   6
     3.2.  RTP Header Extension  . . . . . . . . . . . . . . . . . .   6
   4.  Using Application ID token  . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The RTP [RFC3550] header includes the payload type number and the
   SSRC values of the RTP stream.  RTP defines how you de-multiplex
   streams within an RTP session, but in some use cases, applications
   need further identifiers in order to identify semantics associated
   with particular streams within the session.

   There is ongoing work to define how to support, using SDP [RFC4566],
   multiple RTP media streams in one or more m-lines that define a
   single RTP session (as specified in [RFC3550]).  The work is
   addressing the WebRTC architecture [I-D.ietf-rtcweb-overview], and
   some work will be needed when looking for a general solution in
   MMUSIC that can be used for non-WebRTC systems.

   RTCWEB Plan A [I-D.roach-rtcweb-plan-a] that an m-line in SDP
   represents a single RTP stream.  De-multiplexing is done by payload
   type (PT) number (which MUST be unique), and if unique PTs are not
   feasible, use SSRC information in the SDP to identify the RTP stream.

   RTCWEB Plan B [I-D.uberti-rtcweb-plan] takes a different approach,
   and creates a hierarchy within SDP; an m= line defines an "envelope",
   specifying codec and transport parameters, and [RFC5576] a=ssrc lines
   are used to describe individual media sources within that envelope.
Show full document text