Re: WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023
Michael Richardson <[email protected]>
| Newsgroups | gmane.ietf.dhc |
|---|---|
| Message-ID | <[email protected]> |
Lorenzo Colitti <[email protected]> wrote: > Regarding your "enterprises won't be happy without this" comment... why do > you say this? One of the goals of this document is to get > roughly equivalent forensics and logging abilities to what we have with > IA_NA today (assuming cooperating hosts). But AFAICT the hierarchical Right. So forensics today will point at the IPv4, where the kubernetes or VirtualBox installation exists, and which connect via NAT44. Upgrade to IPv6, and it's a PD delegation. I agree that it's probably enough to be equivalent; but is it really what they want? > notifications you describe aren't something that exists today with IA_NA. > The enterprise either uses a local DHCPv6 server that is authoritative for > the local prefix, or it uses a centralized DHCPv6 server to assign all > addresses. In the former case, the only information about which addresses > are assigned locally is in the logs of the local DHCPv6 server. The > mechanism being proposed in this draft has the same properties. I will withdraw my suggestion that we do something, but I think that we need to say something about this situation, even if it's "out of scope" -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ dhcwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/dhcwg
signature.asc
(application/pgp-signature, 515 B)
-----BEGIN PGP SIGNATURE----- iQFKBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmWdVDIWHG1jcitpZXRm QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZZIfB/4+f8c5IjB5w6+N9lAq7MM7rSLo o26QG+dVMeVyBLZ/F6ENZA5YyGjJZo3iKdcIbycLAGJ8sYEBVC+MNZryO7gkMKEW yILo12rim0tJjMhQ1roVw8yS9KZrxWFXD0xPct91rZtbTryu6LK9EdYzpfz1Rb+z mcKKLpfJT4Fm7jF3/To63hFE6oStcFNiSB1IjGVkD9n/g/qZVndqF4FTiHFNxn89 +cFwmO+p3qbWiAW938XL+3+kipxYOa1ixIqoSWned6MmcPwNgh4T7WYtQYAKTDJD VSaLogrfvHTtUnOPmMuWhTwSOHb5S6N1HSemTT+cNLDT1g8nJmNAjQ4zabTD =L+LF -----END PGP SIGNATURE-----