Hi David,

Looks great!

Thank you, 
RFC Editor/st

> On Mar 13, 2025, at 10:58 PM, David Dong via RT <iana-mat...@iana.org> wrote:
> 
> Hi Sarah,
> 
> This has been completed:
> 
> deprecation Refers to documentation (intended for human consumption) about 
> the deprecation of the link's context. 
> [RFC-ietf-httpapi-deprecation-header-09], section 3
> 
> Registry:
> https://www.iana.org/assignments/link-relations/
> 
> Best regards,
> 
> David Dong
> IANA Services Sr. Specialist
> 
> On Wed Mar 12 12:20:42 2025, starr...@staff.rfc-editor.org wrote:
>> Hi IANA,
>> 
>> Please update "Description" in "Link Relations" registry at
>> https://www.iana.org/assignments/link-relations/ to match the edited
>> document https://www.rfc-editor.org/authors/rfc9745-auth48diff.html:
>> 
>> OLD:
>> Refers to a resource that is documentation (intended for human
>> consumption) about the deprecation of the link's context.
>> 
>> NEW:
>> Refers to documentation (intended for human
>> consumption) about the deprecation of the link's context.
>> 
>> Thank you,
>> RFC Editor/st
>> 
>> 
>>> On Mar 12, 2025, at 7:15 AM, Sarah Tarrant <starr...@staff.rfc-
>>> editor.org> wrote:
>>> 
>>> Hi Sanjay and Erik,
>>> 
>>> Thank you so much for the speedy responses! We have updated
>>> accordingly.
>>> 
>>> We will move this document forward in the publication process at this
>>> time.
>>> 
>>> Sincerely,
>>> RFC Editor/st
>>> 
>>>> On Mar 12, 2025, at 4:06 AM, Erik Wilde <erik.wi...@dret.net> wrote:
>>>> 
>>>> Hello.
>>>> 
>>>> In case my feedback is needed as well.
>>>> 
>>>> On 2025-03-11 21:56, Sanjay Dalal wrote:
>>>>> Thanks. That works, better indeed.
>>>>> ...consumers of a resource (identified by a URI)...
>>>> 
>>>> Looks good to me, let's change it that way.
>>>> 
>>>> Thanks and 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