-----Original Messages----- From:"Joe Clarke (jclarke)" <[email protected]> Send time:Saturday, 08/03/2024 04:06:28 To: "Lin He" <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [Int-area] Review of draft-bi-intarea-savi-wlan
Those are minor compared to the two big issues I see. The first is a limitation we see today with the IETF WiFi network. That is, we want to do IPv6 prefix delegation to wireless clients, and we cannot since the controller is doing mapping like what is described in this draft and not looking at the results of PD leases. How does SAVI address PD? To me, any standard around wireless address validation MUST account for PD. LH>In fact, we have also considered support for PD in the -03 version. Like described in RFC7513, ACs and APs can listen to DHCP-PD messages exchanged between wireless clients and DHCP servers to establish binding between secured MAC addresses and IPv6 prefixes for wireless clients. This is also mentioned in Section 10 of draft-ietf-v6ops-dhcp-pd-per-device-08. [JMC] Figures Lorenzo would account for this. We were trying to run an experiment on this back in SFO but could not. Yes, that text in Section 10 is exactly what I had in mind. SAVI for wireless MUST take PD into account. LH>Copy that. [JMC] Another use case to consider is VMs on wireless hosts behind ACs. Today, those tend to play with chaddr in DHCPv4. I know there are DHCP snooping implementations that do not like this. It might be nice to provide for allowances for such things. LH>We will carefully consider such scenarios:) Joe
_______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
