[dhcwg] Comments regarding draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04

[Marcin Siodelski <[e-mail]>]

Hello,

I have just read the draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04
and I have a few comments to share....

1. It is easy to deduce that there can be just a single instance of the
option carrying the link-layer address in a particular message. However, I
think it should be explicitly mentioned for the clarity of the document.
Note that the standards don't prohibit sending multiple instances of the
option with the certain code. Also, some of the options may be included
only once.

2. I suggest that it is mentioned what a server is supposed to do if it
finds two instances of the option in the single DHCP message. ignore the
options? Ignore the whole message? It is specifically important when
multiple options carry different link-layer addresses.

3. It is said that the Relay Agent MAY add the link-layer option to the
message, but it is NOT said what happens if a client sends this option.
Again, is this ignored by the Relay Agent OR the Server?

4. I suggest that it is explicitly mentioned that the new option does not
replace the DUID in any sense but it rather carries the supplementary
information - the client-id requirements from the RFC3315 still apply.

5. Minor: there is the inconsitency with respect to the name of the option.
In section 3: it is "Client Link-layer Address", in the header of the page
it is "Client Link-layer address", in section 5 it is "client link-layer
address", in section 7 it is "Client Link Layer Address".

Cheers,
Marcin