Just refreshed the JPOP draft as it may be pertinent to both DPOP and access 
token JWT discussion.

Nat Sakimura
Nomura Research Institute

PLEASE READ:This e-mail is confidential and intended for the named recipient 
only. If you are not an intended recipient, please notify the sender and delete 
this e-mail.
________________________________
差出人: internet-dra...@ietf.org <internet-dra...@ietf.org>
送信日時: 月曜日, 7月 22, 2019 11:33 午前
宛先: Nat Sakimura; Kepeng Li; John Bradley
件名: New Version Notification for draft-sakimura-oauth-jpop-05.txt


A new version of I-D, draft-sakimura-oauth-jpop-05.txt
has been successfully submitted by Nat Sakimura and posted to the
IETF repository.

Name:           draft-sakimura-oauth-jpop
Revision:       05
Title:          The OAuth 2.0 Authorization Framework: JWT Pop Token Usage
Document date:  2019-07-22
Group:          Individual Submission
Pages:          12
URL:            
https://www.ietf.org/internet-drafts/draft-sakimura-oauth-jpop-05.txt
Status:         https://datatracker.ietf.org/doc/draft-sakimura-oauth-jpop/
Htmlized:       https://tools.ietf.org/html/draft-sakimura-oauth-jpop-05
Htmlized:       https://datatracker.ietf.org/doc/html/draft-sakimura-oauth-jpop
Diff:           https://www.ietf.org/rfcdiff?url2=draft-sakimura-oauth-jpop-05

Abstract:
   This specification describes how to use JWT POP (Jpop) tokens that
   were obtained through [POPKD] in HTTP requests to access OAuth 2.0
   protected resources.  Only the party in possession of the
   corresponding cryptographic key for the Jpop token can use it to get
   access to the associated resources unlike in the case of the bearer
   token described in [RFC6750] where any party in posession of the
   access token can access the resource.





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.

The IETF Secretariat

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

Reply via email to