Re: [dhcwg] RECONFIGURE Triggered by DHCPv6 Relay Agents (draft-boucadair-dhc-triggered-reconfigure)

Dear Andre,

Please see inline.

Cheers,
Med 

>-----Message d'origine-----
>De : Andre Kostur [mailto:akostur@incognito.com] 
>Envoyé : vendredi 24 août 2012 17:17
>À : BOUCADAIR Mohamed OLNC/NAD/TIP
>Cc : dhcwg@ietf.org
>Objet : Re: [dhcwg] RECONFIGURE Triggered by DHCPv6 Relay 
>Agents (draft-boucadair-dhc-triggered-reconfigure)
>
>A question that popped into my mind is how does the server decide
>whether the client will be doing a Renew, Rebind, or
>Information-Request?  Perhaps the RA MUST supply an OPTION_RECONF_MSG?

Med: What I had initially in mind for this new message: is to not require any change to the way RECONFIGURE is managed by the server but only provide a signal to the DHCPv6 server to issue one. Is there any particular reason you think the RA should be involved in that process?

>
>Also, is the RA expected to monitor the clients as to whether they are
>reconfigure capable, or will the RA rely on the server to be watching
>that?

Med: I would say no.

   Do we want the server to be able to report back to the RA that
>the client cannot do Reconfigure?

Med: I would say no.

>
>
>On Fri, Aug 24, 2012 at 4:49 AM, <mohamed.boucadair@orange.com> wrote:
>>
>> Dear all,
>>
>> I submitted a new I-D defining a new message type to trigger 
>a server to
>> issue a RECONFIGURE message when RSSO is used.
>>
>> The text is available at:
>> 
>https://datatracker.ietf.org/doc/draft-boucadair-dhc-triggered-
>reconfigure
>>
>> Comments and suggestions are more than welcome.
>>
>> Cheers,
>> Med
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>
>
>--
>Andre Kostur
>