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

<mohamed.boucadair@orange.com> Mon, 27 August 2012 05:26 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5249E21F8602 for <dhcwg@ietfa.amsl.com>; Sun, 26 Aug 2012 22:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.07
X-Spam-Level:
X-Spam-Status: No, score=-2.07 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id auXW7SVG+nwg for <dhcwg@ietfa.amsl.com>; Sun, 26 Aug 2012 22:26:40 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1CF21F855F for <dhcwg@ietf.org>; Sun, 26 Aug 2012 22:26:40 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 1106222C61E; Mon, 27 Aug 2012 07:26:38 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id E862D238048; Mon, 27 Aug 2012 07:26:37 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Mon, 27 Aug 2012 07:26:14 +0200
From: mohamed.boucadair@orange.com
To: Andre Kostur <akostur@incognito.com>
Date: Mon, 27 Aug 2012 07:26:13 +0200
Thread-Topic: [dhcwg] RECONFIGURE Triggered by DHCPv6 Relay Agents (draft-boucadair-dhc-triggered-reconfigure)
Thread-Index: Ac2CD8Yw0Ney5h2CTPuIXivEztkbSwCBJL+g
Message-ID: <94C682931C08B048B7A8645303FDC9F36E5332AB59@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E5332AA39@PUEXCB1B.nanterre.francetelecom.fr> <CAL10_BrupUkEdssHn7wYphT3yw6LCcnqc7mJOMdxiuTOhC-=Lw@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36E5332AAED@PUEXCB1B.nanterre.francetelecom.fr> <CAL10_Bo4kE6WWKVYmKBXM3S6Nz_yqKQQ1Ma0Vnenb3nQgjdz5g@mail.gmail.com>
In-Reply-To: <CAL10_Bo4kE6WWKVYmKBXM3S6Nz_yqKQQ1Ma0Vnenb3nQgjdz5g@mail.gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.8.27.42119
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] RECONFIGURE Triggered by DHCPv6 Relay Agents (draft-boucadair-dhc-triggered-reconfigure)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Aug 2012 05:26:41 -0000

Dear Andre,

I see the point. 

I updated the text accordingly. 

Thanks.

Cheers,
Med 

>-----Message d'origine-----
>De : Andre Kostur [mailto:akostur@incognito.com] 
>Envoyé : vendredi 24 août 2012 17:48
>À : BOUCADAIR Mohamed OLNC/NAD/TIP
>Cc : dhcwg@ietf.org
>Objet : Re: [dhcwg] RECONFIGURE Triggered by DHCPv6 Relay 
>Agents (draft-boucadair-dhc-triggered-reconfigure)
>
>Normally the server is being told administratively to reconfigure a
>client, and presumably which of the three methods to use.  This is
>just another form of that.   I could see it being changed to: the RA
>MAY supply an OPTION_RECONF_MSG, and if not supplied, the server may
>determine which form of Reconfigure to use.
>
>On Fri, Aug 24, 2012 at 8:35 AM,  <mohamed.boucadair@orange.com> wrote:
>> 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
>>>
>
>
>
>-- 
>Andre Kostur
>Senior Product Design Engineer
>P: 604-678-2864
>E: akostur@incognito.com
>Toll-Free: 1-800-877-1856
>
>
>F: 604-678-2864
>VoIP: sip:864@sip.incognito.com
>