[dhcwg] Jim Guichard's No Objection on draft-ietf-dhc-addr-n otification-11: (with COMMENT)

Jim Guichard has entered the following ballot position for
draft-ietf-dhc-addr-notification-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-addr-notification/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# Jim Guichard, RTG AD, comments for draft-ietf-dhc-addr-notication

COMMENTS:

141        address registration.  It can do this by including the Address
142        Registration option code the Option Request option (see Section 21.7
143        of [RFC8415]) of the Information-Request, Solicit, Request, Renew, or

Jim> I find the above text a little confusing. RFC 8415 defines the ‘Option
Request’ option with ‘option-code’. I think the above is saying that an
‘Address Registration’ option-code should be included in the ‘Option Request’
option (?). If so, I suggest saying ‘It can do this by including the Address
Registration option-code within the Option Request option (see Section 21.7 of
[RFC8415]’

147        option in its Reply message.  If the network does not support (or is
148        not willing to receive) any address registration information, the
149        client MUST NOT register any addresses.  Otherwise, the client
150        registers addresses as described below.

Jim> What happens if the client ignores the MUST NOT?

153        its interfaces, a client implementing this specification SHOULD
154        multicast an ADDR-REG-INFORM message in order to inform the DHCPv6

Jim> Using which multicast address? It looks like you specify it in section 4.2
so I would suggest referencing that here.



_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]