[Unbearable] RFC 8472 on Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation
rfc-editor@rfc-editor.org Tue, 09 October 2018 01:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: unbearable@ietfa.amsl.com
Delivered-To: unbearable@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F30F1310E2; Mon, 8 Oct 2018 18:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 FgLI72jbemAJ; Mon, 8 Oct 2018 18:40:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BD97131184; Mon, 8 Oct 2018 18:40:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CC3A1B80EB7; Mon, 8 Oct 2018 18:40:20 -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, unbearable@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181009014020.CC3A1B80EB7@rfc-editor.org>
Date: Mon, 08 Oct 2018 18:40:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/k0UZ0_BkFsYbVXi7_9ShtE2ToFM>
Subject: [Unbearable] RFC 8472 on Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"This list is for discussion of proposals for doing better than bearer tokens \(e.g. HTTP cookies, OAuth tokens etc.\) for web applications. The specific goal is chartering a WG focused on preventing security token export and replay attacks.\"" <unbearable.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/unbearable>, <mailto:unbearable-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/unbearable/>
List-Post: <mailto:unbearable@ietf.org>
List-Help: <mailto:unbearable-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/unbearable>, <mailto:unbearable-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 01:40:46 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8472 Title: Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation Author: A. Popov, Ed., M. Nystroem, D. Balfanz Status: Standards Track Stream: IETF Date: October 2018 Mailbox: andreipo@microsoft.com, mnystrom@microsoft.com, balfanz@google.com Pages: 8 Characters: 16842 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tokbind-negotiation-14.txt URL: https://www.rfc-editor.org/info/rfc8472 DOI: 10.17487/RFC8472 This document specifies a Transport Layer Security (TLS) extension for the negotiation of Token Binding protocol version and key parameters. Negotiation of Token Binding in TLS 1.3 and later versions is beyond the scope of this document. This document is a product of the Token Binding 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