Re: [mif] IPv4 similarity in DefRoute-distinct-from-RouteOption (was: Comments on draft-mouton-mif-dhcpv6-drlo-00)

[Alexandru Petrescu <[e-mail]>]

Maximilien,

With respect to one particular point you mention below:

Le 26/09/2011 10:42, maximilien mouton a écrit :
> Hi Simon and Ted,
>
> Le 13/09/2011 20:26, Simon Perreault a écrit :
>> Ted Lemon wrote, on 09/13/2011 02:22 PM:
>>> Could you please clearly articulate a use case where this option
>>> is necessary, and the existing proposed option is not adequate?
>>> Please do not mention operating system data structures. Please do
>>> not say "I find it to be the case that.." Without a use case, I
>>> just don't see the point in discussing this further.
>>
>> +1
[...]
> You can notice that router option and static route option (the
> stateful one) are defined separately since rfc 2132 (DHCP Options).
> Moreover, rfc 3442 (Route Option for DHCP version 4) has a similar
> point of view than what we propose with DRLO.

Looking through RFC2132 and RFC3442 I understand that DHCPv4 uses
distinct options for classful - and incidentally default - route (option
code 33), than for classless routes (121).  The reason for a new option
121 seems to have been the classlessness absence in classful routes at
thetime, and worse 33 option seems non-extensible.

Nonetheless, the IPv4 software ended up with distinct options: one for
default route and one for classless routes.  It would be little
straightforward to port that IPv4 software to IPv6 if this latter had
only one option for both route and default route.

Alex
[...]