Support adoption of this draft. Few editorial comments The draft seems related closely to "draft-ietf-bess-bgp-sdwan-usage", but does not seem to refer to this. Shouldn't a reference be included and terminology be aligned? The main use case is the use of the public Internet for transport - In this context I found the term PE a bit confusing (bgp-sdwan uses c-pe) - Does this imply secure EVPN applicability is IP based underlays ? Restrictions regarding underlay technology could be included for clarity
cheers, Eduard On Thu, May 25, 2023 at 12:36 PM Matthew Bocci (Nokia) < [email protected]> wrote: > Hello, > > > > This email begins a two-week > WG adoption poll for draft-sajassi-bess-secure-evpn-06 [1]. > > Please review the draft and post any comments to the BESS working group > 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, copying the BESS mailing list. The document will > not progress without answers from all the authors and contributors. > > Currently, there is currently no IPR disclosure 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 for adoption closes on June 9th 2023 > > > > Regards, > > Matthew and Stephane > > > > [1] https://datatracker.ietf.org/doc/html/draft-sajassi-bess-secure-evpn > > > _______________________________________________ > BESS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/bess >
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
