[GROW] draft-lucente-grow-bmp-tlv-ebit

Paolo Lucente <paolo@ntt.net> Mon, 17 January 2022 16:28 UTC

Return-Path: <paolo@ntt.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC9533A1320 for <grow@ietfa.amsl.com>; Mon, 17 Jan 2022 08:28:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level:
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_f5gxL6waj3 for <grow@ietfa.amsl.com>; Mon, 17 Jan 2022 08:28:47 -0800 (PST)
Received: from mail4.dllstx09.us.to.gin.ntt.net (mail.gin.ntt.net [IPv6:2001:418:3ff:5::192:26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08D563A1367 for <grow@ietf.org>; Mon, 17 Jan 2022 08:28:46 -0800 (PST)
Received: from [IPV6:2001:418:1456:b09::100d] (unknown [IPv6:2001:418:1456:b09::100d]) by mail4.dllstx09.us.to.gin.ntt.net (Postfix) with ESMTPSA id 809A0EE0144 for <grow@ietf.org>; Mon, 17 Jan 2022 16:28:44 +0000 (UTC)
Message-ID: <4d619c8b-c4c8-c1af-b17c-ed7b9327f964@ntt.net>
Date: Mon, 17 Jan 2022 17:28:42 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
From: Paolo Lucente <paolo@ntt.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/uVhDc4UzbcdPLC_-7AlHuBoOk5I>
Subject: [GROW] draft-lucente-grow-bmp-tlv-ebit
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 16:28:49 -0000

Dear WG colleagues,

A brief email to say i have just refreshed 
draft-lucente-grow-bmp-tlv-ebit to version -02.

The draft expired already for some time, my bad, despite we authors did 
receive some useful feedback at the end of 2020 from Jeff Haas, Thomas 
Graf and Pierre Francois that has now been incorporated in -02.

Maybe it would be also a good idea - if WG chairs are already looking 
for topics for IETF 113 - to present the content of this draft again at 
our next meeting to refresh our minds a bit.

Paolo



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

Name:		draft-lucente-grow-bmp-tlv-ebit
Revision:	02
Title:		Support for Enterprise-specific TLVs in the BGP Monitoring Protocol
Document date:	2022-01-17
Group:		Individual Submission
Pages:		6
URL: 
https://www.ietf.org/archive/id/draft-lucente-grow-bmp-tlv-ebit-02.txt
Status: 
https://datatracker.ietf.org/doc/draft-lucente-grow-bmp-tlv-ebit/
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-lucente-grow-bmp-tlv-ebit
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-lucente-grow-bmp-tlv-ebit-02

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.