I-D Action: draft-thomson-http2-client-certs-01.txt
internet-drafts@ietf.org Fri, 22 January 2016 22:23 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B3F1A8AD1 for <i-d-announce@ietf.org>; Fri, 22 Jan 2016 14:23:14 -0800 (PST)
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-thomson-http2-client-certs-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160122222314.28781.31111.idtracker@ietfa.amsl.com>
Date: Fri, 22 Jan 2016 14:23:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/i-d-announce/ttgAYvQwrT7Ubb4Pa6e1Z9dpmsE>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 22:23:14 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Reactive Certificate-Based Client Authentication in HTTP/2 Authors : Martin Thomson Mike Bishop Filename : draft-thomson-http2-client-certs-01.txt Pages : 19 Date : 2016-01-22 Abstract: Some HTTP servers provide a subset of resources that require additional authentication to interact with. HTTP/1.1 servers rely on TLS renegotiation that is triggered by a request to a protected resource. HTTP/2 made this pattern impossible by forbidding the use of TLS renegotiation. While TLS 1.3 provides an alternate mechanism to obtain client certificates, this mechanism does not map well to usage in TLS 1.2. This document describes a how client authentication might be requested by a server as a result of receiving a request to a protected resource. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-thomson-http2-client-certs/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-thomson-http2-client-certs-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-thomson-http2-client-certs-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-thomson-http2-client-certs-01.t… internet-drafts