Working Group, draft-spallagatti-bfd-vxlan has been adopted by the working group. (And I'm only four days late in replying to the long adoption!)
Authors, please resubmit as draft-ietf-bfd-vxlan. Also, Authors, since my impression is that there are already multiple interoperable implementations of the draft, please consider pushing hard to reach the point where we can publish this ASAP. :-) If the implementations are already publicly done, please unicast me and I'll add them to the BFD status page on the wiki. -- Jeff On Wed, Jan 03, 2018 at 10:49:25AM -0500, Jeffrey Haas wrote: > Working Group, > > As a reminder, we have an active adoption call for the BFD for vxlan > document. We've seen support for it on the list, but a few more people > offering commentary from outside of the author's list would be helpful. :-) > > -- Jeff > > On Thu, Dec 21, 2017 at 07:15:17AM -0800, IETF Secretariat wrote: > > The BFD WG has placed draft-spallagatti-bfd-vxlan in state > > Call For Adoption By WG Issued (entered by Jeffrey Haas) > > > > The document is available at > > https://datatracker.ietf.org/doc/draft-spallagatti-bfd-vxlan/ > > > > Comment: > > The authors of draft-spallagatti-bfd-vxlan have asked for adoption of their > > draft by the BFD working group. The BFD working group is chosen because the > > document has implications on base RFC 5880 procedures. > > > > Given the nature of the document, co-review and coordinated working group > > last call with the nvo3 Working Group is expected. > > > > The last date for comments for this adoption is January 20. This extended > > period is intended to accommodate end of year holidays. > > > > A final note is that adoption is contingent upon our AD confirming this is > > within current WG charter, or permitting us otherwise to re-charter > > appropriately.
