RE: Next question...

["Craig A. Huegen" <chuegen@cisco.com>]

Tony,

On Mon, 9 Dec 2002, Tony Hain wrote:

> As I said earlier, hosts already do the locator selection today. The
> routing system seems to be intact (as much as it is capable of anyway),
> so moving this function to the routing system is not an engineering

Depending upon what your belief is of the current best common practice for
multi-homing, one could argue hosts in IPv4 actually do the identifier
selection and the routers select the path which is analagous to the
concept of a locator.  This is in the case of PI space -- we take this
approach with the multi-homing of Cisco's network, to the extent that
www.cisco.com has a single A record and the routing system has the true
"locators" (in the form of BGP paths).

> If it is petty bickering about control between the host or routing
> system administrators, we can't define a standard that will satisfy both
> so we will end up choosing the winner/looser.

It is certainly not this.  I would love to be able to hand a policy
specification to my counterparts in our desktop standards group and have
them figure out how to apply this, in communication, coordination, etc.
Less work for my team.  But I recognize (as detailed in a previous e-mail)
that the time and effort required to manage the configurations on a
significant number of hosts and various permutations of host
capabilities/extensions is far greater than an extensible policy
infrastructure that allows me as the administrator to change policy and
immediately have it applied across the entire infrastructure.  I can
enhance the policy engine on less than 30 devices globally as opposed to
coordinating features from a number of vendors for a number of operating
systems for 100,000 hosts.

/cah

---
Craig A. Huegen, Chief Network Architect      C i s c o  S y s t e m s
IT Transport, Network Technology & Design           ||        ||
Cisco Systems, Inc., 400 East Tasman Drive          ||        ||
San Jose, CA  95134, (408) 526-8104                ||||      ||||
email: chuegen@cisco.com       CCIE #2100      ..:||||||:..:||||||:..