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

Ken Murchison <murch@fastmail.com> Wed, 24 October 2018 16:44 UTC

Return-Path: <murch@fastmail.com>
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 B2474126F72 for <tzdist-bis@ietfa.amsl.com>; Wed, 24 Oct 2018 09:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=eL4I6Cox; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ibr6aw9+
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 b7KsCVPZ-x2K for <tzdist-bis@ietfa.amsl.com>; Wed, 24 Oct 2018 09:44:03 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 674F8126CB6 for <tzdist-bis@ietf.org>; Wed, 24 Oct 2018 09:44:03 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id C0D7821E1D; Wed, 24 Oct 2018 12:44:01 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 24 Oct 2018 12:44:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm1; bh=Z1Tv0tl5fkuRCPNzB34uYOKUH0O Xr+Bfe2Pov0TlJMo=; b=eL4I6CoxFt5ImfXsYgkLpIo7TQ5YH9dEZ0b8jwSv6DN hHKCyKzzXrwat3zYN/0GpE2VjC5H+iIvM9qWRXx3raNlFiqsIyHpXTp/YDXRKB/s AaYsK+Hz3T97iQe3UCZ1VneOWY+2O6YeeeEnA9qznYbjBMTMen24uOTCaFxUlWIi deRKItpcSSnY4CIbcj76gKoJCXElsFT4ogmcMOi95vMgiy9ivXJpinlN74nktEA3 wl00xYqEryem2TIaEnnz/iTq8/PwQsBnWIDtkXptk2Ltf9GZZldq89ZIn5/IEbhx c/wLiuWPb3ONM2vjgzL0p26b1Ee04pHYtn/dIuerPKA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Z1Tv0t l5fkuRCPNzB34uYOKUH0OXr+Bfe2Pov0TlJMo=; b=Ibr6aw9+eBEOm+BBjdlnJb JInMytfr/FYofks6/nY7WFQzMY+Uv2w0jXUYBc51WWgjDQu36LC7sLmnQ2v862KR wLQmmULe+xs5Xi0qLAiN7TVIs6vI2x1Hw6M6VQMk5nwfPwon8gbaAzNP4XBDVK/R UvwhoVH1lAFNDqYeTP8hYt7fwimMlZOhqb5ZXK6H7zq23FF3AvzgQuajYEvrIBrH rgQrjVPYlBPzfZizsRCVzMQKJPR9jdq2gkDTtHtUykzkE3Ffrzmlf+jPTrIk5TdB TxMzMg7n2/sY2/PS6L+lJCGw9+404mE8YaQBKnumZC3f48YeNlyWby1OASmqqiqA ==
X-ME-Sender: <xms:UKHQW6-lC0MKSx0s0d3gqaMGRLNFfHIHFXQX6JI_pkBcz5iWU-DgTg>
X-ME-Proxy: <xmx:UKHQW9NHbxQXvV5OlR6MOnFG7uMQfOZeXXQpzLvWwQkEdvQ5Z5yTZw> <xmx:UKHQWzJ3Stxlms1Rp9s8SKj_-TsdduVron63A_Sw6w_FiRGyDrAZWQ> <xmx:UKHQW4bIPWw8pJ4Xqk5_J6Md2d0Vzvgytp7ZS_OfCw-5DBeef1jn9A> <xmx:UKHQW0LJxiogrpV4datXRbl5nmTZRIeth7c5PNb9aepjIVLW0nb4Vg> <xmx:UKHQWykOvubmwa2r2qP5PR12gQ2kjECVuK9g4INU4jWoRJlZwS7Qaw> <xmx:UaHQW4Ya7tYZcVuHpqmvQt4yihKY5rOQcZefkW7buVRh37AIW2C2Pg>
Received: from localhost.localdomain (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 2E17D102FB; Wed, 24 Oct 2018 12:44:00 -0400 (EDT)
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: Eliot Lear <lear@cisco.com>, tzdist-bis@ietf.org
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>
From: Ken Murchison <murch@fastmail.com>
Organization: FastMail US LLC
Message-ID: <078b13d1-5be8-bdb6-530b-5c052c9a34d2@fastmail.com>
Date: Wed, 24 Oct 2018 12:43:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <CADZyTk=g-OXGNJiQdwiGHxLDRvdxNuGYZaHXRZ6ztNgo3bdo0g@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------98780ED0A6EAC7C7EA2B8B49"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/H8axLcd4ZSZLTe8bgBtaWXyle5Q>
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 16:44:05 -0000

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?


> * Raising a privacy issue and recommend of using the extension over 
> TLS or a protected channel.

I believe privacy is discussed in the main TZDIST spec (RFC 7808, 
Section 8).  Is referencing this sufficient?


> * Having a discussion on whether we specify the time zones associated 
> to the point or not and how to do this. While this needs some 
> discussions, I believe we could converge rapidly.

Agreed.  I'm open to any and all suggestions.


>
> It would also be helpful to know if there are known implementations or 
> people planning to implement it. I hope this will be implemented soon!

I have an implementation in the open source Cyrus Calendar server.  The 
examples in the draft where generated using that server.


-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC