Re: [GROW] RFC 9069 on Support for Local RIB in the BGP Monitoring Protocol (BMP)

Job Snijders <job@fastly.com> Wed, 16 February 2022 08:48 UTC

Return-Path: <job@fastly.com>
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 CF4113A08C8 for <grow@ietfa.amsl.com>; Wed, 16 Feb 2022 00:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.com
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 OfAX2lAXauvo for <grow@ietfa.amsl.com>; Wed, 16 Feb 2022 00:47:58 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F7D63A0874 for <grow@ietf.org>; Wed, 16 Feb 2022 00:47:58 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id u18so2661348edt.6 for <grow@ietf.org>; Wed, 16 Feb 2022 00:47:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=b8l2Un8gDGYCfMwTBa7b0GtQuYmsWmJaUPdjpGLCcqg=; b=hTfKZCvTQPYQ8c6sLoxgwBkZ1hR2q3IaXTLpaH09OOwueGjmD+NtPhvupw/FjhlUqk L/lqcNNPcgjiCGFUyfTwB2ChJ6kN8+ogcDTcn2zX2yA9wVvbtgVXN1BXb647xwWIH0G/ bdlrQxjPTpftUCMVyVRBnusyexhQasv7Ma/zY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=b8l2Un8gDGYCfMwTBa7b0GtQuYmsWmJaUPdjpGLCcqg=; b=rKC1r+WBzVzqK1QC6KYrqP6vzrfRkhiNB8ex4ymW0s8aWx0JnAl8KgLkwJJ6nqfzaz IeJ4P/oH3pBlPMRMSYRKSxHgkYxzHKOSSrL+TNQR0J4AgbOIutw9TUlvaIwVGp4vaIvx RIW1USLdnzfoJTIA8fSJtjath9gJGyXevssNUqXa3q93WdBpzm20V7obRHTcflFzEq9B oTW+ou5UqJFgyhI412aUbkVzasGvK38rRkOgRmDOHPDlI9ilTTXmf+uSjSReZAIlU0dX yQZ4VaKYRuVgkZY5cK7SUk5/cEjz/WlYOmUdfJ79nR2gGrPsLk5Ju7qjmm1P8MOg+KWf a/Rw==
X-Gm-Message-State: AOAM531q3iLuPXve0ChI/avMhKbY+TwGZ5itfayBMCZ2vraUOc7tL710 9Euepz/JiL95tonzNHI5bFVSBtszv6vTizlYcrVYvbQcElyl9y9lV8yRMPxn+1R46k2MVUIVjIS rtHNzMdOC3+dK9D4NfhftuH2ElOB2oyFMSqwf5EIPmGtjaTdQi4g=
X-Google-Smtp-Source: ABdhPJxiNqnoIDawvfP21KI6WUPjuEuoAzcyu2jW8UBBgH5lEbt6tyXxSgc47ItBc/LuUkEQvGOngg==
X-Received: by 2002:a05:6402:375:b0:404:c2be:3b8c with SMTP id s21-20020a056402037500b00404c2be3b8cmr1730134edw.247.1645001275730; Wed, 16 Feb 2022 00:47:55 -0800 (PST)
Received: from snel ([2a10:3781:276:2:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id s30sm4068139ejm.158.2022.02.16.00.47.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Feb 2022 00:47:55 -0800 (PST)
Date: Wed, 16 Feb 2022 09:47:53 +0100
From: Job Snijders <job@fastly.com>
To: grow@ietf.org
Message-ID: <Ygy6OYKQpQTPHQBO@snel>
References: <20220216062503.594086A9C2@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20220216062503.594086A9C2@rfc-editor.org>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/_NqJ4W58RCLyDAOsEbTDd8C0CF4>
Subject: Re: [GROW] RFC 9069 on Support for Local RIB in the BGP Monitoring Protocol (BMP)
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: Wed, 16 Feb 2022 08:48:04 -0000

Hi GROW,

Cause for celebration for the WG, and Tim, Serpil, Manish, & Paolo! :-)

Thank you for your work (and patience, this doc took about 5 years!)

Kind regards,

Job

On Tue, Feb 15, 2022 at 10:25:03PM -0800, rfc-editor@rfc-editor.org wrote:
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 9069
> 
>         Title:      Support for Local RIB in 
>                     the BGP Monitoring Protocol (BMP) 
>         Author:     T. Evens,
>                     S. Bayraktar,
>                     M. Bhardwaj,
>                     P. Lucente
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       February 2022
>         Mailbox:    tievens@cisco.com,
>                     serpil.bayraktar@menlosecurity.com,
>                     manbhard@cisco.com,
>                     paolo@ntt.net
>         Pages:      14
>         Updates:    RFC 7854
> 
>         I-D Tag:    draft-ietf-grow-bmp-local-rib-13.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc9069
> 
>         DOI:        10.17487/RFC9069
> 
> The BGP Monitoring Protocol (BMP) defines access to local Routing
> Information Bases (RIBs). This document updates BMP (RFC 7854) by
> adding access to the Local Routing Information Base (Loc-RIB), as
> defined in RFC 4271. The Loc-RIB contains the routes that have been
> selected by the local BGP speaker's Decision Process.
> 
> This document is a product of the Global Routing Operations Working Group of the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
> standardization state and status of this protocol.  Distribution of this 
> memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce