(2004-06-11, 11:05:33)narten

>> 5.1.1 Processing Rules for Senders
>> 
>> 
>>    The CGA option MUST be present in all Neighbor Solicitation and
>>    Advertisement messages, and MUST be present in Router Solicitation
>>    messages unless they are sent with the unspecified source address.
>>    The CGA option MAY be present in other messages.

MUST? so it's not an option to implement the spec, but then not
actually use a feature? That seems wrong; i.e., end user should be
able to disable or choose not  to use.

-----------

James Kempf: The options only need to be included if the node is
configured to use SEND. How about:

   If a host is configured to accept secure ND messages, the 
   CGA option MUST be present in all Neighbor Solicitation
   and Advertisement messages, and MUST be present in 
   Router Solicitation messages, unless either of these
   message types are sent with the unspecified source address. 
   The CGA option MAY be present in other messages.

-----------

Arkko: Node supports spec, does it always have to insert option.

Kempf: Does the node only do it when configured as secure.

Arkko: But its on sender side.

Aura: Not sure we win by leaving out. 

Arkko: Might want spec to allow you to have option, screen on UI to
mark if you want

Aura: If sender sends insecure message, its behaving as a legacy
host. Config option is OK, can have it.

Arkko: Accptable, don't have Thomas on call.

Aura: If in response to insecure, NA is unicast. Unsolicited must be
sent with CGA, when you send a solicited advert, know if other
endpoint understands CGA.

Action Item: Work text taking into account the sender and when the
options should be included.

-----------

-----------