Subject: [GROW] Fwd: New Version Notification for draft-lucente-grow-bmp-tlv-ebit-00.txt

From: Paolo Lucente <[email-masked]>
Date: Sat, 2 Nov 2019 07:39:41 +0000

Dear GROW WG,

We have submitted draft-lucente-grow-bmp-tlv-ebit-00.txt . We would like to get opportunity to present it in Singapore (IETF 106) and would much welcome feedback on list meanwhile. Abstract below for your convenience.

Paolo

Begin forwarded message:

From: [email-masked]<mailto:[email-masked]>
Subject: New Version Notification for draft-lucente-grow-bmp-tlv-ebit-00.txt
Date: 2 November 2019 at 08:12:07 CET
To: "Paolo Lucente" <[email-masked]<mailto:[email-masked]>>, "Yunan Gu" <[email-masked]<mailto:[email-masked]>>

A new version of I-D, draft-lucente-grow-bmp-tlv-ebit-00.txt
has been successfully submitted by Paolo Lucente and posted to the
IETF repository.

Name: draft-lucente-grow-bmp-tlv-ebit
Revision: 00
Title: Support for Enterprise-specific TLVs in the BGP Monitoring Protocol
Document date: 2019-10-31
Group: Individual Submission
Pages: 6
URL:            https://www.ietf.org/internet-drafts/draft-lucente-grow-bmp-tlv-ebit-00.txt
Status:         https://datatracker.ietf.org/doc/draft-lucente-grow-bmp-tlv-ebit/
Htmlized:       https://tools.ietf.org/html/draft-lucente-grow-bmp-tlv-ebit-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-tlv-ebit

Abstract:
  Message types defined by the BGP Monitoring Protocol (BMP) do
  provision for optional trailing data in TLV - Type, Length, Value -
  format; 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.  With this document we
  want to introduce an Enterprise Bit, or E-bit, for such purpose.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat