[Unbearable] RFC 8473 on Token Binding over HTTP

rfc-editor@rfc-editor.org Tue, 09 October 2018 01:41 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 4D73F131196; Mon, 8 Oct 2018 18:41:08 -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 Ah1jtRWeB1hz; Mon, 8 Oct 2018 18:41:04 -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 ACD85131206; Mon, 8 Oct 2018 18:40:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1331DB80EB7; Mon, 8 Oct 2018 18:40:43 -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: <20181009014043.1331DB80EB7@rfc-editor.org>
Date: Mon, 8 Oct 2018 18:40:43 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/5mzZ6j5VAtZ4R4Cvq4LwPVoOLTo>
Subject: [Unbearable] =?utf-8?q?RFC_8473_on_Token_Binding_over_HTTP?=
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:41:15 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8473

        Title:      Token Binding over HTTP 
        Author:     A. Popov, 
                    M. Nystroem,
                    D. Balfanz, Ed.,
                    N. Harper, 
                    J. Hodges
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2018
        Mailbox:    andreipo@microsoft.com, 
                    mnystrom@microsoft.com, 
                    balfanz@google.com,
                    nharper@google.com, 
                    Jeff.Hodges@KingsMountain.com
        Pages:      25
        Characters: 63182
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tokbind-https-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8473

        DOI:        10.17487/RFC8473

This document describes a collection of mechanisms that allow HTTP
servers to cryptographically bind security tokens (such as cookies
and OAuth tokens) to TLS connections.

We describe both first-party and federated scenarios.  In a first-
party scenario, an HTTP server is able to cryptographically bind the
security tokens that it issues to a client -- and that the client
subsequently returns to the server -- to the TLS connection between
the client and the server.  Such bound security tokens are protected
from misuse, since the server can generally detect if they are
replayed inappropriately, e.g., over other TLS connections.

Federated Token Bindings, on the other hand, allow servers to
cryptographically bind security tokens to a TLS connection that the
client has with a different server than the one issuing the token.

This document is a companion document to "The Token Binding Protocol                   
Version 1.0" (RFC 8471).

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