[Autoconf] Fwd: Some Thoughts on Problem Statement.

A correction, please see below

---------- Forwarded message ----------
From: Shubhranshu <shubranshu@gmail.com>
Date: Nov 24, 2007 1:26 AM
Subject: Some Thoughts on Problem Statement.
To: autoconf@ietf.org

<snip>

- Scenario where no DHCP server is available.

By its very nature, MANET environment does not always assume
availability of any pre-configured server. Even in such scenarios a
MANET router needs to configure an unique prefix. Traditionally,
protocols such as RFC 2462 are used for address configuration of nodes
in stateless manner. However,  RFC 2462 defines address auto
configuration mechanisms for nodes (host and router) and as such it

>>  "2462 defines address auto configuration mechanisms for nodes
(hosts and not routers)".

- Shubhranshu

does not provide any mechanism for allocating "unique prefix(es)" to
the routers. For example, in Figure 2 below, a MANET Router, say MR3,
may need to receive prefix(es) (which can be further subnetted and
used for address configuration of its attached host nodes) from the
MANET Boarder Router /Access Router. Currently no specification exists
that addresses this requirement.

                            -- MR1...MR3 ....MR5
                  /
                /               .
               /                 .
        MR4                   .
                \
                   \
                     \ -- MR2 ...

Fig 2. (same as Fig 2 in draft-ietf-autoconf-statement-02)

Mobile and wireless nature of MANET routers result in dynamic network
topology [MANET-Arch ID, RFC 2501] which has the property of changing
neighbor nodes. These MANET properties result in network partitioning
and merger of initially isolated networks. Normally, once an address
is allocated to a node, it continues using it and collaborating to
detect and resolve duplicates in case its address is allocated to any
other node. Since initially isolated MANETs had allocated  addresses
independent with each other, there remains probability of more than
one node using same address. Currently there is no specification that
solves problem of MANET "network merger detection" and duplicate
address detection/ resolution resulting due to two / more MANETs
merger.

It is desirable that network partitioning is also detected such that
resources / prefixes that were allocated to the outgoing nodes could
be re-used. Currently there is no specification to solve the problem
of MANET  "network merger detection".

_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www1.ietf.org/mailman/listinfo/autoconf