IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Thu, 31 January 2013 13:43 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 D887921F866F for <dhcwg@ietfa.amsl.com>; Thu, 31 Jan 2013 05:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 vVEf6nZ+bbOO for <dhcwg@ietfa.amsl.com>; Thu, 31 Jan 2013 05:43:10 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 483B121F862E for <dhcwg@ietf.org>; Thu, 31 Jan 2013 05:43:10 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUQp07tmoZiD85nDNQE0d7avP8h22Usn5@postini.com; Thu, 31 Jan 2013 05:43:10 PST
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 E26771B8404 for <dhcwg@ietf.org>; Thu, 31 Jan 2013 05:43:09 -0800 (PST)
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 DC0BB190043; Thu, 31 Jan 2013 05:43:09 -0800 (PST) (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.0318.004; Thu, 31 Jan 2013 05:43:09 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sten Carlsen <stenc@s-carlsen.dk>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
Thread-Index: AQHN2aLnWtwi1wyaSEqStm4niIO/zJhXGQSAgA0c1gCAAAxvAIAAAlyA
Date: Thu, 31 Jan 2013 13:43:09 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630747476845@mbx-01.win.nominum.com>
References: <20121214022919.19971.21882.idtracker@ietfa.amsl.com> <CAAfac2gCqq4KxCUt3pd5danhhgdPbNCakBXJwGooPx1jyGEmag@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63074747658A@mbx-01.win.nominum.com> <510A72F2.1060406@s-carlsen.dk>
In-Reply-To: <510A72F2.1060406@s-carlsen.dk>
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="iso-8859-1"
Content-ID: <FDDBDDADF204F34AADFE5E339E0FA13C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
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:43:11 -0000

On Jan 31, 2013, at 8:34 AM, Sten Carlsen <stenc@s-carlsen.dk>
 wrote:
> 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.

I don't know if it's worth the effort either; perhaps we can simply say that mobile devices do not support Reconfigure unless they have really big batteries.   But if there is some desire to support reconfigure on mobile devices, it might be worth doing this.   Mobile devices typically have very accurate clocks; there is no particular reason why a solution can't be specified.

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