This issue is to identify if this inconstancy requires addressing within the client. Therefore, if you are aware of an server implementation that doesn't return the server identifier (Option 54) in ACK and/or NACK dhcp4 responses, please provide details.
The client (v2) currently assumes that the Server Identified (Option 54) is included in the response ACK and NACK packets as per RFC 2131 p28.
This however contradicts RFC 2132 p27.
This issue is to identify if this inconstancy requires addressing within the client. Therefore, if you are aware of an server implementation that doesn't return the server identifier (Option 54) in ACK and/or NACK dhcp4 responses, please provide details.