draft-ietf-webtrans-overview-00.txt   draft-ietf-webtrans-overview-01.txt 
WEBTRANS V. Vasiliev WEBTRANS V. Vasiliev
Internet-Draft Google Internet-Draft Google
Intended status: Standards Track 17 April 2020 Intended status: Standards Track 18 October 2020
Expires: 19 October 2020 Expires: 21 April 2021
The WebTransport Protocol Framework The WebTransport Protocol Framework
draft-ietf-webtrans-overview-00 draft-ietf-webtrans-overview-01
Abstract Abstract
The WebTransport Protocol Framework enables clients constrained by The WebTransport Protocol Framework enables clients constrained by
the Web security model to communicate with a remote server using a the Web security model to communicate with a remote server using a
secure multiplexed transport. It consists of a set of individual secure multiplexed transport. It consists of a set of individual
protocols that are safe to expose to untrusted applications, combined protocols that are safe to expose to untrusted applications, combined
with a model that allows them to be used interchangeably. with a model that allows them to be used interchangeably.
This document defines the overall requirements on the protocols used This document defines the overall requirements on the protocols used
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 19 October 2020. This Internet-Draft will expire on 21 April 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 10, line 24 skipping to change at page 10, line 24
9. References 9. References
9.1. Normative References 9.1. Normative References
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC6454] Barth, A., "The Web Origin Concept", RFC 6454,
DOI 10.17487/RFC6454, December 2011,
<https://www.rfc-editor.org/info/rfc6454>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC6454] Barth, A., "The Web Origin Concept", RFC 6454,
DOI 10.17487/RFC6454, December 2011,
<https://www.rfc-editor.org/info/rfc6454>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
9.2. Informative References 9.2. Informative References
[CSP] W3C, "Content Security Policy Level 3", April 2020, [CSP] W3C, "Content Security Policy Level 3", October 2020,
<https://www.w3.org/TR/CSP/>. <https://www.w3.org/TR/CSP/>.
[RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", [I-D.ietf-quic-http]
RFC 6455, DOI 10.17487/RFC6455, December 2011, Bishop, M., "Hypertext Transfer Protocol Version 3
<https://www.rfc-editor.org/info/rfc6455>. (HTTP/3)", Work in Progress, Internet-Draft, draft-ietf-
quic-http-31, 24 September 2020, <http://www.ietf.org/
internet-drafts/draft-ietf-quic-http-31.txt>.
[I-D.ietf-quic-recovery]
Iyengar, J. and I. Swett, "QUIC Loss Detection and
Congestion Control", Work in Progress, Internet-Draft,
draft-ietf-quic-recovery-31, 24 September 2020,
<http://www.ietf.org/internet-drafts/draft-ietf-quic-
recovery-31.txt>.
[I-D.ietf-quic-transport]
Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed
and Secure Transport", Work in Progress, Internet-Draft,
draft-ietf-quic-transport-31, 24 September 2020,
<http://www.ietf.org/internet-drafts/draft-ietf-quic-
transport-31.txt>.
[I-D.ietf-rtcweb-data-channel] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
Channels", Work in Progress, Internet-Draft, draft-ietf- Channels", Work in Progress, Internet-Draft, draft-ietf-
rtcweb-data-channel-13, 4 January 2015, rtcweb-data-channel-13, 4 January 2015,
<http://www.ietf.org/internet-drafts/draft-ietf-rtcweb- <http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-
data-channel-13.txt>. data-channel-13.txt>.
[I-D.ietf-quic-http] [I-D.ietf-tls-dtls13]
Bishop, M., "Hypertext Transfer Protocol Version 3 Rescorla, E., Tschofenig, H., and N. Modadugu, "The
(HTTP/3)", Work in Progress, Internet-Draft, draft-ietf- Datagram Transport Layer Security (DTLS) Protocol Version
quic-http-23, 12 September 2019, <http://www.ietf.org/ 1.3", Work in Progress, Internet-Draft, draft-ietf-tls-
internet-drafts/draft-ietf-quic-http-23.txt>. dtls13-38, 29 May 2020, <http://www.ietf.org/internet-
drafts/draft-ietf-tls-dtls13-38.txt>.
[RFC8441] McManus, P., "Bootstrapping WebSockets with HTTP/2",
RFC 8441, DOI 10.17487/RFC8441, September 2018,
<https://www.rfc-editor.org/info/rfc8441>.
[I-D.pauly-quic-datagram] [I-D.pauly-quic-datagram]
Pauly, T., Kinnear, E., and D. Schinazi, "An Unreliable Pauly, T., Kinnear, E., and D. Schinazi, "An Unreliable
Datagram Extension to QUIC", Work in Progress, Internet- Datagram Extension to QUIC", Work in Progress, Internet-
Draft, draft-pauly-quic-datagram-04, 22 October 2019, Draft, draft-pauly-quic-datagram-05, 4 November 2019,
<http://www.ietf.org/internet-drafts/draft-pauly-quic- <http://www.ietf.org/internet-drafts/draft-pauly-quic-
datagram-04.txt>. datagram-05.txt>.
[I-D.ietf-tls-dtls13]
Rescorla, E., Tschofenig, H., and N. Modadugu, "The
Datagram Transport Layer Security (DTLS) Protocol Version
1.3", Work in Progress, Internet-Draft, draft-ietf-tls-
dtls13-33, 11 October 2019, <http://www.ietf.org/internet-
drafts/draft-ietf-tls-dtls13-33.txt>.
[RFC7675] Perumal, M., Wing, D., Ravindranath, R., Reddy, T., and M. [RFC0896] Nagle, J., "Congestion Control in IP/TCP Internetworks",
Thomson, "Session Traversal Utilities for NAT (STUN) Usage RFC 896, DOI 10.17487/RFC0896, January 1984,
for Consent Freshness", RFC 7675, DOI 10.17487/RFC7675, <https://www.rfc-editor.org/info/rfc896>.
October 2015, <https://www.rfc-editor.org/info/rfc7675>.
[RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion [RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion
Control", RFC 5681, DOI 10.17487/RFC5681, September 2009, Control", RFC 5681, DOI 10.17487/RFC5681, September 2009,
<https://www.rfc-editor.org/info/rfc5681>. <https://www.rfc-editor.org/info/rfc5681>.
[I-D.ietf-quic-recovery] [RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol",
Iyengar, J. and I. Swett, "QUIC Loss Detection and RFC 6455, DOI 10.17487/RFC6455, December 2011,
Congestion Control", Work in Progress, Internet-Draft, <https://www.rfc-editor.org/info/rfc6455>.
draft-ietf-quic-recovery-23, 11 September 2019,
<http://www.ietf.org/internet-drafts/draft-ietf-quic-
recovery-23.txt>.
[I-D.ietf-quic-transport] [RFC7675] Perumal, M., Wing, D., Ravindranath, R., Reddy, T., and M.
Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed Thomson, "Session Traversal Utilities for NAT (STUN) Usage
and Secure Transport", Work in Progress, Internet-Draft, for Consent Freshness", RFC 7675, DOI 10.17487/RFC7675,
draft-ietf-quic-transport-23, 11 September 2019, October 2015, <https://www.rfc-editor.org/info/rfc7675>.
<http://www.ietf.org/internet-drafts/draft-ietf-quic-
transport-23.txt>.
[RFC0896] Nagle, J., "Congestion Control in IP/TCP Internetworks", [RFC8441] McManus, P., "Bootstrapping WebSockets with HTTP/2",
RFC 896, DOI 10.17487/RFC0896, January 1984, RFC 8441, DOI 10.17487/RFC8441, September 2018,
<https://www.rfc-editor.org/info/rfc896>. <https://www.rfc-editor.org/info/rfc8441>.
Author's Address Author's Address
Victor Vasiliev Victor Vasiliev
Google Google
Email: vasilvv@google.com Email: vasilvv@google.com
 End of changes. 14 change blocks. 
54 lines changed or deleted 54 lines changed or added

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