Le 30 janv. 2014 à 13:38, Alexandru Petrescu <[email protected]> a
écrit :
> Le 30/01/2014 13:28, Ole Troan a écrit :
>>>>> Could it be separate (existing) protocol?
>>>>
>>>> if one had existed, sure.
>>>> requirements from homenet-arch (I might have missed some):
>>>> - must support multi-homing
>>>> - each link should be assigned a stable prefix
>>>> - efficient allocation of prefixes
>>>> - should support both IPv4 and IPv6
>>>
>>> I meant this:
>>>
>>> loosely coupled ---- separate (existing DHCPv6-PD) protocol triggering
>>> route updates to the routing protocol.
>>
>> yes, DHCP PD comes up as a proposed solution quite frequently.
>> I just don't see how you can make DHCP PD fulfill the requirements.
>
> Well it does support multi-homing (Server allocates things to as many
> interfaces as needed), each link can be assigned a stable prefix (provided it
> triggers updates to the Routing protocol), the allocation is efficient
> (Server maintains dynamic databases, leases) and it supports both IPv4 ('IPv4
> subnet allocation' RFC6656, DHCP transition et alia), and IPv6.
>
> I miss something?
Well, in some cases DHCP seems to work, but not when you start imagining
multi-homed networks with multiple routers. Or maybe you can tell me how to
solve this situation with DHCP:
You have ISP1 connected with Router 1. ISP2 connected with Router 2. Router 1,
Router 2, and a third Router (Router 3), are connected on the same link.
ISP1 is delegated the prefix A/56 to Router 1. ISP2 is delegating the prefix
B/56 to Router 2.
A host is connected behind Router 3. How can it get addresses from both
prefixes ?
Cheers,
Pierre
>
> Alex
>
>>
>> cheers,
>> Ole
>>
>
>
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
