RFC 8671 on Support for Adj-RIB-Out in the BGP Monitoring Protocol (BMP)

rfc-editor@rfc-editor.org Wed, 06 November 2019 06:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1615F120C04; Tue, 5 Nov 2019 22:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 5JFCZrYa7uXm; Tue, 5 Nov 2019 22:31:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DD26120C0E; Tue, 5 Nov 2019 22:31:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D1CF8F4073D; Tue, 5 Nov 2019 22:31:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2NzEgb24gU3VwcG9ydCBmb3IgQWRqLVJJQi1PdXQgaW4gdGhlIEJHUCBNb25pdG9yaW5nIFByb3RvY29sIChCTVAp?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, grow@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20191106063117.D1CF8F4073D@rfc-editor.org>
Date: Tue, 5 Nov 2019 22:31:17 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/pTG2llk6IwDxvzw1xk0KMs50q2g>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 06:31:42 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8671

        Title:      Support for Adj-RIB-Out in the 
                    BGP Monitoring Protocol (BMP) 
        Author:     T. Evens, 
                    S. Bayraktar,
                    P. Lucente, 
                    P. Mi,
                    S. Zhuang
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2019
        Mailbox:    tievens@cisco.com, 
                    serpil@cisco.com, 
                    paolo@ntt.net,
                    Penghui.Mi@gmail.com, 
                    zhuangshunwan@huawei.com
        Pages:      9
        Updates:    RFC 7854

        I-D Tag:    draft-ietf-grow-bmp-adj-rib-out-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8671

        DOI:        10.17487/RFC8671

The BGP Monitoring Protocol (BMP) only defines access to the
Adj-RIB-In Routing Information Bases (RIBs).  This document updates
BMP (RFC 7854) by adding access to the Adj-RIB-Out RIBs. It also adds
a new flag to the peer header to distinguish between Adj-RIB-In and
Adj-RIB-Out.

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