> Discussions on this list seem to indicate that globally routable PI might
> not be attainable for very small sites such as my laptop. That would be an
> example of where I can't get my own PI prefix, right?
>
> [EMAIL PROTECTED]
on a site small enough to be its own network (like your laptop), i don't see a
use case for addresses other than ::1/128. ("host-local" is a solved problem.)
if you broaden your example to include multiple virtual operating systems each
needing their own address so that they can communicate over a virtual bridge,
then "lan-local" (fe80::/16) is available.
if your laptop is joining an actual LAN (wired, wireless, etc) then it will
have to have addresses assigned by that actual LAN's administrator, which might
include both fe80::/16 and something else.
it's in that final case where it's "something else" that the question of PI
comes in. i don't think you're suggesting that your laptop have its own PI
for self-communication, and i don't think you're suggesting that your laptop's
PI ought to be connected by a routing protocol to the local network.
at best your need for laptop-level PI would be so that you could perform
routing over a VPN or tunnel whose endpoint was within the local (actual LAN)
administrator's control.
is this a use case worth pursuing for the purpose of defining internet
technology to support it? because it seems to me that the mobile-IP folks
have scratched out a plan for this which involves using on your laptop
addresses assigned by the VPN hub, and speaking no routing protocol.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
