Dear all,

The call for working group adoption ended some time ago, it seems
numerous people are in favor of progressing this work in the GROW
working group.

Authors - please resubmit this draft as 'draft-ietf-grow-bmp-tlv-ebit'

Kind regards,

Job
GROW co-chair

On Fri, Apr 08, 2022 at 04:19:19PM +0200, Job Snijders wrote:
> 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

Reply via email to