Subject: Fwd: New Version Notification for draft-ietf-quic-transport-00.txt

From: Mark Nottingham <[email-masked]>
Date: Tue, 29 Nov 2016 11:16:08 +1100

Everyone,

The editors have submitted the -00 round of drafts, based upon the input documents mentioned in our charter; as discussed in Seoul, these will be our starting points, but that does not imply that we have consensus on their contents.

It's good to see that people have already started logging issues:
  https://github.com/quicwg/base-drafts/issues <https://github.com/quicwg/base-drafts/issues>

As a reminder, this is the process for discussing and resolving those issues, as discussed:
  https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md <https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>

It's expected that there will be substantial changes in the first few rounds of subsequent drafts, as the editors get them into shape for further discussion. Please consider them to be a work-in-progress. 

Cheers,

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-ietf-quic-transport-00.txt
> Date: 29 November 2016 at 11:07:49 am AEDT
> To: "Janardhan Iyengar" <[email-masked]>, "Martin Thomson" <[email-masked]>, <[email-masked]>, "Jana Iyengar" <[email-masked]>
> Resent-From: <[email-masked]>
> Resent-To: [email-masked], [email-masked]
> 
> 
> A new version of I-D, draft-ietf-quic-transport-00.txt
> has been successfully submitted by Martin Thomson and posted to the
> IETF repository.
> 
> Name:		draft-ietf-quic-transport
> Revision:	00
> Title:		QUIC: A UDP-Based Multiplexed and Secure Transport
> Document date:	2016-11-28
> Group:		quic
> Pages:		45
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-quic-transport-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-quic-transport/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-quic-transport-00
> 
> 
> 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.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
> 

--
Mark Nottingham   https://www.mnot.net/