Re: [dhcwg] DHCPv4 INFORM Refresh Time Option
Ted Lemon <Ted.Lemon@nominum.com> Mon, 10 September 2012 02:09 UTC
Return-Path: <Ted.Lemon@nominum.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 8B4EC21F85A8 for <dhcwg@ietfa.amsl.com>; Sun, 9 Sep 2012 19:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level:
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 NLvCozqO1jl6 for <dhcwg@ietfa.amsl.com>; Sun, 9 Sep 2012 19:09:48 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 0130021F8552 for <dhcwg@ietf.org>; Sun, 9 Sep 2012 19:09:47 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUE1L630IEhMhraRCHRaKXLw4O+iw0hcL@postini.com; Sun, 09 Sep 2012 19:09:48 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 11C9C1B8490 for <dhcwg@ietf.org>; Sun, 9 Sep 2012 19:09:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0463519005C; Sun, 9 Sep 2012 19:09:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Sun, 9 Sep 2012 19:09:41 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
Thread-Topic: [dhcwg] DHCPv4 INFORM Refresh Time Option
Thread-Index: Ac2O9aIJmSIHA7SwRXiFsB02PKBpNAAPmAQA
Date: Mon, 10 Sep 2012 02:09:40 +0000
Message-ID: <F66441CE-7358-474C-BC85-3974168286F1@nominum.com>
References: <90903C21C73202418A48BFBE80AEE5EB102CE5@xmb-aln-x06.cisco.com>
In-Reply-To: <90903C21C73202418A48BFBE80AEE5EB102CE5@xmb-aln-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E0451EC4E223954ABD439BFA1BAE6701@nominum.com>
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:09:48 -0000
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)