No, not really. I was thinking of more informal thing. The session is supposed 
to be Wednesday afternoon, so I was thinking that it might be a good idea to do 
a bit of recap among contributors to draw up a battle plan towards IETF 102.


From: Rifaat Shekh-Yusef []
Sent: Wednesday, March 07, 2018 9:22 PM
To: n-sakimura <>
Cc: Brian Campbell <>; oauth <>
Subject: Re: [OAUTH-WG] Call for agenda items


Are you asking for an interim meeting?
We could schedule the Distributed OAuth discussion for the Wednesday meeting; 
that will give you guys sometime to discuss these face-to-face in London.


On Wed, Mar 7, 2018 at 2:00 AM, n-sakimura 
<<>> wrote:
Then let us do it. We need to put all the proposals on the table and strategize 
the design.
Perhaps we need a side meeting as well.


From: OAuth [<>] On 
Behalf Of Brian Campbell
Sent: Wednesday, March 07, 2018 1:31 AM
To: Rifaat Shekh-Yusef <<>>
Cc: oauth <<>>
Subject: Re: [OAUTH-WG] Call for agenda items

I hadn't previously been planning on it but am happy to do so.

On Tue, Mar 6, 2018 at 8:22 AM, Rifaat Shekh-Yusef 
<<>> wrote:

During the interim meeting, 3 drafts mentioned in the context of Distributed 

Brian, Hannes,

Are you planning on presenting your documents?


On Mon, Mar 5, 2018 at 8:09 PM, Nat Sakimura 
<<>> wrote:
I would be interested in hearing that.

Also, as part of "Distributed OAuth", can we do a bit of re-cap on some of the 
previous drafts on the similar topic as we discussed in the interim? i.e., 
Brian's draft (where is the link now?) and my draft 



On Tue, Mar 6, 2018 at 3:30 AM William Denniss 
<<>> wrote:
Hannes & Rifaat,

I would like the opportunity to present on OAuth 2.0 Incremental Authorization 
(draft-wdenniss-oauth-incremental-auth) [an update for which will be posted 
today] and "OAuth 2.0 Device Posture Signals" 

I can also give an update on the status of Device Flow 
(draft-ietf-oauth-device-flow). I expect that to be short now that WGLC has 
concluded and the document has advanced.

Little late to this thread and I see we already have 2 sessions in the draft 
agenda, but I'd like to add my support to keeping both sessions, there's always 
a lot to discuss and in the past we've been able to use any spare time to 
discuss the security topics of the day.


On Tue, Jan 30, 2018 at 4:40 AM Hannes Tschofenig 
<<>> wrote:
Hi all,

It is time already to think about the agenda for the next IETF meeting. Rifaat 
and I were wondering whether we need one or two sessions. We would like to make 
the decision based on the topics we will discuss. Below you can find a first 
version of the agenda with a few remarks. Let us know if you have comments or 
suggestions for additional agenda items.

Hannes & Rifaat

OAuth Agenda

- Welcome and Status Update  (Chairs)

  * OAuth Security Workshop Report

  * Documents in IESG processing
     # draft-ietf-oauth-device-flow-07
     # draft-ietf-oauth-discovery-08
     # draft-ietf-oauth-jwsreq-15
     # draft-ietf-oauth-token-exchange-11

       Remark: Status updates only if needed.

-  JSON Web Token Best Current Practices
   # draft-ietf-oauth-jwt-bcp-00

   Remark: We are lacking reviews on this document.
   Most likely we will not get them during the f2f meeting
   but rather by reaching out to individuals ahead of time.

-  OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access 
   # draft-ietf-oauth-mtls-06

   Remark: Could be completed by the time of the IETF meeting.

- OAuth Security Topics
  # draft-ietf-oauth-security-topics-04

  Remark: We could do a consensus call on parts of the document soon.

- OAuth 2.0 Token Binding
  # draft-ietf-oauth-token-binding-05

  Remark: Document is moving along but we are lacking implementations.

- OAuth 2.0 Device Posture Signals
  # draft-wdenniss-oauth-device-posture-01

  Remark: Interest in the work but we are lacking content (maybe even
  expertise in the group)

- Reciprocal OAuth
  # draft-hardt-oauth-mutual-02

  Remark: We had a virtual interim meeting on this topic and there is
  interest in this work and apparently no competing solutions. The plan
  is to run a call for adoption once we are allowed to add a new milestone
  to our charter.

- Distributed OAuth
  # draft-hardt-oauth-distributed-00

  Remark: We had a virtual interim meeting on this topic and there is
  interest in this work. Further work on the scope is needed.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
OAuth mailing list<>
OAuth mailing list<>

Nat Sakimura

Chairman of the Board, OpenID Foundation

OAuth mailing list<>

OAuth mailing list<>

CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately by 
e-mail and delete the message and any file attachments from your computer. 
Thank you.

OAuth mailing list

Reply via email to