Re: [GROW] Internet-Draft draft-liu-grow-bmp-stats-reports-00

Jeffrey Haas <jhaas@pfrc.org> Tue, 27 February 2024 19:31 UTC

Return-Path: <jhaas@pfrc.org>
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 8319EC151066 for <grow@ietfa.amsl.com>; Tue, 27 Feb 2024 11:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 EhAn4ikBaInz for <grow@ietfa.amsl.com>; Tue, 27 Feb 2024 11:31:00 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9ADC14EB17 for <grow@ietf.org>; Tue, 27 Feb 2024 11:30:59 -0800 (PST)
Received: from smtpclient.apple (172-125-100-52.lightspeed.livnmi.sbcglobal.net [172.125.100.52]) by slice.pfrc.org (Postfix) with ESMTPSA id 7D7481E039; Tue, 27 Feb 2024 14:30:59 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_C8853BCB-51D6-4CB6-8204-B58F9C23E016"
From: Jeffrey Haas <jhaas@pfrc.org>
X-Priority: 3
In-Reply-To: <2afd65dd38e2d5d-00071.Richmail.00002012857950353736@chinamobile.com>
Date: Tue, 27 Feb 2024 14:30:59 -0500
Cc: grow <grow@ietf.org>
Message-Id: <C6348885-C8F8-4565-9315-1442F8A63913@pfrc.org>
References: <2afd65dd38e2d5d-00071.Richmail.00002012857950353736@chinamobile.com>
To: 李金铭 <lijinming@chinamobile.com>
X-Mailer: Apple Mail (2.3696.120.41.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/Inq0LX3XLPJ5L_CgB_6yE20YmYg>
Subject: Re: [GROW] Internet-Draft draft-liu-grow-bmp-stats-reports-00
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, 27 Feb 2024 19:31:01 -0000

Jinming Li,

A few comments on your proposed counters:

Are your "route threshold" counters intended to cover route discards or only routes that are retained in the adj-ribs-in and automatically rejected because they exceed a configured limit?

If the case is intended to cover discards as well, a gauge is probably not the correct type for this.  You can only keep a gauge for state that you know comes and goes.  Discards can be counted (counter type), but not tracked on a per-prefix basis without keeping the prefix.

For your license restriction count, I understand the use case.  However, I have some concerns that the counter is clear in a vendor neutral fashion.  And, similar to the comments above, if this is intended to cover cases where routes are discarded along with the case for keeping the routes a counter may be a more appropriate type.

For the as-path length threshold, please restructure the reference to RFC 4271.  As written, it looks like the citation is intending to say such threshold lengths are a feature of that RFC.  They are not.

The RPKI counters will be popular!  Please consider socializing these counters with the sidrops group.

Please also be aware that for adj-ribs-out for rpki that RFC 8893 might change the behavior somewhat.

-- Jeff




> On Feb 26, 2024, at 8:24 PM, 李金铭 <lijinming@chinamobile.com> wrote:
> 
> Hi all,
> 
> 
>  
> We have submitted a new Internet-Draft draft-liu-grow-bmp-stats-reports-00 which is about BMP Statistics Types.
> 
>  
> As the BGP protocol continues to expand, more and more functional features are implemented through the BGP protocol, which adds more event information to monitor these functional features.This document lists some new statistics types to update RFC 7854 for growing BGP features.
> 
> The New BMP statistics types are used by the monitoring station to observe more interesting events that occur on the router.  
> 
> New types Include RIB-IN Statistics Types for Route Threshold, RIB-IN/RIB-OUT Statistics Types for AS-Path Length Threshold, and RIB-IN/RIB-OUT Statistics Types for Route Origin Validation. 
> 
>  
> If you have some comments and suggestions, please provide feedback.
> 
>  
> The IETF datatracker status page for this Internet-Draft is:
> 
> https://datatracker.ietf.org/doc/draft-liu-grow-bmp-stats-reports/ <https://datatracker.ietf.org/doc/draft-liu-grow-bmp-stats-reports/>
>  
> Best regards,
> 
> Jinming Li
> 
> 
> _______________________________________________
> 
> 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