IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt

Sten Carlsen <stenc@s-carlsen.dk> Thu, 31 January 2013 13:34 UTC

Return-Path: <stenc@s-carlsen.dk>
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 2ED8E21F86B7 for <dhcwg@ietfa.amsl.com>; Thu, 31 Jan 2013 05:34:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level:
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DK=1.009, HTML_MESSAGE=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 gDPTt9ybEDrj for <dhcwg@ietfa.amsl.com>; Thu, 31 Jan 2013 05:34:47 -0800 (PST)
Received: from mail2.s-carlsen.dk (0134100024.0.fullrate.dk [90.185.128.210]) by ietfa.amsl.com (Postfix) with ESMTP id 51F3E21F86B2 for <dhcwg@ietf.org>; Thu, 31 Jan 2013 05:34:47 -0800 (PST)
Received: from silver3airport.s-carlsen.dk (unknown [IPv6:2001:16d8:dd00:81ac:5ab0:35ff:fe78:122b]) by mail2.s-carlsen.dk (Postfix) with ESMTPA id 822D9DF0B for <dhcwg@ietf.org>; Thu, 31 Jan 2013 14:34:43 +0100 (CET)
Message-ID: <510A72F2.1060406@s-carlsen.dk>
Date: Thu, 31 Jan 2013 14:34:42 +0100
From: Sten Carlsen <stenc@s-carlsen.dk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <20121214022919.19971.21882.idtracker@ietfa.amsl.com> <CAAfac2gCqq4KxCUt3pd5danhhgdPbNCakBXJwGooPx1jyGEmag@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63074747658A@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63074747658A@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.5
Content-Type: multipart/alternative; boundary="------------000201030607050200080702"
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
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: Thu, 31 Jan 2013 13:34:48 -0000

I am not sure it is worth the effort, every system will have its own
timings and idiosyncrasies, making something general that will fit most
is unlikely.
I just mentioned this to clarify the discussion a bit.

On 31/01/13 13:50, Ted Lemon wrote:
> If you guys are interested in exploring this issue, why not write up a problem statement?   There's certainly no technical reason why a DHCP server can't send reconfigures within a specified time window, but obviously the current spec doesn't say anything about this.
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

-- 
Best regards

Sten Carlsen

No improvements come from shouting:
       "MALE BOVINE MANURE!!!"

v2.46.0 | Report a Bug | By Email | System Status