Re: [dhcwg] DHCPv4 INFORM Refresh Time Option
"Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com> Mon, 10 September 2012 02:24 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 ED6CA21F8593 for <dhcwg@ietfa.amsl.com>; Sun, 9 Sep 2012 19:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.489
X-Spam-Level:
X-Spam-Status: No, score=-9.489 tagged_above=-999 required=5 tests=[AWL=1.111, 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 7X+arhWThYd5 for <dhcwg@ietfa.amsl.com>; Sun, 9 Sep 2012 19:24:12 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 41D9F21F856D for <dhcwg@ietf.org>; Sun, 9 Sep 2012 19:24:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1265; q=dns/txt; s=iport; t=1347243852; x=1348453452; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=pkRT03DCT6pdu08l6bm9O95xQiImGt2R9b2Ihk2UVZI=; b=bNRL8iGEw+yrYhCaweTPcSbZfjYaKQtmpYRN4HOF11u2EFhA0kKptinq szafuEwQa6eaaE8y6DOMQxkSHHQYZZQ7Z8cOssABEZsJIPHHNyRcCbdQh jgxqSXW4LuQHXku93SH9B02gBU3KbgtUa53h1ZT7s7FihtpKOaRQu9I4v I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EADVOTVCtJXG8/2dsb2JhbABFu0+BB4IgAQEBAwESASc/DAQCAQgRBAEBAQoUCQcyFAkIAQEEDgUIGodoBpp7nxuLE4VWYAOkE4FngmY
X-IronPort-AV: E=Sophos;i="4.80,396,1344211200"; d="scan'208";a="119864548"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 10 Sep 2012 02:24:11 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id q8A2OBxP010222 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Sep 2012 02:24:11 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.246]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0298.004; Sun, 9 Sep 2012 21:24:11 -0500
From: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] DHCPv4 INFORM Refresh Time Option
Thread-Index: Ac2O9aIJmSIHA7SwRXiFsB02PKBpNAAPmAQAAA6VYfA=
Date: Mon, 10 Sep 2012 02:24:10 +0000
Message-ID: <90903C21C73202418A48BFBE80AEE5EB102D5D@xmb-aln-x06.cisco.com>
References: <90903C21C73202418A48BFBE80AEE5EB102CE5@xmb-aln-x06.cisco.com> <F66441CE-7358-474C-BC85-3974168286F1@nominum.com>
In-Reply-To: <F66441CE-7358-474C-BC85-3974168286F1@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.70.241]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19174.001
x-tm-as-result: No--37.171100-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>
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 02:24:13 -0000
>> 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. Thanks, Gaurav -----Original Message----- From: Ted Lemon [mailto:Ted.Lemon@nominum.com] Sent: Monday, September 10, 2012 7:40 AM To: Gaurav Halwasia (ghalwasi) Cc: dhcwg@ietf.org Subject: Re: [dhcwg] DHCPv4 INFORM Refresh Time Option On Sep 9, 2012, at 9:43 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?
- [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)