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

<mohamed.boucadair@orange.com> Fri, 24 August 2012 15:35 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 28BF121F86D5 for <dhcwg@ietfa.amsl.com>; Fri, 24 Aug 2012 08:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.074
X-Spam-Level:
X-Spam-Status: No, score=-2.074 tagged_above=-999 required=5 tests=[AWL=0.174, 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 yoxmE5XzOOjF for <dhcwg@ietfa.amsl.com>; Fri, 24 Aug 2012 08:35:38 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 7243321F86CB for <dhcwg@ietf.org>; Fri, 24 Aug 2012 08:35:38 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id B19FA2DC4FF; Fri, 24 Aug 2012 17:35:37 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 96FBA4C063; Fri, 24 Aug 2012 17:35:37 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Fri, 24 Aug 2012 17:35:15 +0200
From: mohamed.boucadair@orange.com
To: Andre Kostur <akostur@incognito.com>
Date: Fri, 24 Aug 2012 17:35:14 +0200
Thread-Topic: [dhcwg] RECONFIGURE Triggered by DHCPv6 Relay Agents (draft-boucadair-dhc-triggered-reconfigure)
Thread-Index: Ac2CC2Z4IKhdvMmcQSWqXqVlSGmEoQAAa+4Q
Message-ID: <94C682931C08B048B7A8645303FDC9F36E5332AAED@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E5332AA39@PUEXCB1B.nanterre.francetelecom.fr> <CAL10_BrupUkEdssHn7wYphT3yw6LCcnqc7mJOMdxiuTOhC-=Lw@mail.gmail.com>
In-Reply-To: <CAL10_BrupUkEdssHn7wYphT3yw6LCcnqc7mJOMdxiuTOhC-=Lw@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.24.130320
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: Fri, 24 Aug 2012 15:35:39 -0000

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
>