Jeroen Massar wrote:
Mike Saywell wrote:
#2 (related)
For an ad-hoc network to auto-config it needs an address range to use.
It's extremely limiting to confine them to a single subnet.
#3 (to be found at the root of this thread)
A provider independant (i.e. no upstream ISP) network which aims to
provide transit between 2 or more networks (which may or may not be
public).
Effectively all these three boil down to one thing:
- globally unique addresses
- not connected to the internet
A place to register globally unique, but non-internet-connected
address space would be the best place IMHO.
This will take quite some effort but it is quite probably the
best way to avoid problems like mergers.
In the case of the cruise ship, it makes sense for the ship to
"own" a globally unique prefix. But, in the pure ad-hoc case,
all nodes are peers and may be drawn from completely unrelated
interest groups/geographies. In this case, you need to ask: "who
owns the globally unique prefix?" and "what happens if the prefix
owner goes away?". (I'm perfectly happy if these questions can be
answered w/o site-locals, BTW.)
Fred
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
