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

[jnc@mercury.lcs.mit.edu (Noel Chiappa)]

    > From: "marcelo bagnulo" <mbagnulo@ing.uc3m.es>

    >> How can you make IDs survive ISP changes?

    > 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). Let me devil's advocate
for a second...

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?


I guess the answer is two-fold - and both parts assume that when you change
your location, you don't need to do anything manual to get the new location
into the computer which moved.

First, iff you don't expect any incoming connections, then if your identity
stays the same there is nothing to change in the moved computer. (If your
identity changed, you'd have to get that into the computer after it moved. Not
impossible, but an extra problem.)

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.


Did I miss anything?

	Noel