[dhcwg] Re: Adoption of draft-porfiri-dhc-dhcpv4-over-dhcpv6 -ra?
[email protected] Thu, 18 Jul 2024 08:41:05 +0000
| Newsgroups | gmane.ietf.dhc |
|---|---|
| Message-ID | <DU2PR02MB10160AC4A2A98875DA409400F88AC2@DU2PR02MB10160.eurprd02.prod.outlook.com> |
Hi all, I would agree that RAN mention is a distraction if we have other cases to illustrate the need. The RAN case is interesting as the clients (and likely the server) are under the control of the same entity. I fail to see why deploying a hack (4o6 relay) is optimal here. Putting that aside, RFC7341 has a clear applicability scope: This is intended as a special-purpose mechanism that will be implemented **on nodes that must obtain IPv4 configuration** information using DHCPv4 in specific environments where native DHCPv4 is not available. Cheers, Med De : Eric Vyncke (evyncke) <[email protected]> Envoyé : jeudi 18 juillet 2024 07:43 À : Michael Richardson <[email protected]>; Jari Arkko <[email protected]>; dhcwg <[email protected]> Objet : [dhcwg] Re: Adoption of draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra? Hello Michael [and without any hat] I also think that this document would benefit if the RAN use case was removed. I.e., plain DHCPv4 relay over DHCPv6 is interesting enough and more generic. Regards -éric From: Michael Richardson <[email protected]<mailto:[email protected]>> Date: Wednesday, 17 July 2024 at 21:13 To: Jari Arkko <[email protected]<mailto:[email protected]>>, dhcwg <[email protected]<mailto:[email protected]>> Subject: [dhcwg] Re: Adoption of draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra? I reviewed draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-00 I am confused by the radio uni use cases. Is this 5G or what exactly? I assume because this is coming from Ericsson, that it's 5G. I guess I'm surprised DHCPv4 is relevant. I'm also unclear how/if this requires multi-vendor interoperability. I think it probably does, but I'd like to understand where the lines are. It seems like interesting and useful work in eleminating old DHCPv4 infrastructure. I'm happy to adopt the document into DHC. I think that the use case could perhaps be a bit more concrete. Some in the WG have been relucant to work on clearer DHCP server->Relay Agent options for topology (such as PD delegated), with some claiming that the current technique of scraping into the DHCP messages by the relay is "running code". But my impression is that this document would also benefit from. ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ dhcwg mailing list -- [email protected] To unsubscribe send an email to [email protected]