IETF Logo Mail Archive

Re: Addr: Re: BGP-4 - revised I-D

Curtis Villamizar <curtis@ans.net> Sat, 24 August 1996 06:00 UTC

Received: from ietf.org by ietf.org id aa16717; 24 Aug 96 2:00 EDT
Received: from cnri by ietf.org id aa16713; 24 Aug 96 2:00 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa02269; 24 Aug 96 2:00 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id BAA29723 for idr-outgoing; Sat, 24 Aug 1996 01:33:04 -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 BAA29718 for <bgp@merit.edu>; Sat, 24 Aug 1996 01:33:01 -0400 (EDT)
Received: by interlock.ans.net id AA22426 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Sat, 24 Aug 1996 01:32:59 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Sat, 24 Aug 1996 01:32:59 -0400
Message-Id: <199608240531.BAA08428@brookfield.ans.net>
To: "John G. Scudder" <jgs@ieng.com>
Cc: bgp@ans.net
Reply-To: curtis@ans.net
Subject: Re: Addr: Re: BGP-4 - revised I-D
In-Reply-To: Your message of "Fri, 23 Aug 1996 21:06:28 EDT." <v03007824ae4405944243@[152.160.213.42]>
Date: Sat, 24 Aug 1996 01:31:24 -0400
Sender: ietf-archive-request@ietf.org
From: Curtis Villamizar <curtis@ans.net>
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

In message <v03007824ae4405944243@[152.160.213.42]>2]>, "John G. Scudder" writes:
> 
> Furthermore, if this is to be done, there's no special reason to deprecate
> MED.  Just provide a knob to allow stripping it at the border.  If you are
> running a network that includes routers which don't support proper MED
> handling, you'd best turn the "strip MED" knob.
> 
> --John


John,

Proper MED handling wouldbe loop free.  The current BGP4 RFC allows
loops to be formed if a prefix is announced from 3 places by 2 AS all
announcing MED.

MED clearly has to be changed.  The question is which of the two
proposed fixes to use.  Leaving the current loopfull MED is not
useful.  We've seen routing loops.

Curtis

v2.8.7 | Report a Bug | By Email