Re: [OAUTH-WG] RFC 7662 on OAuth 2.0 Token Introspection

Hannes Tschofenig <hannes.tschofenig@gmx.net> Wed, 21 October 2015 08:20 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 403F81B36D9 for <oauth@ietfa.amsl.com>; Wed, 21 Oct 2015 01:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 h8kcMX6r4ABf for <oauth@ietfa.amsl.com>; Wed, 21 Oct 2015 01:20:57 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 225531B36D7 for <oauth@ietf.org>; Wed, 21 Oct 2015 01:20:57 -0700 (PDT)
Received: from [192.168.131.140] ([80.92.122.73]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M8mCe-1Zh97x21gC-00CDPf; Wed, 21 Oct 2015 10:20:53 +0200
To: Justin Richer <jricher@mit.edu>, "<oauth@ietf.org>" <oauth@ietf.org>
References: <20151019225659.76476182534@rfc-editor.org> <6B17AE6C-D494-46EE-9018-5C922EE370B6@mit.edu>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <56274ACB.1040800@gmx.net>
Date: Wed, 21 Oct 2015 10:20:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <6B17AE6C-D494-46EE-9018-5C922EE370B6@mit.edu>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="deFJPMWJ4Ck7aomHq769eGeBaEJujXE8b"
X-Provags-ID: V03:K0:y0uUH9hnVyXwoObyx25KmBa3CaMyn2kmyTeAbAHGj818mvbk9qv sVLddBTa7XPxxD7jnEkkRbahFnGXz6bd5BT+Pnq9tUjmT9pFMoAuxdxD+RhExgZeQQYrZDG x2C9GMdHoaxrbhkYTK22u0GFrbVks2NYKgS3NewdLfES9DMzQiuI6C9nyxi4HOaLKS8R5Ih nrtxYILX5QdFt5UNu4nQQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:MJD1Z5HzNUE=:+bqBrN1k6sqOetw4siexZ3 D6KdzbApDg6I6i7M+dHRX492pvizWmniyMyXO8ZTdYfgAtUaq+ktQj6BTndmOB42AVbhswfjy 1+wV4Fj9GET8u24LChFq937lYRzC8uWcUCq63uEikonDJ57L97xIz7Uak37LKtbadEeD1HvLp Li5V/y0jU5G47ai4UufeAXJjnDRXc50Lbbuaacxuk19D/QOk0x2YDIodN9Qr1OuUjscFbNhkM ry9ybwGsigAgJhbtodYENDUwKMjoXHJA8WxlP6T+WnRUQruOP9n+Vzi0l1Q3m3VysLdgbXJ4Y eAc64e2rakpIQmPtR/pkTVtNEkxWWr3rPMFbIyiFLbI4YJry+WV6OQxqVlblrKXfabjQE8b3f gsvCerS/fLCm+fNdayTfgwZbFHrOp32SpsIL9uPjM3MFq0ohpyUGQOiVtIVV4E54hCAKi1VZK 4djVQQif5GCzUMm1WvQr0Zph9khV7r36TdRbe43DeuM0axK2+ZGpea687CNcePI6GLZJ7ouyU 9iJwzV2wdzjJ/YYFxoG+21oH/QrR6KvYqRphr9DOcYoIslQdJf2fbLNKdXoT2x45K2zCBodo9 PQc+JTyE7sdzVhqAU6T88bcJ1u0WXk4OucvrIoj8h0dOMX329HfgsBiY7f1CZlk724RWncecX PKjJ17Z8LhRCVkxZKyxQ5+d3Ow/fKsJK2QCPO/9YEWY87/ZJnMmFVyaqgL+XXcXwrw4ynurfP lJMbttJfjoemL4aVi7tgioC5ekvl8yTLP2p5O7SS+WgvaNBVAD59j9pdJ8o=
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/-0uqbENKwOumj2EW5BBSQ62g0QY>
Subject: Re: [OAUTH-WG] RFC 7662 on OAuth 2.0 Token Introspection
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 21 Oct 2015 08:20:59 -0000

Thank you Justin for the hard work!

On 10/20/2015 06:32 PM, Justin Richer wrote:
> Thank you to everyone who helped make token introspection into a real standard!
> 
>  — Justin
> 
>> On Oct 19, 2015, at 6:56 PM, rfc-editor@rfc-editor.org wrote:
>>
>> A new Request for Comments is now available in online RFC libraries.
>>
>>
>>        RFC 7662
>>
>>        Title:      OAuth 2.0 Token Introspection 
>>        Author:     J. Richer, Ed.
>>        Status:     Standards Track
>>        Stream:     IETF
>>        Date:       October 2015
>>        Mailbox:    ietf@justin.richer.org
>>        Pages:      17
>>        Characters: 36591
>>        Updates/Obsoletes/SeeAlso:   None
>>
>>        I-D Tag:    draft-ietf-oauth-introspection-11.txt
>>
>>        URL:        https://www.rfc-editor.org/info/rfc7662
>>
>>        DOI:        http://dx.doi.org/10.17487/RFC7662
>>
>> This specification defines a method for a protected resource to query
>> an OAuth 2.0 authorization server to determine the active state of an
>> OAuth 2.0 token and to determine meta-information about this token.
>> OAuth 2.0 deployments can use this method to convey information about
>> the authorization context of the token from the authorization server
>> to the protected resource.
>>
>> This document is a product of the Web Authorization Protocol 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/rfc.html
>>
>> 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
>>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>