Re: [v6ops] Stateful SLAAC (draft-ietf-v6ops-unique-ipv6-prefix-per-host)

[Victor Kuarsingh <[e-mail]>]

On Mon, Nov 13, 2017 at 8:51 AM, Fernando Gont <[e-mail]> wrote:
> On 11/13/2017 09:35 PM, Victor Kuarsingh wrote:
>> On Mon, Nov 13, 2017 at 8:20 AM, Fernando Gont <[e-mail]> wrote:
>>> On 11/13/2017 07:14 PM, Lorenzo Colitti wrote:
>>>> On Mon, Nov 13, 2017 at 6:21 PM, Fernando Gont <[e-mail]
>>>> <mailto:[e-mail]>> wrote:
>>>>
>>>>     >From a operational point of view, one would wonder why pursue this path
>>>>     as opposed to e.g. do DHCPv6
>>>>
>>>>
>>>> As for DHCPv6 specifically, one reason is that DHCPv6-only networks are
>>>> not recommended by the IETF. RFC 7934.
>>>
>>> Yes, sorry: I meant DHCPv6-PD.
>>>
>>> RFC7934:
>>>
>>>     Due to the drawbacks imposed by requiring explicit requests for
>>>     address space (see Section 4), it is RECOMMENDED that the network
>>>     give the host the ability to use new addresses without requiring
>>>     explicit requests.  This can be achieved either by allowing the host
>>>     to form new addresses autonomously (e.g., via SLAAC) or by providing
>>>     the host with a dedicated /64 prefix.  The prefix MAY be provided
>>>     using DHCPv6 PD, SLAAC with per-device VLANs, or any other means.
>>>
>>> Therefore, why re-invent PD in SLAAC?
>>
>> PD is quite vast, and this draft describes a specific set of use
>> cases.  It does not seem like a re-invention of PD in SLACC to me.
>
> Again: Why not use DHCPv6-PD?
>

I would leave this up to the operators to decide. They are designing
their network and know their requirements best.  I don't want to be in
a position of ignoring what operators are saying they need by
suggesting we have it all figured out here at the IETF and are telling
them how to make design decisions.

There are many factors the weigh into why operators make certain
decisions.  There are circumstances were DHCPv6-PD would be quite
valid, and others, as described in the draft, where the methods
described are desirable.  I don't think there is any one way to build
a network (I am yet to have built two that look exactly the same given
different input requirements).

regards,

Victor K