Re: [Tzdist] Next step

Ken Murchison <murch@andrew.cmu.edu> Mon, 19 October 2015 14:14 UTC

Return-Path: <murch@andrew.cmu.edu>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD131A909D for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 07:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 oP2yYRb91egm for <tzdist@ietfa.amsl.com>; Mon, 19 Oct 2015 07:14:31 -0700 (PDT)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60D1B1A9085 for <tzdist@ietf.org>; Mon, 19 Oct 2015 07:14:31 -0700 (PDT)
Received: from localhost.localdomain (cpe-76-180-151-43.buffalo.res.rr.com [76.180.151.43]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.8/8.14.8) with ESMTP id t9JEESNk030236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tzdist@ietf.org>; Mon, 19 Oct 2015 10:14:29 -0400
Message-ID: <5624FAC4.5030008@andrew.cmu.edu>
Date: Mon, 19 Oct 2015 10:14:28 -0400
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: tzdist@ietf.org
References: <CADZyTkmO_PcfWTw-36U_6vo=EuDAnAmvUo6nvPZjkHjb_ALPSQ@mail.gmail.com> <40285_1445262970_t9JDu8BA043191_50DBD330DB51FDFC0C3E86D4@cyrus.local>
In-Reply-To: <40285_1445262970_t9JDu8BA043191_50DBD330DB51FDFC0C3E86D4@cyrus.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.1.29.4820
X-SMTP-Spam-Clean: 33% ( SXL_IP_DYNAMIC 3, TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, BODY_SIZE_800_899 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, NO_URI_HTTPS 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __INT_PROD_GPS 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __MOZILLA_USER_AGENT 0, __PHISH_SPEAR_STRUCTURE_1 0, __RDNS_POOLED_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0)
X-SMTP-Spam-Score: 33%
X-Scanned-By: MIMEDefang 2.74 on 128.2.105.204
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/fEn1b6vcCu9QKdHeI0JOgdmVr1I>
Subject: Re: [Tzdist] Next step
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>, <mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 14:14:32 -0000

On 10/19/2015 09:55 AM, Cyrus Daboo wrote:
> Hi Daniel,
>
> --On October 18, 2015 at 5:39:04 PM +0100 Daniel Migault 
> <daniel.migault@ericsson.com>; wrote:
>
>>     OPTION 1: There is significant interest and energy to work on topics
>> in this area. In that case, we can think of re-chartering the WG. If you
>> see any work in this area, let it us know as soon as possible, so we can
>> define a new charter.
>
> A couple of possible follow-up work items:
>
> 1) Add a location->tzid mapping extension to the tzdist protocol. That 
> ought to be a relatively trivial extension to define if there is 
> interest.
>

Actually, would this be a mapping from something like "Pittsburgh, PA" 
-> "America/New_York", or from GPS coordinates to a tzid, or both?

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University