"optimal" routes and IDPR

[[e-mail]]

I don't believe that the architecture document ever stated that IDPR
CANNOT generate "optimal" routes.  IDPR can generate any kind of
routes that are expressible in terms of the source and transit
policies.  The point is, the route generation and selection procedures
within a domain can be as fancy or as basic as the administrator of
that domain wishes.

Remember that the route servers for a given domain are under the
control of the adminstrator for that domain.  The domain administrator
can choose how to implement the route generation procedures and the
routing information database retention procedures for its own domain.

For example, the administrator for domain X can choose to implement
its route server so that it records all routing information for all
domains and always optimizes its chosen route according to the quality
of service requested for the flow (minimum delay, minimum cost, or
maximum bandwidth).  The administrator for domain Y may implement its
route server so that it stores only routing information from domains
that do not charge for transit service and always selects the first
(not necessarily the "best") route found to a given destination.

The degree of complexity of route generation is entirely the choice
of the administrator of an individual domain.

m