Re: [Autoconf] tentative draft-ietf-autoconf-problem-statement-03.txt and the manetarch document

Shubhranshu wrote:
>> Shubhranshu, I can try to re-formulate that text to express better that
>> that is a problem not a solution.  If one tries to run DHCPv6 Server and
>> a DHCPv6 Relay, and then a Router behind the Relay requests for a prefix
>> (with DHCPv6 PRefix Delegation) then one realizes that (1) the allocated
>> prefix must be hierarchically[*] fit within the prefix administratively
>> assigned on the Relay's interface towards Router and (2) once the prefix
>> is allocated it will unfortunately _not_ be inserted in DHCP Server's
>> routing table (because it is already covered by the routing entry
>> pointing to Relay's prefix).
>>
>> This is a problem from implementation.
>>
>> It could help if we had a requirement (within a bulleted list of Req
>> items) on architecture of unicast prefixes assigned on MANET subnets to
>> be able to be both hierarchical and non-hierarchical - i.e. there should
>> be no strict hierarchical relationship between IPv6 prefixes assigned to
>> the MANET subnets (even when the pictured topology seems hierarchical
>> tree-like).
> 
> Above you said "the allocated prefix must be hierarchically[*] fit.."

[*]: that's what some DHCPv6 implementation requires.  It may be a DHCP 
problem that could be corrected.

> but your requirement in the immediately above paragraph is "there
> should be no strict hierarchical relationship between IPv6 prefixes
> assigned". I guess I am missing something since these two sounds
> contradicting to me.

I agree with you and others that in a MANET Network the IPv6 Addressing 
Architecture should not rely on prefixes being aggregated 
hierarchically.  The AUTOCONF protocol and MANET protocol should work 
regardless of the IPv6 addressing architecture being hierarchical or not 
  hierarchical.  I've probably been not clear enough.  This is a good 
requirement I agree on.

Alex

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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