Mapping RTP streams to CLUE Media Captures
draft-ietf-clue-rtp-mapping-14

Document Type Active Internet-Draft (clue WG)
Last updated 2017-03-07 (latest revision 2017-02-27)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Paul Kyzivat
Shepherd write-up Show (last changed 2017-02-27)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to "Paul Kyzivat" <pkyzivat@alum.mit.edu>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state MISSREF
CLUE WG                                                          R. Even
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                               J. Lennox
Expires: August 31, 2017                                           Vidyo
                                                       February 27, 2017

               Mapping RTP streams to CLUE Media Captures
                   draft-ietf-clue-rtp-mapping-14.txt

Abstract

   This document describes how the Real Time transport Protocol (RTP) is
   used in the context of the CLUE protocol (ControLling mUltiple
   streams for tElepresence).  It also describes the mechanisms and
   recommended practice for mapping RTP media streams defined in Session
   Description Protocol (SDP) to CLUE Media Captures and defines a new
   RTP header extension (CaptureId).

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 31, 2017.

Copyright Notice

   Copyright (c) 2017 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

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

   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.  RTP topologies for CLUE . . . . . . . . . . . . . . . . . . .   3
   4.  Mapping CLUE Capture Encodings to RTP streams . . . . . . . .   4
   5.  MCC Constituent CaptureID definition  . . . . . . . . . . . .   5
     5.1.  RTCP CaptureID SDES Item  . . . . . . . . . . . . . . . .   5
     5.2.  RTP Header Extension  . . . . . . . . . . . . . . . . . .   6
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Communication Security  . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

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

   SIP Offer/Answer [RFC3264] uses SDP [RFC4566]  to describe the
   RTP[RFC3550] media streams.  Each RTP stream has a unique
   Synchronization Source (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 camera or a content created by an
   intermediary device like an MCU (Multipoint Control Unit).

   This document makes recommendations for the CLUE architecture about
   how RTP and RTCP streams should be encoded and transmitted, and how
   their relation to CLUE Media Captures should be communicated.  The
   proposed solution supports multiple RTP topologies [RFC7667].
Show full document text