Could the authors provide further clarification on the following. Is the intent to tie path availability and this functionality? I could see other uses for path availability ie Load Balancing, Fast Convergence, Minimize Path Hiding..
Availability of Paths. Is the draft proposing a mechanism for a speaker to discover alternative paths ? There are a number of existing drafts BGP Best External and Add-Paths for IPV4 and BGP Best External and a Unique RD ( Not a draft ) per VRF Context ensure that we get the second best paths to a ASBR Speaker ( Either PE or ASBR ). The draft does not speak to the approach.. Make before Break. Is this a capabilities negotiation on a per session basis? I would guess so.. Will the set of affected prefixes need to be sent in a BGP Withdrawal message to the RRs from the initiator? If so what is the behavior? It seems that all speakers would then select ASBR2 ( Your Example ).. So there would be no change from the RR towards the iBGP topology? Jim Uttaro -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, April 30, 2010 5:15 PM To: [email protected] Cc: [email protected] Subject: [GROW] I-D ACTION:draft-ietf-grow-bgp-graceful-shutdown-requirements-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Global Routing Operations Working Group of the IETF. Title : Requirements for the graceful shutdown of BGP sessions Author(s) : T. Takeda, B. Decraene, P. Francois, c. pelsser, Z. Ahmad, A. Armengol Filename : draft-ietf-grow-bgp-graceful-shutdown-requirements-02.txt Pages : 16 Date : 2010-4-30 The BGP protocol is heavily used in Service Provider networks both for Internet and BGP/MPLS VPN services. For resiliency purposes, redundant routers and BGP sessions can be deployed to reduce the consequences of an AS Border Router or BGP session breakdown on customers' or peers' traffic. However simply taking down or even bringing up a BGP session for maintenance purposes may still induce connectivity losses during the BGP convergence. This is no more satisfactory for new applications (e.g. voice over IP, on line gaming, VPN). Therefore, a solution is required for the graceful shutdown of a (set of) BGP session(s) in order to limit the amount of traffic loss during a planned shutdown. This document expresses requirements for such a solution. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-grow-bgp-graceful-shutdow n-requirements-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
