One document matched: draft-holmberg-clue-datachannel-00.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-holmberg-clue-datachannel-00" 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>PPID</keyword>
		<keyword>TELEPRESENCE</keyword>
		<keyword>RTCWEB</keyword>
		<keyword>WEBRTC</keyword>
		<abstract>
			<t>
				This document specifies how the usage of the Stream Control 
				Transmission Protocol (SCTP) on top of the Datagram Transport 
				Layer Security (DTLS) protocol (SCTPoDTLS) for transporting CLUE 
				protocol messages between CLUE entities.
			</t>
			<t>
				The document describes the SCTP considerations for CLUE, and
				the SDP Offer/Answer procedures for negotiating a SCTPoDTLS
				connection for CLUE.
			</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 specifies how the usage of the Stream Control 
				Transmission Protocol (SCTP) on top of the Datagram Transport 
				Layer Security (DTLS) protocol (SCTPoDTLS) for transporting CLUE 
				protocol messages between CLUE entities.
			</t>
			<t>
				The document describes the SCTP considerations for CLUE, and
				the SDP Offer/Answer procedures for negotiating a SCTPoDTLS
				connection for CLUE.
			</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>
				CLUE data channel refers to the SCTPoDTLS connection that is established between two
				CLUE entities in order to transport CLUE messages.
			</t>
			<t>
				CLUE message refers to a CLUE protocol message that is sent over the CLUE data channel.
			</t>
			<t>
				CLUE entity refers to a SIP User Agent (UA) device that supports the CLUE
				mechanism (including the CLUE protocol).
			</t>
		</section>

		<section anchor="section.dtls" title="SCTPoDTLS" toc="default">
			<section anchor="section.dtls.gen" title="General" toc="default">
				<t>
					The CLUE data channel is implemented by using the Stream Control 
					Transmission Protocol (SCTP) on top of the Datagram Transport 
					Layer Security (DTLS) protocol [I-D.tuexen-tsvwg-sctp-dtls-encaps].
				</t>
			</section>
			<section anchor="section.dtls.sctp" title="SCTP Considerations" toc="default">
				<section anchor="section.dtls.sctp.streams" title="SCTP Streams" toc="default">
					<t>
						CLUE entities MUST establish two uni-directional STCP streams between
						themselves, one for CLUE messages sent in each direction.
					</t>
				</section>
				<section anchor="section.dtls.sctp.ppid" title="SCTP Payload Protocol Identifier (PPID)" toc="default">
					<t>
						CLUE entities MUST use a PPID value of 50 or 51, according to the 
						procedures in [ref-to-rtcweb-data-channel].
					</t>
				</section>
				<section anchor="section.dtls.sctp.reliability" title="Reliability" toc="default">
					<t>
						CLUE entities MUST use the reliable transport SCTP feature.
					</t>
				</section>
				<section anchor="section.dtls.sctp.order" title="Order" toc="default">
					<t>
						CLUE entities MUST use the ordered delivery SCTP feature.
					</t>
				</section>
				<section anchor="section.dtls.sctp.multihome" title="SCTP Multihoming" toc="default">
					<t>
						CLUE entities MUST NOT use SCTP multihoming.
					</t>
					<t>
						NOTE: The SCTPoDTLS mechanism does not support SCTP multihoming.
					</t>
				</section>
			</section>
		</section>

		<section anchor="section.oa" title="SDP Offer/Answer Procedures" toc="default">
			<t>
				TBD
			</t>
		</section>


		<section anchor="section.sec" title="Security Considerations">
			<t>
				TBD
			</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>
				TBD
			</t>
		</section>
		<section title="Change Log">
			<t>
				[RFC EDITOR NOTE: Please remove this section when publishing]
			</t>
			<t>
				Changes from draft-holmberg-clue-datachannel-xx
				<list style="symbols">
					<t>TBD</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"?>
		</references>
	</back>
</rfc>