IETF Logo Mail Archive

[OAUTH-WG] Fwd: I-D Action: draft-ietf-oauth-token-binding-03.txt

Brian Campbell <bcampbell@pingidentity.com> Mon, 27 March 2017 16:33 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D0A127B57 for <oauth@ietfa.amsl.com>; Mon, 27 Mar 2017 09:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.com
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 iV5kv-pDvaJi for <oauth@ietfa.amsl.com>; Mon, 27 Mar 2017 09:33:04 -0700 (PDT)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB618124D6C for <oauth@ietf.org>; Mon, 27 Mar 2017 09:33:04 -0700 (PDT)
Received: by mail-pg0-x236.google.com with SMTP id 81so30548474pgh.2 for <oauth@ietf.org>; Mon, 27 Mar 2017 09:33:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=LtjUFO8vBHF85SbqmABlIN0rwbyUfTI2FjkfU7G6TQE=; b=KhG4U4at4nE4BaAuNMM+uqdSMgUxs4LdcX1CmENWMeIlud/fXy1b9sCIVM23zku9C2 /yRZJGlISGxmooGc7x320Qu/b6SyKvAqbcwbN0GAOI+RUSKPCQ2jZI9Sd1ipTaIhQuXt o47SX/Xt4anZMqT6/XG/WJtvanDoCGH75Wgz4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=LtjUFO8vBHF85SbqmABlIN0rwbyUfTI2FjkfU7G6TQE=; b=QAz7z0zzqeiKvTqwbJg7OK+A5Dxm4ihpgFUA5vWbgAF67JizDJ847VjT6KqB/ccnLY iYREz2aYIEShcziFcDndaDHnLevba5XilPP0uwgvIQMdH+X1CUvDk6M3MwpgSRd6pvdC 32J5RUA2Ow8YGC7PQN8/XlpVGeEmgggnii7zofRpJv6V3LfkxSUI+odaUr0XJPG/E//N XUQXGWx1rw2Kh8Vd62EJ9KRNljb5TmroiL8UEVTb/yeEPTcyimX1/+qjbfO+FIacyDjz uwkBRFl3PMkyCtumgoWdBR9n9WOJF2UUVBD8NQGcG8mDkfYKBkkvI4jkZoJE1h+gSZeL uFsw==
X-Gm-Message-State: AFeK/H0b+0WBWGK3Y8pNd/5Wcac9mTmTt11etowyWV1PqZDQTOjKvq3xxRAKfC+omUzwL0xVT1v/YZ1NBXxxoq0V
X-Received: by 10.98.159.82 with SMTP id g79mr26526701pfe.189.1490632384059; Mon, 27 Mar 2017 09:33:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.170.138 with HTTP; Mon, 27 Mar 2017 09:32:33 -0700 (PDT)
In-Reply-To: <149063228392.30557.3815696692412964113@ietfa.amsl.com>
References: <149063228392.30557.3815696692412964113@ietfa.amsl.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 27 Mar 2017 11:32:33 -0500
Message-ID: <CA+k3eCTG7RB6SD8756FpHm30DOJgRgWUko7Dtv1y6L_GhnxiKA@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0a542ebe378d054bb8e5c9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/eUDxIdhJOkj5TjE9Tvf21QVh72E>
Subject: [OAUTH-WG] Fwd: I-D Action: draft-ietf-oauth-token-binding-03.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 16:33:07 -0000

-03 only fixes a few mistakes in and around the examples that I noticed
preparing the slides for the IETF 98 Chicago meeting.

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Mon, Mar 27, 2017 at 11:31 AM
Subject: [OAUTH-WG] I-D Action: draft-ietf-oauth-token-binding-03.txt
To: i-d-announce@ietf.org
Cc: oauth@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Web Authorization Protocol of the IETF.

        Title           : OAuth 2.0 Token Binding
        Authors         : Michael B. Jones
                          John Bradley
                          Brian Campbell
                          William Denniss
        Filename        : draft-ietf-oauth-token-binding-03.txt
        Pages           : 26
        Date            : 2017-03-27

Abstract:
   This specification enables OAuth 2.0 implementations to apply Token
   Binding to Access Tokens, Authorization Codes, and Refresh Tokens.
   This cryptographically binds these tokens to a client's Token Binding
   key pair, possession of which is proven on the TLS connections over
   which the tokens are intended to be used.  This use of Token Binding
   protects these tokens from man-in-the-middle and token export and
   replay attacks.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-oauth-token-binding/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-oauth-token-binding-03
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-token-binding-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-token-binding-03


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/

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email