Thank you all for making this happen. Stig and I appreciate all of the hard work.
mike On Fri, Mar 21, 2025 at 3:21 AM Karen Moore <kmo...@staff.rfc-editor.org> wrote: > Hello Gunter, > > Thank you for your reply. We have noted your approval on the AUTH48 status > page (https://www.rfc-editor.org/auth48/rfc9777). > > We now have all approvals for this document and will move it forward in > the publication process (along with RFCs-to-be 9776 and 9778). > > Thank you to Brian for working closely with us on this cluster during > AUTH48 and to all who have contributed their time! > > Best regards, > RFC Editor/kc > > > On Mar 19, 2025, at 11:49 PM, Gunter van de Velde (Nokia) < > gunter.van_de_ve...@nokia.com> wrote: > > > > Hi, > > > > I looked at https://www.rfc-editor.org/authors/rfc9777-auth48diff.html > Table 6 in section 7.3 and approve. > > > > Take care, > > G/ > > > > -----Original Message----- > > From: Karen Moore <kmo...@staff.rfc-editor.org> > > Sent: Thursday, March 20, 2025 1:13 AM > > To: Brian Haberman <br...@innovationslab.net>; Gunter van de Velde > (Nokia) <gunter.van_de_ve...@nokia.com> > > Cc: RFC Errata System <rfc-edi...@rfc-editor.org>; pim-...@ietf.org; > pim-cha...@ietf.org; s...@venaas.com; auth48archive < > auth48archive@rfc-editor.org> > > Subject: Re: [AD] [auth48] AUTH48: RFC-to-be 9777 > <draft-ietf-pim-3810bis-12> for your review > > > > > > CAUTION: This is an external email. Please be very careful when clicking > links or opening attachments. See the URL nok.it/ext for additional > information. > > > > > > > > Hi Brian, > > > > Thank you for providing your approval; it is noted on the AUTH48 status > page for this document (https://www.rfc-editor.org/auth48/rfc9777). > > > > We now await approval from Gunter (for the new text in Table 6 in > Section 7.3) before proceeding with publication. > > > > Best regards, > > RFC Editor/kc > > > >> On Mar 19, 2025, at 3:30 AM, Brian Haberman <br...@innovationslab.net> > wrote: > >> > >> Approved! > >> > >>> On Mar 18, 2025, at 8:40 PM, Karen Moore <kmo...@staff.rfc-editor.org> > wrote: > >>> > >>> Hi Brian and *Gunter (AD), > >>> > >>> Our files have been updated to reflect “source-list” and > “filter-mode”. Please review and let us know if any further changes are > needed or if you approve the document in its current form. > >>> > >>> *Gunter, please review the added text to Table 6 in Section 7.3 as > well as the updates made to the terminology (see list below) and let us > know if you approve. The changes can be reviewed in this file: > https://www.rfc-editor.org/authors/rfc9777-auth48diff.html (see > https://www.rfc-editor.org/authors/rfc9777.txt to read the text in the > Table 6 easier). > >>> > >>> Terms changed to the latter form: > >>> Other Querier Present Timeout --> Other Querier Present Interval > >>> Older Version Host Present Timeout --> Older Version Host Present > >>> Interval Older Version Querier Present Timeout -- > Older Version > >>> Querier Present Interval > >>> > >>> —Files (please refresh)— > >>> The updated XML file is here: > >>> https://www.rfc-editor.org/authors/rfc9777.xml > >>> > >>> The updated output files are here: > >>> https://www.rfc-editor.org/authors/rfc9777.txt > >>> https://www.rfc-editor.org/authors/rfc9777.pdf > >>> https://www.rfc-editor.org/authors/rfc9777.html > >>> > >>> These diff files show all changes made during AUTH48: > >>> https://www.rfc-editor.org/authors/rfc9777-auth48diff.html > >>> https://www.rfc-editor.org/authors/rfc9777-auth48rfcdiff.html (side > >>> by side) > >>> > >>> These diff files show only the changes made during the last edit round: > >>> https://www.rfc-editor.org/authors/rfc9777-lastdiff.html > >>> https://www.rfc-editor.org/authors/rfc9777-lastrfcdiff.html (side by > >>> side) > >>> > >>> These diff files show all changes made to date: > >>> https://www.rfc-editor.org/authors/rfc9777-diff.html > >>> https://www.rfc-editor.org/authors/rfc9777-rfcdiff.html (side by > >>> side) > >>> > >>> Best regards, > >>> RFC Editor/kc > >>> > >>> > >>>> On Mar 18, 2025, at 7:22 AM, Brian Haberman <br...@innovationslab.net> > wrote: > >>>> > >>>> Hi Karen, > >>>> All these changes look good. > >>>> > >>>> Please make the “source list” —> “source-list” and “filter mode” —> > “filter-mode” changes per my response on 9776. > >>>> > >>>> Thanks! > >>>> Brian > >>>> > >>>>> On Mar 17, 2025, at 5:53 PM, Karen Moore < > kmo...@staff.rfc-editor.org> wrote: > >>>>> > >>>>> Hi Brian, > >>>>> > >>>>> Thank you for your reply and clarifications. Our files have been > updated to reflect the following changes: > >>>>> > >>>>> - made “filter timer” (when singular) uppercase > >>>>> - made “query message(s)” uppercase > >>>>> - added “Report” to the title of Appendix A.1 (e.g., "State-Change > >>>>> Report Messages”) > >>>>> - hyphenated “Source List Change Report” (e.g., “Source-List-Change > >>>>> Report”) > >>>>> > >>>>> Please review the changes and let us know if any further updates are > needed or if you approve the document in it’s current form. > >>>>> > >>>>> FYI: Questions that were asked in the thread for RFC-to-be 9776 that > pertain to this document: > >>>>> > >>>>> 1) Please confirm if all lowercase instances of “filter mode” should > be “filter-mode” in RFC-to-be 9777 for consistency. > >>>>> > >>>>> 2) Should all instances of “source list” be “source-list” (the > parameter) in RFCs-to-be 9776 and 9777? > >>>>> > >>>>> > >>>>> —Files (please refresh)— > >>>>> The updated XML file is here: > >>>>> https://www.rfc-editor.org/authors/rfc9777.xml > >>>>> > >>>>> The updated output files are here: > >>>>> https://www.rfc-editor.org/authors/rfc9777.txt > >>>>> https://www.rfc-editor.org/authors/rfc9777.pdf > >>>>> https://www.rfc-editor.org/authors/rfc9777.html > >>>>> > >>>>> These diff files show all changes made during AUTH48: > >>>>> https://www.rfc-editor.org/authors/rfc9777-auth48diff.html > >>>>> https://www.rfc-editor.org/authors/rfc9777-auth48rfcdiff.html (side > >>>>> by side) > >>>>> > >>>>> These diff files show only the changes made during the last edit > round: > >>>>> https://www.rfc-editor.org/authors/rfc9777-lastdiff.html > >>>>> https://www.rfc-editor.org/authors/rfc9777-lastrfcdiff.html (side > >>>>> by side) > >>>>> > >>>>> These diff files show all changes made to date: > >>>>> https://www.rfc-editor.org/authors/rfc9777-diff.html > >>>>> https://www.rfc-editor.org/authors/rfc9777-rfcdiff.html (side by > >>>>> side) > >>>>> > >>>>> Best regards, > >>>>> RFC Editor/kc > >>>>> > >>>>> > >>>>>> On Mar 17, 2025, at 7:26 AM, Brian Haberman < > br...@innovationslab.net> wrote: > >>>>>> > >>>>>> Hi Karen, > >>>>>> > >>>>>>> On Mar 14, 2025, at 6:34 PM, Karen Moore < > kmo...@staff.rfc-editor.org> wrote: > >>>>>>> > >>>>>>> Hi Brian, > >>>>>>> > >>>>>>> Thank you for providing the XML files with updates to the > terminology (per the cluster-wide questions) and answers to our questions. > We have added further updates based on your replies; the updated files are > below. Please see some additional questions/clarifications. > >>>>>>> > >>>>>>> 1) Please let us know if you would like to add any keywords > (beyond those in the title) for use on https://www.rfc-editor.org/search. > >>>>>>> > >>>>>> > >>>>>> Nothing to add. > >>>>>> > >>>>>>> 2) We did not see a reply to this question: > >>>>>>> > >>>>>>> Because this document will likely be published at the same time as > 3376bis, we have updated the reference to refer to RFC 9776. Please let us > know if any corrections are needed. > >>>>>>> > >>>>>>> Please consider whether it is appropriate to refer to [BCP57] and > [STD100], or if referring to the specific RFCs is preferred. > >>>>>>> > >>>>>> > >>>>>> Given the relationship between the documents, I would suggest > keeping the reference to 9776. > >>>>>> > >>>>>>> 3) In RFCs-to-be 9776 and 9777, “Source Timer” is uppercase when > singular; otherwise, the plural form is lowercase. In RFC-to-be 9777, > “filter timer” is lowercase in the running text and uppercase in tables. > Are any further updates needed for consistency (i.e., make the singular > form of “filter timer” uppercase in the running text)? > >>>>>> > >>>>>> The singular form should be capitalized as it refers to a specific > instance. When being referred to in a collection (e.g., source timers), we > kept it lowercase. Please make it consistent. > >>>>>> > >>>>>>> > >>>>>>> 4) We hyphenated some instances of “State Change Report” for > consistency (e.g., “State-Change Report”). This term is also hyphenated in > RFC-to-be 9776. > >>>>>>> > >>>>>> > >>>>>> Correct. > >>>>>> > >>>>>>> We also hyphenated “State Change Record” and “State Change > Messages”; if that is not preferred, please let us know. Should > “State-Change Messages” (title of A.1) perhaps be “State-Change Report > Messages”? > >>>>>>> > >>>>>> > >>>>>> Yes, the title of the appendix should be updated as noted. > >>>>>> > >>>>>>> 5) In the running text, we updated "MLDv2 Multicast Listener > Report” to "Version 2 Multicast Listener Report” (2 instances) to match the > “ICMPv6 “type” Numbers" registry < > https://www.iana.org/assignments/icmpv6-parameters>. > >>>>>>> > >>>>>>> In the running text, we made the following updates (1 instance > each) for consistency and to match the registry. If it is not preferred to > include the values here, please let us know. > >>>>>>> > >>>>>>> Version 1 Multicast Listener Done -> MLDv1 Multicast Listener > >>>>>>> Done (Type = decimal 132) Version 1 Multicast Listener Report -> > >>>>>>> MLDv1 Multicast Listener Report (Type = decimal 131) > >>>>>>> MLDv1 Multicast Listener Report -> MLDv1 Multicast Listener > >>>>>>> Report (Type = decimal 131) > >>>>>>> > >>>>>> > >>>>>> All good changes! > >>>>>> > >>>>>> Regards, > >>>>>> Brian > >>>>>> > >>>>> > >>>> > >>> > >> > > > >
-- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
