RE: BGP-4 changes

rwoundy@vnet.ibm.com Thu, 05 September 1996 23:24 UTC

Received: from ietf.org by ietf.org id aa14779; 5 Sep 96 19:24 EDT
Received: from cnri by ietf.org id aa14775; 5 Sep 96 19:24 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa18395; 5 Sep 96 19:24 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id TAA02695 for idr-outgoing; Thu, 5 Sep 1996 19:03:08 -0400 (EDT)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by merit.edu (8.7.5/merit-2.0) with SMTP id TAA02687 for <bgp@merit.edu>; Thu, 5 Sep 1996 19:03:04 -0400 (EDT)
Sender: ietf-archive-request@ietf.org
From: rwoundy@vnet.ibm.com
Received: by interlock.ans.net id AA06502 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Thu, 5 Sep 1996 19:03:02 -0400
Message-Id: <199609052303.AA06502@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 5 Sep 1996 19:03:02 -0400
Date: Thu, 05 Sep 96 19:03:06 EDT
To: MNittmann@shl.com, bgp@ans.net
Subject: RE: BGP-4 changes
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

*** Resending note of 09/04/96 11:14
Subject: RE: BGP-4 changes

>So you want to (e.g.) be able to say something like "For all MAE-E routes,
>increment MED by 100"?

>I think that the proposed text already allows this, and the details of
>how/when/if to do it should be left to implementors.

>But, I kinda agree with Rich that localpref and policy may be a cleaner way
>to reflect stuff like this.

Thanks, John.

I would be worried about what the value "100" means, with respect
to the metrics of a neighboring AS.  Does it mean two DS-3 hops
or one hundred hops? and what if their link metrics change? etc.

You can safely drop MED attributes, but you modify MED values
at your own risk...

-- Richard Woundy, IBM