[Idr] RFC 8538 on Notification Message Support for BGP Graceful Restart
rfc-editor@rfc-editor.org Sat, 09 March 2019 01:49 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C03E21274D0; Fri, 8 Mar 2019 17:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 bT1zHUBlr0MW; Fri, 8 Mar 2019 17:49:05 -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 B7463126C15; Fri, 8 Mar 2019 17:49:05 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A4B02B824C3; Fri, 8 Mar 2019 17:49:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190309014904.A4B02B824C3@rfc-editor.org>
Date: Fri, 08 Mar 2019 17:49:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/6tIXd4QNyqKu2amcbbXNiRfvFcU>
Subject: [Idr] RFC 8538 on Notification Message Support for BGP Graceful Restart
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2019 01:49:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8538
Title: Notification Message Support for BGP
Graceful Restart
Author: K. Patel,
R. Fernando,
J. Scudder,
J. Haas
Status: Standards Track
Stream: IETF
Date: March 2019
Mailbox: keyur@arrcus.com,
rex@cisco.com,
jgs@juniper.net,
jhaas@juniper.net
Pages: 10
Characters: 21229
Updates: RFC 4724
I-D Tag: draft-ietf-idr-bgp-gr-notification-16.txt
URL: https://www.rfc-editor.org/info/rfc8538
DOI: 10.17487/RFC8538
The BGP Graceful Restart mechanism defined in RFC 4724 limits the
usage of BGP Graceful Restart to BGP messages other than BGP
NOTIFICATION messages. This document updates RFC 4724 by defining an
extension that permits the Graceful Restart procedures to be
performed when the BGP speaker receives a BGP NOTIFICATION message or
the Hold Time expires. This document also defines a new subcode for
BGP Cease NOTIFICATION messages; this new subcode requests a full
session restart instead of a Graceful Restart.
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 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