Hi Jeff, Thank you very much for your feedback.
The idea was that a vendor using this route type could use a value unique to them. In case of not having an OUI, the registration of a new one with the IEEE should be pretty straight forward. We’ll add the informal reference that you mention, thanks. If needed, we are also open to use a generic OUI value that anyone can use. Thanks. Jorge From: BESS <[email protected]> on behalf of Jeff Tantsura <[email protected]> Date: Tuesday, August 20, 2019 at 7:24 PM To: "[email protected]" <[email protected]>, Stephane Litkowski <[email protected]> Subject: Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07 In general I support the adoption. Could the authors please clarify how a company that doesn’t have OUI assigned should populate the OUI field and how interdependency between IEEE registration and EVPN implementation would be handled. Informal references for IEEE OUI handling process would be useful too, perhaps this one - https://standards.ieee.org/products-services/regauth/tut/index.html Cheers, Jeff On Aug 20, 2019, 5:15 AM -0400, Stephane Litkowski <[email protected]>, wrote: Hi, This email begins a two-weeks WG adoption poll for draft-rabadan-bess-vendor-evpn-route-07 [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 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 for adoption closes on 2nd September 2019. Regards, Stephane and Matthew [1] https://datatracker.ietf.org/doc/draft-rabadan-bess-vendor-evpn-route/ _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
