RFC 8470 on Using Early Data in HTTP
rfc-editor@rfc-editor.org Mon, 24 September 2018 15:02 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00CE130EDD for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 24 Sep 2018 08:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xW9t5DKOzoWb for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 24 Sep 2018 08:02:45 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DE9C130EE1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 24 Sep 2018 08:02:44 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1g4SKn-00049k-SY for ietf-http-wg-dist@listhub.w3.org; Mon, 24 Sep 2018 14:59:37 +0000
Resent-Date: Mon, 24 Sep 2018 14:59:37 +0000
Resent-Message-Id: <E1g4SKn-00049k-SY@frink.w3.org>
Received: from uranus.w3.org ([128.30.52.58]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1g4SKi-000497-5l for ietf-http-wg@listhub.w3.org; Mon, 24 Sep 2018 14:59:32 +0000
Received: from www-data by uranus.w3.org with local (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1g4SKh-0003qb-TI for ietf-http-wg@listhub.w3.org; Mon, 24 Sep 2018 14:59:32 +0000
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1g3ND8-0008Fp-SM for ietf-http-wg@listhub.w3.org; Fri, 21 Sep 2018 15:19:14 +0000
Received: from rfc-editor.org ([4.31.198.49]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <wwwrun@rfc-editor.org>) id 1g3ND6-0000z8-Pt for ietf-http-wg@w3.org; Fri, 21 Sep 2018 15:19:13 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id BA96CB80B96; Fri, 21 Sep 2018 08:18:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180921151847.BA96CB80B96@rfc-editor.org>
Date: Fri, 21 Sep 2018 08:18:47 -0700
X-W3C-Hub-Spam-Status: No, score=-6.2
X-W3C-Hub-Spam-Report: AWL=0.966, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1g3ND6-0000z8-Pt dffb2506f86e81c35c1f505512cd9c55
X-caa-id: 5b63b6b668
X-Original-To: ietf-http-wg@w3.org
Subject: RFC 8470 on Using Early Data in HTTP
Archived-At: <https://www.w3.org/mid/20180921151847.BA96CB80B96@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/35927
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
A new Request for Comments is now available in online RFC libraries.
RFC 8470
Title: Using Early Data in HTTP
Author: M. Thomson,
M. Nottingham,
W. Tarreau
Status: Standards Track
Stream: IETF
Date: September 2018
Mailbox: martin.thomson@gmail.com,
mnot@mnot.net,
willy@haproxy.org
Pages: 12
Characters: 25880
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-replay-04.txt
URL: https://www.rfc-editor.org/info/rfc8470
DOI: 10.17487/RFC8470
Using TLS early data creates an exposure to the possibility of a
replay attack. This document defines mechanisms that allow clients
to communicate with servers about HTTP requests that are sent in
early data. Techniques are described that use these mechanisms to
mitigate the risk of replay.
This document is a product of the Hypertext Transfer Protocol Bis Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
- RFC 8470 on Using Early Data in HTTP rfc-editor