Host autoconfiguration capabilities isn't a "rocket space" science, but would certainly greatly help to accommodate the ability to change providers in presence of hierarchical routing. Granted this wouldn't address the problem of dealing with the installed based, but we are not aware of any other alternative (except for the NAT boxes and/or application layer gateway alternative) that wouldn't require *any* changes to the installed base, while at the same time would accommodate hierarchical routing and would allow to change providers.
Noel Chiappa & Yakov Rekhter
Host autoconfiguration requires that DNS be rewritten as well, though, and that's something that hasn't had much work done on it. The implementation of this kind of thing MUST -- repeat -- MUST -- be complete, or it won't get adopted. I could sell to people *right now* the need and want to go to, for example, an integrated bootp/DNS style thing, IF it was integrated all the way down to the level of plug and play. Until it is, the manual configuration requirement is a problem -- and one not easily solved. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity Modem: [+1 312 248-0900] | (shell, PPP, SLIP, leased) in Chicagoland Voice: [+1 312 248-8649] | 6 POPs online through Chicago, all 28.8 Fax: [+1 312 248-9865] | Email to "info@mcs.net" for more information ISDN: Surf at Smokin' Speed | WWW: http://www.mcs.net, gopher: gopher.mcs.net