>  Nodes that use stateless address autoconfiguration SHOULD generate a
>  new CGA and a CGA Parameters data structure as specified in Section 4
>  of [13] each time they run the autoconfiguration procedure.

I hope this isn't what it sounds like it does... Why can't one
continue to reuse the same one one had earlier? That seems like a
performance win. (And networks come and go rather frequently
sometimes, e.g., in the wireless case...)

--------------

James Kempf: The thought behind this is a host will want RFC 3041
address privacy, and therefore will want to change its address
periodically. We can add a qualifier to this for hosts that don't want
to support address privacy:

    Nodes that use stateless address autoconfiguration SHOULD generate a
    new CGA and a CGA Parameters data structure as specified in Section 4
    of [13] each time they run the autoconfiguration procedure if they
    want to support RFC 3041 address privacy [RFC3041], in addition to
    taking other measures specified in RFC 3041.

--------------

Thomas Narten: Actually, does this text even need to be in this
document? Wouldn't this be more appropriate in the other document? (I
also don't think the suggested wording is ideal, as it ties privacy
addresses to the interface config - not sure that is required).

--------------

Arkko: What happens when you run out of config, generate a completely
new CGA. Thomas sent reply, doesn't believe we need text. Suggest move
to CGA draft.

Aura: Is in CGA draft.

Arkko: Is the current text in CGA draft OK?

Aura: Only thing that could be done is to say that it could be run
every time autoconfig procedure.

Arkko: Seems obvious.

Action Items: Remove text, don't update CGA draft.

--------------

--------------