draft-ietf-avtcore-rfc7983bis-03.txt   draft-ietf-avtcore-rfc7983bis-04.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: November 11, 2022 C. Perkins Expires: November 13, 2022 C. Perkins
University of Glasgow University of Glasgow
11 May 2022 12 May 2022
Multiplexing Scheme Updates for QUIC Multiplexing Scheme Updates for QUIC
draft-ietf-avtcore-rfc7983bis-03.txt draft-ietf-avtcore-rfc7983bis-04.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 November 11, 2022. This Internet-Draft will expire on November 13, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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
skipping to change at page 3, line 15 skipping to change at page 3, line 15
1. Introduction 1. Introduction
"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)"
[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 [RFC9147], Session Traversal [RFC3550] receiver to demultiplex DTLS [RFC9147], Session Traversal
Utilities for NAT (STUN) [RFC8489], Secure Real-time Transport Utilities for NAT (STUN) [RFC8489], 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. This document updates [RFC7983] and [RFC5764] to also single port. This document updates [RFC7983] and [RFC5764] to also
allow QUIC [RFC9000] to also be multiplexed on the same port. The allow QUIC [RFC9000] to also be multiplexed on the same port.
scheme described in this document is compatible with QUIC version 2
[I-D.ietf-quic-v2].
The multiplexing scheme described in this document enables multiple The multiplexing scheme described in this document enables multiple
usage scenarios. Peer-to-peer QUIC in WebRTC scenarios, described in usage scenarios. Peer-to-peer QUIC in WebRTC scenarios, described in
[P2P-QUIC] [P2P-QUIC-TRIAL], uses RTP for transport of audio and [P2P-QUIC] [P2P-QUIC-TRIAL], uses RTP for transport of audio and
video along with QUIC for data exchange. For this use case, SRTP video along with QUIC for data exchange. For this use case, SRTP
[RFC3711] is keyed using DTLS-SRTP [RFC5764] and therefore SRTP/SRTCP [RFC3711] is keyed using DTLS-SRTP [RFC5764] and therefore SRTP/SRTCP
[RFC3550], STUN, TURN, DTLS and QUIC need to be multiplexed on the [RFC3550], STUN, TURN, DTLS and QUIC need to be multiplexed on the
same port. Were SRTP to be keyed using QUIC-SRTP, SRTP/SRTCP, STUN, same port. Were SRTP to be keyed using QUIC-SRTP, SRTP/SRTCP, STUN,
TURN and QUIC would need to be multiplexed on the same port. Where TURN and QUIC would need to be multiplexed on the same port. Where
QUIC is used for peer-to-peer transport of data as well as RTP QUIC is used for peer-to-peer transport of data as well as RTP
[I-D.engelbart-rtp-over-quic] STUN, TURN and QUIC need to be [I-D.engelbart-rtp-over-quic] STUN, TURN and QUIC need to be
multiplexed on the same port. multiplexed on the same port.
The scheme described in this document is compatible with QUIC version
2 [I-D.ietf-quic-v2]. However, it is not compatible with QUIC Bit
greasing, as defined in [I-D.ietf-quic-bit-grease]. Therefore, in
situations where multiplexing is desired, QUIC Bit greasing MUST NOT
be negotiated.
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
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Multiplexing of TURN Channels 2. Multiplexing of TURN Channels
TURN channels are an optimization where data packets are exchanged TURN channels are an optimization where data packets are exchanged
with a 4-byte prefix instead of the standard 36-byte STUN overhead with a 4-byte prefix instead of the standard 36-byte STUN overhead
(see Section 3.5 of [RFC8656]). [RFC7983] allocated the values from (see Section 3.5 of [RFC8656]). [RFC7983] allocated the values from
64 to 79 in order to allow TURN channels to be demultiplexed when the 64 to 79 in order to allow TURN channels to be demultiplexed when the
TURN Client does the channel binding request in combination with the TURN Client does the channel binding request in combination with the
demultiplexing scheme described in [RFC7983]. demultiplexing scheme described in [RFC7983].
As noted in [I-D.aboba-avtcore-quic-multiplexing], the first octet of When QUIC Bit greasing is not negotiated, the first octet of a QUIC
a QUIC short header packet falls in the range 64 to 127, thereby short header packet falls in the range 64 to 127, thereby overlapping
overlapping with the allocated range for TURN channels of 64 to 79. with the allocated range for TURN channels of 64 to 79.
The first octet of QUIC long header packets fall in the range 192 to Where QUIC Bit greating is not negotiated, the first octet of QUIC
255. Since QUIC long header packets preceed QUIC short header long header packets fall in the range 192 to 255. Since QUIC long
packets, if no packets with a first octet in the range of 192 to 255 header packets preceed QUIC short header packets, if no packets with
have been received, a packet whose first octet is in the range of 64 a first octet in the range of 192 to 255 have been received, a packet
to 79 can be demultplexed unambiguously as TURN Channel traffic. whose first octet is in the range of 64 to 79 can be demultplexed
Since WebRTC implementations supporting QUIC data exchange do not unambiguously as TURN Channel traffic. Since WebRTC implementations
utilize TURN Channels, once packets with a first octet in the range supporting QUIC data exchange do not utilize TURN Channels, once
of 192 to 255 have been received, a packet whose first octet is in packets with a first octet in the range of 192 to 255 have been
the range of 64 to 127 can be demultiplexed as QUIC traffic. received, a packet whose first octet is in the range of 64 to 127 can
be demultiplexed as QUIC traffic.
3. Updates to RFC 7983 3. Updates to RFC 7983
This document updates the text in Section 7 of [RFC7983] (which in This document updates the text in Section 7 of [RFC7983] (which in
turn updates [RFC5764]) as follows: turn updates [RFC5764]) as follows:
OLD TEXT OLD TEXT
The process for demultiplexing a packet is as follows. The receiver The process for demultiplexing a packet is as follows. The receiver
looks at the first byte of the packet. If the value of this byte is looks at the first byte of the packet. If the value of this byte is
skipping to change at page 5, line 40 skipping to change at page 5, line 40
| [64..79] -+--> forward to TURN Channel | [64..79] -+--> forward to TURN Channel
| [64..127] -+--> forward to QUIC | [64..127] -+--> forward to QUIC
| | (Short Header) | | (Short Header)
| [128..191] -+--> forward to RTP/RTCP | [128..191] -+--> forward to RTP/RTCP
| | | |
| [192..255] -+--> forward to QUIC | [192..255] -+--> forward to QUIC
+----------------+ (Long Header) +----------------+ (Long Header)
Figure 3: The receiver's packet demultiplexing algorithm. Figure 3: The receiver's packet demultiplexing algorithm.
Note: The demultiplexing of QUIC packets requires that QUIC Bit
greasing [I-D.ietf-quic-bit-grease] not be negotiated.
END NEW TEXT END NEW TEXT
4. Security Considerations 4. Security Considerations
The solution discussed in this document could potentially introduce The solution discussed in this document could potentially introduce
some additional security considerations beyond those detailed in some additional security considerations beyond those detailed in
[RFC7983]. Due to the additional logic required, if mis-implemented, [RFC7983]. Due to the additional logic required, if mis-implemented,
heuristics have the potential to mis-classify packets. heuristics have the potential to mis-classify packets.
When QUIC is used only for data exchange, the TLS-within-QUIC When QUIC is used only for data exchange, the TLS-within-QUIC
skipping to change at page 6, line 17 skipping to change at page 6, line 21
impacted by a vulnerability in the QUIC implementation. impacted by a vulnerability in the QUIC implementation.
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-bit-grease]
Thomson, M., "Greasing the QUIC Bit", draft-ietf-quic-bit-
grease (work in progress), November 10, 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 23 skipping to change at page 7, line 32
QUIC", RFC 9001, DOI 10.17487/RFC9001, May 2021, QUIC", RFC 9001, DOI 10.17487/RFC9001, May 2021,
<https://www.rfc-editor.org/info/rfc9001>. <https://www.rfc-editor.org/info/rfc9001>.
[RFC9147] Rescorla, E., Tschofenig, H., and N. Modadugu, "The [RFC9147] Rescorla, E., Tschofenig, H., and N. Modadugu, "The
Datagram Transport Layer Security (DTLS) Protocol Version Datagram Transport Layer Security (DTLS) Protocol Version
1.3", RFC 9147, DOI 10.17487/RFC9147, April 2022, 1.3", RFC 9147, DOI 10.17487/RFC9147, April 2022,
<https://www.rfc-editor.org/info/rfc9147>. <https://www.rfc-editor.org/info/rfc9147>.
6.2. Informative References 6.2. Informative References
[I-D.aboba-avtcore-quic-multiplexing]
Aboba, B., Thatcher, P. and C. Perkins, "QUIC
Multiplexing", draft-aboba-avtcore-quic-multiplexing-04
(work in progress), January 28, 2020.
[I-D.engelbart-rtp-over-quic] [I-D.engelbart-rtp-over-quic]
Ott, J. and M. Engelbart, "RTP over QUIC", draft-engelbart- Ott, J. and M. Engelbart, "RTP over QUIC", draft-engelbart-
rtp-over-quic-02 (work in progress), March 7, 2022. rtp-over-quic-02 (work in progress), March 7, 2022.
[I-D.ietf-quic-v2] [I-D.ietf-quic-v2]
Duke, M., "QUIC Version 2", draft-ietf-quic-v2 (work in Duke, M., "QUIC Version 2", draft-ietf-quic-v2 (work in
progress), April 28, 2022. progress), April 28, 2022.
[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,
 End of changes. 11 change blocks. 
24 lines changed or deleted 31 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/