Re: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-09.txt>

Two comments on revision -09:

I think section 6.2 is not clear that the DUID used by DHCPv4 in a dual-
stack client is a subfield of the client identifier defined in draft-
ietf-dhc-3315id-for-v4.  Here's is some suggested text:

   Sites that wish to permit a single FQDN to contain both A and AAAA
   RRs MUST make use of DHCPv4 clients and servers that support using
   the form of client identifier defined in "Node-Specific Client
   Identifiers for DHCPv4" [6].  A DHCPv4 client that implements this
   form of DHCPv4 client identifier uses the same DUID used in the
   DUID field of the the client identifier to compute the RDATA in the
   DHCID RR.  A DHCPv4 server uses the DUID of the client identifier
   received from the DHCPv4 client to compute the RDATA in the DHCID
   RR.  Otherwise, a dual-stack client that uses older-style DHCPv4
   client identifiers (see [8] and [9]) will only be able to have
   either its A or AAAA records in DNS under a single FQDN because of
   the DHCID RR conflicts that result.

In the Terminology section, I think the document would be better served
by referring DNS terms to the DNS RFCs, DHCP terms to the DHCP RFCs,
etc.

- Ralph

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