as-out metrics

  > One of the "services" that this registry can offer is configuration
  > generation.  With the NSFNET experience and what we anticipate
  > will be expected from the RA, this information is needed to
  > generate the correct configuration files. 

But what does it mean?
Either you announce something or you don't, right?
Or do you mean that only the lowest cost gets announced as long 
as that peering stays up and if it is down the next higher cost ...
Or does it mean a metric (in external routing, huh?)
Or something entirely different that I don't understand?

  > So whereas this information
  > is not binding, and it is not used by tools such as prtraceroute,
  > it would be needed in the generation of router configurations.

Whose? how?
The fist question is the important one. If it is something the
AS which registers it configures, it is probably OK. If it is
something someone else may or may not configure it is not OK
architecturally because as-in and as-out are designed to describe
exactly what the AS itself configures and has authority over.
Any advisory information should be put somewhere else.

Daniel



-------- Logged at  Thu Apr 28 22:11:53 MET DST 1994  ---------