Protocol for Controlling Multiple Streams for Telepresence (CLUE)
draft-ietf-clue-protocol-19
| Document | Type | Active Internet-Draft (clue WG) | |
|---|---|---|---|
| Last updated | 2019-07-05 | ||
| Replaces | draft-presta-clue-protocol | ||
| Stream | IETF | ||
| Intended RFC status | Experimental | ||
| Formats | plain text xml pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Paul Kyzivat | ||
| Shepherd write-up | Show (last changed 2017-02-24) | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved. |
||
| Responsible AD | Adam Roach | ||
| Send notices to | "Daniel C. Burnett" <danielcburnett@gmail.com>, "Paul Kyzivat" <pkyzivat@alum.mit.edu> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
CLUE Working Group R. Presta
Internet-Draft S. P. Romano
Intended status: Experimental University of Napoli
Expires: January 6, 2020 July 5, 2019
Protocol for Controlling Multiple Streams for Telepresence (CLUE)
draft-ietf-clue-protocol-19
Abstract
The CLUE protocol is an application protocol conceived for the
description and negotiation of a telepresence session. The design of
the CLUE protocol takes into account the requirements and the
framework defined within the IETF CLUE working group. A companion
document delves into CLUE signaling details, as well as on the SIP/
SDP session establishment phase. CLUE messages flow over the CLUE
data channel, based on reliable and ordered SCTP over DTLS transport.
Message details, together with the behavior of CLUE Participants
acting as Media Providers and/or Media Consumers, are herein
discussed.
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 January 6, 2020.
Copyright Notice
Copyright (c) 2019 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
Presta & P. Romano Expires January 6, 2020 [Page 1]
Internet-Draft draft-ietf-clue-protocol-19 July 2019
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Overview of the CLUE protocol . . . . . . . . . . . . . . . . 4
5. Protocol messages . . . . . . . . . . . . . . . . . . . . . . 7
5.1. options . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. optionsResponse . . . . . . . . . . . . . . . . . . . . . 11
5.3. advertisement . . . . . . . . . . . . . . . . . . . . . . 12
5.4. ack . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.5. configure . . . . . . . . . . . . . . . . . . . . . . . . 14
5.6. configureResponse . . . . . . . . . . . . . . . . . . . . 15
5.7. Response codes and reason strings . . . . . . . . . . . . 16
6. Protocol state machines . . . . . . . . . . . . . . . . . . . 18
6.1. Media Provider's state machine . . . . . . . . . . . . . 21
6.2. Media Consumer's state machine . . . . . . . . . . . . . 22
7. Versioning . . . . . . . . . . . . . . . . . . . . . . . . . 25
8. Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.1. Extension example . . . . . . . . . . . . . . . . . . . . 27
9. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 29
10. Call flow example . . . . . . . . . . . . . . . . . . . . . . 34
10.1. CLUE message nr. 1: 'options' . . . . . . . . . . . . . 37
10.2. CLUE message nr. 2: 'optionsResponse' . . . . . . . . . 39
10.3. CLUE message nr. 3: 'advertisement' . . . . . . . . . . 39
10.4. CLUE message nr. 4: 'configure + ack' . . . . . . . . . 47
10.5. CLUE message nr. 5: 'confResponse' . . . . . . . . . . . 47
10.6. CLUE message nr. 6: 'advertisement' . . . . . . . . . . 48
10.7. CLUE message nr. 7: 'ack' . . . . . . . . . . . . . . . 58
10.8. CLUE message nr. 8: 'configure' . . . . . . . . . . . . 58
10.9. CLUE message nr. 9: 'confResponse' . . . . . . . . . . . 59
11. Security Considerations . . . . . . . . . . . . . . . . . . . 60
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
12.1. URN Sub-Namespace Registration . . . . . . . . . . . . . 61
12.2. XML Schema registration . . . . . . . . . . . . . . . . 62
Show full document text