RFC 7747 on Basic BGP Convergence Benchmarking Methodology for Data-Plane Convergence
rfc-editor@rfc-editor.org Thu, 14 April 2016 00:49 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 9FB9912D9B6; Wed, 13 Apr 2016 17:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.918
X-Spam-Level:
X-Spam-Status: No, score=-107.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 sgKH0MKL0aMn; Wed, 13 Apr 2016 17:49:01 -0700 (PDT)
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 B46E712D8CA; Wed, 13 Apr 2016 17:49:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 07C44180204; Wed, 13 Apr 2016 17:48:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7747 on Basic BGP Convergence Benchmarking Methodology for Data-Plane Convergence
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160414004848.07C44180204@rfc-editor.org>
Date: Wed, 13 Apr 2016 17:48:48 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/jE_nrhllasIvz6I1SjuPlJG2YPo>
Cc: drafts-update-ref@iana.org, bmwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 14 Apr 2016 00:49:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7747
Title: Basic BGP Convergence Benchmarking Methodology
for Data-Plane Convergence
Author: R. Papneja, B. Parise,
S. Hares, D. Lee,
I. Varlashkin
Status: Informational
Stream: IETF
Date: April 2016
Mailbox: rajiv.papneja@huawei.com,
bparise@skyportsystems.com,
shares@ndzh.com,
dlee@ixiacom.com,
ilya@nobulus.com
Pages: 35
Characters: 65341
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bmwg-bgp-basic-convergence-05.txt
URL: https://www.rfc-editor.org/info/rfc7747
DOI: http://dx.doi.org/10.17487/RFC7747
BGP is widely deployed and used by several service providers as the
default inter-AS (Autonomous System) routing protocol. It is of
utmost importance to ensure that when a BGP peer or a downstream link
of a BGP peer fails, the alternate paths are rapidly used and routes
via these alternate paths are installed. This document provides the
basic BGP benchmarking methodology using existing BGP convergence
terminology as defined in RFC 4098.
This document is a product of the Benchmarking Methodology Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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