Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
draft-ietf-clue-signaling-13

Document Type Active Internet-Draft (clue WG)
Last updated 2017-11-20
Replaces draft-kyzivat-clue-signaling
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Roni Even
Shepherd write-up Show (last changed 2017-03-14)
IESG IESG state AD Evaluation::AD Followup
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adam Roach
Send notices to "Daniel C. Burnett" <danielcburnett@gmail.com>, "Roni Even" <roni.even@mail01.huawei.com>
Network Working Group                                          R. Hansen
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                              P. Kyzivat
Expires: May 24, 2018
                                                                 L. Xiao
                                                                  Huawei
                                                               C. Groves
                                                       November 20, 2017

  Session Signaling for Controlling Multiple Streams for Telepresence
                                 (CLUE)
                      draft-ietf-clue-signaling-13

Abstract

   This document specifies how CLUE-specific signaling such as the CLUE
   protocol and the CLUE data channel are used in conjunction with each
   other and with existing signaling mechanisms such as SIP and SDP to
   produce a telepresence call.

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 https://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 May 24, 2018.

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
   (https://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

Hansen, et al.            Expires May 24, 2018                  [Page 1]
Internet-Draft               CLUE Signaling                November 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Media Feature Tag Definition  . . . . . . . . . . . . . . . .   4
   4.  SDP Grouping Framework CLUE Extension Semantics . . . . . . .   4
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  The CLUE data channel and the CLUE grouping semantic  . .   4
     4.3.  CLUE-controlled media and the CLUE grouping semantic  . .   5
     4.4.  SDP semantics for CLUE-controlled media . . . . . . . . .   5
       4.4.1.  Signaling CLUE Encodings  . . . . . . . . . . . . . .   5
         4.4.1.1.  Referencing Encodings in the CLUE protocol  . . .   6
       4.4.2.  Negotiating receipt of CLUE Capture Encodings in SDP    7
     4.5.  SDP Offer/Answer Procedures . . . . . . . . . . . . . . .   7
       4.5.1.  Generating the Initial Offer  . . . . . . . . . . . .   7
       4.5.2.  Generating the Answer . . . . . . . . . . . . . . . .   8
         4.5.2.1.  Negotiating use of CLUE and the CLUE data channel   8
         4.5.2.2.  Negotiating CLUE-controlled media . . . . . . . .   8
         4.5.2.3.  Negotiating non-CLUE controlled media . . . . . .   8
       4.5.3.  Processing the initial Offer/Answer negotiation . . .   9
         4.5.3.1.  Successful CLUE negotiation . . . . . . . . . . .   9
         4.5.3.2.  CLUE negotiation failure  . . . . . . . . . . . .   9
       4.5.4.  Modifying the session . . . . . . . . . . . . . . . .  10
         4.5.4.1.  Adding and removing CLUE-controlled media . . . .  10
         4.5.4.2.  Enabling CLUE mid-call  . . . . . . . . . . . . .  10
         4.5.4.3.  Disabling CLUE mid-call . . . . . . . . . . . . .  10
         4.5.4.4.  CLUE protocol failure mid-call  . . . . . . . . .  11
   5.  Interaction of CLUE protocol and SDP negotiations . . . . . .  11
     5.1.  Independence of SDP and CLUE negotiation  . . . . . . . .  12
     5.2.  Constraints on sending media  . . . . . . . . . . . . . .  13
     5.3.  Recommendations for operating with non-atomic operations   13
   6.  Interaction of CLUE protocol and RTP/RTCP CaptureID . . . . .  14
     6.1.  CaptureID reception during MCC redefinition . . . . . . .  14
   7.  Multiplexing of CLUE-controlled media using BUNDLE  . . . . .  15
Show full document text