Re: [mif] draft-ietf-mif-dhcpv6-route-option-04 published

Ted Lemon <Ted.Lemon@nominum.com> Tue, 27 March 2012 15:52 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99E5D21F88C6 for <mif@ietfa.amsl.com>; Tue, 27 Mar 2012 08:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.47
X-Spam-Level:
X-Spam-Status: No, score=-106.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wYS75wgM8mL for <mif@ietfa.amsl.com>; Tue, 27 Mar 2012 08:52:20 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 9A33921F88C4 for <mif@ietf.org>; Tue, 27 Mar 2012 08:52:16 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKT3HiMOHPgtMmsI/ayLnTMLtG+eqWAon8@postini.com; Tue, 27 Mar 2012 08:52:16 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 AEE4B1B81E4 for <mif@ietf.org>; Tue, 27 Mar 2012 08:52:15 -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 A0EDA190068; Tue, 27 Mar 2012 08:52:15 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Tue, 27 Mar 2012 08:52:15 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [mif] draft-ietf-mif-dhcpv6-route-option-04 published
Thread-Index: AQHM8uBsQi4512i5cE6t8t5dPnex2ZZnd0OAgAACEYCABGRggIAAcFuAgAFcGoCAABh6gIAQ5pEA///UD5w=
Date: Tue, 27 Mar 2012 15:52:14 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472C3F41@mbx-02.win.nominum.com>
References: <20120224101611.22703.52041.idtracker@ietfa.amsl.com> <4F47688B.10508@gmail.com> <4F5E2F61.9040009@gmail.com> <611FBED3-349A-43E7-B4B9-0BC313EA4F7A@nominum.com> <4F61E04F.4020800@gmail.com> <DF5F4B7B-7486-4878-A096-084BDA1CB7C4@nominum.com> <4F636291.7060104@gmail.com> <DCF9392C-CE26-4587-A912-23EC7044B0F3@nominum.com>, <4F71A47C.7050906@gmail.com>
In-Reply-To: <4F71A47C.7050906@gmail.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mif <mif@ietf.org>
Subject: Re: [mif] draft-ietf-mif-dhcpv6-route-option-04 published
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2012 15:52:20 -0000

> What is the reason of _not_ representing lifetimes in the same manner
> across protocols?  We do represent Types and other things in the same
> manner, why not lifetimes?

2^16 seconds is 18 hours.