Summary of discussion of this issue:
Several respondents noted that this issue is essentially
the same as "DDNS-DHCP : Use DHCID RR just for DHCP
or extend for other update mechanisms?" I've summarized
the responses to both issues here.
There were three responses to the effect that the DHCID
RR should be reserved for DHCP. No other uses for the
DHCID RR have been identified either in discussion (with
the exception of one mention of PPP) or
in deployment of the DDNS-DHCP interaction mechanism.
Adding the capability in anticipation of future,
as-yet-undefined protocols would add complexity with
little or no added value.
> The DHCID RR data consists of a type code and a hash
> of the identifier of the updater of the record. Should
> it be generalized (perhaps as a side effect of generalizing
> the use of the DHCID RR to other types of resolution)
> to a type code and type-specific data? That is, should
> the DHCID RR allow for other forms of data in addition
> to a 16-byte MD5 hash value to be stored with the type code?
the word 'unsubscribe' in a single line as the message text body.