[GROW] I-D Action: draft-ietf-grow-bmp-tlv-ebit-05.txt

internet-drafts@ietf.org Tue, 19 March 2024 04:50 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: grow@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: grow@ietf.org
Message-ID: <171082380711.46506.6394431167067579486@ietfa.amsl.com>
Date: Mon, 18 Mar 2024 21:50:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/FvXEqYX5uIi5hRVcAoOi6CH8jDI>
Subject: [GROW] I-D Action: draft-ietf-grow-bmp-tlv-ebit-05.txt

Internet-Draft draft-ietf-grow-bmp-tlv-ebit-05.txt is now available. It is a
work item of the Global Routing Operations (GROW) WG of the IETF.

   Title:   Support for Enterprise-specific TLVs in the BGP Monitoring Protocol
   Authors: Paolo Lucente
            Yunan Gu
   Name:    draft-ietf-grow-bmp-tlv-ebit-05.txt
   Pages:   7
   Dates:   2024-03-18

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 a TLV message body, ie.  Route Mirroring and Stats
   Reports, or optional TLVs at the end of a BMP message, ie.  Peer Up
   and Peer Down.  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 IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-tlv-ebit/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-ebit-05

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bmp-tlv-ebit-05

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[GROW] I-D Action: draft-ietf-grow-bmp-tlv-ebit-0… internet-drafts