datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Mapping RTP streams to CLUE media captures
draft-even-clue-rtp-mapping-05

Active Internet-Draft (None)
Document Stream: No stream defined
Last updated: 2013-02-01
Intended RFC status: (None)
Other versions: plain text, pdf, html

Document shepherd:(None)
Shepherd writeup

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

CLUE WG                                                          R. Even
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                               J. Lennox
Expires: August 5, 2013                                            Vidyo
                                                        February 1, 2013

               Mapping RTP streams to CLUE media captures
                   draft-even-clue-rtp-mapping-05.txt

Abstract

   This document describes mechanisms and recommended practice for
   mapping RTP media streams defined in SDP to CLUE media captures.

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 5, 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.

Even & Lennox            Expires August 5, 2013                 [Page 1]
Internet-Draft             RTP mapping to CLUE             February 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  RTP topologies for CLUE  . . . . . . . . . . . . . . . . . . .  3
   4.  Mapping CLUE Media Captures to RTP streams . . . . . . . . . .  5
     4.1.  Review of current directions in MMUSIC, AVText and
           AVTcore  . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.2.  Requirements of a solution . . . . . . . . . . . . . . . .  7
     4.3.  Static Mapping . . . . . . . . . . . . . . . . . . . . . .  9
     4.4.  Dynamic mapping  . . . . . . . . . . . . . . . . . . . . .  9
       4.4.1.  RTP header extension . . . . . . . . . . . . . . . . . 10
       4.4.2.  Restricted approach  . . . . . . . . . . . . . . . . . 10
     4.5.  Recommendations  . . . . . . . . . . . . . . . . . . . . . 11
   5.  Application to CLUE Media Requirements . . . . . . . . . . . . 11
   6.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     6.1.  Static mapping . . . . . . . . . . . . . . . . . . . . . . 13
     6.2.  Dynamic Mapping  . . . . . . . . . . . . . . . . . . . . . 16
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 17
     10.2. Informative References . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

Even & Lennox            Expires August 5, 2013                 [Page 2]
Internet-Draft             RTP mapping to CLUE             February 2013

1.  Introduction

   Telepresence systems can send and receive multiple media streams.
   The CLUE framework [I-D.ietf-clue-framework] defines media captures
   as a source of Media, such as from one or more Capture Devices.  A
   Media Capture (MC) may be the source of one or more Media streams.  A
   Media Capture may also be constructed from other Media streams.  A
   middle box can express Media Captures that it constructs from Media
   streams it receives.

   SIP offer answer [RFC3264] uses SDP [RFC4566] to describe the
   RTP[RFC3550] media streams.  Each RTP stream has a unique SSRC within
   its RTP session.  The content of the RTP stream is created by an
   encoder in the endpoint.  This may be an original content from a