Manageability of the QUIC Transport Protocol
draft-kuehlewind-quic-manageability-00
|
| Document |
Type |
|
Active Internet-Draft (quic WG)
|
|
Last updated |
|
2017-06-15
(latest revision 2017-03-09)
|
|
Replaces |
|
draft-kuehlewind-quic-appman
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
Adopted by a WG
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group M. Kuehlewind
Internet-Draft B. Trammell
Intended status: Informational ETH Zurich
Expires: September 10, 2017 D. Druta
AT&T
March 09, 2017
Manageability of the QUIC Transport Protocol
draft-kuehlewind-quic-manageability-00
Abstract
This document discusses manageability of the QUIC transport protocol,
focusing on caveats impacting network operations involving QUIC
traffic. Its intended audience is network operators, as well as
content providers that rely on the use of QUIC-aware middleboxes,
e.g. for load balancing.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 10, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Kuehlewind, et al. Expires September 10, 2017 [Page 1]
Internet-DraftManageability of the QUIC Transport Protocol March 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. Features of the QUIC Wire Image . . . . . . . . . . . . . . . 3
2.1. QUIC Packet Header Structure . . . . . . . . . . . . . . 3
2.2. Integrity Protection of the Wire Image . . . . . . . . . 4
2.3. Connection ID and Rebinding . . . . . . . . . . . . . . . 4
2.4. Packet Numbers . . . . . . . . . . . . . . . . . . . . . 5
2.5. Greasing . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Specific Network Management Tasks . . . . . . . . . . . . . . 5
3.1. Stateful Treatment of QUIC Traffic . . . . . . . . . . . 5
3.2. Measurement of QUIC Traffic . . . . . . . . . . . . . . . 6
3.3. DDoS Detection and Mitigation . . . . . . . . . . . . . . 6
3.4. QoS support and ECMP . . . . . . . . . . . . . . . . . . 7
3.5. Load balancing . . . . . . . . . . . . . . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
QUIC [I-D.ietf-quic-transport] is a new transport protocol currently
under development in the IETF quic working group, focusing on support
of semantics as needed for HTTP/2 [I-D.ietf-quic-http]. Based on
current deployment practices, QUIC is encapsulated in UDP and
encrypted by default. The current version of QUIC integrates TLS
[I-D.ietf-quic-tls] to encrypt all payload data and most header
information. Given QUIC is an end-to-end transport protocol, all
information in the protocol header, even that which can be inspected,
is is not meant to be mutable by the network, and will therefore be
integrity-protected to the extent possible.
This document provides guidance for network operation on the
management of QUIC traffic. This includes guidance on how to
Show full document text