Re: Helpful BGP Feature

EDS@rhqvm21.vnet.ibm.com Mon, 03 February 1997 21:23 UTC

Received: from cnri by ietf.org id aa09467; 3 Feb 97 16:23 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa22416; 3 Feb 97 16:23 EST
Received: (from daemon@localhost) by merit.edu (8.8.5/merit-2.0) id PAA26838 for idr-outgoing; Mon, 3 Feb 1997 15:32:22 -0500 (EST)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by merit.edu (8.8.5/merit-2.0) with SMTP id PAA26833 for <bgp@merit.edu>; Mon, 3 Feb 1997 15:32:18 -0500 (EST)
From: EDS@rhqvm21.vnet.ibm.com
Received: by interlock.ans.net id AA13578 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Mon, 3 Feb 1997 15:32:13 -0500
Message-Id: <199702032032.AA13578@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 3 Feb 1997 15:32:13 -0500
Date: Mon, 03 Feb 1997 15:05:22 -0500
To: bgp@ans.net
Subject: Re: Helpful BGP Feature
Sender: owner-idr@merit.edu
Precedence: bulk

Paul,
Thank you for your reply.
>How does this differ from a current implementation where
>explicit neighbors are defined ...
I dont believe current implementations provide sufficient
granularity, and are defined in a static manner anyway.

If you could specify what features are available in
"current implementation" that you are referring to
it may be helpful in understanding this.
Thanks