RFC 7313 on Enhanced Route Refresh Capability for BGP-4

rfc-editor@rfc-editor.org Tue, 22 July 2014 18:47 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F5B1B2BC5 for <ietf-announce@ietfa.amsl.com>; Tue, 22 Jul 2014 11:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 GQ3EOyTTBQr9 for <ietf-announce@ietfa.amsl.com>; Tue, 22 Jul 2014 11:47:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4FCE91B2BCF for <ietf-announce@ietf.org>; Tue, 22 Jul 2014 11:47:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C168F18047C; Tue, 22 Jul 2014 11:46:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7313 on Enhanced Route Refresh Capability for BGP-4
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140722184615.C168F18047C@rfc-editor.org>
Date: Tue, 22 Jul 2014 11:46:15 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/sWchi5xD-xIPqhUEivM9iJw0Wt0
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 22 Jul 2014 18:47:32 -0000

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

        
        RFC 7313

        Title:      Enhanced Route Refresh Capability for BGP-4 
        Author:     K. Patel, E. Chen, B. Venkatachalapathy
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2014
        Mailbox:    keyupate@cisco.com, 
                    enkechen@cisco.com, 
                    balaji_pv@hotmail.com
        Pages:      8
        Characters: 15111
        Updates:    RFC 2918

        I-D Tag:    draft-ietf-idr-bgp-enhanced-route-refresh-10.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7313.txt

In this document, we enhance the existing BGP route refresh
mechanisms to provide for the demarcation of the beginning and the
ending of a route refresh.  The enhancement can be used to facilitate
correction of BGP Routing Information Base (RIB) inconsistencies in a
non-disruptive manner.  This document updates RFC 2918.

This document is a product of the Inter-Domain Routing 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 Internet
Official Protocol Standards (STD 1) 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/rfc.html

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