draft-ietf-quic-transport-34.txt		draft-ietf-quic-transport-latest.txt
	QUIC Working Group J. Iyengar, Ed.		QUIC Working Group J. Iyengar, Ed.
	Internet-Draft Fastly		Internet-Draft Fastly
	Intended status: Standards Track M. Thomson, Ed.		Intended status: Standards Track M. Thomson, Ed.
	Expires: July 19, 2021 Mozilla		Expires: July 24, 2021 Mozilla
	January 15, 2021		January 20, 2021
	QUIC: A UDP-Based Multiplexed and Secure Transport		QUIC: A UDP-Based Multiplexed and Secure Transport
	draft-ietf-quic-transport-34		draft-ietf-quic-transport-latest
	Abstract		Abstract
	This document defines the core of the QUIC transport protocol. QUIC		This document defines the core of the QUIC transport protocol. QUIC
	provides applications with flow-controlled streams for structured		provides applications with flow-controlled streams for structured
	communication, low-latency connection establishment, and network path		communication, low-latency connection establishment, and network path
	migration. QUIC includes security measures that ensure		migration. QUIC includes security measures that ensure
	confidentiality, integrity, and availability in a range of deployment		confidentiality, integrity, and availability in a range of deployment
	circumstances. Accompanying documents describe the integration of		circumstances. Accompanying documents describe the integration of
	TLS for key negotiation, loss detection, and an exemplary congestion		TLS for key negotiation, loss detection, and an exemplary congestion
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	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 July 19, 2021.		This Internet-Draft will expire on July 24, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 11, line 32 ¶		skipping to change at page 11, line 32 ¶
	fixed value, optionality, or repetitions. Individual fields use the		fixed value, optionality, or repetitions. Individual fields use the
	following notational conventions, with all lengths in bits:		following notational conventions, with all lengths in bits:
	x (A): Indicates that x is A bits long		x (A): Indicates that x is A bits long
	x (i): Indicates that x holds an integer value using the variable-		x (i): Indicates that x holds an integer value using the variable-
	length encoding in Section 16		length encoding in Section 16
	x (A..B): Indicates that x can be any length from A to B; A can be		x (A..B): Indicates that x can be any length from A to B; A can be
	omitted to indicate a minimum of zero bits and B can be omitted to		omitted to indicate a minimum of zero bits and B can be omitted to
	indicate no set upper limit; values in this format always end on		indicate no set upper limit; values in this format always end on a
	an byte boundary		byte boundary
	x (L) = C: Indicates that x has a fixed value of C with the length		x (L) = C: Indicates that x has a fixed value of C with the length
	described by L, which can use any of the three length forms above		described by L, which can use any of the three length forms above
	x (L) = C..D: Indicates that x has a value in the range from C to D,		x (L) = C..D: Indicates that x has a value in the range from C to D,
	inclusive, with the length described by L, as above		inclusive, with the length described by L, as above
	[x (L)]: Indicates that x is optional (and has length of L)		[x (L)]: Indicates that x is optional (and has length of L)
	x (L) ...: Indicates that zero or more instances of x are present		x (L) ...: Indicates that zero or more instances of x are present
	skipping to change at page 174, line 7 ¶		skipping to change at page 174, line 7 ¶
	Cotton, M., "Early IANA Allocation of Standards Track Code		Cotton, M., "Early IANA Allocation of Standards Track Code
	Points", BCP 100, RFC 7120, DOI 10.17487/RFC7120, January		Points", BCP 100, RFC 7120, DOI 10.17487/RFC7120, January
	2014, <https://www.rfc-editor.org/info/rfc7120>.		2014, <https://www.rfc-editor.org/info/rfc7120>.
	[IPv4] Postel, J., "Internet Protocol", STD 5, RFC 791,		[IPv4] Postel, J., "Internet Protocol", STD 5, RFC 791,
	DOI 10.17487/RFC0791, September 1981,		DOI 10.17487/RFC0791, September 1981,
	<https://www.rfc-editor.org/info/rfc791>.		<https://www.rfc-editor.org/info/rfc791>.
	[QUIC-INVARIANTS]		[QUIC-INVARIANTS]
	Thomson, M., "Version-Independent Properties of QUIC",		Thomson, M., "Version-Independent Properties of QUIC",
	draft-ietf-quic-invariants-13 (work in progress), January		draft-ietf-quic-invariants-latest (work in progress).
	2021.
	[QUIC-RECOVERY]		[QUIC-RECOVERY]
	Iyengar, J., Ed. and I. Swett, Ed., "QUIC Loss Detection		Iyengar, J., Ed. and I. Swett, Ed., "QUIC Loss Detection
	and Congestion Control", draft-ietf-quic-recovery-34 (work		and Congestion Control", draft-ietf-quic-recovery-latest
	in progress), January 2021.		(work in progress).
	[QUIC-TLS]		[QUIC-TLS]
	Thomson, M., Ed. and S. Turner, Ed., "Using Transport		Thomson, M., Ed. and S. Turner, Ed., "Using Transport
	Layer Security (TLS) to Secure QUIC", draft-ietf-quic-		Layer Security (TLS) to Secure QUIC", draft-ietf-quic-tls-
	tls-34 (work in progress), January 2021.		latest (work in progress).
	[RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,		[RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,
	DOI 10.17487/RFC1191, November 1990,		DOI 10.17487/RFC1191, November 1990,
	<https://www.rfc-editor.org/info/rfc1191>.		<https://www.rfc-editor.org/info/rfc1191>.
	[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>.
End of changes. 7 change blocks.
	12 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.44jr. The latest version is available from http://tools.ietf.org/tools/rfcdiff/