One document matched: draft-ietf-mmusic-sctp-sdp-08.xml
<?xml version="1.0"?>
<?rfc symrefs="yes"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc sortrefs="no" ?>
<rfc category="std" docName="draft-ietf-mmusic-sctp-sdp-08" ipr="trust200902">
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<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>
<address>
<postal>
<street>Hirsalantie 11</street>
<code>02420</code>
<city>Jorvas</city>
<country>Finland</country>
</postal>
<email>christer.holmberg@ericsson.com</email>
</address>
</author>
<author initials="S." surname="Loreto" fullname="Salvatore Loreto">
<organization>Ericsson</organization>
<address>
<postal>
<street>Hirsalantie 11</street>
<code>02420</code>
<city>Jorvas</city>
<country>Finland</country>
</postal>
<email>Salvatore.Loreto@ericsson.com</email>
</address>
</author>
<author initials="G." surname="Camarillo" fullname="Gonzalo Camarillo">
<organization>Ericsson</organization>
<address>
<postal>
<street>Hirsalantie 11</street>
<code>02420</code>
<city>Jorvas</city>
<country>Finland</country>
</postal>
<email>Gonzalo.Camarillo@ericsson.com</email>
</address>
</author>
<date year="2014"/>
<area>RAI</area>
<workgroup>MMUSIC</workgroup>
<keyword>SCTP, SDP, DTLS</keyword>
<abstract>
<t>
SCTP (Stream Control Transmission Protocol) is a transport protocol used to
establish associations between two endpoints.
</t>
<t>
This specification describes how
to describe SCTP associations using the Session Description Protocol (SDP),
and defines the following new SDP Media Description protocol identifiers
(proto values):'SCTP', 'SCTP/DTLS' and 'DTLS/SCTP'.
</t>
<t>
The specification also describes how to use the new proto values together
with the SDP Offer/Answer mechanism in order to negotiate and establish
SCTP associations, and how to indicate the SCTP application usage.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
SDP (Session Description Protocol) <xref target="RFC4566"/> provides a
general-purpose format for describing multimedia sessions in announcements
or invitations. TCP-Based Media Transport in the Session Description Protocol
(SDP) <xref target="RFC4145"/> specifies a general mechanism for describing and
establishing TCP (Transmission Control Protocol) <xref target="RFC5246"/> streams.
Connection-Oriented Media Transport over the Transport Layer Security (TLS)
Protocol in the Session Description Protocol (SDP) <xref target="RFC4572"/>
extends RFC4145 <xref target="RFC4145"/> for describing TCP-based media
streams that are protected using TLS.
</t>
<t>
SCTP (Stream Control Transmission Protocol) is a transport protocol used to
establish associations between two endpoints.
</t>
<t>
This specification describes how
to describe SCTP associations using the Session Description Protocol (SDP)
<xref target="RFC4566"/>, and defines the following new SDP Media Description
<xref target="RFC4566"/> protocol identifiers (proto values):'SCTP', 'SCTP/DTLS'
and 'DTLS/SCTP'.
</t>
<t>
The specification also describes how to use the new proto values together
with the SDP Offer/Answer mechanism <xref target="RFC3264"/> in order to
negotiate and establish SCTP associations, and how to indicate the SCTP
application usage.
</t>
<t>
NOTE: TLS is designed to run on top of a byte-stream oriented transport
protocol providing a reliable, in-sequence delivery like TCP.
<xref target="RFC6083"/> presents serious limitations with
transporting SCTP on top of TLS. Therefore, defining a mechanism
to negotiate media streams transported using SCTP on top of TLS
is outside the scope of this specification.
</t>
</section>
<section title="Terminology">
<t>
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described
in BCP 14, <xref target="RFC2119">RFC 2119</xref> and indicate
requirement levels for compliant implementations.
</t>
</section>
<section title="SCTP Terminology">
<t>
SCTP Association: A protocol relationship between SCTP endpoints,
composed of the two SCTP endpoints and protocol state information
including Verification Tags and the currently active set of
Transmission Sequence Numbers (TSNs), etc. An association can be
uniquely identified by the transport addresses used by the
endpoints in the association. Two SCTP endpoints MUST NOT have
more than one SCTP association between them at any given time.
</t>
<t>
SCTP Stream: 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>
SCTP Transport address: A transport address is traditionally defined by
a network-layer address, a transport-layer protocol, and a
transport-layer port number. In the case of SCTP running over IP,
a transport address is defined by the combination of an IP address
and an SCTP port number (where SCTP is the transport protocol).
</t>
</section>
<section title="SDP Media Descriptions" anchor="m-line">
<section title="General" anchor="m-line-gen">
<t>
This section defines the following new SDP Media Description (m- line)
protocol identifiers (proto values) for describing an SCTP association:
'SCTP', 'SCTP/DTLS' and 'DTLS/SCTP'. The section also describes how an
m- line, associated with the proto values, is created.
</t>
<t>
The following is the format for an 'm' line, as specified in RFC4566
<xref target="RFC4566"/>:
</t>
<figure>
<artwork><![CDATA[
m=<media> <port> <proto> <fmt> ...
]]></artwork>
</figure>
<t>
The 'SCTP', 'SCTP/DTLS' and 'DTLS/SCTP' proto values are similar
to both the 'UDP' and 'TCP' proto values in that they only
describe the transport protocol and not the upper-layer
protocol.
</t>
<t>
NOTE: When the 'DTLS/SCTP' proto value is used, the underlying
transport protocol is either UDP or TCP.
</t>
<t>
The m- line fmt value, identifying the application-layer protocol,
MUST be registered by IANA.
</t>
</section>
<section title="Protocol Identifiers" anchor="proto">
<t>
The new proto values are defined as below:
</t>
<t>
<list style="symbols">
<t>
The 'SCTP' proto value describes an SCTP association, as
defined in <xref target="RFC4960"/>.
</t>
<t>
The 'SCTP/DTLS' proto value describes a Datagram Transport Layer
Security (DTLS) <xref target="RFC6347"/> connection on top of an
SCTP association, as defined in <xref target="RFC6083"/>.
</t>
<t>
The 'DTLS/SCTP' proto value describes an SCTP association on top of
a DTLS connection, as defined in <xref target="I-D.ietf-tsvwg-sctp-dtls-encaps"/>.
</t>
</list>
</t>
<t>
NOTE: In the case of 'DTLS/SCTP', the actual transport protocol below
DTLS is either UDP or TCP.
</t>
<t>
OPEN ISSUE #1: It is FFS whether separate proto values will be used, depending
on whether the underlying transport protocol is UDP (e.g. 'UDP/DTLS/SCTP') or
TCP (e.g. 'TCP/DTLS/SCTP').
</t>
</section>
<section title="Media Format Management" anchor="media">
<t>
<xref target="RFC4566"/> defines that specifications defining new proto values must
define the rules by which their media format (fmt) namespace is managed.
Use of an existing MIME subtype for the format is encouraged. If no MIME subtype
exists, it is recommended that a suitable one is registered through the
IETF process <xref target="RFC6838"/> <xref target="RFC4289"/> by production of, or
reference to, a standards-track RFC that defines the transport protocol for the format.
</t>
<t>
An m- line with a proto value of 'SCTP', 'SCTP/DTLS' or 'DTLS/SCTP' always describe
a single SCTP association.
</t>
<t>
In addition, such m- line MUST further indicate the application-layer protocol
using an 'fmt' identifier. There MUST be exactly one 'fmt' value per m- line associated
with the proto values defined in this specification. The "fmt" namespace associated
with those proto values describes the generic application usage of the entire SCTP
association, including the associated SCTP streams.
</t>
<t>
NOTE: A mechanism on how to describe, and manage, individual SCTP streams within an
SCTP association, is outside the scope of this specification.
</t>
</section>
<section title="Syntax" anchor="m-line-syn">
<figure>
<artwork><![CDATA[
sctp-m-line = %x6d "="
("application" SP sctp-port SP "SCTP" SP sctp-fmt CRLF) /
("application" SP sctp-port SP "SCTP/DTLS" SP sctp-fmt CRLF) /
("application" SP udp-port SP "DTLS/SCTP" SP sctp-fmt CRLF)
sctp-port = port
udp-port = port
sctp-fmt = association-usage
association-usage = token
]]></artwork>
</figure>
</section>
<section title="Example">
<figure>
<artwork><![CDATA[
m=application 12345 DTLS/SCTP webrtc-datachannel
a=fmtp:webrtc-datachannel max-message-size=100000
]]></artwork>
</figure>
</section>
</section>
<section title="SDP 'sctp-port' Attribute" anchor="attr-sctp-port">
<section title="General" anchor="attr-sctp-port-gen">
<t>
This section defines a new SDP media-level attribute, 'sctp-port'.
The attribute can be associated with an SDP media descriptor (m- line)
with a 'DTLS/SCTP' proto value, in which case the m- line
port value indicates the port of the underlying transport
protocol (UDP or TCP).
</t>
<t>
If the SDP sctp-port attribute is not present, the default value
is 5000.
</t>
<t>
Usage of the SDP sctp-port attribute with other proto values
is not specified, and MUST be discarded if received.
</t>
</section>
<section title="Syntax" anchor="attr-sctp-port-syn">
<figure>
<artwork><![CDATA[
sctp-port-attr = "a=sctp-port:" portnumber
port-number = port
port = 1*DIGIT
]]></artwork>
</figure>
</section>
</section>
<section title="SDP 'fmtp' Attribute" anchor="attr-max-message-size">
<section title="General" anchor="attr-max-message-size-gen">
<t>
The SDP 'fmtp' attribute can be used with an m- line, associated with an
SCTP association, to indicate the maximum message size that an SCTP endpoint
is willing to receive, for a particular SCTP association usage, on that
SCTP association.
</t>
<t>
The remote peer MUST assume that larger messages will be rejected by the
SCTP endpoint. SCTP endpoints need to decide on appropriate behaviour in
case a message that exceeds the maximum size needs to be sent.
</t>
<t>
If the SDP 'fmtp' attribute contains a maximum message size value of zero,
it indicates the SCTP endpoint will handle messages of any size, subject
to memory capacity etc.
</t>
<t>
If the SDP 'fmtp' attribute is not present, the default value is 64K.
</t>
</section>
<section title="Syntax" anchor="attr-max-message-size-syn">
<figure>
<artwork><![CDATA[
sctpmap-attr = "a=fmtp:" association-usage [max-message-size]
max-message-size = "max-message-size" EQUALS 1*DIGIT
]]></artwork>
</figure>
</section>
</section>
<section title="SCTP Association Management" anchor="sec-attributes-mgmt">
<section title="General" anchor="sec-attributes-mgmt-gen">
<t>
The management of an SCTP association is identical to the management
of a TCP connection. An SCTP endpoints MUST follow the rules in
Section 6 of <xref target="RFC4145"/> to manage SCTP associations.
Whether to use the SCTP ordered or unordered delivery service is up
to the applications using the SCTP association, and this specification
does not define a mechanism to indicate the type of delivery service
using SDP.
</t>
</section>
<section title="SDP setup Attribute" anchor="sec-attributes-setup">
<t>
If the m- line proto field value is 'SCTP/DTLS' or 'DTLS/SCTP', the SDP setup
attribute <xref target="RFC4145"/> is used to determine the TLS roles, following
the proceduresin <xref target="RFC4572"/> (the 'active' endpoint will take the TLS client role).
</t>
<t>
The SDP setup attribute is not used to determine which endpoint initiates the
SCTP association. Instead, both endpoints MUST initiate the SCTP association, and
MUST use the same SCTP port as client port and server port (in order to prevent
two separate SCTP associations from being established).
</t>
<t>
However, if the proto field value is 'DTLS/SCTP', and the transport layer
protocol is TCP (SCTP is carried on top of TCP), the SDP setup attribute is
also used to negotiate which endpoint will initiate the TCP connection (send TCP
SYN), following the procedures in <xref target="RFC4145"/>.
</t>
</section>
<section title="SDP connection Attribute" anchor="sec-attributes-connection">
<t>
The SDP connection attribute is used following the procedures in
<xref target="RFC4145"/>, with the additional SCTP specific
considerations described in this section.
</t>
<t>
In general, the SDP connection attribute only applies to an SCTP
association. Therefore, if the m- line proto field value is
'DTLS/SCTP', a connection attribute 'new' value will not
automatically re-establish an existing DTLS connection, unless
some DTLS properties are also changed in a way which require the
DTLS connection to be re-established.
</t>
<t>
However, if the m- line proto field value is 'SCTP/DTLS', if the
SCTP association is re-established, the DTLS connection also needs
to be re-established.
</t>
<t>
OPEN ISSUE #2: Verify that the above statement regarding 'SCTP/DTLS' is
correct.
</t>
</section>
</section>
<section title="SDP Offer/Answer Procedures">
<section title="General">
<t>
This section defines the SDP Offer/Answer <xref target="RFC3264"/>
procedures for negotiating and establishing an SCTP association. Unless
explicitly stated, the procedures apply to all protocol identifier
values ('SCTP', 'SCTP/DTLS' and 'DTLS/SCTP') defined in this specification.
</t>
<t>
If the m- line proto value is 'SCTP/DTLS' or 'DTLS/SCTP', each endpoint MUST
provide a certificate fingerprint, using the SDP 'fingerprint' attribute
<xref target="RFC4145"/>, if the endpoint supports, and is willing to use,
a cipher suite with an associated certificate.
</t>
<t>
The authentication certificates are interpreted and validated as
defined in <xref target="RFC4572"/>. Self-signed certificates can
be used securely, provided that the integrity of the SDP description
is assured as defined in <xref target="RFC4572"/>.
</t>
<t>
NOTE: The procedures apply to a specific m- line describing an SCTP association.
If an offer or answer contains multiple m- line describing SCTP associations,
the procedures are applied separately to each m- line. The procedures related to
SDP attributes apply to attributes associated with the m- line describing
the SCTP association.
</t>
<t>
EDITOR'S NOTE: The offer/answer proceudres for the max-message-size value still need to
be added.
</t>
</section>
<section title="Generating the Initial SDP Offer" anchor="sec-oa-initial-offer">
<t>
When the offerer creates an offer, if the m- line proto field value is 'SCTP/DTLS'
or 'DTLS/SCTP', the offerer MUST insert an SDP setup attribute in the offer, in
order to determine the TLS roles, and in cases where SCTP is transported on TCP,
determine which endpoint is responsible for establishing the TCP connection
[<xref target="sec-attributes-setup"/>].
</t>
<t>
The offerer MAY insert an SDP connection attribute, with a 'new' value, in the offer.
</t>
<t>
If the value of the m- line proto field is set to 'DTLS/SCTP', the offerer MAY
insert an SDP sctp-port attribute, with a value indicating the local SCTP port, in
the offer.
</t>
</section>
<section title="Generating the SDP Answer">
<t>
When the answerer receives an offer, which contains an m- line describing
an SCTP association, it MUST insert a corresponding m- line, with an
identical m- line proto field value, in the associated answer, following
the procedures in <xref target="RFC3264"/>.
</t>
<t>
If the answerer accepts the offered m- line, it assigns the other m- line
field values according to <xref target="m-line"/>.
</t>
<t>
If the offer contains an SDP setup attribute, the answerer MUST insert a
setup attribute in the answer, following the rules in <xref target="RFC4572"/>
and <xref target="RFC4145"/> (if applicable).
</t>
<t>
If the value of the m- line proto field is set to 'DTLS/SCTP', the answerer MAY
insert an SDP sctp-port attribute, with a value indicating the local SCTP port,
in the answer.
</t>
<t>
Once the answerer has sent the answer, if the SCTP association associated with
the m- line has yet not been established, or if an existing SCTP association is to be
re-established, the answer MUST start establishing the SCTP association towards
the peer.
</t>
<t>
If the answerer does not accept the m- line in the offer, it MUST assign a zero value
to the port field of the corresponding m- line in the answer. In addition, the answerer
MUST NOT insert an SDP setup attribute, or an SDP sctp-port attribute, in the answer.
</t>
</section>
<section title="Offerer Processing of the SDP Answer">
<t>
When the offerer receives an answer, if the SCTP association associated with
the m- line has not yet been established, or if an existing SCTP association is
to be re-established, the offerer MUST start establishing the SCTP association
towards the peer.
</t>
<t>
If the m- line port field value in the answer is zero, the offerer MUST terminate
the SCTP association (if it exists) associated with the m- line.
</t>
</section>
<section title="Modifying the Session">
<t>
When an offerer sends an updated offer, in order to modify a previously negotiated
SCTP association, it follows the rules in <xref target="sec-oa-initial-offer" />, with
the following exceptions:
</t>
<t>
If the offerer wants to re-establish an existing SCTP association associated with
the m- line, the offerer MUST insert an SDP connection attribute, with a 'new' value,
in the offer.
</t>
<t>
If the m- line proto field value is 'SCTP/DTLS' or 'DTLS/SCTP', and the offer is not
intended to re-establish the DTLS connection, the offerer MUST NOT insert a SDP setup
attribute with a value that changes the previously determined TLS roles in the offer.
</t>
<t>
If the offerer wants to disable a previously established SCTP association, it MUST set
the port value of the m- line associated with the SCTP association to zero, following
the procedures in <xref target="RFC3264"/>. The offerer MUST NOT insert an SDP setup
attribute, or an SDP sctp-port attribute, in the offer.
</t>
<t>
NOTE: Different SCTP association applications might define protocol procedures etc that
need to be performed before an SCTP association is terminated. Such procedures are
outside the scope of this specification.
</t>
</section>
</section>
<section title="Multihoming Considerations">
<t>
SCTP supports multihoming. An SCTP endpoint is considered
multihomed if it has more than one IP address on which SCTP
can be used. An SCTP endpoint inform the remote peer about
its IP addresses using the address parameters in the INIT/INIT-ACK
chunk. Therefore, when SDP is used to describe an SCTP association,
while the "c=" line contains the address which was used to negotiate
the SCTP association, multihomed SCTP endpoints might end up using
other IP addresses.
</t>
<t>
If an endpoint removes the IP address <xref target="RFC5061"/> that
it offered in the SDP "c=" line associated with the SCTP association,
it MUST send a new Offer, in which the "c=" line contains an IP address
with is valid within the SCTP association.
</t>
<t>
NOTE: In some network environments, intermediaries performing gate-
and firewall control use the address information in the SDP "c=" and
"m=" lines to authorize media, and will not pass media sent using
other addresses. In such network environment, if an SCTP endpoints
wants to change the address information on which media is sent and
received, it needs to send an updated Offer, in which the SDP "c="
and "m=" lines contain the new address information.
</t>
<t>
Multihoming is not supported when sending SCTP on top of DTLS,
as DTLS does not expose address management to its upper layer.
</t>
</section>
<section title="NAT Considerations">
<section title="General">
<t>
SCTP features not present in UDP or TCP, including the checksum
(CRC32c) value calculated on the whole packet (rather than
just the header), and multihoming, introduce new challenges
for NAT traversal. <xref target="I-D.ietf-behave-sctpnat"/>
defines an SCTP specific variant of NAT, which provides similar
features of Network Address and Port Translation (NAPT).
</t>
<t>
Current NATs typically do not support SCTP. <xref target="RFC6951"/>
defines a mechanism for sending SCTP on top of UDP, which makes it
possible to use SCTP with NATs and firewalls that do not support SCTP.
</t>
</section>
<section title="ICE Considerations">
<t>
At the time of writing this specification, no procedures have been
defined for using ICE ICE (Interactive Connectivity Establishment)
<xref target="RFC5768"/> together with SCTP. Such procedures, including
the associated SDP Offer/Answer procedures, are outside the scope of
this specification, and might be defined in a future specification.
</t>
</section>
</section>
<section title="Examples">
<t>
TODO: ADD EXAMPLES HERE
</t>
</section>
<section title="Security Considerations">
<t>
<xref target="RFC4566"/> defines general SDP security considerations, while
<xref target="RFC3264"/>, <xref target="RFC4145"/> and <xref target="RFC4572"/>
define security considerations when using the SDP Offer/Answer mechanism
to negotiate media streams.
</t>
<t>
<xref target="RFC4960"/> defines general SCTP security considerations.
security considerations on SCTP in general, while <xref target="RFC6083"/>
defines security considerations when using DTLS on top of
SCTP.
</t>
<t>
This specification does not introduce new security considerations in addition
to those defined in the specifications listed above.
</t>
</section>
<section title="IANA Considerations">
<section title="New SDP proto values" anchor="iana-sdp-proto" toc="default">
<t>
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number
of this document.]
</t>
<t>
This document updates the "Session Description Protocol (SDP) Parameters" registry,
following the procedures in <xref target="RFC4566" pageno="false" format="default"/>,
by adding the following values to the table in the SDP "proto" field registry:
</t>
<texttable anchor="table_SDP_proto_values" title='SDP "proto" field values'>
<ttcol align='center'>Type</ttcol>
<ttcol align='center'>SDP Name</ttcol>
<ttcol align='center'>Reference</ttcol>
<c>proto</c>
<c>SCTP</c>
<c>[RFCXXXX]</c>
<c>proto</c>
<c>SCTP/DTLS</c>
<c>[RFCXXXX]</c>
<c>proto</c>
<c>DTLS/SCTP</c>
<c>[RFCXXXX]</c>
</texttable>
</section>
<section title="New SDP Attribute" anchor="sctp-port-iana-sdp-attribute" toc="default">
<t>
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number
of this document.]
</t>
<t>
This document defines a new SDP media-level attribute,'sctp-port', as follows:
</t>
<figure>
<artwork align="left"><![CDATA[
Attribute name: sctp-port
Type of attribute: media
Subject to charset: No
Purpose: Indicate the SCTP port value associated
with the SDP Media Description.
Appropriate values: Integer
Contact name: Christer Holmberg
Contact e-mail: christer.holmberg@ericsson.com
Reference: RFCXXXX
]]></artwork>
</figure>
</section>
<section title="association-usage Name Registry" anchor="iana-assusage-registry" toc="default">
<t>
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number
of this document.]
</t>
<t>
This specification creates a new IANA registry, following the procedures in
<xref target="RFC5226"/>, for the "fmt" namespace associated with the
'SCTP', 'SCTP/DTLS' and 'DTLS/SCTP' protocol identifiers. Each "fmt" value
describes the usage of an entire SCTP association, including all SCTP streams
associated with the SCTP association.
</t>
<t>
NOTE: Usage indication of individual SCTP streams is outside the scope of this
specification.
</t>
<t>
The "fmt" value, "association-usage", used with these "proto" is required.
It is defined in section <xref target="m-line"/>.
</t>
<t>
As part of this registry, IANA maintains the following information:
</t>
<t>
<list style='hanging'>
<t hangText="association-usage Name:">.The identifier of the
subprotocol, as will be used in the <sctp-fmtp> subfield.</t>
<t hangText="association-usage reference:">A reference to the
document in which the the association usage is defined.</t>
</list>
</t>
<t>
association-usage names are to be subject to the "First Come First Served"
IANA registration policy [RFC5226].
</t>
<t>
IANA is asked to add initial values to the registry.
</t>
<figure anchor="exempleIANA" title="">
<artwork><![CDATA[
| name | Reference |
-+--------------------+-------------------------------------+
| webrtc-datachannel | draft-ietf-rtcweb-data-protocol-xx |
-+----------------------------------------------------------|
]]></artwork>
</figure>
</section>
</section>
<section title="Acknowledgments">
<t>
The authors wish to thank Harald Alvestrand, Randell Jesup, Paul Kyzivat,
Michael Tuexen for their comments and useful feedback.
</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.3264"?>
<?rfc include="reference.RFC.4145"?>
<?rfc include="reference.RFC.4289"?>
<?rfc include="reference.RFC.4566"?>
<?rfc include="reference.RFC.4572"?>
<?rfc include="reference.RFC.4960"?>
<?rfc include="reference.RFC.5061"?>
<?rfc include="reference.RFC.5226"?>
<?rfc include="reference.RFC.5246"?>
<?rfc include="reference.RFC.6347"?>
<?rfc include="reference.RFC.6838"?>
<?rfc include="reference.I-D.draft-ietf-tsvwg-sctp-dtls-encaps-06"?>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.6083"?>
<?rfc include="reference.RFC.5768"?>
<?rfc include="reference.RFC.6951"?>
<?rfc include="reference.I-D.draft-ietf-behave-sctpnat-09"?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 20:42:39 |