This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-uttaro-idr-bgp-persistence.
Abstract:
For certain AFI/SAFI combinations it is desirable that a BGP speaker
be able to retain routing state learned over a session that has
terminated. By maintaining routing state forwarding may be
preserved. This technique works effectively as long as the AFI/SAFI
is primarily used to realize services that do not depend on
exchanging BGP routing state with peers or customers. There may be
exceptions based upon the amount and frequency of route exchange that
allow for this technique. Generally the BGP protocol tightly couples
the viability of a session and the routing state that is learned over
it. This is driven by the history of the protocol and it's
application in the internet space as a vehicle to exchange routing
state between administrative authorities. This document addresses
new services whose requirements for persistence diverge from the
Internet routing point of view.
Authors:
James Uttaro <ju1738@att.com>
Adam Simpson <adam.simpson@alcatel-lucent.com>
Rob Shakir <rjs@cw.net>
Clarence Filsfils <cf@cisco.com>
Pradosh Mohapatra <pmohapat@cisco.com>
Bruno Decraene <bruno.decraene@orange.com>
John Scudder <jgs@juniper.net>
Yakov Rekhter <yakov@juniper.net>
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)
datatracker.ietf.org