Hi Xiao Min, thank you for your suggestions. I've updated the draft to address your concern. Please let me know if you agree with the changes highlighted in the attached diff (the working version also includes updates that address the editorial updates suggested by Donald Eastlake).
Regards, Greg On Tue, Jul 4, 2023 at 1:12 AM <xiao.m...@zte.com.cn> wrote: > Hi all, > > > I support progressing this document to publication. > > At the same time, I strongly suggest the authors to rethink about the > scope of this document. > > This document introduces two cases of using active OAM protocols for > Geneve, the first case is to use the Management VNI, and the second case is > to use the VNIs really deployed in the NVE, that's fine to me. However, > it's said that the OAM encapsulation defined in Section 2.2 can be used for > both cases, I don't think so. As specified in draft-ietf-nvo3-bfd-geneve, > in order to use the VNIs really deployed, VAP based OAM solution is > necessary, i.e., the MAC/IP address of VAP must be used as long as it's > available, and then the VNI can be identified through VAP-to-VNI mapping. > Besides, for the second case, both Ethernet over Geneve encap and IP over > Geneve encap are needed. So with that said, the OAM encap defined in > Section 2.2 can be slightly tweaked to be applicable to the first case > only, and the OAM encap for the second case can be made outside the scope > of this document. > > > Best Regards, > > Xiao Min > Original > *From: *SamAldrin <aldrin.i...@gmail.com> > *To: *NVO3 <nvo3@ietf.org>;nvo3-cha...@ietf.org <nvo3-cha...@ietf.org>; > draft-ietf-nvo3-geneve-...@ietf.org <draft-ietf-nvo3-geneve-...@ietf.org>; > *Date: *2023年06月28日 14:27 > *Subject: **[nvo3] Working Group Last Call and IPR Poll for > draft-ietf-nvo3-geneve-oam-07* > _______________________________________________ > nvo3 mailing list > nvo3@ietf.org > https://www.ietf.org/mailman/listinfo/nvo3 > > This email begins a two-week working group last call for > draft-ietf-nvo3-geneve-oam-07 > > (https://datatracker.ietf.org/doc/draft-ietf-nvo3-geneve-oam/ > <https://datatracker.ietf.org/doc/draft-ietf-nvo3-bfd-geneve/>). > > > > Please review the draft and post any comments to the NVO3 working group > list. If you have read the latest version of the draft but have no comments > and believe it is ready for publication as an informational RFC, please > also indicate so to the WG email list. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as an Author or a Contributor of this document, please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > > > Currently there are no IPR disclosures against this document. > > > > If you are not listed as an Author or a Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet been > disclosed in conformance with IETF rules. > > > > This poll will run until Friday 12th July 2023. > > > > Regards > > > > Sam and Matthew > > >
<<< text/html; charset="US-ASCII"; name="draft-ietf-nvo3-geneve-oam-08.diff.html": Unrecognized >>>
_______________________________________________ nvo3 mailing list nvo3@ietf.org https://www.ietf.org/mailman/listinfo/nvo3
