Hi Carlos, thank you for your support and the comment about the reference to BFD for Multipoint Networks draft. You have a point, and I agree that the sentence and thus the reference can be removed altogether. I'll check with other authors and will update the group accordingly.
Regards, Greg On Thu, Oct 25, 2018 at 9:07 PM Carlos Pignataro (cpignata) < cpign...@cisco.com> wrote: > +1. Support publication as this is useful and technically sound. > > I do not understand why [I-D.ietf-bfd-multipoint] is a Normative > reference, or frankly a reference at all. I do not think there’s a need to > reference every potential thin outside scope. > > Thanks, > > — Carlos Pignataro > > On Oct 22, 2018, at 9:56 AM, Donald Eastlake <d3e...@gmail.com> wrote: > > I support publication of this draft. It is a useful OAM building block. > > Thanks, > Donald > =============================== > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > 1424 Pro Shop Court, Davenport, FL 33896 USA > d3e...@gmail.com > > > On Wed, Oct 17, 2018 at 6:14 PM Jeffrey Haas <jh...@pfrc.org> wrote: > >> Working Group, >> >> This starts the Working Group Last Call for BFD for VxLAN. This last call >> ends the Friday after IETF, November 9. >> >> https://datatracker.ietf.org/doc/draft-ietf-bfd-vxlan/ >> >> Please comment whether you believe this document is ready to advance or >> not.. >> >> There is currently one IPR statement on this draft: >> https://datatracker.ietf.org/ipr/3193/ >> >> Authors, please publicly state to the mailing list whether you know of any >> additional IPR that impacts this draft. >> >> -- Jeff & Reshad >> >> >> >> ----- Forwarded message from Greg Mirsky <gregimir...@gmail.com> ----- >> >> Date: Mon, 8 Oct 2018 07:47:19 -0700 >> From: Greg Mirsky <gregimir...@gmail.com> >> To: rtg-bfd WG <rtg-bfd@ietf.org>, Marc Binderberger <m...@sniff.de> >> Cc: bfd-cha...@ietf.org >> Subject: Fwd: New Version Notification for draft-ietf-bfd-vxlan-03.txt >> >> Dear All, >> the new version is to address comments from Marc (big thank you, Marc). >> Please note that IDNits err on downref to the normative reference >> to Informational RFC 7348. >> >> Regards, >> Greg >> >> >
