Re: [GROW] I-D Action: draft-ietf-grow-bmp-path-marking-tlv-00.txt

Luuk Hendriks <luuk@nlnetlabs.nl> Tue, 24 October 2023 09:44 UTC

Return-Path: <luuk@nlnetlabs.nl>
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 44633C14CF17 for <grow@ietfa.amsl.com>; Tue, 24 Oct 2023 02:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nlnetlabs.nl
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VsJiCtVAGEM for <grow@ietfa.amsl.com>; Tue, 24 Oct 2023 02:44:28 -0700 (PDT)
Received: from mout-b-110.mailbox.org (mout-b-110.mailbox.org [195.10.208.55]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E094C14CF13 for <grow@ietf.org>; Tue, 24 Oct 2023 02:44:25 -0700 (PDT)
Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-110.mailbox.org (Postfix) with ESMTPS id 4SF6b840cRz9vQ9; Tue, 24 Oct 2023 11:44:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nlnetlabs.nl; s=MBO0001; t=1698140660; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hjJagSJxycG/is7tkaGo6G+JakVnIYlqGPTfu3ZPLQk=; b=EnuEG55WF2XOKlV2S/HRFQjXtYbt/iprQYlJgTJOmJgKl+K5UzrhiDOgFDOI+Ndz9uqvvg /mmLeNCrnfkE1XBwNg7v598sbnioVuruuEy4iKOa20RRAJH8/JfZFr1C427LS4kqTjJFYm H2fIaahOn3x3xEUVz9FmR0h9+yYUKrDucVSXMTlLLVBgVKQQuY1C1VslHCk65kJXUJCmdI yMmkvgl4tfeKrklrziEBiBkSo0SVRZ0Gt82o76Jkz7TnAHl8/urx0MGYyI763Cvbl2I7Yp ODYDlQBsn3/j+l8yBKnvkf+jOqyKBYgws/SP21uaoCFDvuYGfvVzvozObOdngQ==
Date: Tue, 24 Oct 2023 11:44:19 +0200
From: Luuk Hendriks <luuk@nlnetlabs.nl>
To: Camilo Cardona <juancamilo.cardona@imdea.org>
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Message-ID: <ZTeR8wYZk1M95qbi@corley.shackle.nl>
References: <169461402395.58243.17951039358048107442@ietfa.amsl.com> <56F998CC-D877-4F64-ADCA-D66C8B70D884@imdea.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <56F998CC-D877-4F64-ADCA-D66C8B70D884@imdea.org>
X-Rspamd-Queue-Id: 4SF6b840cRz9vQ9
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/8xg6d5dmo5Xq4CcyGtfSDAuxhoI>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-path-marking-tlv-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 24 Oct 2023 09:44:33 -0000

Hi Camilo, all,


I remember being confused when reading the previous version about which
Path Statuses would apply to which RIBs, whether they apply to only a
single RIB or perhaps multiple, etc. The implementation note described
in 3.3 clears that up, and I think it deserves a more prominent place
earlier on in the document eventually.

All those implementation seem very useful and good food for thought,
thanks for adding them. Regarding the alternatives for combining
standard and enterprise status (3.4), do you think we have enough bits
available for replication of the standard definitions in the enterprise
space (option #1)? With the currently listed 11 statuses, the 11 LSB
bits are used, perhaps a couple more should be reserved (16 in total?
20?) for the standard definitions. That leaves 16 or 12 bits for the
actual enterprise statuses.
Might very well be sufficient, but at the same time it's sort of scarce
and new statuses should be defined with care.



Some nits:

Sec 1:

    'or in the BMP Update Message'
    ->
    'or in the BMP Route Monitoring Message' ?

    'BMP server'
    ->
    'BMP station' (for consistency with other documents)

Sec 2.1

If no reason code is carried, according to the text 'this field is
empty'. Does that mean it's two bytes worth of zeroes (MUST be zeroes)?
Or is the field omitted altogether? In other words, is the Length always
6, or is it 4 whenever there is no reason code?

The caption under Table 2 says 'Path Type' while the text uses the term
'Path Status'. There are 11 entries in the table, the text mentions '10'.


In Table 2, Reason Code 0x0007 is listed twice.


Sec 2.2

The second bullet point under Figure 3 says 'Type = 1 (15 bits)', I
think that ' = 1' is an (incorrect) leftover and should go?

The ordering of bullet points is inconsistent with the figure, i.e.
'PEN' is explained after Index is. Also with the 'N' meaning 'Number'
already, the 'Number' in 'PEN Number' is redundant.
Super nit: the capitalization of octets/Octets is inconsistent in those
bullet points.



Thanks,
 luuk




On Tue 19 Sep 2023, 11:36, Camilo Cardona wrote:
> Hello Grow,  
> 
> There is a new version of the draft-ietf-grow-bmp-path-marking, now a working group document.   
> 
> Compared to the previous version, we added some notes regarding implementation. Many of them were discussed thanks to the work from Maxence Younsi, who implemented the feature in FRRouting. He presented his work in the previous GROW session.  
> 
> Please give it a read, and let us know if there are any thoughts, criticism, etc.  
> 
> Thanks, 
> Draft authors
> 
> 
> > On 13 Sep 2023, at 09:07, internet-drafts@ietf.org wrote:
> > 
> > Internet-Draft draft-ietf-grow-bmp-path-marking-tlv-00.txt is now available.
> > It is a work item of the Global Routing Operations (GROW) WG of the IETF.
> > 
> >   Title:   BMP Extension for Path Status TLV
> >   Authors: Camilo Cardona
> >            Paolo Lucente
> >            Pierre Francois
> >            Yunan Gu
> >            Thomas Graf
> >   Name:    draft-ietf-grow-bmp-path-marking-tlv-00.txt
> >   Pages:   11
> >   Dates:   2023-09-11
> > 
> > Abstract:
> > 
> >   The BGP Monitoring Protocol (BMP) provides an interface for obtaining
> >   BGP Path information.  BGP Path Information is conveyed within BMP
> >   Route Monitoring (RM) messages.  This document proposes an extension
> >   to BMP to convey the status of a path after being processed by the
> >   BGP process.  This extension makes use of the TLV mechanims described
> >   in draft-ietf-grow-bmp-tlv [I-D.ietf-grow-bmp-tlv] and
> >   draft-ietf-grow-bmp-tlv-ebit [I-D.ietf-grow-bmp-tlv-ebit].
> > 
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-path-marking-tlv/
> > 
> > There is also an HTMLized version available at:
> > https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-path-marking-tlv-00
> > 
> > Internet-Drafts are also available by rsync at:
> > rsync.ietf.org::internet-drafts
> > 
> > 
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
> 

> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow