Re: to be draft-ohta-multi6-8plus8-00.txt

[Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>]

Noel;

>     > Well, this is a plus but it is not the problem that we are trying to
>     > solve here, right?
>     > .. we could have a multihoming solution that don't provide this
> 
> Not that I'm arguing *against* doing this, but I'm just curious as to what the
> perceived need is (for having the identity not change if you stop buying
> service from your old ISP and switch to a new one).

Please be aware that we buy service from multiple ISPs, some of which
may change.

> I mean, when you change ISP's, if you expect any incoming connections (i.e. if
> you're in a directory database with some fixed name) then you have to go into
> the database(s) (DNE, etc) and update it to show your new location. So what's
> the issue if you have to change the identity field too?

With ISP independent ID, you don't have to change ID hardcoded in
some file such as domain_name<->ID mapping.

> If you do expect incoming connections, you still don't have to change anything
> in the computer, just the DNS/etc record(s) - and if one day we get secure DNS
> with secure updates, presumably the moved computer could update the DNS
> automatically.

It is a classic misunderstanding on possibility of automatic
renumbering ignoring DNS glue, which is too subtle to
understand without much expertise in DNS.

							Masataka Ohta