draft-ietf-avtcore-rfc7983bis-00.txt   draft-ietf-avtcore-rfc7983bis-01.txt 
AVTCORE Working Group B. Aboba AVTCORE Working Group B. Aboba
INTERNET-DRAFT Microsoft Corporation INTERNET-DRAFT Microsoft Corporation
Updates: 7983, 5764 G. Salgueiro Updates: 7983, 5764 G. Salgueiro
Category: Standards Track Cisco Systems Category: Standards Track Cisco Systems
Expires: May 21, 2021 C. Perkins Expires: November 25, 2021 C. Perkins
University of Glasgow University of Glasgow
21 November 2020 23 May 2021
Multiplexing Scheme Updates for QUIC Multiplexing Scheme Updates for QUIC
draft-ietf-avtcore-rfc7983bis-00.txt draft-ietf-avtcore-rfc7983bis-01.txt
Abstract Abstract
This document defines how QUIC, Datagram Transport Layer Security This document defines how QUIC, Datagram Transport Layer Security
(DTLS), Real-time Transport Protocol (RTP), RTP Control Protocol (DTLS), Real-time Transport Protocol (RTP), RTP Control Protocol
(RTCP), Session Traversal Utilities for NAT (STUN), Traversal Using (RTCP), Session Traversal Utilities for NAT (STUN), Traversal Using
Relays around NAT (TURN), and ZRTP packets are multiplexed on a Relays around NAT (TURN), and ZRTP packets are multiplexed on a
single receiving socket. single receiving socket.
This document updates RFC 7983 and RFC 5764. This document updates RFC 7983 and RFC 5764.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 May 21, 2021. This Internet-Draft will expire on November 25, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 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
skipping to change at page 3, line 18 skipping to change at page 3, line 18
(SRTP) Extension for Datagram Transport Layer Security (DTLS)" (SRTP) Extension for Datagram Transport Layer Security (DTLS)"
[RFC7983] defines a scheme for a Real-time Transport Protocol (RTP) [RFC7983] defines a scheme for a Real-time Transport Protocol (RTP)
[RFC3550] receiver to demultiplex DTLS [RFC6347], Session Traversal [RFC3550] receiver to demultiplex DTLS [RFC6347], Session Traversal
Utilities for NAT (STUN) [RFC5389], Secure Real-time Transport Utilities for NAT (STUN) [RFC5389], Secure Real-time Transport
Protocol (SRTP) / Secure Real-time Transport Control Protocol (SRTCP) Protocol (SRTP) / Secure Real-time Transport Control Protocol (SRTCP)
[RFC3711], ZRTP [RFC6189] and TURN Channel packets arriving on a [RFC3711], ZRTP [RFC6189] and TURN Channel packets arriving on a
single port. single port.
This document updates [RFC7983] and [RFC5764] to also allow QUIC [I- This document updates [RFC7983] and [RFC5764] to also allow QUIC [I-
D.ietf-quic-transport] to be multiplexed on the same port. For peer- D.ietf-quic-transport] to be multiplexed on the same port. For peer-
to-peer operation in WebRTC scenarios as described in [WEBRTC- to-peer operation in WebRTC scenarios as described in [P2P-QUIC][P2P-
QUIC][WEBRTC-QUIC-TRIAL], RTP is used to transport audio and video QUIC-TRIAL], RTP is used to transport audio and video and QUIC is
and QUIC is used for data exchange, SRTP [RFC3711] is keyed using used for data exchange, SRTP [RFC3711] is keyed using DTLS-SRTP
DTLS-SRTP [RFC5764] and therefore SRTP/SRTCP [RFC3550], STUN, TURN, [RFC5764] and therefore SRTP/SRTCP [RFC3550], STUN, TURN, DTLS
DTLS [RFC6347] and QUIC need to be multiplexed on the same port. [RFC6347] and QUIC need to be multiplexed on the same port.
Since new versions of QUIC are allowed to change aspects of the wire Since new versions of QUIC are allowed to change aspects of the wire
image, there is no guarantee that future versions of QUIC beyond image, there is no guarantee that future versions of QUIC beyond
version 1 will adhere to the multiplexing scheme described in this version 1 will adhere to the multiplexing scheme described in this
document. document.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 6, line 15 skipping to change at page 6, line 15
5. IANA Considerations 5. IANA Considerations
This document does not require actions by IANA. This document does not require actions by IANA.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-quic-tls] [I-D.ietf-quic-tls]
Thomson, M. and S. Turner, "Using Transport Layer Security Thomson, M. and S. Turner, "Using Transport Layer Security
(TLS) to Secure QUIC", draft-ietf-quic-tls-32 (work in (TLS) to Secure QUIC", draft-ietf-quic-tls-34 (work in
progress), October 20, 2020. progress), January 15, 2021.
[I-D.ietf-quic-transport] [I-D.ietf-quic-transport]
Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed
and Secure Transport", draft-ietf-quic-transport-32 (work and Secure Transport", draft-ietf-quic-transport-34 (work
in progress), October 20, 2020. in progress), January 15, 2021.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI Requirement Levels", BCP 14, RFC 2119, DOI
10.17487/RFC2119, March 1997, <http://www.rfc- 10.17487/RFC2119, March 1997, <http://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, July Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, July
2003, <http://www.rfc-editor.org/info/rfc3550>. 2003, <http://www.rfc-editor.org/info/rfc3550>.
skipping to change at page 7, line 28 skipping to change at page 7, line 28
[RFC6189] Zimmermann, P., Johnston, A., Ed., and J. Callas, "ZRTP: [RFC6189] Zimmermann, P., Johnston, A., Ed., and J. Callas, "ZRTP:
Media Path Key Agreement for Unicast Secure RTP", RFC 6189, Media Path Key Agreement for Unicast Secure RTP", RFC 6189,
DOI 10.17487/RFC6189, April 2011, <http://www.rfc- DOI 10.17487/RFC6189, April 2011, <http://www.rfc-
editor.org/info/rfc6189>. editor.org/info/rfc6189>.
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347, Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
January 2012, <http://www.rfc-editor.org/info/rfc6347>. January 2012, <http://www.rfc-editor.org/info/rfc6347>.
[WEBRTC-QUIC] [P2P-QUIC] Thatcher, P., Aboba, B. and R. Raymond, "QUIC API For Peer-
Thatcher, P. and B. Aboba, "QUIC API For Peer-to-Peer to-Peer Connections", W3C ORTC Community Group Draft (work
Connections", W3C Community Group Draft (work in progress), in progress), 23 May 2021, <https://github.com/w3c/p2p-
January 2020, <https://w3c.github.io/webrtc-quic> webtransport>
[WEBRTC-QUIC-TRIAL] [P2P-QUIC-TRIAL]
Hampson, S., "RTCQuicTransport Coming to an Origin Trial Hampson, S., "RTCQuicTransport Coming to an Origin Trial
Near You (Chrome 73)", January 2019, Near You (Chrome 73)", January 2019,
<https://developers.google.com/web/updates/ <https://developers.google.com/web/updates/
2019/01/rtcquictransport-api> 2019/01/rtcquictransport-api>
Acknowledgments Acknowledgments
We would like to thank Martin Thomson, Roni Even and other We would like to thank Martin Thomson, Roni Even and other
participants in the IETF QUIC and AVTCORE working groups for their participants in the IETF QUIC and AVTCORE working groups for their
discussion of the QUIC multiplexing issue, and their input relating discussion of the QUIC multiplexing issue, and their input relating
 End of changes. 10 change blocks. 
19 lines changed or deleted 19 lines changed or added

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