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

Daniel Migault <daniel.migault@ericsson.com> Wed, 24 October 2018 16:36 UTC

Return-Path: <mglt.ietf@gmail.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 0549E130DED for <tzdist-bis@ietfa.amsl.com>; Wed, 24 Oct 2018 09:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] 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 o7yyGtCz-1c2 for <tzdist-bis@ietfa.amsl.com>; Wed, 24 Oct 2018 09:36:29 -0700 (PDT)
Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (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 41B4E126DBF for <tzdist-bis@ietf.org>; Wed, 24 Oct 2018 09:36:29 -0700 (PDT)
Received: by mail-lj1-f175.google.com with SMTP id c4-v6so5398986lja.4 for <tzdist-bis@ietf.org>; Wed, 24 Oct 2018 09:36:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dRgTZZjoS0XVI9jWdUXeVwfsvYSkRPvkb2B3H7OopTQ=; b=qMwyBsD/FXOCmA7t9SISy6WgIPW+FCbhPAHO0KqHHjiznAn14kt41D8Ap8NOQCjK8k 2BeBLLoZiaRiZk5AQDbjUafwP9534yoFf4Zvk6YwrsBTJOLCYrfx1Iw5vESd9bULkcDK 8FceVM5hk9fArmNSeNlZVST+Vf5QNZJtCJmOpWMKfiWb2x3Ai7PLlA3xIWuzFxPdMRqh Z+dWb6pNLcIZiGyqT853so9/iT4D9Pa9gkx+jGVaGtnjs7cYTB8wk3IzypVulJoVu8aL JawjZxm2/TDOPYcXLQ9/61E6FC/oWxsQzown2SqE0M3yOTevzBUoxGUJpP9IjKYnZhox RCgw==
X-Gm-Message-State: AGRZ1gLsWTdNMkgPEwUYPmuAZ13zVqOG4+cZZOJEdSI7aZLiWKc/LzED ksYZqLjoMFN7kT8viLLZ7Rhl+E3pcfn6Ytr10s8=
X-Google-Smtp-Source: AJdET5eblPMN/teraaEaoVeViLXVhKt+PKDOwrnPZzPE/l0h5tdfknPiTVohHI8bK0sAZNNng4oh8/3sOz/Sac4VnNc=
X-Received: by 2002:a2e:980f:: with SMTP id a15-v6mr2476686ljj.6.1540398987340; Wed, 24 Oct 2018 09:36:27 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <d61f46cc-08ea-6872-45d8-f3b6a8c5a3da@fastmail.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Wed, 24 Oct 2018 12:36:15 -0400
Message-ID: <CADZyTk=g-OXGNJiQdwiGHxLDRvdxNuGYZaHXRZ6ztNgo3bdo0g@mail.gmail.com>
To: murch@fastmail.com
Cc: Eliot Lear <lear@cisco.com>, tzdist-bis@ietf.org
Content-Type: multipart/alternative; boundary="00000000000073eec20578fc1607"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/I6hgUs3p_oumVRaqSTjJ6QIsgK0>
Subject: [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:36:31 -0000

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.
* Raising a privacy issue and recommend of using the extension over TLS or
a protected channel.
* 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.

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!

Of course if you have other comments, please raise them!

Yours,
Daniel