Re: diffs to draft-ietf-idr-bgp4-03.txt
Yakov Rekhter <yakov@cisco.com> Tue, 17 September 1996 14:12 UTC
Received: from cnri by ietf.org id aa13999; 17 Sep 96 10:12 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa03145; 17 Sep 96 10:12 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id JAA12406
for idr-outgoing; Tue, 17 Sep 1996 09:33:43 -0400 (EDT)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by
merit.edu (8.7.5/merit-2.0) with SMTP id JAA12399 for <bgp@merit.edu>;
Tue, 17 Sep 1996 09:33:40 -0400 (EDT)
Received: by interlock.ans.net id AA07315
(InterLock SMTP Gateway 3.0 for bgp@ans.net);
Tue, 17 Sep 1996 09:33:37 -0400
Received: by interlock.ans.net (Internal Mail Agent-1);
Tue, 17 Sep 1996 09:33:37 -0400
Message-Id: <199609171333.GAA15572@hubbub.cisco.com>
To: curtis@ans.net
Cc: bgp@ans.net
Subject: Re: diffs to draft-ietf-idr-bgp4-03.txt
In-Reply-To: Your message of "Sat, 14 Sep 96 00:20:09 EDT."
<199609140420.AAA21003@brookfield.ans.net>
Date: Tue, 17 Sep 96 06:33:33 PDT
From: Yakov Rekhter <yakov@cisco.com>
Sender: owner-idr@merit.edu
Precedence: bulk
Curtis, > If a particular AS has multiple BGP speakers and is providing transit > service for other ASs, then care must be taken to ensure a consistent > view of routing within the AS. A consistent view of the interior > routes of the AS is provided by the interior routing protocol. A > consistent view of the routes exterior to the AS can be provided by > ! having all BGP speakers within the AS maintain direct IBGP connections > ! with each other. Alternately the interior routing protocol can > ! pass BGP information among routers within an AS, taking care not to > ! lose BGP attributes that will be needed by EBGP speakers if transit > ! connectivity is being providided. For the purpose of discussion, > ! it is assumed that BGP information is passed within an AS using > ! IBGP. Care must be taken to ensure that the interior routers have > ! all been updated with transit information before the EBGP speakers > ! announce to other ASs that transit service is being provided. Despite the fact that the notion of using IGP to carry BGP information within an AS isn't new, and had been discussed within the IDR WG on more than one occassion, we've yet to see any progress in this area. So, why should the BGP spec describe something that doesn't exist ? Yakov.
- diffs to draft-ietf-idr-bgp4-03.txt Curtis Villamizar
- Re: diffs to draft-ietf-idr-bgp4-03.txt Yakov Rekhter
- Re: diffs to draft-ietf-idr-bgp4-03.txt Curtis Villamizar
- Re: diffs to draft-ietf-idr-bgp4-03.txt Yakov Rekhter
- Re: diffs to draft-ietf-idr-bgp4-03.txt Yakov Rekhter
- Re: diffs to draft-ietf-idr-bgp4-03.txt David J. LeRoy
- Re: diffs to draft-ietf-idr-bgp4-03.txt John G. Scudder
- Re: diffs to draft-ietf-idr-bgp4-03.txt John G. Scudder
- Re: diffs to draft-ietf-idr-bgp4-03.txt Curtis Villamizar
- Re: diffs to draft-ietf-idr-bgp4-03.txt Curtis Villamizar
- Re: diffs to draft-ietf-idr-bgp4-03.txt Curtis Villamizar
- RE: diffs to draft-ietf-idr-bgp4-03.txt NITTMANN Michael (MSMail)