[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [dhcwg] Ambiguity in RFC 2131 (pages 37 & 38)
On Aug 9, 2005, at 1:12 AM, Soumava Das wrote:
Another point is that I did not get is why "sname would only ever
be filled
in by the DHCP server, never by the client, and the same is true
for file."
RFC 2131 page 23 last paragraph indicates that options in a DHCP
message
might extend into the 'sname' and 'file' fields. Nowhere in the RFC
had I
found anything which indicates that only servers might use the 'option
overload' option. In case clients can use the 'option overload'
option, then
the client might fill in the 'sname' and 'file' fields also.
Of course a client might overload into sname and file, but it's never
going to send an *actual* server name or filename. That's all I meant.
_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg