In DHCP, each Authorization Claim is encoded as a DHCP Authentication Option [RFC3118], using the
I wonder why RFC8415 and it’s Authentication Option (section 21.11) isn’t at least referenced. They are formatted the same but there’s hopefully more interest in v6 and I suspect a lot more deployment of this option in v6 as the Reconfiguration Key Authentication Protocol is used (require) for certain devices?
Also would referencing section 10 of 8415 be better than “in canonical form”?
Representation and Use of Domain Names
So that domain names may be encoded uniformly, a domain name or a
list of domain names is encoded using the technique described in
Section 3.1 of [RFC1035]. A domain name, or list of domain names, in
DHCP MUST NOT be stored in compressed form as described in
Section 4.1.4 of [RFC1035].
From Bernie:
For 5.2.1,
In DHCP, each Authorization Claim is encoded as a DHCP Authentication Option [RFC3118], using the
I wonder why RFC8415 and it’s Authentication Option (section 21.11) isn’t at least referenced. They are formatted the same but there’s hopefully more interest in v6 and I suspect a lot more deployment of this option in v6 as the Reconfiguration Key Authentication Protocol is used (require) for certain devices?
Also would referencing section 10 of 8415 be better than “in canonical form”?
Representation and Use of Domain Names
So that domain names may be encoded uniformly, a domain name or a list of domain names is encoded using the technique described in Section 3.1 of [RFC1035]. A domain name, or list of domain names, in DHCP MUST NOT be stored in compressed form as described in Section 4.1.4 of [RFC1035].