Re: IDR WG agenda

Curtis Villamizar <curtis@ans.net> Thu, 27 February 1997 22:00 UTC

Received: from cnri by ietf.org id aa12749; 27 Feb 97 17:00 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa24218; 27 Feb 97 17:00 EST
Received: (from daemon@localhost) by merit.edu (8.8.5/merit-2.0) id QAA18239 for idr-outgoing; Thu, 27 Feb 1997 16:21:02 -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 QAA18231 for <bgp@merit.edu>; Thu, 27 Feb 1997 16:20:46 -0500 (EST)
Received: by interlock.ans.net id AA08310 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Thu, 27 Feb 1997 16:20:43 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 27 Feb 1997 16:20:43 -0500
Message-Id: <199702272118.QAA03060@brookfield.ans.net>
To: Vince Fuller <vaf@wr.bbnplanet.com>
Cc: curtis@ans.net, Yakov Rekhter <yakov@cisco.com>, bgp@ans.net
Reply-To: curtis@ans.net
Subject: Re: IDR WG agenda
In-Reply-To: Your message of "Thu, 27 Feb 1997 11:22:05 PST." <CMM.0.90.2.857071325.vaf@hq.barrnet.net>
Date: Thu, 27 Feb 1997 16:18:41 -0500
From: Curtis Villamizar <curtis@ans.net>
Sender: owner-idr@merit.edu
Precedence: bulk

In message <CMM.0.90.2.857071325.vaf@hq.barrnet.net>, Vince Fuller writes:
>     Isn't that MED with a BGP community to send MED no further?
> 
> Is this "BGP community" in the sense of the IRR or in the sense of the
> community attribute? An IRR community isn't very useful to most of us and
> while a well-known community attribute number could be defined to mean this,
> none exists at present (though that might be a reasonable solution).

I meant a yet to be defined BGP community.  Making it a well known
community would help.

> There was also some feeling among the large provider community that overloadi
> ng
> MED in this way could cause other problems, so a separate attribute may be
> preferred.

Getting the right next hop is a common use for MED.  I think what you
are asking for is something like this that is guarenteed not to be
propogated further.

> Other comments from anyone familiar with the problem to be solved here?
> 
> 	--Vince

Curtis