draft-aboba-avtcore-quic-multiplexing-03.txt   draft-aboba-avtcore-quic-multiplexing-04.txt 
AVTCORE Working Group B. Aboba AVTCORE Working Group B. Aboba
INTERNET-DRAFT Microsoft Corporation INTERNET-DRAFT Microsoft Corporation
Category: Informational P. Thatcher Category: Informational P. Thatcher
Expires: July 23, 2019 Google Expires: July 28, 2020 Google
C. Perkins C. Perkins
University of Glasgow University of Glasgow
23 January 2019 28 January 2020
QUIC Multiplexing QUIC Multiplexing
draft-aboba-avtcore-quic-multiplexing-03.txt draft-aboba-avtcore-quic-multiplexing-04.txt
Abstract Abstract
If QUIC is to be used in a peer-to-peer manner, with NAT traversal, If QUIC is to be used for peer-to-peer data transport with NAT
then it is necessary to be able to demultiplex QUIC and other traversal, then it is necessary to be able to demultiplex QUIC and
protocols used in WebRTC on a single UDP port. This memo discusses other protocols used in WebRTC on a single UDP port. This memo
options for demultiplexing. discusses a proposed scheme for demultiplexing.
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 23, 2019. This Internet-Draft will expire on 28 July 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Subsequent changes . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Informative references . . . . . . . . . . . . . . . . . . 5 5.1. Informative references . . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 7 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
QUIC [I-D.ietf-quic-transport] is a new network transport protocol. QUIC [I-D.ietf-quic-transport] is a new network transport protocol.
While it is initially intended as a replacement for TCP in order to While it is initially intended as a replacement for TCP in order to
better support HTTP/2 [RFC7540] it should eventually be useful as a better support HTTP/2 [RFC7540], with the introduction of datagram
general purpose transport. HTTP is an asymmetric client-server support [I-D.pauly-quic-datagram] it will also support unreliable as
protocol, but other uses of QUIC might operate in a peer-to-peer well as reliable transport. HTTP is an asymmetric client-server
manner and so will need effective NAT traversal using ICE [RFC5245], protocol, but other uses of QUIC support peer-to-peer operation and
which which makes use of STUN [RFC5389] and TURN [RFC5766] to so will need effective NAT traversal using ICE [RFC5245], which which
discover NAT bindings. Therefore for QUIC to be utilized for peer- makes use of STUN [RFC5389] and TURN [RFC5766] to discover NAT
to-peer data transport, QUIC and STUN must be able to multiplex on bindings. Therefore for QUIC to be utilized for peer-to-peer data
the same port. transport, QUIC and STUN must be able to multiplex on the same port.
In a WebRTC scenario where RTP is used to transport audio and video In a WebRTC scenario where RTP is used to transport audio and video
and QUIC is used for data exchange, SRTP [RFC3711] is keyed using and QUIC is used for data exchange, SRTP [RFC3711] is keyed using
DTLS-SRTP [RFC5764] and therefore SRTP/SRTCP [RFC3550], STUN, TURN, DTLS-SRTP [RFC5764] and therefore SRTP/SRTCP [RFC3550], STUN, TURN,
DTLS [RFC6347] and QUIC will need to be multiplexed on the same port. DTLS [RFC6347] and QUIC will need to be multiplexed on the same port.
Within the W3C, a Javascript API for the use of QUIC for peer-to-peer Within the W3C, a Javascript API for the use of QUIC for peer-to-peer
data exchange [WEBRTC-QUIC] is under development within the ORTC data exchange [WEBRTC-QUIC] is under development within the ORTC
Community Group. Community Group, and an Origin Trial [WEBRTC-QUIC-TRIAL] implementing
an early version of this API shipped in the Chrome and Edge browsers.
Due to lack of demultiplexing support, the Origin Trial could only
support peer-to-peer use of QUIC over a standalone ICE transport, as
defined in [WEBRTC-ICE].
As noted in [RFC7983] Figure 3, protocol demultiplexing currently As noted in [RFC7983] Figure 3, protocol demultiplexing currently
relies upon differentiation based on the first octet, as follows: relies upon differentiation based on the first octet, as follows:
+----------------+ +----------------+
| [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
| | | |
| [128..191] -+--> forward to RTP/RTCP | [128..191] -+--> forward to RTP/RTCP
+----------------+ +----------------+
Figure 1: RFC 7983 packet demultiplexing algorithm. Figure 1: RFC 7983 packet demultiplexing algorithm.
As noted by Colin Perkins and Lars Eggert in [QUIC-Issue] this As noted by Colin Perkins and Lars Eggert in [QUIC-Issue][QUIC-MULTI]
created a potential conflict with the design of the QUIC headers this created a potential conflict with the design of the QUIC headers
described in versions of [I-D.ietf-quic-transport] prior to -08. described in versions of [I-D.ietf-quic-transport] prior to -08.
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. Solution 2. Solution
At IETF 100, Colin Perkins presented a demultiplexing proposal [QUIC- As of draft 18, the QUIC Long Header packet type field defined in [I-
MULTI]. The proposal which was subsequently proposed as a Pull D.ietf-quic-transport] Section 17.2 appears as follows:
Request to the QUIC Transport specification and merged in draft-ietf-
quic-transport-08, involved renumbering of the QUIC long header
packet type field as well as inverting the sense of the "C" bit in
the short header packet.
The demultiplexing algorithm resulting from the changes appears as
follows:
+----------------+
| [0..3] -+--> forward to STUN
| |
| [16..19] -+--> forward to ZRTP
| |
packet --> | [20..63] -+--> forward to DTLS
| |
| [64..79] -+--> forward to TURN Channel
| [64..127] -+--> forward to QUIC (Short Header)
| |
| [128..191] -+--> forward to RTP/RTCP
| [250..255] +--> forward to QUIC (Long Header)
+----------------+
Figure 2: Revised packet demultiplexing algorithm.
Note that while the above diagram has a potential conflict between
packets sent in TURN Channels and the QUIC short header, this
conflict is not considered serious for WebRTC where TURN Channels are
rarely used.
2.1. Subsequent changes
Since then, additional changes have been made to the QUIC transport
headers. As of draft 18, the QUIC Long Header packet type field
defined in [I-D.ietf-quic-transport] Section 17.2 appears as follows:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|1|1|T T|X|X|X|X| |1|1|T T|X|X|X|X|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Where: Where:
T = Long Packet Type (0x0 - 0x3) T = Long Packet Type (0x0 - 0x3)
X = Type-Specific Bits. X = Type-Specific Bits.
skipping to change at page 5, line 35 skipping to change at page 4, line 42
| | | |
| [64..79] -+--> forward to TURN Channel | [64..79] -+--> forward to TURN Channel
| [64..127] -+--> forward to QUIC (Short Header) | [64..127] -+--> forward to QUIC (Short Header)
| | | |
| [128..191] -+--> forward to RTP/RTCP | [128..191] -+--> forward to RTP/RTCP
| [192..255] +--> forward to QUIC (Long Header) | [192..255] +--> forward to QUIC (Long Header)
+----------------+ +----------------+
Figure 3: Packet demultiplexing algorithm in Draft 18. Figure 3: Packet demultiplexing algorithm in Draft 18.
Note that while the above diagram has a potential conflict between
packets sent in TURN Channels and the QUIC short header, this
conflict is not considered serious for WebRTC where TURN Channels are
rarely used.
3. Security Considerations 3. Security Considerations
The solutions 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]. [RFC7983].
Due to the additional logic required, if mis-implemented, heuristics Due to the additional logic required, if mis-implemented, heuristics
have the potential to mis-classify packets. have the potential to mis-classify packets.
When QUIC is used for only for data exchange, the TLS-within-QUIC When QUIC is used for only for data exchange, the TLS-within-QUIC
exchange [I-D.ietf-quic-tls] derives keys used solely to protect the exchange [I-D.ietf-quic-tls] derives keys used solely to protect the
QUIC data packets. If properly implemented, this should not affect QUIC data packets. If properly implemented, this should not affect
the transport of SRTP nor the derivation of SRTP keys via DTLS-SRTP, the transport of SRTP nor the derivation of SRTP keys via DTLS-SRTP,
skipping to change at page 6, line 15 skipping to change at page 5, line 25
4. IANA Considerations 4. IANA Considerations
This document does not require actions by IANA. This document does not require actions by IANA.
5. References 5. References
5.1. Informative References 5.1. Informative 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-18 (work in (TLS) to Secure QUIC", draft-ietf-quic-tls-25 (work in
progress), January 23, 2019. progress), January 22, 2020.
[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-18 (work and Secure Transport", draft-ietf-quic-transport-25 (work
in progress), January 23, 2019. in progress), January 22, 2020.
[I-D.pauly-quic-datagram]
Pauly, T., Kinnear, E. and D. Schinazi, "An Unreliable
Datagram Extension to QUIC", draft-pauly-quic-datagram-05
(work in progress), November 04, 2019.
[QUIC-Issue] Perkins, C., "QUIC header format/demultiplexing", [QUIC-Issue] Perkins, C., "QUIC header format/demultiplexing",
https://github.com/quicwg/base-drafts/issues/426, March, https://github.com/quicwg/base-drafts/issues/426, March,
2017. 2017.
[QUIC-MULTI] Perkins, C., "QUIC Multiplexing and Peer-to-Peer", [QUIC-MULTI] Perkins, C., "QUIC Multiplexing and Peer-to-Peer",
presentation to IETF AVTCORE WG at IETF 100, presentation to IETF AVTCORE WG at IETF 100,
<https://datatracker.ietf.org/meeting/100/materials/ <https://datatracker.ietf.org/meeting/100/materials/
slides-100-avtcore-quic-multiplexing-with-rtp-03>, November slides-100-avtcore-quic-multiplexing-with-rtp-03>, November
2017. 2017.
skipping to change at page 7, line 37 skipping to change at page 7, line 5
Transfer Protocol Version 2 (HTTP/2)", RFC 7540, DOI Transfer Protocol Version 2 (HTTP/2)", RFC 7540, DOI
10.17487/RFC7540, May 2015, <https://www.rfc- 10.17487/RFC7540, May 2015, <https://www.rfc-
editor.org/info/rfc7540>. editor.org/info/rfc7540>.
[RFC7983] Petit-Huguenin, M. and G. Salgueiro, "Multiplexing Scheme [RFC7983] Petit-Huguenin, M. and G. Salgueiro, "Multiplexing Scheme
Updates for Secure Real-time Transport Protocol (SRTP) Updates for Secure Real-time Transport Protocol (SRTP)
Extension for Datagram Transport Layer Security (DTLS)", Extension for Datagram Transport Layer Security (DTLS)",
RFC 7983, DOI 10.17487/RFC7983, September 2016, RFC 7983, DOI 10.17487/RFC7983, September 2016,
<https://www.rfc-editor.org/info/rfc7983>. <https://www.rfc-editor.org/info/rfc7983>.
[WEBRTC-ICE] Thatcher, P. and B. Aboba, "ICE Transport Extensions for
WebRTC", W3C Editor's Draft (work in progress), January
2020, <https://w3c.github.io/webrtc-ice>
[WEBRTC-QUIC] [WEBRTC-QUIC]
Thatcher, P. and B. Aboba, "QUIC API For WebRTC", W3C Thatcher, P. and B. Aboba, "QUIC API For Peer-to-Peer
Editor's Draft (work in progress), October 2018, Connections", W3C Community Group Draft (work in progress),
<https://w3c.github.io/webrtc-quic> January 2020, <https://w3c.github.io/webrtc-quic>
[WEBRTC-QUIC-TRIAL]
Hampson, S., "RTCQuicTransport Coming to an Origin Trial
Near You (Chrome 73)", January 2019,
<https://developers.google.com/web/updates/
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
to potential solutions. to potential solutions.
Authors' Addresses Authors' Addresses
 End of changes. 18 change blocks. 
66 lines changed or deleted 55 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/