Re: BGP-4 changes

["John G. Scudder" <[e-mail]>]

At 8:03 AM -0700 8/29/96, Yakov Rekhter wrote:
>
>  external link it must be possible (based on local configuration) to
>  remove or override the value of the attribute. This shall be done
             ^^^^^^^^
The meaning of "override" is not clear to me.  Furthermore, you can't
remove the value of the attribute since there is no distinguished "no
value" value.  You have to remove the whole attribute.  Try:

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
the attribute or alter its value.  This shall be done prior to determining
the degree of preference of the route.

>  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
                      ^
                       select the route or routes with 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.

Some of this stuff might be slightly easier to be precise about if the
sense were inverted from a process of selecting one best route to that of
removing all non-best routes.  For example that last paragraph would be
something like

       ...remove from consideration all routes which do not have the
       lowest value of the MED attribute.

But, I don't think it's that important.

--John

--
John Scudder                        email:  [e-mail]
Internet Engineering Group, LLC     phone:  [phone]
122 S. Main, Suite 280              fax:    [phone]
Ann Arbor, MI  41804                www:    http://www.ieng.com