draft-ietf-avtcore-rfc5764-mux-fixes-05.txt   draft-ietf-avtcore-rfc5764-mux-fixes-06.txt 
AVTCORE M. Petit-Huguenin AVTCORE M. Petit-Huguenin
Internet-Draft Impedance Mismatch Internet-Draft Impedance Mismatch
Updates: 5764 (if approved) G. Salgueiro Updates: 5764 (if approved) G. Salgueiro
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 29, 2016 January 26, 2016 Expires: September 3, 2016 March 2, 2016
Multiplexing Scheme Updates for Secure Real-time Transport Protocol Multiplexing Scheme Updates for Secure Real-time Transport Protocol
(SRTP) Extension for Datagram Transport Layer Security (DTLS) (SRTP) Extension for Datagram Transport Layer Security (DTLS)
draft-ietf-avtcore-rfc5764-mux-fixes-05 draft-ietf-avtcore-rfc5764-mux-fixes-06
Abstract Abstract
This document defines how Datagram Transport Layer Security (DTLS), This document defines how Datagram Transport Layer Security (DTLS),
Real-time Transport Protocol (RTP), Real-time Transport Control Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),
Protocol (RTCP), Session Traversal Utilities for NAT (STUN), and Session Traversal Utilities for NAT (STUN), and Traversal Using
Traversal Using Relays around NAT (TURN) packets are multiplexed on a Relays around NAT (TURN) packets are multiplexed on a single
single receiving socket. It overrides the guidance from SRTP receiving socket. It overrides the guidance from SRTP Extension for
Extension for DTLS [RFC5764], which suffered from three issues DTLS [RFC5764], which suffered from three issues described and fixed
described and fixed in this document. in this document.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 29, 2016. This Internet-Draft will expire on September 3, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Implicit Allocation of Codepoints for New STUN Methods . . . 4 3. Implicit Allocation of Codepoints for New STUN Methods . . . 4
4. Implicit Allocation of New Codepoints for TLS ContentTypes . 4 4. Implicit Allocation of New Codepoints for TLS ContentTypes . 5
5. Multiplexing of TURN Channels . . . . . . . . . . . . . . . . 5 5. Multiplexing of TURN Channels . . . . . . . . . . . . . . . . 5
6. RFC 5764 Updates . . . . . . . . . . . . . . . . . . . . . . 6 6. RFC 5764 Updates . . . . . . . . . . . . . . . . . . . . . . 6
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9.1. STUN Methods . . . . . . . . . . . . . . . . . . . . . . 8 9.1. STUN Methods . . . . . . . . . . . . . . . . . . . . . . 8
9.2. TLS ContentType . . . . . . . . . . . . . . . . . . . . . 9 9.2. TLS ContentType . . . . . . . . . . . . . . . . . . . . . 9
9.3. TURN Channel Numbers . . . . . . . . . . . . . . . . . . 9 9.3. TURN Channel Numbers . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Normative References . . . . . . . . . . . . . . . . . . 10 11.1. Normative References . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . 11 11.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Release notes . . . . . . . . . . . . . . . . . . . 11 Appendix A. Release notes . . . . . . . . . . . . . . . . . . . 11
A.1. Modifications between draft-ietf-avtcore-rfc5764-mux- A.1. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-05 and draft-ietf-avtcore-rfc5764-mux-fixes-04 . . 12 fixes-06 and draft-ietf-avtcore-rfc5764-mux-fixes-05 . . 12
A.2. Modifications between draft-ietf-avtcore-rfc5764-mux- A.2. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-04 and draft-ietf-avtcore-rfc5764-mux-fixes-03 . . 12 fixes-05 and draft-ietf-avtcore-rfc5764-mux-fixes-04 . . 12
A.3. Modifications between draft-ietf-avtcore-rfc5764-mux- A.3. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-03 and draft-ietf-avtcore-rfc5764-mux-fixes-02 . . 12 fixes-04 and draft-ietf-avtcore-rfc5764-mux-fixes-03 . . 12
A.4. Modifications between draft-ietf-avtcore-rfc5764-mux- A.4. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-02 and draft-ietf-avtcore-rfc5764-mux-fixes-01 . . 12 fixes-03 and draft-ietf-avtcore-rfc5764-mux-fixes-02 . . 12
A.5. Modifications between draft-ietf-avtcore-rfc5764-mux- A.5. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-01 and draft-ietf-avtcore-rfc5764-mux-fixes-00 . . 12 fixes-02 and draft-ietf-avtcore-rfc5764-mux-fixes-01 . . 12
A.6. Modifications between draft-ietf-avtcore-rfc5764-mux- A.6. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-01 and draft-ietf-avtcore-rfc5764-mux-fixes-00 . . 12
A.7. Modifications between draft-ietf-avtcore-rfc5764-mux-
fixes-00 and draft-petithuguenin-avtcore-rfc5764-mux- fixes-00 and draft-petithuguenin-avtcore-rfc5764-mux-
fixes-02 . . . . . . . . . . . . . . . . . . . . . . . . 13 fixes-02 . . . . . . . . . . . . . . . . . . . . . . . . 13
A.7. Modifications between draft-petithuguenin-avtcore-rfc5764 A.8. Modifications between draft-petithuguenin-avtcore-rfc5764
-mux-fixes-00 and draft-petithuguenin-avtcore-rfc5764 -mux-fixes-00 and draft-petithuguenin-avtcore-rfc5764
-mux-fixes-01 . . . . . . . . . . . . . . . . . . . . . . 13 -mux-fixes-01 . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
Section 5.1.2 of Secure Real-time Transport Protocol (SRTP) Extension Section 5.1.2 of Secure Real-time Transport Protocol (SRTP) Extension
for DTLS [RFC5764] defines a scheme for a Real-time Transport for DTLS [RFC5764] defines a scheme for a Real-time Transport
Protocol (RTP) [RFC3550] receiver to demultiplex Datagram Transport Protocol (RTP) [RFC3550] receiver to demultiplex Datagram Transport
Layer Security (DTLS) [RFC6347], Session Traversal Utilities for NAT Layer Security (DTLS) [RFC6347], Session Traversal Utilities for NAT
(STUN) [RFC5389] and Secure Real-time Transport Protocol (STUN) [RFC5389] and Secure Real-time Transport Protocol
(SRTP)/Secure Real-time Transport Control Protocol (SRTCP) [RFC3711] (SRTP)/Secure RTP Control Protocol (SRTCP) [RFC3711] packets that are
packets that are arriving on the RTP port. Unfortunately, this arriving on the RTP port. Unfortunately, this demultiplexing scheme
demultiplexing scheme has created problematic issues: has created problematic issues:
1. It implicitly allocated codepoints for new STUN methods without 1. It implicitly allocated codepoints for new STUN methods without
an IANA registry reflecting these new allocations. an IANA registry reflecting these new allocations.
2. It implicitly allocated codepoints for new Transport Layer 2. It implicitly allocated codepoints for new Transport Layer
Security (TLS) ContentTypes without an IANA registry reflecting Security (TLS) ContentTypes without an IANA registry reflecting
these new allocations. these new allocations.
3. It did not take into account the fact that the Traversal Using 3. It did not take into account the fact that the Traversal Using
Relays around NAT (TURN) usage of STUN can create TURN channels Relays around NAT (TURN) usage of STUN can create TURN channels
skipping to change at page 7, line 45 skipping to change at page 7, line 45
match any known range then the packet MUST be dropped and an alert match any known range then the packet MUST be dropped and an alert
MAY be logged. This process is summarized in Figure 3. MAY be logged. This process is summarized in Figure 3.
+----------------+ +----------------+
| [0..3] -+--> forward to STUN | [0..3] -+--> forward to STUN
| | | |
packet --> | [20..63] -+--> forward to DTLS packet --> | [20..63] -+--> forward to DTLS
| | | |
| [64..79] -+--> forward to TURN Channel | [64..79] -+--> forward to TURN Channel
| | | |
| [128..191] -+--> forward to RTP | [128..191] -+--> forward to RTP/RTCP
+----------------+ +----------------+
Figure 3: The DTLS-SRTP receiver's packet demultiplexing algorithm. Figure 3: The DTLS-SRTP receiver's packet demultiplexing algorithm.
END NEW TEXT END NEW TEXT
7. Implementation Status 7. Implementation Status
[[Note to RFC Editor: Please remove this section and the reference to [[Note to RFC Editor: Please remove this section and the reference to
[RFC6982] before publication.]] [RFC6982] before publication.]]
skipping to change at page 12, line 5 skipping to change at page 12, line 5
[I-D.ietf-mmusic-sdp-bundle-negotiation] [I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings, Holmberg, C., Alvestrand, H., and C. Jennings,
"Negotiating Media Multiplexing Using the Session "Negotiating Media Multiplexing Using the Session
Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle- Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle-
negotiation-23 (work in progress), July 2015. negotiation-23 (work in progress), July 2015.
Appendix A. Release notes Appendix A. Release notes
This section must be removed before publication as an RFC. This section must be removed before publication as an RFC.
A.1. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-05 and A.1. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-06 and
draft-ietf-avtcore-rfc5764-mux-fixes-05
o Addresses Colin's WGLC review comments
A.2. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-05 and
draft-ietf-avtcore-rfc5764-mux-fixes-04 draft-ietf-avtcore-rfc5764-mux-fixes-04
o Removed some remnants of the ordering from Section 6 o Removed some remnants of the ordering from Section 6
o Moved Terminology from Section 5 to Section 2 o Moved Terminology from Section 5 to Section 2
A.2. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-04 and A.3. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-04 and
draft-ietf-avtcore-rfc5764-mux-fixes-03 draft-ietf-avtcore-rfc5764-mux-fixes-03
o Removed Section on "Demultiplexing Algorithm Test Order" o Removed Section on "Demultiplexing Algorithm Test Order"
o Split the Introduction into separate sections o Split the Introduction into separate sections
A.3. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-03 and A.4. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-03 and
draft-ietf-avtcore-rfc5764-mux-fixes-02 draft-ietf-avtcore-rfc5764-mux-fixes-02
o Revert to the RFC 5389, as the stunbis reference was needed only o Revert to the RFC 5389, as the stunbis reference was needed only
for STUN over SCTP. for STUN over SCTP.
A.4. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-02 and A.5. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-02 and
draft-ietf-avtcore-rfc5764-mux-fixes-01 draft-ietf-avtcore-rfc5764-mux-fixes-01
o Remove any discussion about SCTP until a consensus emerges in o Remove any discussion about SCTP until a consensus emerges in
TRAM. TRAM.
A.5. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-01 and A.6. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-01 and
draft-ietf-avtcore-rfc5764-mux-fixes-00 draft-ietf-avtcore-rfc5764-mux-fixes-00
o Instead of allocating the values that are common on each registry, o Instead of allocating the values that are common on each registry,
the specification now only reserves them, giving the possibility the specification now only reserves them, giving the possibility
to allocate them in case muxing is irrelevant. to allocate them in case muxing is irrelevant.
o STUN range is now 0-3m with 2-3 being Designated Expert. o STUN range is now 0-3m with 2-3 being Designated Expert.
o TLS ContentType 0-19 and 64-255 are now reserved. o TLS ContentType 0-19 and 64-255 are now reserved.
skipping to change at page 13, line 7 skipping to change at page 13, line 12
TURN channels packets then the whole channel numbers are TURN channels packets then the whole channel numbers are
available. available.
o If not the prefix is between 64 and 79. o If not the prefix is between 64 and 79.
o First byte test order is now by incremental values, so failure is o First byte test order is now by incremental values, so failure is
deterministic. deterministic.
o Redraw the demuxing diagram. o Redraw the demuxing diagram.
A.6. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-00 and A.7. Modifications between draft-ietf-avtcore-rfc5764-mux-fixes-00 and
draft-petithuguenin-avtcore-rfc5764-mux-fixes-02 draft-petithuguenin-avtcore-rfc5764-mux-fixes-02
o Adoption by WG. o Adoption by WG.
o Add reference to STUNbis. o Add reference to STUNbis.
A.7. Modifications between draft-petithuguenin-avtcore-rfc5764-mux- A.8. Modifications between draft-petithuguenin-avtcore-rfc5764-mux-
fixes-00 and draft-petithuguenin-avtcore-rfc5764-mux-fixes-01 fixes-00 and draft-petithuguenin-avtcore-rfc5764-mux-fixes-01
o Change affiliation. o Change affiliation.
Authors' Addresses Authors' Addresses
Marc Petit-Huguenin Marc Petit-Huguenin
Impedance Mismatch Impedance Mismatch
Email: marc@petit-huguenin.org Email: marc@petit-huguenin.org
 End of changes. 22 change blocks. 
29 lines changed or deleted 36 lines changed or added

This html diff was produced by rfcdiff 1.43. The latest version is available from http://tools.ietf.org/tools/rfcdiff/