W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2018

Protocol Action: 'Using Early Data in HTTP' to Proposed Standard (draft-ietf-httpbis-replay-04.txt)

From: The IESG <iesg-secretary@ietf.org>
Date: Fri, 29 Jun 2018 05:36:42 -0700
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: httpbis-chairs@ietf.org, The IESG <iesg@ietf.org>, mcmanus@ducksong.com, ietf-http-wg@w3.org, draft-ietf-httpbis-replay@ietf.org, alexey.melnikov@isode.com, rfc-editor@rfc-editor.org, Patrick McManus <mcmanus@ducksong.com>
Message-ID: <153027580246.30400.17639150568655499321.idtracker@ietfa.amsl.com>
The IESG has approved the following document:
- 'Using Early Data in HTTP'
  (draft-ietf-httpbis-replay-04.txt) as Proposed Standard

This document is the product of the Hypertext Transfer Protocol Working Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-httpbis-replay/




Technical Summary

This document defines requirements for the sending and handling of
early data at the HTTP layer. Early data is data associated with the
0-RTT phases of TLS 1.3 and QUIC and is subject to being replayed. The
document creates mechanisms for Clients, Servers, and Intermediaries
to communicate the status of early data and minimize the risk of
replay. It is applicable to all versions of HTTP.

Working Group Summary

Development of this document mostly focused on the relationship of
intermediaries with early data on both the client and server side of
their connection. Issues with partly recevied early data also
underwent considerable revision but without significant controversy.

Document Quality

Participation in the document's review and development was very
broad. The three authors come from a client, a CDN, and an
intermediary background. There was a high level of discussion
throughout the process and the Working Group Last Call received review
comments from 12 different individuals indicating thorough review.

There was strong consensus in the working group for this document with
many also expressing an eagerness to have it deployed in the same time
frame as TLS 1.3 deployment.

There are known implementations in a browser, server, and intermediary
and statements of intent to implement from several other parties.

Personnel

Patrick McManus is the document shepherd; Alexey Melnikov is the
responsible Area Director.
Received on Friday, 29 June 2018 12:37:06 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 1 July 2018 20:17:20 UTC