Re: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 13 September 2011 16:16 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3674C21F8A69 for <mif@ietfa.amsl.com>; Tue, 13 Sep 2011 09:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.43
X-Spam-Level:
X-Spam-Status: No, score=-2.43 tagged_above=-999 required=5 tests=[AWL=-0.181, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HynPqkzS-7d9 for <mif@ietfa.amsl.com>; Tue, 13 Sep 2011 09:16:35 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 649B421F86AA for <mif@ietf.org>; Tue, 13 Sep 2011 09:16:35 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p8DGIe5k022493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <mif@ietf.org>; Tue, 13 Sep 2011 18:18:40 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p8DGIeo0023004 for <mif@ietf.org>; Tue, 13 Sep 2011 18:18:40 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.183]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p8DGIaGL017783 for <mif@ietf.org>; Tue, 13 Sep 2011 18:18:40 +0200
Message-ID: <4E6F825C.3080303@gmail.com>
Date: Tue, 13 Sep 2011 18:18:36 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: mif@ietf.org
References: <3CF88B99A9ED504197498BC6F6F04B81040FBDA9@XMB-BGL-41E.cisco.com> <4E6E7A72.9030208@gmail.com> <4E6EAFC2.5060906@gmail.com> <4E6EDEA8.3080108@gmail.com> <CFDF82EE-052B-4A61-AE1B-152337822B6E@nominum.com>
In-Reply-To: <CFDF82EE-052B-4A61-AE1B-152337822B6E@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [mif] Comments on draft-mouton-mif-dhcpv6-drlo-00
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2011 16:16:36 -0000

Le 13/09/2011 15:01, Ted Lemon a écrit :
> On Sep 13, 2011, at 12:40 AM, maximilien mouton wrote:
>> In this case an Information-Request when client's lifetime expires
>> (or is close to) is sufficient especially if lifetime's upper limit
>> is higher.
>
> One thing to be crystal clear about is that even if an option is
> added that contains a lifetime, it would be a major extension of the
> DHCP protocol to propose that the client include that lifetime in its
>  calculations for when to renew. Adding an option is a minor
> extension. I would oppose a major extension for this purpose; I don't
> know how the working group as a whole would feel about it, but I
> suspect there would be a great deal of skepticism.
>
> The way lifetimes of configuration information are handled is either
>  with the IRT, in the case of stateless DHCPv6, or with the lease
> renewal timer, in the case of stateful. So if you put a lifetime in a
> route option, I don't see what good it would do.

I agree DHCP has its separate means to deal with lifetimes.

Default route (not route in general) has a particular lifetime
characteristic when managed with ND.

It is good that lifetime of ND and of DHCP are coherent when used on
default route.

Alex

>
>
>
> _______________________________________________ mif mailing list
> mif@ietf.org https://www.ietf.org/mailman/listinfo/mif