Noel,
I think the "street address" analogy is not close
enough - anymore than longitude and latitude numbers or
any other description of physical location.
The problem with physical location portability is
that the location remains even if you're not in it. So
someone else might need to describe their own physical
location using the same description.
Number assignments, however are substantially more
portable.
It is certainly possible for an IPv6 address pool
manager to allocate personalized IPv6 addresses from an
IPv6 address pool that they manage and thereby assume
responsibility for end-delivery (by any means possible)
- thus providing for indefinite address portability.
In this sense, this is more analogous to phone number
portability or tax identifiers.
--
Eric
--> -----Original Message-----
--> From: jnc(_at_)mercury(_dot_)lcs(_dot_)mit(_dot_)edu
[mailto:jnc(_at_)mercury(_dot_)lcs(_dot_)mit(_dot_)edu]
--> Sent: Tuesday, March 28, 2006 10:06 AM
--> To: ietf(_at_)ietf(_dot_)org
--> Cc: jnc(_at_)mercury(_dot_)lcs(_dot_)mit(_dot_)edu
--> Subject: RE: Stupid NAT tricks and how to stop them.
-->
--> > From: "Michel Py"
<michel(_at_)arneill-py(_dot_)sacramento(_dot_)ca(_dot_)us>
-->
--> >> Tim Chown wrote:
--> >> If you deploy IPv6 NAT, you may as well stay with IPv4.
-->
--> > You're the one who convinced me some three years ago
--> that there will
--> > be IPv6 NAT no matter what, what's the message here?
-->
--> I think Tim's point is that the only realistic options are:
-->
--> i) IPv4+NAT
--> ii) IPv6 without NAT.
-->
--> The IPv6+NAT option makes little (no?) economic/technical
--> sense - it has all
--> the operational downsides of IPv4+NAT, plus to which you
--> have the cost/hassle
--> of deploying v6.
-->
-->
--> > and possibly allocate PI to everybody which is
--> another pre-requisite
--> > to get rid of NAT.
-->
--> We aren't *ever* going to give everyone PI space (at least,
--> PI space in
--> whatever namespace the routers use to forward packets), any
--> more than we are
--> going to let them take their street addresses with them
--> when they move.
-->
--> Routing (i.e. path-finding) algorithms simply cannot cope
--> with tracking 10^9
--> individual destinations (see prior message).
-->
--> Noel
-->
--> _______________________________________________
--> Ietf mailing list
--> Ietf(_at_)ietf(_dot_)org
--> https://www1.ietf.org/mailman/listinfo/ietf
-->
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf