[auth48] Re: AUTH48: RFC-to-be 9845 for your review

Authors, While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file. 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18) 19) 20) 21) 22) 23) 24)

[auth48] AUTH48: RFC-to-be 9845 for your review

*IMPORTANT* Updated 2025/08/15 RFC Author(s): -- Instructions for Completing AUTH48 Your document has now entered AUTH48. Once it has been reviewed and approved by you and all coauthors, it will be published as an RFC. If an author is no longer available, there are sever

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

What Paul said. -Tim On Aug 15, 2025 at 9:48:57 PM, Paul Hoffman wrote: > On Aug 15, 2025, at 17:46, Karen Moore > wrote: > > > Hi Paul and Tim, > > > We have noted your approvals on the AUTH48 status page < > https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9839__;!!PtGJab4!7o

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

On Aug 15, 2025, at 17:46, Karen Moore wrote: > > Hi Paul and Tim, > > We have noted your approvals on the AUTH48 status page >

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

Hi Paul and Tim, We have noted your approvals on the AUTH48 status page . Please confirm if you would like to update the text per Rob’s suggestion below. Otherwise, we will move forward with publication. Current (Section 3): [RFC9413], "Maintainin

[auth48] Re: AUTH48: RFC-to-be 9826 for your review

Hi Dhruv, Thank you for your reply. We have updated our files to reflect your changes. We have a few follow-up questions: > 3) > > Dhruv: Maybe the initial revision? For question 12 above, would the following update be correct? Original: The initial document is based on the PCEP MIB [RFC742

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

Hi, Do you want to change this part: "3. Dealing with Problematic Code Points [RFC9413], "Maintaining Robust Protocols"," To "3. Dealing with Problematic Code Points "Maintaining Robust Protocols" [RFC9413], Just because it reads a little weird with an RFC number reference at the start. No big

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

I agree with Paul’s feedback and also have looked at the Auth48 diff and agree that the changes made are correct and responsive to that feedback. I approve this latest version. -Tim On Aug 15, 2025 at 5:02:32 PM, Paul Hoffman wrote: > On Aug 15, 2025, at 12:10, Karen Moore > wrote: > > > We h

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

On Aug 15, 2025, at 12:10, Karen Moore wrote: > > We have updated our files with the suggested updates. Please review and let > us know if any further updates are needed or if you approve the document in > its current form. > > We will await approvals from each author prior to moving forward i

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

Hi Paul, We have updated our files with the suggested updates. Please review and let us know if any further updates are needed or if you approve the document in its current form. We will await approvals from each author prior to moving forward in the publication process. --FILES-- Note that i

[auth48] Re: AUTH48: RFC-to-be 9768 for your review

Hi Mirja, Thanks for your close review and the explanations provided. We have updated the document as described below. We will wait to hear from Richard and/or Bob regarding this the author comments in the XML file. In addition, this question should have been included previously. Please let

[auth48] Re: [Ext] [AD] Re: AUTH48: RFC-to-be 9839 for your review

Thanks for the edits on this document! Comments below. > 1) “Unicode”, “UTF-8”, “Surrogates”, “Noncharacters”, “Control characters” > 2) Sure. > 3) We prefer option B. > 4) This is correct. We even asked a careful external reviewer to check, and he approved as well. > 5) This is co

[auth48] Re: AUTH48: RFC-to-be 9788 for your review

Hi Authors, Thank you for the updated XML file. We have updated the other document files accordingly; see below. Once we have received Bernie's approval, we will ask IANA to update their registry accordingly. After the IANA updates are complete, we will move this document forward in the public

[auth48] Re: AUTH48: RFC-to-be 9787 for your review

Hi Authors , Thank you for the updated XML file. We have updated the other document files accordingly; see below. We will await Bernie’s approval prior to moving this document forward in the publication process. Please see the AUTH48 status page for this document here: https://www.rfc-editor.o