Re: FW: I-D Action: draft-templin-6man-dhcpv6-ndopt-07.txt

[Mikael Abrahamsson <[e-mail]>]

On Mon, 17 Dec 2018, Templin (US), Fred L wrote:

> This draft version introduces  a new method for updating clients with new configuration
> information when using the combined IPv6ND/DHCPv6 messaging service that has been
> discussed on this list.  It is based on the notion of an "unsolicited RA/Reply" from the router
> to the client. In this method, after the initial configuration exchange the router can at any
> time issue a new RA with an embedded DHCPv6 Reply message to cause the client to
> update its configuration information.
>
> This is different from DHCPv6 Reconfigure in that it is the router and not the DHCPv6
> server that initiates the update. There have been negative statements about DHCPv6
> Reconfigure on this list, so it would be interesting to hear what people think about
> this approach.
>
> Also new in this version is citation of 'draft-naveen-slaac-prefix-management'. In terms
> of a *solicited* IPv6ND-based prefix delegation service, this method would seem to
> obviate the need for any new PIO flag bits or options in the IPv6ND message. If an
> *unsolicited* PD service was needed, then that may necessitate the definition of a
> new PIO flag.
>
> Comments welcome,

I read the diff between -06 and -07 to find the two sections that were 
updated. It's an interesting approach to send an update with the same XID 
but now perhaps with much lower timers or similar. I do not know the 
DHCPv6 state machine well enough to say how this interacts with the rest 
of the DHCPv6 specifications?

I also see that the RA/PIO based way of performing PD is there.

How does this interact with the DHCPv6 PD messages that might be present 
in the same packet? What about doing DHCPv6 only for stateless and replace 
all stateful processing and put that into the "outer" RA part using PIO? 
I'd like to see that stateful is only done by one mechanism and that DHCP 
was only used for stateless information.

Thoughts?

-- 
Mikael Abrahamsson    email: [e-mail]