One document matched: draft-ietf-clue-datachannel-07.xml
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3261 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3261.xml">
<!ENTITY RFC3264 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3264.xml">
]>
<?rfc toc="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
<?rfc sortrefs="no" ?>
<?rfc strict="yes" ?>
<rfc ipr="trust200902" category="std" docName="draft-ietf-clue-datachannel-07" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title abbrev="CLUE Data Channel">
CLUE Protocol Data Channel
</title>
<author initials="C.H." surname="Holmberg" fullname="Christer Holmberg">
<organization>Ericsson</organization>
<address>
<postal>
<street>Hirsalantie 11</street>
<code>02420</code>
<city>Jorvas</city>
<country>Finland</country>
</postal>
<email>christer.holmberg@ericsson.com</email>
</address>
</author>
<date year="2015" />
<area>Transport</area>
<workgroup>CLUE Working Group</workgroup>
<keyword>SIP</keyword>
<keyword>SDP</keyword>
<keyword>DTLS</keyword>
<keyword>SCTP</keyword>
<keyword>DATA</keyword>
<keyword>CHANNEL</keyword>
<keyword>DCEP</keyword>
<keyword>DATA_CHANNEL_OPEN</keyword>
<keyword>DATA_CHANNEL_ACK</keyword>
<keyword>PPID</keyword>
<keyword>TELEPRESENCE</keyword>
<keyword>RTCWEB</keyword>
<keyword>WEBRTC</keyword>
<abstract>
<t>
This document defines how to use the WebRTC Data Channel
mechanism in order to realize a data channel, referred to
as a CLUE data channel, for transporting CLUE protocol
messages between two CLUE entities.
</t>
<t>
The document defines how to describe the SCTPoDTLS association
used to realize the CLUE data channel using the Session Description
Protocol (SDP), and defines usage of SDP-based "SCTP over DTLS" data
channel negotiation mechanism for establishing a CLUE data channel.
</t>
<t>
Details and procedures associated with the CLUE protocol, and the
SDP Offer/Answer procedures for negotiating usage of a CLUE data
channel, are outside the scope of this document.
</t>
</abstract>
</front>
<middle>
<section title="Introduction" toc="default">
<t>
This document defines how to use the WebRTC Data Channel
mechanism <xref target="I-D.ietf-rtcweb-data-channel"
pageno="false" format="default" /> in order to realize a
data channel, referred to as a CLUE data channel, for
transporting CLUE protocol messages between two CLUE entities.
</t>
<t>
The document defines how to describe the SCTPoDTLS association
<xref target="I-D.ietf-tsvwg-sctp-dtls-encaps" pageno="false"
format="default" /> used to realize the CLUE data channel using
the Session Description Protocol (SDP) <xref target="RFC4566"
pageno="false" format="default" />, and defines usage of the
SDP-based "SCTP over DTLS" data channel negotiation mechanism
<xref target="I-D.ejzak-mmusic-data-channel-sdpneg"
pageno="false" format="default" />. This includes SCTP
considerations specific to a CLUE data channel, the SDP Media
Description (m- line) values, and usage of SDP attributes specific
to a CLUE data channel.
</t>
<t>
Details and procedures associated with the CLUE protocol, and the
SDP Offer/Answer <xref target="RFC3264" pageno="false" format="default" />
procedures for negotiating usage of a CLUE data channel, are outside
the scope of this document.
</t>
<t>
NOTE: The usage of the Data Channel Establishment Protocol (DCEP)
<xref target="I-D.ietf-rtcweb-data-protocol" pageno="false" format="default" />
for establishing a CLUE data channel is outside the scope of this document.
</t>
</section>
<section title="Conventions" toc="default">
<t>
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 BCP 14, RFC 2119 <xref target="RFC2119" pageno="false" format="default" />.
</t>
<t>
SCTPoDTLS association refers to an SCTP association carried
over an DTLS connection <xref target="I-D.ietf-tsvwg-sctp-dtls-encaps"
pageno="false" format="default" />.
</t>
<t>
WebRTC Data Channel refers to a SCTPoDTLS association <xref
target="I-D.ietf-tsvwg-sctp-dtls-encaps" pageno="false"
format="default" /> that is used to transport non-media data
between two entities, according to the procedures in
<xref target="I-D.ietf-rtcweb-data-channel" pageno="false"
format="default" />.
</t>
<t>
CLUE data channel refers to a WebRTC Data Channel <xref
target="I-D.ietf-rtcweb-data-channel" pageno="false"
format="default" /> realization, with a specific set of
SCTP characteristics, with the purpose of transporting CLUE
protocol <xref target="I-D.ietf-clue-protocol" pageno="false"
format="default" /> messages between two CLUE entities.
</t>
<t>
CLUE entity refers to a SIP User Agent (UA) <xref target="RFC3261"
pageno="false" format="default" /> that supports the CLUE data channel
and the CLUE protocol.
</t>
<t>
CLUE session refers to a SIP session <xref target="RFC3261"
pageno="false" format="default" /> between to SIP UAs, where a
CLUE data channel, associated with the SIP session, has been
established between the SIP UAs.
</t>
<t>
<xref target="RFC4960" pageno="false" format="default" /> defines an
SCTP stream as a unidirectional logical channel established from one
to another associated SCTP endpoint, within which all user messages
are delivered in sequence except for those submitted to the unordered
delivery service.
</t>
<t>
<xref target="RFC4960" pageno="false" format="default" /> defines an
SCTP identifier as a unsigned integer, which identifies a SCTP stream.
</t>
</section>
<section anchor="section.dtls" title="CLUE Data Channel" toc="default">
<section anchor="section.cdc.gen" title="General" toc="default">
<t>
This section describes the realization of a CLUE Data Channel.
This includes a set of SCTP characteristics specific to a
CLUE Data Channel, the values of the m- line describing
the SCTPoDTLS association associated with the WEBRTC
Data Channel, and the usage of the SDP-based "SCTP
over DTLS" data channel negotiation mechanism for creating the
CLUE Data Channel.
</t>
<t>
As described in <xref target="I-D.ietf-rtcweb-data-channel"
pageno="false" format="default" />, the SCTP streams realizing
a WebRTC Data Channel must be associated with the same SCTP association.
In addition, both SCTP streams realizing the WebRTC Data Channel must
use the same SCTP stream identifier value. These rules also apply to
a CLUE Data Channel.
</t>
<t>
Within a given CLUE session, a CLUE entity MUST use a single CLUE
Data Channel for transport of all CLUE messages towards its peer.
</t>
</section>
<section anchor="section.oa" title="SDP Considerations" toc="default">
<section anchor="section.oa.gen" title="General" toc="default">
<t>
This section defines how to construct the SDP Media Description
(m- line) for describing the SCTPoDTLS association used to realize
a WebRTC Data Channel. The section also defines how to construct
the SDP dcmap attribute, used with the SDP-based "SCTP over DTLS" data
channel negotiation mechanism for establishing a CLUE Data Channel
on the SCTPoDTLS association.
</t>
<t>
NOTE: Other protocols than SDP for negotiating usage of a SCTPoDTLS
association for realizing a WebRTC Data Channel are outside the scope
of this specification.
</t>
<t>
<xref target="I-D.ietf-clue-signaling" pageno="false" format="default" />
describes the SDP Offer/Answer procedures for negotiating a CLUE session,
including the CLUE controlled media streams and the CLUE Data Channel.
</t>
<section anchor="section.oa.mediadesc" title="SDP Media Description Fields" toc="default">
<t>
As defined in <xref target="I-D.ietf-mmusic-sctp-sdp" pageno="false" format="default" />,
the field values of an m- line describing an SCTPoDTLS association are set as following:
</t>
<texttable anchor="table_SDP_mediadesc" title='SDP "proto" field values'>
<ttcol align='center'>media</ttcol>
<ttcol align='center'>port</ttcol>
<ttcol align='center'>proto</ttcol>
<ttcol align='center'>fmt</ttcol>
<c>"application"</c>
<c>UDP port value</c>
<c>"UDP/DTLS/SCTP"</c>
<c>application usage</c>
<c>"application"</c>
<c>TCP port value</c>
<c>"TCP/DTLS/SCTP"</c>
<c>application usage</c>
</texttable>
<t>
As defined in <xref target="I-D.ietf-mmusic-sctp-sdp" pageno="false" format="default" />, when
the SCTPoDTLS association is used to realize a WebRTC data channel, the value of the
application usage part is 'webrtc-datachannel'.
</t>
</section>
<section anchor="section.oa.sctpport" title="SDP sctp-port Attribute" toc="default">
<t>
As defined in <xref target="I-D.ietf-mmusic-sctp-sdp" pageno="false" format="default" />, the
SDP sctp-port attribute value is set to the SCTP port of the SCTPoDTLS association.
</t>
</section>
</section>
<section anchor="section.oa.dcmap" title="SDP dcpmap Attribute" toc="default">
<t>
When the SDP-based "SCTP over DTLS" data channel negotiation mechanism is used
to establish a CLUE data channel, the values of the SDP dcmap attribute
<xref target="I-D.ejzak-mmusic-data-channel-sdpneg" pageno="false" format="default" />,
associated with the m- line describing the SCTPoDTLS association used to realize the
WebRTC Data Channel, are set as following:
</t>
<texttable anchor="table_SDP_dcmap" title='SDP dcmap attribute values'>
<ttcol align='center'>stream-id</ttcol>
<ttcol align='center'>subprotocol</ttcol>
<ttcol align='center'>label</ttcol>
<ttcol align='center'>ordered</ttcol>
<ttcol align='center'>max-retr</ttcol>
<ttcol align='center'>max-time</ttcol>
<c>Value of the SCTP stream used to realize the CLUE data channel</c>
<c>"CLUE"</c>
<c>Application specific</c>
<c>N/A</c>
<c>N/A</c>
<c>N/A</c>
</texttable>
</section>
<section anchor="section.oa.dcsa" title="SDP dcsa Attribute" toc="default">
<t>
The SDP dcsa attribute <xref target="I-D.ejzak-mmusic-data-channel-sdpneg" pageno="false"
format="default" /> is not used when establishing a CLUE data channel.
</t>
</section>
<section anchor="section.oa.example" title="Example" toc="default">
<figure anchor="figure_SDP_example" title="SDP Media Description for a CLUE Data Channel">
<artwork><![CDATA[
m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
a=sctp-port: 5000
a=dcmap:2 subprotocol="CLUE"
]]></artwork>
</figure>
</section>
</section>
<section anchor="section.cdc.sctp" title="SCTP Considerations" toc="default">
<section anchor="section.dtls.sctp.ppid" title="SCTP Payload Protocol Identifier (PPID)" toc="default">
<t>
A CLUE entity MUST use the PPID value 51 when sending a CLUE message
on a CLUE data channel.
</t>
<t>
NOTE: As described in <xref target="I-D.ietf-rtcweb-data-channel"
pageno="false" format="default" />, the PPID value 51 indicates that
the SCTP message contains data encoded in a UTF-8 format. The PPID
value 51 does not indicate what application protocol the SCTP message
is associated with, only the format in which the data is encoded.
</t>
<texttable anchor="table_SCTP_PPID" title='CLUE Data Channel PPID Values'>
<ttcol align='center'>Protocol</ttcol>
<ttcol align='center'>PPID Value</ttcol>
<c>CLUE</c>
<c>51</c>
</texttable>
</section>
<section anchor="section.cdc.sctp.reliability" title="Reliability" toc="default">
<t>
The usage of SCTP for the CLUE Data Channel ensures reliable
transport of CLUE protocol <xref target="I-D.ietf-clue-protocol"
pageno="false" format="default" /> messages.
</t>
<t>
A CLUE entity MUST NOT use the partial reliability and limited retransmission
extensions defined in <xref target="RFC3758" pageno="false" format="default" />.
</t>
<t>
NOTE: <xref target="I-D.ietf-rtcweb-data-channel" pageno="false" format="default" />
requires the support of the partial reliability extension defined in
<xref target="RFC3758" pageno="false" format="default" />. This is not needed for
a CLUE Data Channel, as messages are required to always be sent reliably.
<xref target="I-D.ietf-rtcweb-data-channel" pageno="false" format="default" /> also
mandates support of the limited retransmission policy defined in
<xref target="I-D.ietf-tsvwg-sctp-prpolicies" pageno="false" format="default" />.
</t>
</section>
<section anchor="section.cdc.sctp.order" title="Order" toc="default">
<t>
A CLUE entity MUST use the ordered delivery SCTP service,
as described in section 6.6 of <xref target="RFC4960" pageno="false" format="default" />.
</t>
</section>
<section anchor="section.cdc.sctp.streamreset" title="Stream Reset" toc="default">
<t>
A CLUE entity MUST support the stream reset extension defined in <xref target="RFC6525"
pageno="false" format="default" />.
</t>
<t>
The dynamic address reconfiguration extension defined in <xref target="RFC5061"
pageno="false" format="default" /> MUST be used to signal the support of the stream
reset extension defined in <xref target="RFC6525" pageno="false" format="default" />.
Other features of <xref target="RFC5061" pageno="false" format="default" /> MUST NOT
be used.
</t>
</section>
<section anchor="section.cdc.sctp.multihome" title="SCTP Multihoming" toc="default">
<t>
SCTP multi-homing is not supported for SCTPoDTLS associations, and can therefor
not be used for a CLUE data channel.
</t>
</section>
<section anchor="section.cdcp.proc.close" title="Close CLUE Data Channel" toc="default">
<t>
As described in <xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" />, in order to close a data channel, a SCTP reset
message <xref target="RFC6525" pageno="false" format="default" /> is sent,
in order to close the SCTP stream associated with the data channel. The
SCTPoDTLS association, and other data channels established on the same
association, are not affected by the SCTP reset message.
</t>
</section>
</section>
</section>
<section anchor="section.sec" title="Security Considerations">
<t>
This specification does not introduce new security considerations, in addition to those
defined in <xref target="I-D.ietf-rtcweb-data-channel" pageno="false" format="default" />
and <xref target="I-D.ietf-rtcweb-data-protocol" pageno="false" format="default" />. Security
considerations associated with the CLUE protocol are defined in <xref target="I-D.ietf-clue-protocol"
pageno="false" format="default" />.
</t>
</section>
<section anchor="section.iana" title="IANA Considerations">
<section anchor="section.iana.dc" title="New WebRTC Data Channel Protocol Value">
<t>
[RFC EDITOR NOTE: Please replace RFC-XXXX with the RFC number of this document.]
</t>
<t>
This document adds the 'CLUE' value to the "WebSocket Subprotocol Name Registry"
as follows:
</t>
<figure>
<artwork align="left"><![CDATA[
Subprotocl Identifier: CLUE
Subprotocol Common Name: CLUE
Subprotocol Definition: RFC-XXXX
]]></artwork>
</figure>
</section>
<section anchor="section.iana.sdp" title="New SDP dcmap attribute subprotocol value">
<t>
[RFC EDITOR NOTE: Please replace RFC-XXXX with the RFC number of this document.]
</t>
<t>
OPEN ISSUE: <xref target="I-D.ejzak-mmusic-data-channel-sdpneg" pageno="false"
format="default" /> has not yet created a registry for new subprotocol values.
</t>
</section>
</section>
<section title="Acknowledgments">
<t>
Thanks to Paul Kyzivat and Christian Groves for comments on the document.
</t>
</section>
<section title="Change Log">
<t>
[RFC EDITOR NOTE: Please remove this section when publishing]
</t>
<t>
Changes from draft-ietf-clue-datachannel-06
<list style="symbols">
<t>Usage of DCEP removed.</t>
</list>
</t>
<t>
Changes from draft-ietf-clue-datachannel-05
<list style="symbols">
<t>"DTLS/SCTP" split into "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP".</t>
<t>Removed note regarding optionality of including the SDP
sctp-port attribute.</t>
<t>Added defintion of 'SCTPoDTLS association' to the
Conventions.</t>
<t>Reference to RFC 4566 (SDP) added.</t>
</list>
</t>
<t>
Changes from draft-ietf-clue-datachannel-04
<list style="symbols">
<t>Defines DCEP and external SDP negotiation as two separate mechanisms
for negotiating a CLUE data channel.</t>
<t>Updates based on technical changes in referenced specifications.</t>
<t>Reference to draft-ietf-mmusic-sctp-sdp added.</t>
</list>
</t>
<t>
Changes from draft-ietf-clue-datachannel-03
<list style="symbols">
<t>IANA considerations added.</t>
<t>Editorial changes based on comments from Christian Groves.</t>
</list>
</t>
<t>
Changes from draft-ietf-clue-datachannel-02
<list style="symbols">
<t>SDP m- line example fixed.</t>
<t>OPEN ISSUE #1 closed.</t>
<t>- It was agreed (IETF#91) to use draft-ejzak-mmusic-data-channel-sdpneg,
as it was adopted as a WG item in MMUSIC.
</t>
<t>- Details for draft-ejzak-mmusic-data-channel-sdpneg usage added.</t>
<t>SDP Offer/Answer procedures removed, as they will be defined in the CLUE protocol draft.</t>
<t>References updated.</t>
</list>
</t>
<t>
Changes from draft-ietf-clue-datachannel-01
<list style="symbols">
<t>Support of interleaving "MUST"->"SHOULD".</t>
<t>Example updated.</t>
<t>Reference update.</t>
</list>
</t>
<t>
Changes from draft-ietf-clue-datachannel-00
<list style="symbols">
<t>SDP Offer/Answer procedures structures according to RFC 3264.</t>
<t>Reference update.</t>
</list>
</t>
<t>
Changes from draft-holmberg-clue-datachannel-04
<list style="symbols">
<t>Draft submitted as draft-ietf-clue-data-channel-00.</t>
<t>Editorial nits fixed.</t>
<t>Changes based on comments from Paul Kyzivat (http://www.ietf.org/mail-archive/web/clue/current/msg03559.html).</t>
<t>- Proto value fixed.</t>
<t>- Explicit text that the partial reliability and limited retransmission
policies MUST NOT be used.</t>
<t>- Added open issue on whether the DCEP 'protocol' field value for CLUE
should contain a version number.</t>
<t>- Removed paragraph saying that an offerer must not insert more than
one m- line describing an SCTPoDTLS association to be used to
realize a CLUE Data Channel, as the draft already states that
only one CLUE Data Channel per CLUE session shall be opened.</t>
<t>- Added reference to draft-ietf-rtcweb-data-protocol regarding details
on reseting SCTP streams.</t>
<t>- Added text saying that the value of the DCEP 'channel type' MUST
be DATA_CHANNEL_RELIABLE.</t>
<t>- Clarified that DCEP must be supported, and used in the absence of another
mechanism for opening a CLUE Data Channel.</t>
</list>
</t>
<t>
Changes from draft-holmberg-clue-datachannel-03
<list style="symbols">
<t>Procedures updated, based on WG agreement (IETF#89) to
use DCEP for the CLUE data channel.</t>
<t>Procedures updated, based on WG agreement (IETF#89) that
offerer is responsible for sending DCEP DATA_CHANNEL_OPEN.</t>
<t>Editorial changes, and alignments caused by
changes in referenced specifications.</t>
</list>
</t>
<t>
Changes from draft-holmberg-clue-datachannel-02
<list style="symbols">
<t>PPID value for CLUE messages added</t>
<t>References updated</t>
</list>
</t>
<t>
Changes from draft-holmberg-clue-datachannel-01
<list style="symbols">
<t>More text added</t>
</list>
</t>
<t>
Changes from draft-holmberg-clue-datachannel-00
<list style="symbols">
<t>Editorial corrections based on comments from Paul K</t>
</list>
</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.3261"?>
<?rfc include="reference.RFC.3264"?>
<?rfc include="reference.RFC.4566"?>
<?rfc include="reference.RFC.4960"?>
<?rfc include="reference.RFC.5061"?>
<?rfc include="reference.RFC.6525"?>
<reference anchor="I-D.ietf-clue-protocol">
<front>
<title abbrev="CLUE protocol">
CLUE protocol
</title>
<author fullname="Roberta Presta" initials="R.P" surname="Presta">
<organization>University of Napoli</organization>
</author>
<author fullname="Simon Pietro Romano" initials="S P.R" surname="Romano">
<organization>University of Napoli</organization>
</author>
<date day="24" month="October" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-clue-protocol-02.txt" />
</reference>
<reference anchor="I-D.ietf-clue-signaling">
<front>
<title abbrev="CLUE signaling">
CLUE Signaling
</title>
<author fullname="Paul Kyzivat" initials="P.K" surname="Kyzivat">
</author>
<author fullname="Lennard Xiao" initials="L.X" surname="Xiao">
<organization>Huawei</organization>
</author>
<author fullname="Christian Groves" initials="C.G" surname="Groves">
<organization>Huawei</organization>
</author>
<author fullname="Robert Hansen" initials="S P.R" surname="Romano">
<organization>Cisco</organization>
</author>
<date day="27" month="October" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-clue-signaling-04.txt" />
</reference>
<reference anchor="I-D.ietf-tsvwg-sctp-dtls-encaps">
<front>
<title abbrev="SCTP over DLTS">
DTLS Encapsulation of SCTP Packets
</title>
<author fullname="Michael Tuexen" initials="M.T" surname="Tuexen">
<organization>Muenster University of Applied Sciences</organization>
</author>
<author fullname="Randall Stewart" initials="R.S" surname="Stewart">
<organization>Adara Networks</organization>
</author>
<author fullname="Randell Jesup" initials="R.J" surname="Jesup">
<organization>WorldGate Communications</organization>
</author>
<author fullname="Salvatore Loreto" initials="S.L" surname="Loreto">
<organization>Ericsson</organization>
</author>
<date day="15" month="January" year="2015" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-tsvwg-sctp-dtls-encaps-08.txt" />
</reference>
<reference anchor="I-D.ietf-mmusic-sctp-sdp">
<front>
<title abbrev="The SCTP protocol identifier for SDP">
Stream Control Transmission Protocol (SCTP)-Based Media
Transport in the Session Description Protocol (SDP)
</title>
<author initials="C." surname="Holmberg" fullname="Christer Holmberg">
<organization>Ericsson</organization>
</author>
<author initials="S." surname="Loreto" fullname="Salvatore Loreto">
<organization>Ericsson</organization>
</author>
<author initials="G." surname="Camarillo" fullname="Gonzalo Camarillo">
<organization>Ericsson</organization>
</author>
<date day="15" month="January" year="2015" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-mmusic-sctp-sdp-12.txt" />
</reference>
<reference anchor="I-D.ietf-rtcweb-data-channel">
<front>
<title abbrev="WebRTC Data Channels">
WebRTC Data Channels
</title>
<author fullname="Randell Jesup" initials="R.J" surname="Jesup">
<organization>WorldGate Communications</organization>
</author>
<author fullname="Salvatore Loreto" initials="S.L" surname="Loreto">
<organization>Ericsson</organization>
</author>
<author fullname="Michael Tuexen" initials="M.T" surname="Tuexen">
<organization>Muenster University of Applied Sciences</organization>
</author>
<date day="4" month="January" year="2015" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-rtcweb-data-channel-13.txt" />
</reference>
<reference anchor="I-D.ietf-tsvwg-sctp-prpolicies">
<front>
<title abbrev="Additional PR-SCTP Policies">
Additional Policies for the Partial Reliability Extension of the Stream
Control Transmission Protocol
</title>
<author fullname="Michael Tuexen" initials="M.T" surname="Tuexen">
<organization>Muenster University of Applied Sciences</organization>
</author>
<author fullname="Robin Seggelmann" initials="R.S" surname="Seggelmann">
<organization>T-Systems International GmbH</organization>
</author>
<author fullname="Randall Stewart" initials="R.S" surname="Stewart">
<organization>Netflix, Inc.</organization>
</author>
<author fullname="Salvatore Loreto" initials="S.L" surname="Loreto">
<organization>Ericsson</organization>
</author>
<date day="10" month="December" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-tsvwg-sctp-prpolicies-06.txt" />
</reference>
<reference anchor="I-D.ejzak-mmusic-data-channel-sdpneg">
<front>
<title abbrev="SDP-based 'SCTP over DTLS' data channel negotiation">
SDP-based "SCTP over DTLS" data channel negotiation
</title>
<author fullname="Keith Drage" initials="K.D" surname="Drage">
<organization>Alcatel-Lucent</organization>
</author>
<author fullname="Raju Makaraju" initials="R.M" surname="Makaraju">
<organization>Alcatel-Lucent</organization>
</author>
<author fullname="Juergen Stoetzer-Bradler" initials="J.S" surname="Stoetzer-Bradler">
<organization>Alcatel-Lucent</organization>
</author>
<author fullname="Richard Ejzak" initials="R.E" surname="Ejzak">
<organization>Unaffiliated</organization>
</author>
<author fullname="Jerome Marcon" initials="J.M" surname="Marcon">
<organization>Unaffiliated</organization>
</author>
<date day="27" month="January" year="2015" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-mmusic-data-channel-sdpneg-00.txt" />
</reference>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.3758"?>
<reference anchor="I-D.ietf-rtcweb-data-protocol">
<front>
<title abbrev="WebRTC Data Channel Establishment Protocol">
WebRTC Data Channel Establishment Protocol
</title>
<author fullname="Randell Jesup" initials="R.J" surname="Jesup">
<organization>WorldGate Communications</organization>
</author>
<author fullname="Salvatore Loreto" initials="S.L" surname="Loreto">
<organization>Ericsson</organization>
</author>
<author fullname="Michael Tuexen" initials="M.T" surname="Tuexen">
<organization>Muenster University of Applied Sciences</organization>
</author>
<date day="4" month="January" year="2015" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-rtcweb-data-protocol-09.txt" />
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 02:56:44 |