> > Will the above support using the DUID/IAID form of a client ID for > > DHCPv4 as well, per RFC 4361? I had filed 6386331 some time back to > > record that we should look into this issue. The above text seems > > slightly DHCPv6-specific, so I'm guessing you haven't scoped that in yet. > > No, I hadn't; thanks for mentioning it. I haven't started looking yet > at the outstanding RFEs. (Right now, I'm looking at the detailed > design.) > > Yes, it seems reasonable to include that, and I'll look into it. > > The RFC recommends making the system default to having the same > binding association (client ID) for v4 and v6. I'm not so sure that's > wise, as it means that we'll not only break existing configurations, > but also existing DHCP server configuration tools.
Agreed. However, is there a possibility this be used to provide client ID's when performing DHCP over IPv4 logical interfaces? This has been one of the issues associated with making DHCP feasible in a zone. > (Looks like Bill missed author's last call on his name ... :-/) But at least the "Authors' Addresses" information is correct, ensuring limitless SPAM :-) -- meem _______________________________________________ networking-discuss mailing list [email protected]
