Hi Sanjay and Erik,

We had one more question regarding the following original sentence.

>> 1) <!-- [rfced] Please clarify "(in the sense of URI)" here. Also note that 
>> we do
>> not see "URI" used elsewhere in the document.
>> 
>> Original:
>>   The Deprecation HTTP response header field is used to signal to
>>   consumers of a resource (in the sense of URI) that the resource will
>>   be or has been deprecated.
>> -->
> 
> 
> [sd] it is ok as-is

Just so that it's clear to the reader, does "in the sense of URI" mean 
"identified by a URI"? We'd like to update for clarity if there is no objection.

Suggested:
  The Deprecation HTTP response header field is used to signal to
  consumers of a resource (identified by a URI) that the resource will
  be or has been deprecated.

Thank you,
RFC Editor/st


> On Mar 11, 2025, at 8:52 AM, Sarah Tarrant <starr...@staff.rfc-editor.org> 
> wrote:
> 
> All,
> 
> We have now received all necessary approvals and consider AUTH48 complete:
> https://www.rfc-editor.org/auth48/rfc9745
> 
> Thank you for your attention and guidance during the AUTH48 process.
> 
> We will move this document forward in the publication process at this time.
> 
> Sincerely,
> RFC Editor/st
> 
>> On Mar 11, 2025, at 8:16 AM, Erik Wilde <erik.wi...@dret.net> wrote:
>> 
>> Hello all.
>> 
>> My apologies for the delay.
>> 
>> On 2025-03-11 14:04, Sarah Tarrant wrote:
>>> Thank you for your reply. We have marked your approval on the AUTH48 status 
>>> page for this document (see https://www.rfc-editor.org/auth48/rfc9745).
>>> We will await approvals from each of the parties listed at the AUTH48 
>>> status page prior to moving this document forward in the publication 
>>> process.
>> 
>> I approve as well.
>> 
>> And thanks, @Sanjay, for doing the final round of feedback.
>> 
>> Kind regards,
>> 
>> Erik.
>> 
>> -- 
>> Erik Wilde | mailto:erik.wi...@dret.net    |
>>          | https://youtube.com/ErikWilde |
> 

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

Reply via email to