Re: WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023
Daryll Swer <[email protected]>
| Newsgroups | gmane.ietf.dhc |
|---|---|
| Message-ID | <CACyFTPE0+aV35JgVCL62T3NKL_tFkxuvM=Wfq0xpcw5_Ra-u_A@mail.gmail.com> |
Hello I found this draft proposal particularly interesting, for its given use-case, I do see it potentially being a very good solution. I have a query to the authors of this proposal. I noticed there's a line under 4.2.1, that says: > or within a prefix delegated to the client. Does this imply that, if for example, I have a DHCPv6 server running on a VLAN, and on this particular VLAN, I delegate via ia_pd to my client, a /56, the client needs to inform back to my DHCPv6 server through ADDR-REG-INFORM, whenever the client uses some addresses out of the delegated /56? If the implication is yes, then would this not make it a redundant functionality? As the DHCPv6 server will, anyway, already have knowledge of which client received which ia_pd prefix, therefore if we do need to identify a particular /128 IPv6 address client origin, we can do so by looking at the ia_pd pools. Thanks. *--* Best Regards Daryll Swer Website: daryllswer.com <https://www.daryllswer.com> _______________________________________________ dhcwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/dhcwg