I support the publication of the draft as an RFC. Below are some minor editorial comments.
Anoop == Multiple sections Probably better to replace all uses of Ethernet Segment with ES rather than use them at random. Section 1 Expand first use of "SID". will keeo following -> will keep following Section 2.2 A value of 01 indicates the intend to use -> A value of 01 indicates the intent to use A value of 10 indicates the intend to use -> A value of 10 indicates the intent to use On Wed, Jan 26, 2022 at 1:50 AM <[email protected]> wrote: > Hello Working Group, > > > > This email starts a two weeks Working Group Last Call on > draft-ietf-bess-evpn-mh-split-horizon [1]. > > > > This poll runs until *the 9th of Feb*. > > > > 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. > > > > There is no IPR currently disclosed. > > > > 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. > > > > We are also polling for any existing implementation as per [2]. > > > > Thank you, > > Stephane & Matthew > > > > [1] > https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-mh-split-horizon/ > > [2] > https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > _______________________________________________ > BESS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/bess >
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
