Hi Ahmed, This draft is a mostly repost of draft-rtgwg-bgp-pic-02.txt, that I commented at the time but never get an answer. Although after 3 years I’m afraid that I lost the context, in principle I would welcome an answer
https://mailarchive.ietf.org/arch/msg/rtgwg/HrCYUfrUht7L8bBqqqYS-zqt7SA I also assume that the IPR is equally applicable https://mailarchive.ietf.org/arch/msg/ipr-announce/Ff0cZMBybeBfn3o-TxyUqLDYE8Q but the datatracker has no record of it https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-bashandy-rtgwg-bgp-pic Thanks, Bruno From: rtgwg [mailto:[email protected]] On Behalf Of Ahmed Bashandy (bashandy) Sent: Wednesday, October 14, 2015 11:12 AM To: [email protected] Cc: Pradosh Mohapatra Subject: Fwd: New Version Notification for draft-bashandy-rtgwg-bgp-pic-00.txt Hi This a draft that explains the architecture of BGP Prefix Independent Convergence and how the architecture allows a router achieve convergence after internal and/or external topology changes that does not depend on the number BGP prefixes on a router Please take a look All comments are most welcomed Thanks Ahmed -------- Original Message -------- Subject: New Version Notification for draft-bashandy-rtgwg-bgp-pic-00.txt Date: Wed, 14 Oct 2015 02:04:14 -0700 From: <[email protected]><mailto:[email protected]> To: Clarence Filsfils <[email protected]><mailto:[email protected]>, Ahmed Bashandy <[email protected]><mailto:[email protected]>, Prodosh Mohapatra <[email protected]><mailto:[email protected]>, "Pradosh Mohapatra" <[email protected]><mailto:[email protected]> A new version of I-D, draft-bashandy-rtgwg-bgp-pic-00.txt has been successfully submitted by Ahmed Bashandy and posted to the IETF repository. Name: draft-bashandy-rtgwg-bgp-pic Revision: 00 Title: Abstract Document date: 2015-10-12 Group: Individual Submission Pages: 19 URL: https://www.ietf.org/internet-drafts/draft-bashandy-rtgwg-bgp-pic-00.txt Status: https://datatracker.ietf.org/doc/draft-bashandy-rtgwg-bgp-pic/ Htmlized: https://tools.ietf.org/html/draft-bashandy-rtgwg-bgp-pic-00 Abstract: In the network comprising thousands of iBGP peers exchanging millions of routes, many routes are reachable via more than one path. Given the large scaling targets, it is desirable to restore traffic after failure in a time period that does not depend on the number of BGP prefixes. In this document we proposed a technique by which traffic can be re-routed to ECMP or pre-calculated backup paths in a timeframe that does not depend on the number of BGP prefixes. The objective is achieved through organizing the forwarding chains in a hierarchical manner and sharing forwarding elements among the maximum possible number of routes. The proposed technique achieves prefix independent convergence while ensuring incremental deployment, complete transparency and automation, and zero management and provisioning effort Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
