IETF Logo Mail Archive

Re: [Tzdist-bis] draft-tzdist-geolocate Status and Next Steps

Guy Harris <guy@alum.mit.edu> Wed, 24 October 2018 22:47 UTC

Return-Path: <guy@alum.mit.edu>
X-Original-To: tzdist-bis@ietfa.amsl.com
Delivered-To: tzdist-bis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C903F130E1A for <tzdist-bis@ietfa.amsl.com>; Wed, 24 Oct 2018 15:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yef4vb9Bqhfc for <tzdist-bis@ietfa.amsl.com>; Wed, 24 Oct 2018 15:47:58 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE6FC12F18C for <tzdist-bis@ietf.org>; Wed, 24 Oct 2018 15:47:58 -0700 (PDT)
Received: from [192.168.42.66] (173-228-4-9.dsl.dynamic.fusionbroadband.com [173.228.4.9]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w9OMlpo8027943 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 24 Oct 2018 15:47:51 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Guy Harris <guy@alum.mit.edu>
In-Reply-To: <078b13d1-5be8-bdb6-530b-5c052c9a34d2@fastmail.com>
Date: Wed, 24 Oct 2018 15:47:49 -0700
Cc: Daniel Migault <daniel.migault@ericsson.com>, tzdist-bis@ietf.org, Eliot Lear <lear@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EED3A400-9BB3-4BCB-A0C1-1C9D85C00E04@alum.mit.edu>
References: <CADZyTkkU8pYjdp=g-ubLnmxmXNWpYjvEeTW7R9Gt6DvTBgULQA@mail.gmail.com> <fb72649b-f4c0-c488-a704-8d524187b81b@cs.ucla.edu> <CADZyTkmb0x3KnZDz20Nk9i7Pa05piQ2rvA1S6Oy4RoQxQBqbFQ@mail.gmail.com> <47bd811f-b30b-4165-b51d-ade47f17a1ce@fastmail.com> <3d2b8bcb-ffb7-1b04-518c-4f8e5436bac0@cisco.com> <d61f46cc-08ea-6872-45d8-f3b6a8c5a3da@fastmail.com> <CADZyTk=g-OXGNJiQdwiGHxLDRvdxNuGYZaHXRZ6ztNgo3bdo0g@mail.gmail.com> <078b13d1-5be8-bdb6-530b-5c052c9a34d2@fastmail.com>
To: Ken Murchison <murch@fastmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Sonic-CAuth: UmFuZG9tSVbMsAMTF5zUb+5dDW76ZCd2SMUjmefGR347Gt/0JGZzxNxX+Y/tc/UUXZSIwr843sCoZD6q119H7m1Qls9OuQ8i
X-Sonic-ID: C;8LlC1t7X6BGoZf+mSH5B5g== M;XBWA1t7X6BGoZf+mSH5B5g==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/jLPxn9-XmSoONhwT39PXwqp64ow>
Subject: Re: [Tzdist-bis] draft-tzdist-geolocate Status and Next Steps
X-BeenThere: tzdist-bis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Extensions to Time Zone Data Distribution Service <tzdist-bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist-bis/>
List-Post: <mailto:tzdist-bis@ietf.org>
List-Help: <mailto:tzdist-bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist-bis>, <mailto:tzdist-bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2018 22:48:00 -0000

On Oct 24, 2018, at 9:43 AM, Ken Murchison <murch@fastmail.com> wrote:

> On 10/24/18 12:36 PM, Daniel Migault wrote:
>> I believe we could have a consensus on the next version, and start the WGLC on November 5.
>> 
>> Here is my view on the draft status.
>> * Maybe clarifying the scope of the draft. I believe that one sentence could clearly mention the draft does not expect to go beyond a mobile phone requesting the current TZ.
> 
> Probably "mobile device" (not necessarily a phone), yes?

The draft itself says

   Clients using a Time Zone Data Distribution Service (TZDIST),
   particularly mobile clients, may not have prior knowledge of which
   time zone is appropriate for a particular geographic region.

in the introduction, so "mobile client", perhaps?

Or is the goal here to clarify what a "mobile client" is?  If so, it needs to include laptop computers, even if some might not deem them "devices".

v2.23.0 | Report a Bug | By Email