Every time I think I couldn't be more impressed with the people who do
actual standards work, someone raises the bar.

Thanks Sergey!

Hutch


On Fri, Apr 7, 2017 at 10:42 AM Sergey Beryozkin <[email protected]>
wrote:

> Hi John
>
> I spotted it probably after the 10th iteration :-)
>
> Cheers, Sergey
> On 07/04/17 14:54, John Bradley wrote:
> > It was a test to see who was really reading it:)
> >
> > On Fri, Apr 7, 2017 at 1:58 PM, Sergey Beryozkin <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     Hi Brian
> >
> >     Thanks, a minor typo in the example,
> >     "x5t#s256" as opposed to "x5t#S256"
> >
> >     (sorry if it was already reported, might've missed it)
> >
> >     Cheers, Sergey
> >     On 30/03/17 22:15, Brian Campbell wrote:
> >
> >         This document, which I hope to present and discuss briefly at
> >         tomorrow's
> >         meeting, replaces (but keeps the feature) the Mutual TLS
> >         Authentication
> >         for OAuth Clients
> >         <
> https://tools.ietf.org/html/draft-campbell-oauth-tls-client-auth-00
> >         <
> https://tools.ietf.org/html/draft-campbell-oauth-tls-client-auth-00>>
> >         that was published leading up to the Seoul meeting
> >         <
> https://www.ietf.org/mail-archive/web/oauth/current/msg16704.html
> >         <
> https://www.ietf.org/mail-archive/web/oauth/current/msg16704.html>>
> >         and
> >         adds mutual TLS sender constrained access to OAuth protected
> >         resources.
> >         The concept for the latter was largely derived from one of the
> >         options
> >         in the JPOP draft
> >         <https://tools.ietf.org/html/draft-sakimura-oauth-jpop-04
> >         <https://tools.ietf.org/html/draft-sakimura-oauth-jpop-04>>. I
> >         apologize
> >         for the 11th hour publication but hope some folks will have a
> >         chance to
> >         read it.
> >
> >         ---------- Forwarded message ----------
> >         From: ** <[email protected]
> >         <mailto:[email protected]>
> >         <mailto:[email protected] <mailto:
> [email protected]>>>
> >         Date: Thu, Mar 30, 2017 at 3:49 PM
> >         Subject: New Version Notification for
> >         draft-campbell-oauth-mtls-00.txt
> >         To: Brian Campbell <[email protected]
> >         <mailto:[email protected]>
> >         <mailto:[email protected]
> >         <mailto:[email protected]>>>, Nat Sakimura
> >         <[email protected] <mailto:[email protected]>
> >         <mailto:[email protected] <mailto:[email protected]>>>,
> >         Torsten Lodderstedt
> >         <[email protected] <mailto:[email protected]>
> >         <mailto:[email protected]
> >         <mailto:[email protected]>>>, John Bradley
> >         <[email protected] <mailto:[email protected]>
> >         <mailto:[email protected] <mailto:[email protected]>>>
> >
> >
> >
> >         A new version of I-D, draft-campbell-oauth-mtls-00.txt
> >         has been successfully submitted by Brian Campbell and posted to
> the
> >         IETF repository.
> >
> >         Name:           draft-campbell-oauth-mtls
> >         Revision:       00
> >         Title:          Mutual TLS Profiles for OAuth Clients
> >         Document date:  2017-03-30
> >         Group:          Individual Submission
> >         Pages:          10
> >         URL:
> >
> https://www.ietf.org/internet-drafts/draft-campbell-oauth-mtls-00.txt
> >         <
> https://www.ietf.org/internet-drafts/draft-campbell-oauth-mtls-00.txt>
> >         <
> https://www.ietf.org/internet-drafts/draft-campbell-oauth-mtls-00.txt
> >         <
> https://www.ietf.org/internet-drafts/draft-campbell-oauth-mtls-00.txt>>
> >         Status:
> >          https://datatracker.ietf.org/doc/draft-campbell-oauth-mtls/
> >         <https://datatracker.ietf.org/doc/draft-campbell-oauth-mtls/>
> >         <https://datatracker.ietf.org/doc/draft-campbell-oauth-mtls/
> >         <https://datatracker.ietf.org/doc/draft-campbell-oauth-mtls/>>
> >         Htmlized:
> >          https://tools.ietf.org/html/draft-campbell-oauth-mtls-00
> >         <https://tools.ietf.org/html/draft-campbell-oauth-mtls-00>
> >         <https://tools.ietf.org/html/draft-campbell-oauth-mtls-00
> >         <https://tools.ietf.org/html/draft-campbell-oauth-mtls-00>>
> >         Htmlized:
> >
> https://datatracker.ietf.org/doc/html/draft-campbell-oauth-mtls-00
> >         <
> https://datatracker.ietf.org/doc/html/draft-campbell-oauth-mtls-00>
> >         <
> https://datatracker.ietf.org/doc/html/draft-campbell-oauth-mtls-00
> >         <
> https://datatracker.ietf.org/doc/html/draft-campbell-oauth-mtls-00>>
> >
> >
> >         Abstract:
> >            This document describes Transport Layer Security (TLS) mutual
> >            authentication using X.509 certificates as a mechanism for
> >         both OAuth
> >            client authentication to the token endpoint as well as for
> sender
> >            constrained access to OAuth protected resources.
> >
> >
> >
> >
> >         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 <http://tools.ietf.org>
> >         <http://tools.ietf.org>.
> >
> >         The IETF Secretariat
> >
> >
> >
> >
> >
> >         _______________________________________________
> >         OAuth mailing list
> >         [email protected] <mailto:[email protected]>
> >         https://www.ietf.org/mailman/listinfo/oauth
> >         <https://www.ietf.org/mailman/listinfo/oauth>
> >
> >
> >     _______________________________________________
> >     OAuth mailing list
> >     [email protected] <mailto:[email protected]>
> >     https://www.ietf.org/mailman/listinfo/oauth
> >     <https://www.ietf.org/mailman/listinfo/oauth>
> >
> >
>
> _______________________________________________
> OAuth mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/oauth
>
_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to