Re: Helpful BGP Feature

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

Received: from cnri by ietf.org id aa08737; 3 Feb 97 16:03 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa21878; 3 Feb 97 16:03 EST
Received: (from daemon@localhost) by merit.edu (8.8.5/merit-2.0) id PAA26420 for idr-outgoing; Mon, 3 Feb 1997 15:21:52 -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 PAA26411 for <bgp@merit.edu>; Mon, 3 Feb 1997 15:21:47 -0500 (EST)
From: EDS@rhqvm21.vnet.ibm.com
Received: by interlock.ans.net id AA13085 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Mon, 3 Feb 1997 15:21:43 -0500
Message-Id: <199702032021.AA13085@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 3 Feb 1997 15:21:43 -0500
Date: Mon, 03 Feb 1997 14:55:32 -0500
To: bgp@ans.net
Subject: Re: Helpful BGP Feature
Sender: owner-idr@merit.edu
Precedence: bulk

Yakov,
Thank you for your reply.
>It seems that what you are asking for is fairl similar to
>DIST_LIST_INCL attribute in IDRP. Correct ?
I believe that DIST_LIST_INCL simply
"lists the RDIs of the routeing domains and confederations
to which the routeing information may be distributed."
an RDI or confederation an RDI may contain a very large number
of routers. It does not specify or restrict which of
thousands or more routers(along th path and attached
to it)are provided with the information.
Any info on the granularity that could be implemented as
well as the action that should (/not) be taken by routers
along the path would be appreciated.
Thanks, Ed Segal