For 18.1.12, could we use:

If the client has not detected having moved to a new link but detects a 
significant change regarding the prefixes available on the link, the client 
SHOULD initiate one of the Renew/Reply, Confirm/Reply or 
Information-request/Reply exchanges. A change is considered significant when 
one or more on-link prefixes are added, and/or one or more existing on-link 
prefixes are deprecated. The reason for this is that such a significant change 
may indicate a configuration change at the server. However, a client MUST 
rate-limit such initiation attempts to avoid flooding a server with requests 
when there are link issues (for example, only doing one of these at most every 
30 seconds).

This also seems more consistent with earlier text in this section?

- Bernie 

> On Dec 15, 2025, at 4:41 PM, Michael Richardson <[email protected]> wrote:
> 
> 
> I have read the 9915 top to bottom.
> I think the phrasing at 18.2.12:
> 
>> A client not detected as having moved to a new link SHOULD initiate
> 
> is still pretty awkward.
> The new phrasing, seems to suggest that an external entity is going to detect
> the client has moved.  But, it's the client has to do the detection.
> I think the problem is that the sentences are too long/too few.
> I can live with this, but maybe someone else has a suggestion here.
> 
> ---- non-issues:
> 
> A question about the many minor changes where a list item has a : added.
> The colon appears in the <dt> as text, it's not produced by xml2rfc.
> Someone did s,</dt>,:</dt>,g right?
> So that seems like a stylistic thing that (authors) should just be more aware
> of.  It seems like it aught to be something xml2rfc "enforces"
> 
> I'm also curious about the how/why IA_PD-options got hyphen wrapped (section
> 21.22), but in our text it was just moved to a new line.
> 
> Glad we did 3.Background this way!
> 
> --
> Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> <signature.asc>
-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to