Re: [dhcwg] DHCPv4 INFORM Refresh Time Option
"Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com> Mon, 10 September 2012 03:53 UTC
Return-Path: <ghalwasi@cisco.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 9E0C521F853B for <dhcwg@ietfa.amsl.com>; Sun, 9 Sep 2012 20:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.859
X-Spam-Level:
X-Spam-Status: No, score=-9.859 tagged_above=-999 required=5 tests=[AWL=0.740, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 VAd7bV07oBTo for <dhcwg@ietfa.amsl.com>; Sun, 9 Sep 2012 20:53:24 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 1F66421F852A for <dhcwg@ietf.org>; Sun, 9 Sep 2012 20:53:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1556; q=dns/txt; s=iport; t=1347249204; x=1348458804; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=KnVpvzfSzI6utRjbC9707Y0yOuP0jS2s6KPDeeKwg0k=; b=g7A1vTOUUQaFE1yjN2UkCu+VLEO+NHU126geh46YtNi3X+4+R/cw4bBs obH6Djt6tB4jbnEePvoXec2Te2+cLkjDE1O1S1YAdCVQTvrjZEeN0gvS6 yNF29/kjdjPSU4WFxSjYb8TUXNG5KShdmOi9gcrUzsqI2n+bAqfhXrxhK Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKxjTVCtJV2Z/2dsb2JhbABFu1CBB4IgAQEBAwESASc/BQcEAgEIDgMEAQEBChQJBzIUCQgBAQQOBQgah2gGmnmfJYsThVZgA6QTgWeCZg
X-IronPort-AV: E=Sophos;i="4.80,396,1344211200"; d="scan'208";a="119838429"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 10 Sep 2012 03:53:23 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8A3rNau007330 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Sep 2012 03:53:23 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.246]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.001; Sun, 9 Sep 2012 22:53:23 -0500
From: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
To: Andre Kostur <akostur@incognito.com>
Thread-Topic: [dhcwg] DHCPv4 INFORM Refresh Time Option
Thread-Index: Ac2O9aIJmSIHA7SwRXiFsB02PKBpNAAPmAQAAA6VYfD//4CTAIAATrCA
Date: Mon, 10 Sep 2012 03:53:22 +0000
Message-ID: <90903C21C73202418A48BFBE80AEE5EB102FCA@xmb-aln-x06.cisco.com>
References: <90903C21C73202418A48BFBE80AEE5EB102CE5@xmb-aln-x06.cisco.com> <F66441CE-7358-474C-BC85-3974168286F1@nominum.com> <90903C21C73202418A48BFBE80AEE5EB102D5D@xmb-aln-x06.cisco.com> <CAL10_BoOb8UAgNrmTQ-3Q_Zzgd4O7mTwb6U=zfZJ2DATR14LTA@mail.gmail.com>
In-Reply-To: <CAL10_BoOb8UAgNrmTQ-3Q_Zzgd4O7mTwb6U=zfZJ2DATR14LTA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.100.74]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19174.001
x-tm-as-result: No--40.206700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DHCPv4 INFORM Refresh Time Option
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, 10 Sep 2012 03:53:24 -0000
Hi Andre, > As another option, did you consider using Lease Time/T1/T2 instead of having a completely new option for this? [Gaurav] This is on the lines of DHCPv6. DHCPv6 also has information refresh time option. Moreover, Lease Time/T1/T2 does not make much sense in case of INFORM and anyway standard also does not allow this. Thanks, Gaurav -----Original Message----- From: Andre Kostur [mailto:akostur@incognito.com] Sent: Monday, September 10, 2012 9:01 AM To: Gaurav Halwasia (ghalwasi) Cc: Ted Lemon; dhcwg@ietf.org Subject: Re: [dhcwg] DHCPv4 INFORM Refresh Time Option On Sun, Sep 9, 2012 at 7:24 PM, Gaurav Halwasia (ghalwasi) <ghalwasi@cisco.com> wrote: >>> Appreciate your comments and suggestions. We are also looking to have the WG take this on as a work item. > >>Do we have any reasonable expectation that any clients will implement this feature? > [Gaurav] Yes, I think so. Certainly not going to get implemented by most. Moreover, DHCP INFORM apart from being used by literal end host devices, also gets used in a lot of other deployments/scenarios. One of the vendor uses it for network discovery. In one another use-case, local dhcp servers on Hubs (in Hub and Spoke) kind of deployments needs to periodically refresh the local config parameters from the central server which it can use while replying to dhcp requests on it's LAN. As another option, did you consider using Lease Time/T1/T2 instead of having a completely new option for this? -- Andre Kostur
- [dhcwg] DHCPv4 INFORM Refresh Time Option Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] DHCPv4 INFORM Refresh Time Option Ted Lemon
- Re: [dhcwg] DHCPv4 INFORM Refresh Time Option Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] DHCPv4 INFORM Refresh Time Option Andre Kostur
- Re: [dhcwg] DHCPv4 INFORM Refresh Time Option Gaurav Halwasia (ghalwasi)