BGP-4 changes

Yakov Rekhter <yakov@cisco.com> Thu, 29 August 1996 18:39 UTC

Received: from ietf.org by ietf.org id aa13809; 29 Aug 96 14:39 EDT
Received: from cnri by ietf.org id aa13805; 29 Aug 96 14:39 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa12305; 29 Aug 96 14:39 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id LAA07324 for idr-outgoing; Thu, 29 Aug 1996 11:03:29 -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 LAA07319 for <bgp@merit.edu>; Thu, 29 Aug 1996 11:03:26 -0400 (EDT)
Received: by interlock.ans.net id AA12398 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Thu, 29 Aug 1996 11:03:24 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 29 Aug 1996 11:03:24 -0400
Message-Id: <199608291507.IAA09634@hubbub.cisco.com>
To: bgp@ans.net
Subject: BGP-4 changes
Date: Thu, 29 Aug 96 08:03:22 PDT
Sender: ietf-archive-request@ietf.org
From: Yakov Rekhter <yakov@cisco.com>
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

Folks,

Let me propose that we'll make the following changes to the
spec:

1. Add to 5.1.4 the following:

  MULTI_EXIT_DISC shall not be considered when comparing routes received from
  different neighboring ASs.

  When a route with the MULTI_EXIT_DISC attribute is received over an
  external link it must be possible (based on local configuration) to 
  remove or override the value of the attribute. This shall be done 
  prior to determining the degree of preference of the route.

2. Replace 9.1.2.1 clause (a) with the following:

     a) If the local system is configured to take into account
      MULTI_EXIT_DISC, and the candidate routes differ in their
      MULTI_EXIT_DISC attribute but were received from the same
      neighboring AS, select the route that has the lowest
      value of the MULTI_EXIT_DISC attribute.  A route with
      MULTI_EXIT_DISC shall be preferred to a route without
      MULTI_EXIT_DISC.

Comments ?

Yakov.