<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div><br></div><div><pre style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"><i>On Tue, Jun 7, 2022 at 3:15 PM Erik Edwards via Kea-users </i><i><<a href="https://lists.isc.org/mailman/listinfo/kea-users">kea-users at lists.isc.org</a>> wrote:
</i>>><i>
</i>>><i> I second this. I have several network switches that choke on the
</i>>><i> returned option.
</i>><i>
</i>><i> This appears to be RFC-compliant behavior on Kea's part, based on
</i>><i> section 3 of RFC 6842: <a href="https://www.rfc-editor.org/rfc/rfc6842.">https://www.rfc-editor.org/rfc/rfc6842.</a></i></pre><pre style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);"><br></pre><pre style="-webkit-text-size-adjust: auto; background-color: rgb(255, 255, 255);">Erik, the RFC only covers client identifiers. I don’t see any mention of host name being affected by this RFC</pre></div></body></html>