Dear Grow WG I think this is very useful work and I support WG adoption.
I think this idea of vendor specific TLV E bit id very helpful for interoperability between vendors during early pre standard development phases when vendors have proprietary features. This may also help operators to get involved in early development phase with this circumvention of interoperability. Kind Regards Gyan On Wed, Apr 13, 2022 at 3:59 AM Benoit Claise <benoit.claise= [email protected]> wrote: > Dear all, > > I specifically appreciate the reuse of the IPFIX PEN mechanism, which > facilitates an efficient a collection system for combined data and > control plane monitoring. Hence support. > > Regards, Benoit > > On 4/13/2022 3:51 AM, Zhuangshunwan wrote: > > Hi GROW WG, > > > > I have read this document and participated in the previous discussion of > the proposal. I think it is a very useful document and I support its > adoption. > > > > Kindest Regards, > > Shunwan > > > >> -----Original Message----- > >> From: GROW [mailto:[email protected]] On Behalf Of Job Snijders > >> Sent: Friday, April 8, 2022 10:19 PM > >> To: [email protected] > >> Subject: [GROW] Working Group Adoption Call: > >> draft-lucente-grow-bmp-tlv-ebit (Ends 02/May/2022) > >> > >> Hi GROW, > >> > >> At the IETF 113 GROW session Paolo asked whether this working group > could > >> consider adoption for draft-lucente-grow-bmp-tlv-ebit. > >> > >> This message is a request to the group for feedback on whether this > >> internet-draft should be adopted. > >> > >> Title: > >> Support for Enterprise-specific TLVs in the BGP Monitoring Protocol > >> Abstract: > >> Message types defined by the BGP Monitoring Protocol (BMP) do > >> provision for data in TLV - Type, Length, Value - format, either in > >> the shape of optional TLVs at the end of a BMP message or Stats > >> Reports TLVs. However the space for Type value is unique and > >> governed by IANA. To allow the usage of vendor-specific TLVs, a > >> mechanism to define per-vendor Type values is required. In this > >> document we introduce an Enterprise Bit, or E-bit, for such purpose. > >> > >> The Internet-Draft can be found here: > >> https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-tlv-ebit > >> > >> Please share with the mailing list if you are think this work should be > >> adopted by GROW, willing to review and/or otherwise contribute to this > >> draft! > >> > >> WG Adoption call ends May 2nd, 2022. > >> > >> Kind regards, > >> > >> Job > >> > >> _______________________________________________ > >> GROW mailing list > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/grow > > _______________________________________________ > > GROW mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/grow > > . > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email [email protected] <[email protected]>* *M 301 502-1347*
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
