Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for-v4-03

On Aug 11, 2004, at 2:58 PM, Bernie Volz wrote:
> I believe this really is more appropriate in
> draft-ietf-dhc-implementation-*.txt, though the (01) draft appears to 
> have
> expired. In particular, in section 2.4/2.5:

Yeah.   I don't have a lot of help to offer with this.   If a PXE 
client can't be configured with a specific client identifier, there's 
not a whole lot to be done about it.   It's definitely a mistake to 
just use the mac address as an identifier and ignore the client 
identifier.   Probably a post-boot client in a PXE environment should 
just use the identifier the PXE client used.   Such a client can't do 
ngtrans anyway, since its boot prom is IPv4-only.   Or if it can do 
ngtrans, the way to do it is to just get a restricted IPv4 address, 
load the O.S. , and then use the O.S. DHCP client to get a proper IP 
address, and throw away the address that PXE got.   You can easily hack 
most DHCP servers to allocate PXE addresses out of a non-routable 
subnet (e.g., 10.x.x.x).

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg