RE: [curtis@ans.net: Re: BGP4 stuff: Local Preference Computation]

"NITTMANN Michael (MSMail)" <MNittmann@shl.com> Fri, 06 September 1996 16:34 UTC

Received: from ietf.org by ietf.org id aa09810; 6 Sep 96 12:34 EDT
Received: from cnri by ietf.org id aa09806; 6 Sep 96 12:34 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa10552; 6 Sep 96 12:34 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id LAA17038 for idr-outgoing; Fri, 6 Sep 1996 11:50:34 -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 LAA17026 for <bgp@merit.edu>; Fri, 6 Sep 1996 11:50:29 -0400 (EDT)
Received: by interlock.ans.net id AA25805 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Fri, 6 Sep 1996 11:50:28 -0400
Received: by interlock.ans.net (Internal Mail Agent-2); Fri, 6 Sep 1996 11:50:28 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Fri, 6 Sep 1996 11:50:28 -0400
Message-Id: <c=US%a=_%p=SHL%l=SHL/CANADAW/001B58E8@cocms1.calwdc.shl.com>
Sender: ietf-archive-request@ietf.org
From: "NITTMANN Michael (MSMail)" <MNittmann@shl.com>
To: Curtis Villamizar <curtis@ans.net>, "John G. Scudder" <jgs@ieng.com>
Cc: "bgp@ans.net" <bgp@ans.net>, "cristina@midnight.com" <cristina@midnight.com>, "rwoundy@VNET.IBM.COM" <rwoundy@vnet.ibm.com>
Subject: RE: [curtis@ans.net: Re: BGP4 stuff: Local Preference Computation]
Date: Fri, 6 Sep 1996 08:41:28 -0600
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3
Encoding: 55 TEXT
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

For that one, how about making implementors always set a localpref, but the 
default value in the middle of the value range. That's then equal for all so 
it has no effect within the IBGP realm.

Mike

----------
From:  Curtis Villamizar[SMTP:curtis@ans.net]
Sent:  Donnerstag, 5. September 1996 16:58
To:  John G. Scudder
Cc:  curtis@ans.net; cristina@midnight.com; bgp@ans.net; 
rwoundy@VNET.IBM.COM
Subject:  Re: [curtis@ans.net: Re: BGP4 stuff: Local Preference Computation] 



In message <v03007823ae54d65762ae@[152.160.213.42]>2]>, "John G. Scudder" 
writes:
> At 2:55 PM -0400 9/5/96, Curtis Villamizar wrote:
> >The preconfigured policy information is then put into the LOCAL_PREF
> >attribute.  This text should be more clear.  It seems that everyone
> >who has already implemented BGP4 agrees on the interpretation but the
> >text was never very clear.
> >
> >Don't send LOCAL_PREF to an EBGP peer.  Don't accept LOCAL_PREF from
> >an EBGP peer.  Decide what your preference is based on configured
> >policy.  Then put that into LOCAL_PREF.  Then use LOCAL_PREF as the
> >first value in a comparison.
> 
> Speaking of things which aren't clear, the RFC (and draft) list LOCAL_PREF
> as a "discretionary" attribute.  It is of course *not* discretionary. 
 It's
> required on IBGP connections and forbidden on EBGP.  The implementor (or
> operator) has no discretion as to whether LOCAL_PREF is sent.
> 
> This should be fixed by reclassifying LOCAL_PREF as well-known mandatory.
> 
> [Other than the text being just plain wrong, the other possibility is that
> "discretionary" is being used to mean something like "this is only
> mandatory in some cases".  This is a terrible misuse of the language if
> true, and should still be fixed, if necessary by inventing some new term
> like "well-known sometimes-mandatory" or something.  (Note that the RFC
> nowhere defines "discretionary" so we are left with the dictionary
> definition, e.g. "left to discretion: exercised at one's own discretion".)  
]
> 
> --John


Let's just make it mandatory.  When is it not mandatory?  When there
is only one router in an AS?  Otherwise we have to define how you
compare no LOCAL_PREF to a route with LOCAL_PREF.

Curtis