Helpful BGP Feature

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

Received: from cnri by ietf.org id aa01927; 3 Feb 97 13:48 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa18085; 3 Feb 97 13:48 EST
Received: (from daemon@localhost) by merit.edu (8.8.5/merit-2.0) id NAA23382 for idr-outgoing; Mon, 3 Feb 1997 13:11:36 -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 NAA23377 for <bgp@merit.edu>; Mon, 3 Feb 1997 13:11:29 -0500 (EST)
From: EDS@rhqvm21.vnet.ibm.com
Received: by interlock.ans.net id AA06854 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Mon, 3 Feb 1997 13:11:25 -0500
Message-Id: <199702031811.AA06854@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 3 Feb 1997 13:11:25 -0500
Date: Mon, 03 Feb 1997 12:36:28 -0500
To: bgp@ans.net
Subject: Helpful BGP Feature
Sender: owner-idr@merit.edu
Precedence: bulk

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.

Avoiding having to wait for Service Providers to enter the policy
changes,which sometimes can only occur during monthly
change windows.
Thanks, Ed Segal EDS@RHQVM21.VNET.IBM.COM 914 784-3259