Hi, RFC editors,
Thanks for your hard work. Based on the last updates, as a co-author, I approve
the publication of this document to be RFC 9915.
Best regards,
Sheng
Megan Ferguson<[email protected]> On
Friday, Dec 19, 2025, 1:21 wrote:
Michael and Bernie,
Thank you for your replies.
Bernie - we have recorded your approval at the AUTH48 status page (see link
below).
Michael - responses inline with [rfced].
>
>>> 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.
>>>
>> [rfced] The submitted XML file contained a non-breaking hyphen in that
>> instance. We did not keep the non-breaking hyphen, as typically words
>> that "naturally" contain hyphens can contain line breaks in
RFCs. If
>> you want that particular term to be kept together, please let us know
>> and we will insert the entity (&nbhy;)
>
> Ah. I had looked at your XML, but not ours...
> I suspect that RFC8415 had the non-breaking space, my guess... inserted by
the RPC.
> I see it not hyphen-wrapped in 8415.
> I don't have the XML for it handy, so I can't tell for sure :-)
> {The XML in our git didn't have a non-breaking hyphen there}
>
> **I'd rather it (&nbhy;) was put back so that someone doing a search ^S
> IA_PD-options will find it**
[rfced] We have reverted to use the &nbhy; as requested. Please
refresh the files below to view.
>
>
>> Please let us know if this is not correct (i.e., it should be part of
>> an existing STD). See the complete list of Internet Standards
here:
>> https://www.rfc-editor.org/standards
>
> I think that it's correct that it's a new STD.
> Glad we caught that. Should it have been more clearly noted in some
way/
[rfced] It was clearly noted in the typical manner (Protocol Action mail); our
mistake to not have updated the document earlier in the process.
Please review the files carefully as we do not make changes after
publication.
The files have been posted here (please refresh):
https://www.rfc-editor.org/authors/rfc9915.txt
https://www.rfc-editor.org/authors/rfc9915.pdf
https://www.rfc-editor.org/authors/rfc9915.html
https://www.rfc-editor.org/authors/rfc9915.xml
The relevant diff files have been posted here (please refresh):
https://www.rfc-editor.org/authors/rfc9915-diff.html (comprehensive diff)
https://www.rfc-editor.org/authors/rfc9915-rfcdiff.html (comprehensive side by
side)
https://www.rfc-editor.org/authors/rfc9915-auth48diff.html (AUTH48 changes only)
https://www.rfc-editor.org/authors/rfc9915-auth48rfcdiff.html (AUTH48 side by
side)
https://www.rfc-editor.org/authors/rfc9915-lastdiff.html (last version to this)
https://www.rfc-editor.org/authors/rfc9915-lastrfcdiff.html (last to this side
by side)
Please contact us with any further updates/questions/comments you may
have.
We will await approvals from each of the parties listed on the AUTH48 status
page prior to moving forward to publication.
The AUTH48 status page for this document is available here:
https://www.rfc-editor.org/auth48/rfc9915
Thank you.
Megan Ferguson
RFC Production Center--
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]
