One document matched: draft-ietf-clue-datachannel-01.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-01" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title abbrev="CLUE Protocol 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="2014" />
<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, together with the Data Channel Establishment
Protocol (DCEP) in order to establish a data channel,
referred to as CLUE Data Channel, for transporting CLUE
protocol messages between two CLUE entities.
</t>
<t>
The document defines the SCTP considerations specific
to a CLUE Data Channel, the SDP offer/answer procedures
for negotiating the establishment of, and the DCEP procedures
for opening, a CLUE Data Channel.
</t>
<t>
Details and procedures associated with the CLUE protocol 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" />, together with the Data Channel
Establishment Protocol (DCEP) <xref target="I-D.ietf-rtcweb-data-protocol"
pageno="false" format="default" /> in order to establish a data channel,
referred to as CLUE Data Channel, for transporting CLUE protocol
<xref target="I-D.ietf-clue-protocol" pageno="false"
format="default" /> messages between CLUE entities.
</t>
<t>
The document defines the SCTP considerations specific to a
CLUE Data Channel, the SDP offer/answer <xref target="RFC3264"
pageno="false" format="default" /> procedures for negotiating
the establishment of, and the DCEP procedures for opening, a
CLUE Data Channel.
</t>
<t>
Details and procedures associated with the CLUE protocol are
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>
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" />, with a specific set of SCTP characteristics,
and usage of the Data Channel Establishment Protocol (DCEP)
<xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" /> in order to open a WebRTC Data Channel for
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, and usage of the Data Channel Establishment Protocol (DCEP)
<xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" /> in order to open a WebRTC Data Channel for
the purpose of transporting CLUE protocol <xref target="I-D.ietf-clue-protocol"
pageno="false" format="default" /> messages between two CLUE entities.
</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.cdc.dcep" title="Data Channel Establishment Protocol (DCEP) Usage" toc="default">
<t>
A CLUE entity MUST support the Data Channel Establishment Protocol (DCEP)
<xref target="I-D.ietf-rtcweb-data-channel" pageno="false" format="default" />,
which can be used in order to open a WebRTC Data Channel.
</t>
<t>
In the absence of some other mechanism, a CLUE entity MUST use DCEP in order
to open a CLUE Data Channel.
</t>
<t>
NOTE: This document does not define any other mechanism for opening a CLUE Data
Channel, but such might be defined in future specifications.
</t>
<t>
The details of the DCEP usage with a CLUE Data Channel are described in
<xref target="section.cdcp.proc.open" pageno="false" format="default" />.
</t>
</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>
As described in <xref target="I-D.ietf-rtcweb-data-protocol"
pageno="false" format="default" />, the PPID value 50 is
used when sending a DCEP message on a WebRTC Data Channel.
</t>
<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 is transported
in a WebRTC Data Channel, 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>DCEP</c>
<c>50</c>
<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.interleaving" title="Interleaving" toc="default">
<t>
A CLUE entity MUST support the message interleaving mechanism
defined in <xref target="I-D.ietf-tsvwg-sctp-ndata" pageno="false"
format="default" />.
</t>
</section>
<section anchor="section.cdc.sctp.multihome" title="SCTP Multihoming" toc="default">
<t>
SCTP multihoming cannot be used for a CLUE Data Channel.
</t>
<t>
NOTE: SCTPoDTLS does not support SCTP multihoming.
</t>
</section>
</section>
</section>
<section anchor="section.cdcp" title="CLUE Data Channel Procedures" toc="default">
<section anchor="section.cdcp.proc.open" title="Open CLUE Data Channel" toc="default">
<t>
Once the SCTP association, to be used to realized the CLUE
Data Channel, has been established, the offerer <xref target="RFC3264"
pageno="false" format="default" /> is responsible for opening
the CLUE Data Channel. If DCEP is used, the offerer MUST send
a DCEP DATA_CHANNEL_OPEN message <xref target="I-D.ietf-rtcweb-data-protocol"
pageno="false" format="default" />. The value of the 'protocol' field
MUST be "CLUE". The value of the 'channel type' MUST be
'DATA_CHANNEL_RELIABLE'.
</t>
<t>
OPEN ISSUE: We need to determine whether we shall include a version
number in the 'protocol' field value for CLUE.
</t>
<t>
NOTE: A new 'protocol' value for CLUE needs to be
registered with IANA in the 'Protocol Registry' defined by
<xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" />.
</t>
<t>
Once the offerer has received the associated DCEP DATA_CHANNEL_ACK
message <xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" />, the CLUE Data channel has been opened.
</t>
<t>
If the offerer receives a DCEP DATA_CHANNEL_OPEN message, for the
purpose of opening a CLUE Data Channel, the offerer MUST reset the
SCTP stream, in order to prevent two CLUE Data Channels from being
established within the same CLUE session. The offerer MUST NOT send
a DCEP DATA_CHANNEL_ACK message.
</t>
</section>
<section anchor="section.cdcp.proc.close" title="Close CLUE Data Channel" toc="default">
<t>
DCEP <xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" /> does not define a message for closing a WebRTC Data Channel.
As described in <xref target="I-D.ietf-rtcweb-data-protocol" pageno="false"
format="default" />, in order to close a CLUE Data Channel, a SCTP reset
message is sent, in order to close the SCTP stream associated with the CLUE
Data Channel. The SCTP association, and WebRTC Data Channels associated with
other SCTP streams, are not affected by the SCTP reset message.
</t>
<t>
<xref target="section.oa.mod" pageno="false" format="default" /> describes
how to terminate the SCTP association used for the CLUE data channel.
</t>
</section>
<section anchor="section.cdcp.proc.sctp" title="SCTP Association Failure" toc="default">
<t>
In case of SCTP association failure, the offerer is responsible for trying to re-establish the
SCTP association (including sending a new SDP offer, if needed). Once the SCTP association
has been successfully re-established, the offerer is responsible for sending a
DCEP DATA_CHANNEL_OPEN message.
</t>
</section>
</section>
<section anchor="section.oa" title="SDP Offer/Answer Procedures" toc="default">
<section anchor="section.oa.gen" title="General" toc="default">
<t>
This section describes how an SDP media description ("m=") line describing
a SCTPoDTLS association, to be used to realize a CLUE Data Channel, is created,
and how it is used in SDP offers and answers <xref target="RFC3264" pageno="false"
format="default" />.
</t>
<t>
NOTE: The procedures associated with creating an "m=" line describing media
(e.g. audio and video) for a CLUE session are outside the scope
of this document.
</t>
<t>
OPEN ISSUE (Q1): It is FFS whether the SDP-based WebRTC Data Channel Negotiation mechanism
<xref target="I-D.ejzak-dispatch-webrtc-data-channel-sdpneg" pageno="false" format="default" />
will be used with the CLUE Data Channel. It depends on whether the draft will progress in MMUSIC,
and whether it will be finalized before the publication of the CLUE mechanism.
</t>
<t>
OPEN ISSUE (Q2): As the SDP offer/answer procedures are generic to SCTPoDTLS association, it is
FFS whether we need to specify them, or whether we can simply refer to draft-ietf-mmusic-sctp-sdp.
</t>
</section>
<section anchor="section.oa.mediadesc" title="SDP Media Description Fields" toc="default">
<t>
The field values of the "m=" line for the 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>DTLS port value</c>
<c>"DTLS/SCTP"</c>
<c>SCTP port value</c>
</texttable>
</section>
<section anchor="section.oa.sctpmap" title="SDP sctpmap Attribute" toc="default">
<t>
The field values of the SDP sctpmap attribute, associated with the "m=" line describing
the SCTPoDTLS association, are set as following:
</t>
<texttable anchor="table_SDP_sctpmap" title='SDP "proto" field values'>
<ttcol align='center'>sctpmap-number</ttcol>
<ttcol align='center'>app</ttcol>
<c>fmt value of the "m=" line</c>
<c>"webrtc-datachannel"</c>
</texttable>
</section>
<section anchor="section.oa.ino" title="Generating the Initial Offer" toc="default">
<t>
The procedures for the offerer follow the normal procedures defined in
<xref target="RFC3264" pageno="false" format="default" />.
</t>
<t>
When the offerer creates an offer, which contains an "m=" line describing a SCTPoDTLS
association, it assigns the field values to the "m=" line according to the procedures in
<xref target="section.oa.mediadesc" pageno="false" format="default" />. In addition,
the offerer MUST insert an SDP sctpmap attribute associated with the "m=" line.
</t>
<t>
If an offerer, in a subsequent offer, wants to disable the CLUE Data Channel,
it assigns a zero port value to the "m=" line describing the SCTPoDTLS association
used to realize the CLUE Data Channel.
</t>
</section>
<section anchor="section.oa.ans" title="Generating the Answer" toc="default">
<t>
The procedures for the answerer follow the normal procedures defined
in <xref target="RFC3264" pageno="false" format="default" />.
</t>
<t>
If the answerer receives an offer, which contains an "m=" line describing
a SCTPoDTLS association, and the answerer accepts the "m=" line, it
inserts an "m=" line in the corresponding answer, and assigns the
"m=" line field values according to the procedures in Section 4.2.
</t>
<t>
If the answerer receives an offer, which contains an "m=" line describing
a SCTPoDTLS association, and the answerer does not accept the "m=" line, it
inserts an "m=" line in the corresponding answer, and assigns a
zero port value to the "m=" line, according to the procedures in
<xref target="RFC3264" pageno="false" format="default" />.
</t>
<t>
If the answerer receives an offer, in which a zero port value has been
assigned to an "m=" line describing the SCTPoDTLS association, it inserts
an "m=" line in the corresponding answer, and assigns a zero port value
to the "m=" line, according to the procedures in <xref target="RFC3264"
pageno="false" format="default" />
</t>
<t>
OPEN ISSUE (Q3): We need to determine whether an "m=" line describing an
SCTPoDTLS association can be used together with bundle-only, in which
case there will be cases where an offer with a zero port value will
create a corresponding answer with a non-zero port value.
</t>
</section>
<section anchor="section.oa.opa" title="Offerer Processing of the Answer" toc="default">
<t>
When the offerer receives an SDP answer and, if the offerer ends
up being active it MUST initiate a DTLS handshake by
sending a DTLS ClientHello message on the negotiated media
stream, towards the IP address and port of the answerer.
</t>
</section>
<section anchor="section.oa.mod" title="Modifying the Session" toc="default">
<t>
Once an offer/answer exchange has been completed, either
endpoint MAY send a new offer in order to modify the session.
The endpoints can reuse the existing SCTPoDTLS association if
the key fingerprint values and transport parameters indicated
by each endpoint are unchanged are unchanged. Otherwise, following
the rules as for the initial offer/answer exchange, the endpoints
can negotiate and create a new SCTPoDTLS association and, once created,
delete the previous SCTPoDTLS association, following the same rules
of for the initial offer/answer exchange.
</t>
<t>
If an offerer wants to disable the CLUE Data Channel in an offer, it
assigns a zero port value to the "m=" line representing the SCTPoDTLS
association used to realize the 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 SCTP/DTLS 54111
a=sctpmap:54111 webrtc-datachannel
]]></artwork>
</figure>
</section>
</section>
<section anchor="section.sec" title="Security Considerations">
<t>
This specification does not introduce new security considerations, in addition to those
defined in [ref-to-data-channel] and [ref-to-data-protocol]. Security considerations associated
with the CLUE protocol are defined in [ref-to-clue-protocol].
</t>
</section>
<section anchor="section.iana" title="IANA Considerations">
<t>
[RFC EDITOR NOTE: Please replace RFC-XXXX with the RFC number of this document.]
</t>
</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-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.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="June" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-clue-protocol-01.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="4" month="July" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-tsvwg-sctp-dtls-encaps-05.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="July" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-rtcweb-data-channel-11.txt" />
</reference>
<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="July" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-rtcweb-data-protocol-07.txt" />
</reference>
<reference anchor="I-D.ietf-tsvwg-sctp-ndata">
<front>
<title abbrev="SCTP N-DATA Chunk">
Stream Schedulers and a New Data Chunk for the Stream Control
Transmission Protocol
</title>
<author fullname="Randall Stewart" initials="R.S" surname="Stewart">
<organization>Adara Networks</organization>
</author>
<author fullname="Michael Tuexen" initials="M.T" surname="Tuexen">
<organization>Muenster University of Applied Sciences</organization>
</author>
<author fullname="Salvatore Loreto" initials="S.L" surname="Loreto">
<organization>Ericsson</organization>
</author>
<author fullname="Robin Seggelmann" initials="R.S" surname="Seggelmann">
<organization>T-Systems International GmbH</organization>
</author>
<date day="4" month="July" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-tsvwg-sctp-ndata-01.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>Adara Networks</organization>
</author>
<author fullname="Salvatore Loreto" initials="S.L" surname="Loreto">
<organization>Ericsson</organization>
</author>
<date day="29" month="October" year="2014" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-tsvwg-sctp-prpolicies-03.txt" />
</reference>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.3758"?>
<reference anchor="I-D.ejzak-dispatch-webrtc-data-channel-sdpneg">
<front>
<title abbrev="SDP-based WebRTC data channel negotiation">
SDP-based WebRTC data channel negotiation
</title>
<author fullname="Richard Ejzak" initials="R.E" surname="Ejzak">
<organization>Alcatel-Lucent</organization>
</author>
<author fullname="Jerome Marcon" initials="J.M" surname="Marcon">
<organization>Alcatel-Lucent</organization>
</author>
<date day="14" month="October" year="2013" />
</front>
<seriesInfo name="Internet-Draft" value="draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt" />
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 02:57:26 |