WG MMUSIC Keith Drage, Ed. Internet Draft Juergen Stoetzer-Bradler Intended status: Standards track Albrecht Schwarz Expires: March 2016 Alcatel-Lucent September 30, 2015 BFCP floor control signalling over Data Channels draft-schwarz-mmusic-bfcp-usage-data-channel-00.txt Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on March 30, 2016. Schwarz Expires March 30, 2016 [Page 1] Internet-Draft BFCP over Data Channels September 2015 Copyright Notice Copyright (c) 2015 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. Abstract This document specifies how the Binary Floor Control Protocol (BFCP) can be instantiated as a data channel sub-protocol, using the SDP offer/answer exchange-based external negotiation defined in [I- D.ietf-mmusic-data-channel-sdpneg]. Two network configurations are documented: a WebRTC end-to-end configuration (connecting two BFCP over data channel endpoints), and a gateway configuration (connecting an BFCP over data channel endpoint with an BFCP over TCP/IP (or over UDP/IP) endpoint). << Editor's note: version 00 relates to a skeleton draft with scope on the general document structure >> Table of Contents 1. Introduction...................................................3 1.1. Motivation................................................3 1.2. Framework of WebRTC data applications.....................3 2. Conventions....................................................4 2.1. Prescriptive language.....................................4 2.2. Notation..................................................4 3. Terminology and abbreviations..................................4 3.1. Terminology used..........................................4 3.2. Abbreviations used........................................4 4. Prinicples.....................................................5 4.1. BFCP Data Channel.........................................5 4.2. Session Mapping...........................................5 5. End-to-End Configuration.......................................5 5.1. Basic BFCP Support........................................5 5.1.1. Session Negotiation..................................5 5.1.1.1. Use of dcmap Attribute..........................5 5.1.1.2. Use of dcsa Attribute...........................5 5.1.1.3. Example SDP Negotiation.........................5 Schwarz Expires March 30, 2016 [Page 2] Internet-Draft BFCP over Data Channels September 2015 5.1.2. Session Opening......................................5 5.1.3. Data Framing.........................................6 5.1.4. Data Sending and Reporting...........................6 5.1.5. Session Closing......................................6 5.2. Support of BFCP-specific Functions........................6 6. Gateway Configurations.........................................6 6.1. Introduction..............................................6 6.2. Gateway-embedded Interworking Functions for BFCP..........6 6.3. Example gateway configuration in more detail..............6 7. Security Considerations........................................6 8. IANA Considerations............................................7 9. References.....................................................7 9.1. Normative References......................................7 9.2. Informative References....................................8 10. Acknowledgments...............................................8 11. CHANGE LOG...................................................10 11.1. Initial draft-schwarz-mmusic-bfcp-usage-data-channel-00.10 11.2. Changes against draft-schwarz-mmusic-bfcp-usage-data- channel-01....................................................10 1. Introduction 1.1. Motivation FIXTHIS 1.2. Framework of WebRTC data applications There are multiple IP application protocols which using WebRTC data channels as transport, such as MSRP or T.140 besides BFCP. The SDP- based indication and negotiation of such WebRTC data applications at call control signalling level follows common principles. The first WebRTC application from this suite is/was the MSRP-based instant messaging service for WebRTC, see [I-D.ietf-mmusic-msrp-usage-data- channel]. This specification for BFCP was derived from that document and uses an aligned clause structuring. It may be noted that the BFCP protocol as such is simpler in comparison to the MSRP, which requires an extended set of SDP elements (in comparison to BFCP) for the description of specific MSRP services and their protocol parameter settings. The NAT traversal situation at IP application protocol layer ("Layer(s) 4+") is also simpler for BFCP than for MSRP because BFCP does not carry network and/or transport address information in the BFCP message. Schwarz Expires March 30, 2016 [Page 3] Internet-Draft BFCP over Data Channels September 2015 2. Conventions 2.1. Prescriptive language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119]. 2.2. Notation None. 3. Terminology and abbreviations 3.1. Terminology used This document uses the following terms: : definition as specified in [RFC####]. 3.2. Abbreviations used DTLS Datagram Transport Layer Security GCP Gateway Control Protocol ITU-T International Telecommunication Union Telecommunication Standardization Sector IWF Interworking Function JSEP Javascript Session Establishment Protocol MG (H.248) Media Gateway MGC (H.248) Media Gateway Controller SCTP Stream Control Transmission Protocol SDP Session Description Protocol SIP Session Initiation Protocol TCP Transmission Control Protocol TLS Transport Layer Security Schwarz Expires March 30, 2016 [Page 4] Internet-Draft BFCP over Data Channels September 2015 UA User Agent UDP User Datagram Protocol 4. Prinicples 4.1. BFCP Data Channel FIXTHIS 4.2. Session Mapping In this design, the BFCP "session" maps to the SCTP association and the "SCTP stream pair" assigned to the data channel, and each BFCP "session" maps to one data channel exactly. 5. End-to-End Configuration FIXTHIS 5.1. Basic BFCP Support 5.1.1. Session Negotiation 5.1.1.1. Use of dcmap Attribute FIXTHIS 5.1.1.2. Use of dcsa Attribute FIXTHIS 5.1.1.3. Example SDP Negotiation FIXTHIS 5.1.2. Session Opening FIXTHIS Schwarz Expires March 30, 2016 [Page 5] Internet-Draft BFCP over Data Channels September 2015 5.1.3. Data Framing FIXTHIS 5.1.4. Data Sending and Reporting FIXTHIS 5.1.5. Session Closing FIXTHIS 5.2. Support of BFCP-specific Functions FIXTHIS 6. Gateway Configurations 6.1. Introduction FIXTHIS 6.2. Gateway-embedded Interworking Functions for BFCP FIXTHIS 6.3. Example gateway configuration in more detail FIXTHIS 7. Security Considerations FIXTHIS Schwarz Expires March 30, 2016 [Page 6] Internet-Draft BFCP over Data Channels September 2015 8. IANA Considerations FIXTHIS 9. References 9.1. Normative References [RFC2119] RFC 2119 (03/1997), "Key words for use in RFCs to Indicate Requirement Levels", BCP 14. [RFC3264] RFC 3264 (06/2002), "An Offer/Answer Model with the Session Description Protocol (SDP)". [RFC4566] RFC 4566 (07/2006), "SDP: Session Description Protocol". [RFC4582] RFC 4582 (11/2006), "The Binary Floor Control Protocol (BFCP)". [RFC4582bis] draft-ietf-bfcpbis-rfc4582bis (09/2015), "The Binary Floor Control Protocol (BFCP)". [RFC4583] RFC 4583 (11/2006), "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams". [RFC4583bis] draft-ietf-bfcpbis-rfc4583bis (09/2015), "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams". [I-D.ietf-rtcweb-data-protocol] draft-ietf-rtcweb-data-channel (##/2015), "WebRTC Data Channel Establishment Protocol". [I-D.ietf-rtcweb-data-channel] http://tools.ietf.org/wg/rtcweb/draft-ietf-rtcweb-data- channel/draft-ietf-rtcweb-data-channel (##/2015), "WebRTC Data Channels". [I-D.ietf-mmusic-data-channel-sdpneg] draft-ietf-mmusic-data- channel-sdpneg (##/2015), "SDP-based Data Channel Negotiation". [I-D.ietf-mmusic-msrp-usage-data-channel] draft-ietf-mmusic-msrp- usage-data-channel (##/2015), "MSRP over Data Channels". Schwarz Expires March 30, 2016 [Page 7] Internet-Draft BFCP over Data Channels September 2015 9.2. Informative References [RFC4376] RFC 4376 (02/2006), "Requirements for Floor Control Protocols". [I-D.ietf-rtcweb-gateways] draft-ietf-rtcweb-gateways (##/2015), "WebRTC Gateways". [ITU-T H.248.94] Recommendation ITU-T H.248.94 (10/2015), "Web- based real-time communication services - H.248 protocol support and profile guidelines". Status: still work in progress in ITU-T SG16 Question 3 Free copy via: FIXTHIS [3GPP 29.334] 3GPP TS 29.334 Release 13 (2015), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IMS Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3". Free copy via: ftp://ftp.3gpp.org/specs/archive/29_series/29.334/ 10. Acknowledgments FIXTHIS Schwarz Expires March 30, 2016 [Page 8] Internet-Draft BFCP over Data Channels September 2015 Authors' Addresses Keith Drage (editor) Alcatel-Lucent Quadrant, Stonehill Green, Westlea Swindon UK Email: keith.drage@alcatel-lucent.com Dr. Juergen Stoetzer-Bradler Alcatel-Lucent Lorenzstrasse 10 D-70435 Stuttgart GERMANY Email: Juergen.Stoetzer-Bradler@alcatel-lucent.com Dr. Albrecht Schwarz Alcatel-Lucent Lorenzstrasse 10 D-70435 Stuttgart GERMANY Email: Albrecht.Schwarz@alcatel-lucent.com Schwarz Expires March 30, 2016 [Page 9] Internet-Draft BFCP over Data Channels September 2015 11. CHANGE LOG 11.1. Initial draft-schwarz-mmusic-bfcp-usage-data-channel-00 o The initial document represents a skeleton where almost all clauses are still empty. o The intention is to propose a document structure aligned with the MSRP draft. 11.2. Changes against draft-schwarz-mmusic-bfcp-usage-data-channel-01 o <> Schwarz Expires March 30, 2016 [Page 10]