Daniel,

The document has been updated accordingly. (The last change is fine because the 
term now matchs the referenced document [research.jcs_14].)  The revised files 
are here (please refresh):
  https://www.rfc-editor.org/authors/rfc9700.html
  https://www.rfc-editor.org/authors/rfc9700.txt
  https://www.rfc-editor.org/authors/rfc9700.pdf
  https://www.rfc-editor.org/authors/rfc9700.xml

This diff file shows all changes from the approved I-D:
  https://www.rfc-editor.org/authors/rfc9700-diff.html
  https://www.rfc-editor.org/authors/rfc9700-rfcdiff.html (side by side)

This diff file shows the changes made during AUTH48 thus far:
  https://www.rfc-editor.org/authors/rfc9700-auth48diff.html
  https://www.rfc-editor.org/authors/rfc9700-auth48rfcdiff.html (side by side)

This diff file shows only the changes since the last posted version:
  https://www.rfc-editor.org/authors/rfc9700-lastrfcdiff.html

We will wait to hear from J. Bradley and A. Labunets before continuing the 
publication process. This page shows the AUTH48 status of your document:
  https://www.rfc-editor.org/auth48/rfc9700

Thank you.
RFC Editor/ar

> On Jan 28, 2025, at 12:17 PM, Daniel Fett <m...@danielfett.de> wrote:
> 
> Hi Alice,
> 
> While we're waiting for the other coauthors to approve, I was notified of a 
> few minor editorial things that escaped our attention, please see the 
> attached PDF.
> 
> I support the suggested change to "redirection URI". For the last item, I'm 
> not sure what's correct and trust your knowledge :-)
> 
> Thanks,
> Daniel
> 
> Am 27.01.25 um 21:05 schrieb Alice Russo:
>> Daniel,
>> 
>> Thank you for letting us know. We have recorded your approval on the AUTH48 
>> status page (
>> https://www.rfc-editor.org/auth48/rfc9700
>> ).  We updated the date on the document to 'January 2025'. 
>> 
>> We await word from your coauthors before continuing the publication process. 
>> 
>> The files are here:
>>    
>> https://www.rfc-editor.org/authors/rfc9700.txt
>> 
>>    
>> https://www.rfc-editor.org/authors/rfc9700.pdf
>> 
>>    
>> https://www.rfc-editor.org/authors/rfc9700.html
>> 
>>    
>> https://www.rfc-editor.org/authors/rfc9700.xml
>> 
>> 
>> Diff of all changes from the I-D:
>>    
>> https://www.rfc-editor.org/authors/rfc9700-diff.html
>>  
>>    
>> https://www.rfc-editor.org/authors/rfc9700-rfcdiff.html
>>  (side by side)
>> 
>> Diff of the changes made during AUTH48:
>>    
>> https://www.rfc-editor.org/authors/rfc9700-auth48diff.html
>>  
>>    
>> https://www.rfc-editor.org/authors/rfc9700-auth48rfcdiff.html
>>  (side by side)
>> 
>> Diff of only the most recent changes:
>>    
>> https://www.rfc-editor.org/authors/rfc9700-lastdiff.html
>>  
>>    
>> https://www.rfc-editor.org/authors/rfc9700-lastrfcdiff.html
>>  (side by side)
>> 
>> Thank you.
>> RFC Editor/ar
>> 
>> [FYI, new email address: 
>> aru...@staff.rfc-editor.org
>> ]
>> 
>> 
>>> On Jan 27, 2025, at 10:02 AM, Daniel Fett <m...@danielfett.de>
>>>  wrote:
>>> 
>>> Hi Alice,
>>> 
>>> Today, we were finally able to discuss the potential addition to this 
>>> document in the working group. There was a consensus in the call that we 
>>> will not add anything to the document.
>>> 
>>> I therefore give my "go" for publication.
>>> 
>>> Thank you,
>>> Daniel
>>> 
>>> Am 20.12.24 um 01:18 schrieb Alice Russo:
>>> 
>>>> Daniel,
>>>> Checking in on this document; any update on the normative change?
>>>> 
>>>> Thank you.
>>>> RFC Editor/ar
>>>> 
> <Suggested Changes to OAuth Security BCP (Typos).pdf>

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to