[OAUTH-WG] Re: WG Last Call: draft-ietf-oauth-identity-chaining-05 (Ends 2025-09-08)

[Brian Campbell <[e-mail]>]

As best I recall, the shepherding of this one was put on the back burner to
free up folks' time for preparations for the Montreal meeting. Which is
perfectly reasonable but it seems to have gotten somewhat forgotten about
in the intervening time. Can we re-engage with the publication process?

On Fri, Sep 12, 2025 at 10:20 AM Brian Campbell <[e-mail]>
wrote:

> And we've got a -06 out hopefully addressing feedback received during WGLC
> and ready for shepherding considerations
> https://mailarchive.ietf.org/arch/msg/oauth/qfK9VoUURc8oih-I3I6OGi_0JQg/
>
> On Tue, Sep 9, 2025 at 2:50 PM Brian Campbell <[e-mail]>
> wrote:
>
>> Thanks Rifaat,
>>
>> https://github.com/oauth-wg/oauth-identity-chaining/pull/171 has updates
>> aimed at addressing the feedback received during WGLC. We'll get a new
>> version of the draft published once we've aligned on the changes and merged
>> that.
>>
>> On Mon, Sep 8, 2025 at 7:12 AM Rifaat Shekh-Yusef <
>> [e-mail]> wrote:
>>
>>> Brian,
>>>
>>> Submit a new version of the draft that addresses these concerns.
>>> After that the chairs will review the document and start working on the
>>> document shepherd write up.
>>>
>>> Regards,
>>>  Rifaat & Hannes
>>>
>>>
>>>
>>>
>>> On Fri, Sep 5, 2025 at 1:09 PM Brian Campbell <
>>> [e-mail]> wrote:
>>>
>>>> The feedback was otherwise positive, which I didn't capture in the
>>>> issue, but is maybe relevant to the overall WGLC sentiment.
>>>>
>>>> On Tue, Sep 2, 2025 at 3:10 PM Brian Campbell <
>>>> [e-mail]> wrote:
>>>>
>>>>> I received some feedback off-list that seemed like it could be
>>>>> considered as part of WGLC, which I tried to summarize at
>>>>> https://github.com/oauth-wg/oauth-identity-chaining/issues/169
>>>>>
>>>>> On Mon, Aug 25, 2025 at 6:40 AM Rifaat Shekh-Yusef via Datatracker <
>>>>> [e-mail]> wrote:
>>>>>
>>>>>>
>>>>>> Subject: WG Last Call: draft-ietf-oauth-identity-chaining-05 (Ends
>>>>>> 2025-09-08)
>>>>>>
>>>>>> This message starts a 2-week WG Last Call for this document.
>>>>>>
>>>>>> Abstract:
>>>>>>    This specification defines a mechanism to preserve identity and
>>>>>>    authorization information across trust domains that use the OAuth
>>>>>> 2.0
>>>>>>    Framework.
>>>>>>
>>>>>> Discussion Venues
>>>>>>
>>>>>>    This note is to be removed before publishing as an RFC.
>>>>>>
>>>>>>    Discussion of this document takes place on the Web Authorization
>>>>>>    Protocol Working Group mailing list ([e-mail]) which is
>>>>>>    archived at https://mailarchive.ietf.org/arch/browse/oauth/.
>>>>>>
>>>>>>    Source for this draft and an issue tracker can be found at
>>>>>>    https://github.com/oauth-wg/oauth-identity-chaining.
>>>>>>
>>>>>> File can be retrieved from:
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-chaining/
>>>>>>
>>>>>> Please review and indicate your support or objection to proceed with
>>>>>> the
>>>>>> publication of this document by replying to this email keeping
>>>>>> [e-mail]
>>>>>> in copy. Objections should be motivated and suggestions to resolve
>>>>>> them are
>>>>>> highly appreciated.
>>>>>>
>>>>>> Authors, and WG participants in general, are reminded again of the
>>>>>> Intellectual Property Rights (IPR) disclosure obligations described
>>>>>> in BCP 79
>>>>>> [1]. Appropriate IPR disclosures required for full conformance with
>>>>>> the
>>>>>> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are
>>>>>> aware of
>>>>>> any. Sanctions available for application to violators of IETF IPR
>>>>>> Policy can
>>>>>> be found at [3].
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> [1] https://datatracker.ietf.org/doc/bcp78/
>>>>>> [2] https://datatracker.ietf.org/doc/bcp79/
>>>>>> [3] https://datatracker.ietf.org/doc/rfc6701/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>> *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.*
>>>
>>>

-- 
_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._