I-D Action: draft-hamilton-quic-transport-protocol-01.txt

internet-drafts@ietf.org Mon, 31 October 2016 23:36 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-hamilton-quic-transport-protocol-01.txt
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147795699058.23221.6359733035310456915.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2016 16:36:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/tCY3pRO4jGi-pTZBHPikTG6PbXU>
Reply-To: internet-drafts@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : QUIC: A UDP-Based Multiplexed and Secure Transport
        Authors         : Ryan Hamilton
                          Janardhan Iyengar
                          Ian Swett
                          Alyssa Wilk
	Filename        : draft-hamilton-quic-transport-protocol-01.txt
	Pages           : 45
	Date            : 2016-10-31

Abstract:
   QUIC is a multiplexed and secure transport protocol that runs on top
   of UDP.  QUIC builds on past transport experience, and implements
   mechanisms that make it useful as a modern general-purpose transport
   protocol.  Using UDP as the basis of QUIC is intended to address
   compatibility issues with legacy clients and middleboxes.  QUIC
   authenticates all of its headers, preventing third parties from from
   changing them.  QUIC encrypts most of its headers, thereby limiting
   protocol evolution to QUIC endpoints only.  Therefore, middleboxes,
   in large part, are not required to be updated as new protocol
   versions are deployed.  This document describes the core QUIC
   protocol, including the conceptual design, wire format, and
   mechanisms of the QUIC protocol for connection establishment, stream
   multiplexing, stream and connection-level flow control, and data
   reliability.  Accompanying documents describe QUIC's loss recovery
   and congestion control, and the use of TLS 1.3 for key negotiation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hamilton-quic-transport-protocol/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-hamilton-quic-transport-protocol-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-hamilton-quic-transport-protocol-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-hamilton-quic-transport-protoco… internet-drafts