[dhcwg] Re: Opsdir telechat review of draft-ietf-dhc-rfc8415 bis-09
Michael Richardson <[email protected]> Wed, 16 Apr 2025 13:34:04 -0400
| Newsgroups | gmane.ietf.dhc |
|---|---|
| Message-ID | <[email protected]> |
Thank you for this review, and your nit edits. I will turn your nits into one or two pull requests so that we can be sure we got them right. They don't look controversial at first glance. That should be easy to do before the IESG telechat on this document. Your higher level comments seem more difficult to deal with :-( I'm not entirely sure how much change we can/should make to a document that is going towards Internet Standard. I've asked the authors to convene next week to discuss this. The implied MUSTs concern me most. Perhaps there is someone who could comment more about how important it is to keep text similar. One reason we do not reference any new work (like RFFC9663) is that we might not have implementation experience there, and IS are supposed to be about what has actually been implemented. For instance, has anyone actually implemented RFC9243 (the YANG model)? In some sense, this is outside of RFC8415bis in the sense that 8415bis deals with stuff that goes out the "southbound" interface. DHCP messages. While 9243 is about what goes out the "northbound" interface. -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ dhcwg mailing list -- [email protected] To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 515 B)
-----BEGIN PGP SIGNATURE----- iQFKBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmf/6gwWHG1jcitpZXRm QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZVcvB/0Uhw+gfPZIxcokc0LD35uj/4LN GwZ6VGjRZstzDjmiwrs4yh62RBA/J4jSVL4gZXL4wzkxL3BBaqiGZcMFK8SSreN6 5y1gXuy9fY8LIUm4OwT09DC8NSr/aDHHezLZ6jKIQgeb9186JrzOpGsTHx9lOpYp bWx0oqbFNzvGsZScC/5VKAiO9dSF1Oqm4EOfoGSlZZHTQ159mT8mYt2JkZNKXKAn Ic5V00jwKY1XL4M9rFu/knK4EAaf7AXM/T1b8nKGPcCoZ93NDmju/SfW8t7ivESR uFrp6C5zKwBWMoJZK1qkmvdyPMzs1qRfvWFj+jmCQwTFAIfrna27sk5UC0rS =f2DK -----END PGP SIGNATURE-----