Hi Alice, thank you for your question. I think that the appropriate level of reference to draft-ietf-mpls-p2mp-bfd is normative.
Regards, Greg On Tue, May 6, 2025 at 1:23 PM Alice Russo <aru...@staff.rfc-editor.org> wrote: > David and coauthors, > > Thank you for your reply, David; your information has been updated as > requested. A reference question: > > Should draft-ietf-mpls-p2mp-bfd be a normative reference because of the > "MUST" in the "For IPv6" sentence in Section 2.3 (pasted below)? We note > that draft is currently in AUTH48 state as RFC-to-be 9870. If you make the > reference normative, then this document will refer to it by RFC number, and > they will be published at the same time. > > Inner IP header: > Destination IP: The IP address MUST be set to the loopback > address 127.0.0.1/32 for IPv4 version. For IPv6, the address > MUST be selected from the Dummy IPv6 Prefix 100:0:0:1::/64 > [P2MP-BFD]. > > For background, "Normative references specify documents that must be read > to understand or implement the technology in the new RFC, or whose > technology must be present for the technology in the new RFC to work." -- > quoting the IESG statement ( > https://datatracker.ietf.org/doc/statement-iesg-iesg-statement-normative-and-informative-references-20060419/ > ). > > > Re: David's updates > > The revised files are here (please refresh): > https://www.rfc-editor.org/authors/rfc9772.html > https://www.rfc-editor.org/authors/rfc9772.txt > https://www.rfc-editor.org/authors/rfc9772.pdf > https://www.rfc-editor.org/authors/rfc9772.xml > > This diff file shows all changes from the approved I-D: > https://www.rfc-editor.org/authors/rfc9772-diff.html > https://www.rfc-editor.org/authors/rfc9772-rfcdiff.html (side by side) > > This diff file shows only the changes since the last posted version: > https://www.rfc-editor.org/authors/rfc9772-lastrfcdiff.html > > Re: > > With those changes, I approve the resulting document. > > We have recorded your approval. This page shows the AUTH48 status > of your document: > https://www.rfc-editor.org/auth48/rfc9772 > > Thank you. > RFC Editor/ar > > > On May 6, 2025, at 1:03 PM, Black, David <david.bl...@dell.com> wrote: > > > > Hi Alice, > > > > I have reviewed the document and the changes made by the RFC Editor. > All of the changes are fine – the RFC Editor has done the usual thorough > job of editing, and your attention to the details is greatly appreciated. > > > > Please change my affiliation from “Dell EMC” to “Dell” and remove the > physical/postal mail address (“176 South Street Hopkinton, MA, 01748 > United States of America”). With those changes, I approve the resulting > document. > > > > Thanks, --David > > > > From: Greg Mirsky <gregimir...@gmail.com> > > Sent: Monday, May 5, 2025 4:59 PM > > To: Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com> > > Cc: Alice Russo <aru...@staff.rfc-editor.org>; sbout...@ciena.com; > Black, David <david.bl...@dell.com>; santosh.pallaga...@gmail.com; > nvo3-...@ietf.org; nvo3-cha...@ietf.org; Matthew Bocci (Nokia) < > matthew.bo...@nokia.com>; auth48archive@rfc-ed < > auth48archive@rfc-editor.org>; RFC Editor <rfc-edi...@rfc-editor.org> > > Subject: Re: [AD] Re: AUTH48: RFC-to-be 9772 > <draft-ietf-nvo3-geneve-oam-16> for your review > > > > [EXTERNAL EMAIL] > > > > Hi Alice, > > to get on the record, I approve it. > > > > Regards, > > Greg > > >
-- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
