Hi Authors and Erik (AD)*,

*Erik (AD) - This is a friendly reminder that we are awaiting your review and 
approval regarding the BCP 14 key word update from “MUST not” to “MUST NOT” in 
the sentence below:

Original:
 In particular, enabling or disabling the P flag MUST not trigger
 automatic changes in the A flag value set by the router.

Current:
 In particular, enabling or disabling the P flag MUST NOT trigger
 automatic changes in the A flag value set by the router.

See this diff file:
https://www.rfc-editor.org/authors/rfc9762-auth48diff.html

Additionally, we are still awaiting word regarding this query:
>> 6) <!-- [rfced] *AD and authors - There is an open erratum report against RFC
>> 4861 regarding the text that is being updated in Section 9.1 of this
>> document. Are any updates needed?
>> 
>> See https://www.rfc-editor.org/errata/eid8055.
>> -->
> 
> There is no conflict in spirit between the filed erratum and this
> document. But if the erratum is approved then the text of this
> document should be updated to reflect the erratum, and say:
> “Note: If none of the M, O, or P (draft-ietf-6man-pio-pflag) flags are
> set, this indicates that no information is available via DHCPv6 from
> the router, or from other nodes that the router has been made aware
> of".
> 
> With my 6MAN chair hat on: let the chairs discuss it with the AD. I
> think it would be better if the decision for the erratum is made
> before this draft is published.


Authors - We will await any further changes you may have and approvals from 
each author and the *AD prior to moving forward in the publication process.

The files have been posted here (please refresh):
https://www.rfc-editor.org/authors/rfc9762.txt
https://www.rfc-editor.org/authors/rfc9762.pdf
https://www.rfc-editor.org/authors/rfc9762.html
https://www.rfc-editor.org/authors/rfc9762.xml

The relevant diff files are posted here:
https://www.rfc-editor.org/authors/rfc9762-diff.html (comprehensive diff)
https://www.rfc-editor.org/authors/rfc9762-auth48diff.html (all AUTH48 changes)

Please see the AUTH48 status page for this document here:
https://www.rfc-editor.org/auth48/rfc9762

Thank you,
RFC Editor/ap

> On Apr 18, 2025, at 1:12 PM, Alanna Paloma <apal...@staff.rfc-editor.org> 
> wrote:
> 
> Hi Jen,
> 
> Thank you for clarifying. We’ve updated to use “prefix delegation”.
> 
> The files have been posted here (please refresh):
> https://www.rfc-editor.org/authors/rfc9762.txt
> https://www.rfc-editor.org/authors/rfc9762.pdf
> https://www.rfc-editor.org/authors/rfc9762.html
> https://www.rfc-editor.org/authors/rfc9762.xml
> 
> The relevant diff files are posted here:
> https://www.rfc-editor.org/authors/rfc9762-diff.html (comprehensive diff)
> https://www.rfc-editor.org/authors/rfc9762-auth48diff.html (all AUTH48 
> changes)
> 
> We will await any further changes you may have and approvals from each author 
> and the AD prior to moving forward in the publication process.
> 
> Please see the AUTH48 status page for this document here:
> https://www.rfc-editor.org/auth48/rfc9762
> 
> Thank you,
> RFC Editor/ap
> 
>> On Apr 18, 2025, at 5:44 AM, Jen Linkova <furr...@gmail.com> wrote:
>> 
>> On Thu, Apr 10, 2025 at 4:23 AM Alanna Paloma
>> <apal...@staff.rfc-editor.org> wrote:
>>> Authors - Thank you for your reply.  We have updated as requested. Please 
>>> not that there is one remaining terminology query that has not yet been 
>>> addressed:
>>>>> b) Throughout the text, the following terminology appears to be used
>>>>> inconsistently. Please review these occurrences and let us know if/how 
>>>>> they
>>>>> may be made consistent.
>>>>> 
>>>>> Prefix Delegation vs. prefix delegation
>> 
>> Oh sorry, I thought I answered it but I think I wasn't clear that my
>> answer was referring to both 'preferred lifetime' and 'prefix
>> delegation'.
>> 
>> RFC8415 uses non-capitalized versions everywhere (except in section
>> titles and figure legends)
>> So let’s use the lowercase version.
>> 
>> Thank you!
>> 
>> -- 
>> Cheers, Jen Linkova
> 

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

Reply via email to