as-out metrics

  > Laurent Joncheray <lpj at merit.edu> writes:
  > > Explanation understood.
  > > What does the peer do with this number?
  > 
  > 	It should use it to compute the best route. But most of the routers
  > ignore it (or, should i say, sysadmins prefer to have static preferences!)
  > 
  > > Is its use defined by the protocol?
  > > My first impulse is to register this as
  > > bgp-metric: <metric> <as> ...
  > > since it is protocol specific and needs a specific value configured
  > > rhather than a relative cost.
  > > Is this acceptable?
  > 
  > 	Why changing everything? ALC handle this metric
  > correctly, i don't see any need to create another attribute.

Why? For clarity!

The cost in as-in is relative. The absolute numbers do not have any meaning.
It defines a static preference independent of protocol.

The bgp-metric is something different, applicable only to BGP and its
use by the peer is not predicatble. So to my mind it should go somewhere
else. 

But I'll sleep over it.

Daniel



-------- Logged at  Thu Apr 28 23:08:20 MET DST 1994  ---------