draft-ietf-avtcore-rfc7983bis-04.txt   draft-ietf-avtcore-rfc7983bis-05.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 13, 2022 C. Perkins Expires: December 31, 2022 C. Perkins
University of Glasgow University of Glasgow
12 May 2022 30 June 2022
Multiplexing Scheme Updates for QUIC Multiplexing Scheme Updates for QUIC
draft-ietf-avtcore-rfc7983bis-04.txt draft-ietf-avtcore-rfc7983bis-05.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 13, 2022. This Internet-Draft will expire on December 31, 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. allow QUIC [RFC9000] to be multiplexed on the same port.
The multiplexing scheme described in this document enables multiple The multiplexing scheme described in this document supports multiple
usage scenarios. Peer-to-peer QUIC in WebRTC scenarios, described in use cases. 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], transports audio and video over SRTP,
video along with QUIC for data exchange. For this use case, SRTP alongside QUIC, used 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/RTCP
[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 While the scheme described in this document is compatible with QUIC
2 [I-D.ietf-quic-v2]. However, it is not compatible with QUIC Bit version 2 [I-D.ietf-quic-v2], it is not compatible with QUIC bit
greasing, as defined in [I-D.ietf-quic-bit-grease]. Therefore, in greasing [I-D.ietf-quic-bit-grease]. As a result, endpoints that
situations where multiplexing is desired, QUIC Bit greasing MUST NOT wish to use multiplexing on their socket MUST NOT send the
be negotiated. grease_quic_bit transport parameter.
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] allocates 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].
When QUIC Bit greasing is not negotiated, the first octet of a QUIC In the absence of QUIC bit greasing, the first octet of a QUIC packet
short header packet falls in the range 64 to 127, thereby overlapping (e.g. a short header packet in QUIC v1 or v2) may fall in the range
with the allocated range for TURN channels of 64 to 79. 64 to 127, thereby overlapping with the allocated range for TURN
channels of 64 to 79. However, in practice this overlap does not
represent a problem. TURN channel packets will only be received from
a TURN server to which TURN allocation and channel-binding requests
have been sent. Therefore a TURN client receiving packets from the
source IP address and port of a TURN server only needs to
disambiguate STUN (i.e. regular TURN) packets from TURN channel
packets; (S)RTP, (S)RTCP, ZRTP, DTLS or QUIC packets will not be sent
from a source IP address and port that had previously responded to
TURN allocation or channel-binding requests.
Where QUIC Bit greating is not negotiated, the first octet of QUIC As a result, if the source IP address and port of a packet does not
long header packets fall in the range 192 to 255. Since QUIC long match that of a responding TURN server, a packet with a first octet
header packets preceed QUIC short header packets, if no packets with of 64 to 127 can be unambiguously demultiplexed as QUIC.
a first octet in the range of 192 to 255 have been received, a packet
whose first octet is in the range of 64 to 79 can be demultplexed
unambiguously as TURN Channel traffic. Since WebRTC implementations
supporting QUIC data exchange do not utilize TURN Channels, once
packets with a first octet in the range of 192 to 255 have been
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 13 skipping to change at page 5, line 13
END OLD TEXT END OLD TEXT
NEW TEXT NEW 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
in between 0 and 3 (inclusive), then the packet is STUN. If the in between 0 and 3 (inclusive), then the packet is STUN. If the
value is between 16 and 19 (inclusive), then the packet is ZRTP. If value is between 16 and 19 (inclusive), then the packet is ZRTP. If
the value is between 20 and 63 (inclusive), then the packet is DTLS. the value is between 20 and 63 (inclusive), then the packet is DTLS.
If the value is in between 128 and 191 (inclusive) then the packet is If the value is in between 128 and 191 (inclusive) then the packet is
RTP (or RTCP, if both RTCP and RTP are being multiplexed over the RTP (or RTCP, if both RTCP and RTP are being multiplexed over the
same destination port). If the value is between 80 and 127 or between same destination port). If the value is between 64 and 79 inclusive
192 and 255 (inclusive) then the packet is QUIC. If the value is and has a source IP address and port of a responding TURN Server,
between 64 and 79 inclusive, then if a packet has been previously then it is TURN Channel. If the value is between 64 and 127 inclusive
forwarded that is in the range of 192 and 255, then the packet is and the source IP address and port does not correspond to a TURN
QUIC, otherwise it is TURN Channel. Server, or if the value is between 192 and 255 inclusive, then it is
QUIC.
If the value does not match any known range, then the packet MUST be If the value does not match any known range, then the packet MUST be
dropped and an alert MAY be logged. This process is summarized in dropped and an alert MAY be logged. This process is summarized in
Figure 3. Figure 3.
+----------------+ +----------------+
| [0..3] -+--> forward to STUN | [0..3] -+--> forward to STUN
| | | |
| [16..19] -+--> forward to ZRTP | [16..19] -+--> forward to ZRTP
| | | |
packet --> | [20..63] -+--> forward to DTLS packet --> | [20..63] -+--> forward to DTLS
| | | |
| [64..79] -+--> forward to TURN Channel | [64..79] -+--> forward to TURN Channel
| [64..127] -+--> forward to QUIC | [64..127] -+--> forward to QUIC
| | (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) +----------------+
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 Note: Endpoints that wish to demultiplex QUIC MUST NOT send the
greasing [I-D.ietf-quic-bit-grease] not be negotiated. grease_quic_bit transport parameter, described in
[I-D.ietf-quic-bit-grease].
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.
skipping to change at page 8, line 9 skipping to change at page 8, line 9
webtransport> webtransport>
[P2P-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, Jonathan Lennox and
participants in the IETF QUIC and AVTCORE working groups for their other participants in the IETF QUIC and AVTCORE working groups for
discussion of the QUIC multiplexing issue, and their input relating their discussion of the QUIC multiplexing issue, and their input
to potential solutions. relating to potential solutions.
Authors' Addresses Authors' Addresses
Bernard Aboba Bernard Aboba
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
USA USA
Email: bernard.aboba@gmail.com Email: bernard.aboba@gmail.com
 End of changes. 16 change blocks. 
42 lines changed or deleted 46 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/