[6lo] Murray Kucherawy's No Objection on draft-ietf-6lo-multicast-registration-18: (with COMMENT)

[Murray Kucherawy via Datatracker <[e-mail]>]

Murray Kucherawy has entered the following ballot position for
draft-ietf-6lo-multicast-registration-18: 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-6lo-multicast-registration/



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

In Section 7.3:

   A device that wishes to refresh its state, e.g., upon reboot if it
   may have lost some registration state, SHOULD send an asynchronous
   NA(EARO) with this new status value. That asynchronous multicast
   NA(EARO) SHOULD be sent to the all-nodes link scope multicast address
   (ff02::1) and Target MUST be set to the link local address that was
   exposed previously by this node to accept registrations

"SHOULD" gives me a choice.  So if I want to refresh my state, but I don't do
those things, has my state still been reset?  I'm not sure you want SHOULD
here, and it feels like at least one of these needs to be MUST, or you could
just change "SHOULD send" to "sends" to make it normal behavior when wants to
reset state.

In Section 2.3, you define these terms, but never use them: 6BBR, AMC, AMR.