Re: Helpful BGP Feature

Yakov Rekhter <yakov@cisco.com> Mon, 03 February 1997 19:03 UTC

Received: from cnri by ietf.org id aa03742; 3 Feb 97 14:03 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa18487; 3 Feb 97 14:03 EST
Received: (from daemon@localhost) by merit.edu (8.8.5/merit-2.0) id NAA23706 for idr-outgoing; Mon, 3 Feb 1997 13:30:00 -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 NAA23701 for <bgp@merit.edu>; Mon, 3 Feb 1997 13:29:57 -0500 (EST)
Received: by interlock.ans.net id AA07697 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Mon, 3 Feb 1997 13:29:52 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 3 Feb 1997 13:29:52 -0500
Message-Id: <199702031829.KAA10098@puli.cisco.com>
To: EDS@rhqvm21.vnet.ibm.com
Cc: bgp@ans.net
Subject: Re: Helpful BGP Feature
In-Reply-To: Your message of "Mon, 03 Feb 97 12:36:28 EST." <199702031811.AA06854@interlock.ans.net>
Date: Mon, 03 Feb 1997 10:29:49 -0800
From: Yakov Rekhter <yakov@cisco.com>
Sender: owner-idr@merit.edu
Precedence: bulk

Ed,

> It may be helpful to add a feature to allow for Directed Route
> announcements. The originator of a BGP Route, for example, could
> specify in an optional attribute, the desired recipient(s) of the
> Route Advertisement e.g.listing the AS numbers or IP addresses of
> the Networks or even the specific gateways that should receive
> the Route Advertisement.
> 
> This would allow for capabilities including:
> 
> Creating Virtual Private Networks. Controlling access to a
> destination.
> 
> Limiting where Route advertisements are propogated. Not all
> destinations need or want to be in all the Global Routing tables.
> Avoiding the need to get Network Service Providers to place
> complex policy statements on their Routers - which may not
> have the desired granularity anyway.

It seems that what you are asking for is fairly similar to
DIST_LIST_INCL attribute in IDRP. Correct ?

Yakov.