idnits 2.17.1 draft-ietf-mmusic-sctp-sdp-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 7 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (February 13, 2014) is 3718 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 4347 (Obsoleted by RFC 6347) ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Obsolete normative reference: RFC 4572 (Obsoleted by RFC 8122) ** Obsolete normative reference: RFC 4960 (Obsoleted by RFC 9260) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) == Outdated reference: A later version (-09) exists of draft-ietf-behave-sctpnat-08 Summary: 7 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MMUSIC S. Loreto 3 Internet-Draft G. Camarillo 4 Intended status: Standards Track Ericsson 5 Expires: August 17, 2014 February 13, 2014 7 Stream Control Transmission Protocol (SCTP)-Based Media Transport in the 8 Session Description Protocol (SDP) 9 draft-ietf-mmusic-sctp-sdp-06 11 Abstract 13 SCTP (Stream Control Transmission Protocol) is a transport protocol 14 used to establish associations between two endpoints. This document 15 describes how to express media transport over SCTP in SDP (Session 16 Description Protocol). This document defines the 'SCTP', 'SCTP/DTLS' 17 and 'DTLS/SCTP' protocol identifiers for SDP. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 17, 2014. 36 Copyright Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Protocol Identifier . . . . . . . . . . . . . . . . . . . . . 4 56 4. Media Formats . . . . . . . . . . . . . . . . . . . . . . . . 5 57 4.1. Media Descriptions . . . . . . . . . . . . . . . . . . . . 5 58 5. Media attributes . . . . . . . . . . . . . . . . . . . . . . . 6 59 5.1. sctpmap Attribute . . . . . . . . . . . . . . . . . . . . 6 60 6. The Setup and Connection Attributes and Association 61 Management . . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 7. Multihoming . . . . . . . . . . . . . . . . . . . . . . . . . 7 63 8. Network Address Translation (NAT) Considerations . . . . . . . 8 64 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 65 9.1. Actpass/Passive . . . . . . . . . . . . . . . . . . . . . 9 66 9.2. Existing Connection Reuse . . . . . . . . . . . . . . . . 9 67 9.3. SDP description for SCTP over DTLS Connection . . . . . . 10 68 10. Security Considerations . . . . . . . . . . . . . . . . . . . 11 69 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 70 11.1. sctpmap attribute . . . . . . . . . . . . . . . . . . . . 11 71 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 72 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 13.1. Normative References . . . . . . . . . . . . . . . . . . . 12 74 13.2. Informative References . . . . . . . . . . . . . . . . . . 13 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 77 1. Introduction 79 SDP (Session Description Protocol) [RFC4566] provides a general- 80 purpose format for describing multimedia sessions in announcements or 81 invitations. TCP-Based Media Transport in the Session Description 82 Protocol (SDP) [RFC4145] specifies a general mechanism for describing 83 and establishing TCP (Transmission Control Protocol) streams. 84 Connection-Oriented Media Transport over the Transport Layer Security 85 (TLS) Protocol in the Session Description Protocol (SDP) [RFC4572] 86 extends RFC4145 [RFC4145] for describing TCP-based media streams that 87 are protected using TLS (Transport Layer Security) [RFC5246]. 89 This document defines three new protocol identifiers: 91 SCTP : to describe SCTP-based [RFC4960] media streams. 93 SCTP/DTLS : to describe media streams transported using the Datagram 94 Transport Layer Security (DTLS) [RFC4347] protocol over SCTP, as 95 specified in [RFC6083]. DTLS over SCTP provides communications 96 privacy for applications that use SCTP as their transport 97 protocol. 99 DTLS/SCTP : to describe media streams transported using SCTP on top 100 of the Datagram Transport Layer Security (DTLS) protocol, as 101 defined in [I-D.tuexen-tsvwg-sctp-dtls-encaps]. 103 The authentication certificates are interpreted and validated as 104 defined in RFC4572 [RFC4572]. Self-signed certificates can be used 105 securely, provided that the integrity of the SDP description is 106 assured as defined in RFC4572 [RFC4572]. 108 TLS is designed to run on top of a byte-stream oriented transport 109 protocol providing a reliable, in-sequence delivery like TCP. Since 110 no-one so far has implemented SCTP over TLS, due to some serious 111 limitations described in [RFC6083], this document does not make use 112 of TLS over SCTP as described in RFC3436 [RFC3436]. 114 Additionally, this document specifies the use of the 'setup' and 115 'connection' SDP attributes to establish SCTP associations. These 116 attributes were defined in RFC4145 [RFC4145] for TCP. This document 117 discusses their use with SCTP. 119 2. Terminology 121 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 122 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT 123 RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as 124 described in BCP 14, RFC 2119 [RFC2119] and indicate requirement 125 levels for compliant implementations. 127 3. Protocol Identifier 129 The following is the format for an 'm' line, as specified in RFC4566 130 [RFC4566]: 132 m= ... 134 This document defines three new values for the 'proto' field: 'SCTP', 135 'SCTP/DTLS' and 'DTLS/SCTP'. 137 The 'SCTP', 'SCTP/DTLS' and 'DTLS/SCTP' protocol identifiers are 138 similar to both the 'UDP' and 'TCP' protocol identifiers in that they 139 only describe the transport protocol and not the upper-layer 140 protocol. 142 Media described using an 'm' line containing the 'SCTP' protocol 143 identifier are carried using SCTP [RFC4960]. 145 The 'SCTP/DTLS' protocol identifier indicates that the media 146 described will use the Datagram Transport Layer Security (DTLS) 147 [RFC4347] over SCTP as specified in [RFC6083]. 149 The 'DTLS/SCTP' protocol identifier indicates that the media 150 described will use SCTP on top of the Datagram Transport Layer 151 Security (DTLS) protocol as specified in 152 [I-D.tuexen-tsvwg-sctp-dtls-encaps]. The actual layer below DTLS can 153 be plain UDP or what ICE agrees on (in the case ICE is used to 154 negotiate the actual transport flow). The lower layer used is 155 identified from the elements present inside the m= line block. 157 An 'm' line that specifies 'SCTP' or 'SCTP/DTLS' or 'DTLS/SCTP' MUST 158 further qualify the application-layer protocol using an fmt 159 identifier. 161 An 'm' line that specifies 'SCTP/DTLS' or 'DTLS/SCTP' MUST provide a 162 certificate fingerprint only if the endpoint supports, and is willing 163 to use, a cipher suite with an associated certificate. An SDP 164 attribute (an 'a' line) is used to transport and exchange end point 165 certificate. The authentication certificates are interpreted and 166 validated as defined in [RFC4572]. 168 4. Media Formats 170 The SDP specification, [RFC4566], states that specifications defining 171 new proto values, like the SCTP, SCTP/DTLS and DTLS/SCTP proto values 172 defined in this RFC, must define the rules by which their media 173 format (fmt) namespace is managed. Use of an existing MIME subtype 174 for the format is encouraged. If no MIME subtype exists, it is 175 RECOMMENDED that a suitable one is registered through the IETF 176 process [RFC4288] [RFC4289] by production of, or reference to, a 177 standards-track RFC that defines the transport protocol for the 178 format. 180 4.1. Media Descriptions 182 The media description change slightly depending on the actual 183 . 185 If the sub-field is 'SCTP' or 'SCTP/DTLS' 187 the is the SCTP transport port and follows the same active/ 188 passive offer/answer model described in Section 4.1 of [RFC4145]; 190 the sub-field carries the same port number value specified 191 in the and the mandatory SDP "sctpmap" attribute contains 192 the actual media format within the protocol parameter. 194 m=application 54111 SCTP/DTLS 54111 195 a=sctpmap:54111 t38 1 197 Running SCTP over DTLS make possible to have multiple SCTP 198 associations on top of the same DTLS connection; each SCTP 199 association make use of a distinct port number that is mainly used to 200 demultiplex the associations. 202 If the sub-field is 'DTLS/SCTP' 204 the is the UDP transport port; 206 the sub-field carries the SCTP port number and the mandatory 207 SDP "sctpmap" attribute contains the actual media format within 208 the protocol parameter. The SCTP port number is the UA chosen 209 port to use on the DTLS channel. 211 When a list of SCTP port number identifiers is given, this implies 212 that all of these associations MUST run on top of the same DTLS 213 connection. For the payload type assignments the "a=sctpmap:" 214 attribute (see Section 5.1) SHOULD be used to map from a port number 215 to a media encoding name that identifies the payload format 216 transported by the association or the actual application protocol 217 running on top of it. 219 m=application 54111 DTLS/SCTP 5000 220 c=IN IP4 79.97.215.79 221 a=sctpmap:5000 webrtc-datachannel max-message-size=100000 streams=16 223 5. Media attributes 225 5.1. sctpmap Attribute 227 The sctpmap attribute maps from a port number (as used in an "m=" 228 line) to an encoding name denoting the payload format to be used on 229 top of the SCTP association or the actual protocol running on top of 230 it. 232 The sctpmap MUST include the app parameter indicating the application 233 running on top of the association. 235 The sctpmap line should also contain the max-message-size parameter 236 indicating the maximum message size, in bytes, the endpoint is 237 willing to accept. 239 The peer should assume that larger message will be rejected by the 240 endpoint, though it is up to the endpoint decide the appropriate 241 behaviour. 243 A parameter with value of '0' will signal a best effort attempt, 244 subject to the current endpoint memory capacity, to handle 245 messages of any size. 247 If the parameter is not present, the implementation should provide 248 a default, with a suggested value of 64K. 250 It may also provide the stream parameter to specify the initial 251 number of incoming streams to be supported by each side of the 252 association. 254 If this parameter is not present, the implementation should 255 provide a default, with a suggested value of 16. 257 sctpmap-attr = "a=sctpmap:" sctpmap-number 258 app [max-message-size] [streams] 259 sctpmap-number = 1*DIGIT 260 app = token 261 max-message-size = "max-message-size" EQUALS 1*DIGIT 262 streams = "streams" EQUALS 1*DIGIT" 264 For the "a=sctpmap:" attribute line in the offer, there MUST be a 265 corresponding "a=sctpmap:" attribute line in the answer. 267 Any offered association MAY be rejected in the answer, for any 268 reason. If an association offer is rejected, the offerer and 269 answerer MUST NOT establish an SCTP association for it. To reject an 270 SCTP association, the SCTP port number in the "a=sctpmap:" attribute 271 line in the answer MUST be set to zero. 273 Any offered association with an "a=sctpmap:" attribute line providing 274 an incoming stream number of zero or larger than 65535 MUST be 275 rejected in the answer. An offered association answered with an 276 "a=sctpmap:" attribute line providing an incoming stream number of 277 zero or larger than 65535 MUST NOT be established. 279 6. The Setup and Connection Attributes and Association Management 281 The use of the 'setup' and 'connection' attributes in the context of 282 an SCTP association is identical to the use of these attributes in 283 the context of a TCP connection. That is, SCTP endpoints MUST follow 284 the rules in Sections 4 and 5 of RFC 4145 [RFC4145] when it comes to 285 the use of the 'setup' and 'connection' attributes in offer/answer 286 [RFC3264] exchanges. 288 The management of an SCTP association is identical to the management 289 of a TCP connection. That is, SCTP endpoints MUST follow the rules 290 in Section 6 of RFC 4145 [RFC4145] to manage SCTP associations. 291 Whether to use the SCTP ordered or unordered delivery service is up 292 to the applications using the SCTP association. 294 7. Multihoming 296 An SCTP endpoint, unlike a TCP endpoint, can be multihomed. An SCTP 297 endpoint is considered to be multihomed if it has more than one IP 298 address. A multihomed SCTP endpoint informs a remote SCTP endpoint 299 about all its IP addresses using the address parameters of the INIT 300 or the INIT-ACK chunk (depending on whether the multihomed endpoint 301 is the one initiating the establishment of the association). 303 Therefore, once the address provided in the 'c' line has been used to 304 establish the SCTP association (i.e., to send the INIT chunk), 305 address management is performed using SCTP. This means that two SCTP 306 endpoints can use addresses that were not listed in the 'c' line but 307 that were negotiated using SCTP mechanisms. 309 During the lifetime of an SCTP association, the endpoints can add and 310 remove new addresses from the association at any point [RFC5061]. If 311 an endpoint removes the IP address listed in its 'c' line from the 312 SCTP association, the endpoint SHOULD update the 'c' line (e.g., by 313 sending a re-INVITE with a new offer) so that it contains an IP 314 address that is valid within the SCTP association. 316 In some environments, intermediaries performing firewall control use 317 the addresses in offer/answer exchanges to perform media 318 authorization. That is, policy-enforcement network elements do not 319 let media through unless it is sent to the address in the 'c' line. 321 In such network environments, the SCTP endpoints can only exchange 322 media using the IP addresses listed in their 'c' lines. In these 323 environments, an endpoint wishing to use a different address needs to 324 update its 'c' line (e.g., by sending a re-INVITE with a new offer) 325 so that it contains the new IP address. 327 It is worth to underline that when using SCTP on top of DTLS, only 328 single homed SCTP associations can be used, since DTLS does not 329 expose any address management to its upper layer. 331 8. Network Address Translation (NAT) Considerations 333 SCTP specific features (not present in UDP/TCP), such as the checksum 334 (CRC32c) value calculated on the whole packet (not just the header) 335 or its multihoming capabilities, present new challenges for NAT 336 traversal. [I-D.ietf-behave-sctpnat] describes an SCTP specific 337 variant of NAT, which provides similar features of Network Address 338 and Port Translation (NAPT). 340 Current NATs do not typically support SCTP. As an alternative to 341 design SCTP specific NATs, Encapsulating SCTP into UDP [RFC6951] 342 makes it possible to use SCTP in networks with legacy NAT and 343 firewalls not supporting SCTP. 345 At the time of writing, the work on NAT traversal for SCTP is still 346 work in progress. Additionally, no extension has been defined to 347 integrate ICE (Interactive Connectivity Establishment) [RFC5768] with 348 SCTP and its multihoming capabilities either. Therefore, this 349 specification does not define how to describe SCTP-over-UDP streams 350 in SDP or how to establish and maintain SCTP associations using ICE. 351 Should these features be specified for SCTP in the future, there will 352 be a need to specify how to use them in an SDP environment as well. 354 9. Examples 356 The following examples show the use of the 'setup' and 'connection' 357 SDP attributes. As discussed in Section 6, the use of these 358 attributes with an SCTP association is identical to their use with a 359 TCP connection. For the purpose of brevity, the main portion of the 360 session description is omitted in the examples, which only show 'm' 361 lines and their attributes (including 'c' lines). 363 9.1. Actpass/Passive 365 An offerer at 192.0.2.2 signals its availability for an SCTP 366 association at SCTP port 54111. Additionally, this offerer is also 367 willing to initiate the SCTP association: 369 m=application 54111 SCTP 54111 370 c=IN IP4 192.0.2.2 371 a=setup:actpass 372 a=connection:new 373 a=sctpmap:54111 t38 1 375 Figure 1 377 The endpoint at 192.0.2.1 responds with the following description: 379 m=application 54321 SCTP 54321 380 c=IN IP4 192.0.2.1 381 a=setup:passive 382 a=connection:new 383 a=sctpmap:t54321 t38 1 385 Figure 2 387 This will cause the offerer (at 192.0.2.2) to initiate an SCTP 388 association to port 54321 at 192.0.2.1. 390 9.2. Existing Connection Reuse 392 Subsequent to the exchange in Section 9.1, another offer/answer 393 exchange is initiated in the opposite direction. The endpoint at 394 192.0.2.1, which now acts as the offerer, wishes to continue using 395 the existing association: 397 m=application 54321 SCTP * 398 c=IN IP4 192.0.2.1 399 a=setup:passive 400 a=connection:existing 402 Figure 3 404 The endpoint at 192.0.2.2 also wishes to use the existing SCTP 405 association and responds with the following description: 407 m=application 54111 SCTP * 408 c=IN IP4 192.0.2.2 409 a=setup:active 410 a=connection:existing 412 Figure 4 414 The existing SCTP association between 192.0.2.2 and 192.0.2.1 will be 415 reused. 417 9.3. SDP description for SCTP over DTLS Connection 419 This example shows the usage of SCTP over DTLS. 421 An offerer at 192.0.2.2 signals the availability of a webrtc- 422 DataChannel session over SCTP/DTLS. The DTLS connection runs on top 423 of port 54111. 425 m=application 54111 DTLS/SCTP 5000 426 c=IN IP4 192.0.2.2 427 a=setup:actpass 428 a=connection:new 429 a=fingerprint:SHA-1 \ 430 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 431 a=sctpmap:5000 webrtc-DataChannel max-message-size=100000 streams=16 433 Figure 5 435 The endpoint at 192.0.2.1 responds with the following description: 437 m=application 62442 DTLS/SCTP 5001 438 c=IN IP4 192.0.2.1 439 a=setup:actpass 440 a=connection:new 441 a=fingerprint:SHA-1 \ 442 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 443 a=sctpmap:5001 webrtc-DataChannel max-message-size=100000 streams=16 445 Figure 6 447 10. Security Considerations 449 See RFC 4566 [RFC4566] for security considerations on the use of SDP 450 in general. See RFC 3264 [RFC3264], RFC 4145 [RFC4145] and RFC 4572 451 [RFC4572] for security considerations on establishing media streams 452 using offer/answer exchanges. See RFC 4960 [RFC4960] for security 453 considerations on SCTP in general and [RFC6083] for security 454 consideration using DTLS on top of SCTP. This specification does not 455 introduce any new security consideration in addition to the ones 456 discussed in those specifications. 458 11. IANA Considerations 460 This document defines three new proto values: 'SCTP', 'SCTP/DTLS' and 461 'DTLS/SCTP'. Their formats are defined in Section 3. These proto 462 values should be registered by the IANA under "Session Description 463 Protocol (SDP) Parameters" under "proto". 465 11.1. sctpmap attribute 467 This document defines a new SDP session and media-level attribute: 469 'sctpmap'. Its format is defined in Section 5.1. This attribute 470 should be registered by IANA under "Session Description Protocol 471 (SDP) Parameters" under "att-field" (both session and media 472 level)". 474 The 'sctpmap' attribute also 476 'sctpmap'. Its format is defined in Section 5.1. This attribute 477 should be registered by IANA under "Session Description Protocol 478 (SDP) Parameters" under "att-field" (both session and media 479 level)". 481 The sctpmap also specifies tree parameters: 483 The mandatory 'app' parameter indicating the application running 484 on top of the association. 486 The optional max-message-size parameter indicating the maximum 487 message size, in bytes, the endpoint is willing to accept. 489 The optional streams parameter indicating the maximum message 490 size, in bytes, the endpoint is willing to accept. 492 The 'stream' attribute indicating the initial number of incoming 493 streams supported by each side of the association. 495 sctpmap-attr = "a=sctpmap:" sctpmap-number 496 app [max-message-size] [streams] 497 sctpmap-number = 1*DIGIT 498 app = token 499 max-message-size = "max-message-size" EQUALS 1*DIGIT 500 streams = "streams" EQUALS 1*DIGIT" 502 [Open Issue] This specification has to creats a new IANA registry 503 named "SCTP Application" to register all the possible values of the 504 'app' parameter and register as first value "webrtc-datachannel" for 505 draft-ietf-rtcweb-data-channel. 507 12. Acknowledgments 509 The authors wish to thank Harald Alvestrand, Randell Jesup, Paul 510 Kyzivat, Michael Tuexen for their comments and useful feedback. 512 13. References 514 13.1. Normative References 516 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 517 Requirement Levels", BCP 14, RFC 2119, March 1997. 519 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 520 with Session Description Protocol (SDP)", RFC 3264, 521 June 2002. 523 [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in 524 the Session Description Protocol (SDP)", RFC 4145, 525 September 2005. 527 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 528 Registration Procedures", RFC 4288, December 2005. 530 [RFC4289] Freed, N. and J. Klensin, "Multipurpose Internet Mail 531 Extensions (MIME) Part Four: Registration Procedures", 532 BCP 13, RFC 4289, December 2005. 534 [RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer 535 Security", RFC 4347, April 2006. 537 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 538 Description Protocol", RFC 4566, July 2006. 540 [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the 541 Transport Layer Security (TLS) Protocol in the Session 542 Description Protocol (SDP)", RFC 4572, July 2006. 544 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 545 RFC 4960, September 2007. 547 [RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. 548 Kozuka, "Stream Control Transmission Protocol (SCTP) 549 Dynamic Address Reconfiguration", RFC 5061, 550 September 2007. 552 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 553 (TLS) Protocol Version 1.2", RFC 5246, August 2008. 555 [I-D.tuexen-tsvwg-sctp-dtls-encaps] 556 Jesup, R., Loreto, S., Stewart, R., and M. Tuexen, "DTLS 557 Encapsulation of SCTP Packets for RTCWEB", 558 draft-tuexen-tsvwg-sctp-dtls-encaps-01 (work in progress), 559 July 2012. 561 13.2. Informative References 563 [RFC3436] Jungmaier, A., Rescorla, E., and M. Tuexen, "Transport 564 Layer Security over Stream Control Transmission Protocol", 565 RFC 3436, December 2002. 567 [RFC6083] Tuexen, M., Seggelmann, R., and E. Rescorla, "Datagram 568 Transport Layer Security (DTLS) for Stream Control 569 Transmission Protocol (SCTP)", RFC 6083, January 2011. 571 [RFC5768] Rosenberg, J., "Indicating Support for Interactive 572 Connectivity Establishment (ICE) in the Session Initiation 573 Protocol (SIP)", RFC 5768, April 2010. 575 [RFC6951] Tuexen, M. and R. Stewart, "UDP Encapsulation of Stream 576 Control Transmission Protocol (SCTP) Packets for End-Host 577 to End-Host Communication", RFC 6951, May 2013. 579 [I-D.ietf-behave-sctpnat] 580 Stewart, R., Tuexen, M., and I. Ruengeler, "Stream Control 581 Transmission Protocol (SCTP) Network Address Translation", 582 draft-ietf-behave-sctpnat-08 (work in progress), 583 February 2013. 585 Authors' Addresses 587 Salvatore Loreto 588 Ericsson 589 Hirsalantie 11 590 Jorvas 02420 591 Finland 593 Email: Salvatore.Loreto@ericsson.com 595 Gonzalo Camarillo 596 Ericsson 597 Hirsalantie 11 598 Jorvas 02420 599 Finland 601 Email: Gonzalo.Camarillo@ericsson.com