
From nobody Fri Jul 18 05:28:55 2014
Return-Path: <iesg-secretary@ietf.org>
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 B78A71B29A0; Fri, 18 Jul 2014 05:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 6Ga5iqlFRpJD; Fri, 18 Jul 2014 05:21:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D19BB1B2997; Fri, 18 Jul 2014 05:21:21 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140718122121.9152.82951.idtracker@ietfa.amsl.com>
Date: Fri, 18 Jul 2014 05:21:21 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/X5TSorIJXkFk8XOULNoYqoF8sO8
X-Mailman-Approved-At: Fri, 18 Jul 2014 05:28:53 -0700
Cc: tzdist WG <tzdist@ietf.org>
Subject: [Tzdist] WG Review: Time Zone Data Distribution Service (tzdist)
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>, <mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 18 Jul 2014 12:21:23 -0000

A new IETF working group has been proposed in the Applications Area. The
IESG has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2014-07-28.

Time Zone Data Distribution Service (tzdist)
------------------------------------------------
Current Status: Proposed WG

Assigned Area Director:
  Barry Leiba <barryleiba@computer.org>

Mailing list
  Address: tzdist@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/tzdist
  Archive: http://www.ietf.org/mail-archive/web/tzdist/

Charter:

Time Zone Data Distribution Service (tzdist)

-----------------------------------------------------------

A time zone is a region that has a uniform local time for legal,
commercial, and social purposes, with some regions using daylight saving
time (DST) rules for part of the year. A local time is defined as a
standard offset from Coordinated Universal Time (UTC), and a set of DST
rules.  Time zone data represents the history, current, and future local
time rules for these regions, together with an associated time zone
identifier.

Time zone data is a critical element of computer systems and devices that
make use of local time. In particular, it is critical to any calendaring
and scheduling system, such as iCalendar (RFC 5545). Daylight saving
time rules, which affect local UTC offsets, can change - sometimes at
very short notice (just a few days) - as those rules are typically
defined by political processes.  Currently, there is no efficient, fast
way to ensure that time zone data is updated in a timely and reliable
manner on devices that need it.  Time zone changes are often delivered as
operating system updates, and are thus tied to release schedules that
can trail the actual time zone changes by a significant period of time. A
service is needed that can provide timely, reliable updates.

One added benefit of such a service for iCalendar is the ability for
calendaring clients and servers to agree on common, standard definitions
of time zone data, removing the need to pass time zone data directly "by
value" in iCalendar data. By allowing clients and servers to use
time zones "by reference" significant network bandwidth and storage
savings can be achieved.

This working group will:

- Define a time zone data distribution protocol that allows for
efficient, timely updates of time zone data to be delivered to clients.
This protocol must scale to vast numbers of clients, such as the
potential "internet of things" devices, as well as to today's desktop
computers and servers.

- Define an extension to CalDAV (RFC 4791) to allow clients and servers
to use time zones "by reference" to improve the efficiency of the overall
protocol.

The working group will use the following drafts as initial input for its
work:
draft-douglass-timezone-service-11
draft-daboo-caldav-timezone-ref-01

The working group will work under the following parameters:

- The time zone data distribution protocol will initially be targeted at
iCalendar-based clients, but should be flexible enough to deliver
time zone data in other formats.

- The time zone data will be based on the Time Zone Database
(http://www.iana.org/time-zones) but must be able to include any source
of time zone data.

- The time zone data distribution protocol should also offer an API to
allow thin clients to easily make use of time zone data by querying for
UTC offsets, offloading the sometimes complex work of expanding
recurrence rules to the service. This API should be extensible to
support other types of time zone operations in the future.

- The time zone data distribution protocol will use current security
protocols to protect the integrity and confidentiality of the data as
it is distributed, and may also address these issues with respect
to retrieval of data from its original source (such as the Time Zone
Database). Even public time zone data can represent a significant
privacy exposure when it is associated with the user or endpoint
that is retrieving it.

The following are Out of scope for the working group:

- Any changes to the Time Zone Database process or infrastructure,
as documented in RFC 6557. However, the WG may work with IANA
in order to make integrity checking information, such as public keys,
readily accessible for protocol use.

- The naming process for time zone identifiers.  The working group can
consider adding a mechanism, such as a "namespace" prefix, to
differentiate different time zone sources, but the nature of the time
zone
identifiers used will be controlled by the sources themselves.

- Lookup protocols or APIs to map a location to a time zone.

Milestones:

TBD


From cdlt23@gmail.com  Wed Jul 23 14:05:53 2014
Return-Path: <cdlt23@gmail.com>
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 110EA1A00F9 for <tzdist@ietfa.amsl.com>; Wed, 23 Jul 2014 14:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level: 
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 fixbuTP_yTDD for <tzdist@ietfa.amsl.com>; Wed, 23 Jul 2014 14:05:50 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 426BB1A0067 for <tzdist@ietf.org>; Wed, 23 Jul 2014 14:05:50 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id hq11so3375322vcb.2 for <tzdist@ietf.org>; Wed, 23 Jul 2014 14:05:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=3knSuBk6WpQdeyYeqnHV81oUNSWWjrcY5wtTH/Bhe8w=; b=eEW869Wf9t72tim1BN83+4Yv1CWQ0ueHeu3npcSTDhjHKvp2/l3MAIByGXQbrJrBbY IfZKj/I+X+BkQSRN/BKW0f2mnn/tcbZjF4k46l3SR8DVa6mF42G1JkAGqPLAwUvSgcSQ Ua1XfoLuWXtCnN5gw4w6J9yCKHj/6E1xoe9DI/xb6OssYL8lQ4OPShMqiqfKdeOBT/+M VbFWNGwwNfS4n89Uthlgkv4Q9zq85WAm+O1o+pVhTyYl7COaMIQ9oFGiIvBtW8ZEuD0B m0nq3M/hW05qNEEz30GKaiv7P9sZRXwF8fIdfv0tJ1FGUqBYyozOJc2uBejPKIPb5FwK csjQ==
MIME-Version: 1.0
X-Received: by 10.52.141.76 with SMTP id rm12mr5085299vdb.71.1406149549426; Wed, 23 Jul 2014 14:05:49 -0700 (PDT)
Sender: cdlt23@gmail.com
Received: by 10.220.132.141 with HTTP; Wed, 23 Jul 2014 14:05:49 -0700 (PDT)
In-Reply-To: <20140718122121.9152.82951.idtracker@ietfa.amsl.com>
References: <20140718122121.9152.82951.idtracker@ietfa.amsl.com>
Date: Wed, 23 Jul 2014 18:05:49 -0300
X-Google-Sender-Auth: FQsqqfAXQgTsHZArYIeFrqtUJ44
Message-ID: <CAOj9aUW4+SUGKWTD9f26LqwM1+xzS5wPNJmbk4MdEdVcYB4XgA@mail.gmail.com>
From: "Cristian F. Perez Monte" <cristian.perez@gridtics.frm.utn.edu.ar>
To: tzdist@ietf.org
Content-Type: multipart/alternative; boundary=bcaec51b14dd65274604fee2b455
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/pb0Q8cCTa4m9F7ikD89EVps9OdE
Subject: Re: [Tzdist] WG Review: Time Zone Data Distribution Service (tzdist)
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 21:17:17 -0000

--bcaec51b14dd65274604fee2b455
Content-Type: text/plain; charset=UTF-8

Hi all,
I suggest a new simple network protocol for timezone data distribution
without http for use in thin devices and IoT.
Best Regards
Cristian

On Fri, Jul 18, 2014 at 9:21 AM, The IESG <iesg-secretary@ietf.org> wrote:

> A new IETF working group has been proposed in the Applications Area. The
> IESG has not made any determination yet. The following draft charter was
> submitted, and is provided for informational purposes only. Please send
> your comments to the IESG mailing list (iesg at ietf.org) by 2014-07-28.
>
> Time Zone Data Distribution Service (tzdist)
> ------------------------------------------------
> Current Status: Proposed WG
>
> Assigned Area Director:
>   Barry Leiba <barryleiba@computer.org>
>
> Mailing list
>   Address: tzdist@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/tzdist
>   Archive: http://www.ietf.org/mail-archive/web/tzdist/
>
> Charter:
>
> Time Zone Data Distribution Service (tzdist)
>
> -----------------------------------------------------------
>
> A time zone is a region that has a uniform local time for legal,
> commercial, and social purposes, with some regions using daylight saving
> time (DST) rules for part of the year. A local time is defined as a
> standard offset from Coordinated Universal Time (UTC), and a set of DST
> rules.  Time zone data represents the history, current, and future local
> time rules for these regions, together with an associated time zone
> identifier.
>
> Time zone data is a critical element of computer systems and devices that
> make use of local time. In particular, it is critical to any calendaring
> and scheduling system, such as iCalendar (RFC 5545). Daylight saving
> time rules, which affect local UTC offsets, can change - sometimes at
> very short notice (just a few days) - as those rules are typically
> defined by political processes.  Currently, there is no efficient, fast
> way to ensure that time zone data is updated in a timely and reliable
> manner on devices that need it.  Time zone changes are often delivered as
> operating system updates, and are thus tied to release schedules that
> can trail the actual time zone changes by a significant period of time. A
> service is needed that can provide timely, reliable updates.
>
> One added benefit of such a service for iCalendar is the ability for
> calendaring clients and servers to agree on common, standard definitions
> of time zone data, removing the need to pass time zone data directly "by
> value" in iCalendar data. By allowing clients and servers to use
> time zones "by reference" significant network bandwidth and storage
> savings can be achieved.
>
> This working group will:
>
> - Define a time zone data distribution protocol that allows for
> efficient, timely updates of time zone data to be delivered to clients.
> This protocol must scale to vast numbers of clients, such as the
> potential "internet of things" devices, as well as to today's desktop
> computers and servers.
>
> - Define an extension to CalDAV (RFC 4791) to allow clients and servers
> to use time zones "by reference" to improve the efficiency of the overall
> protocol.
>
> The working group will use the following drafts as initial input for its
> work:
> draft-douglass-timezone-service-11
> draft-daboo-caldav-timezone-ref-01
>
> The working group will work under the following parameters:
>
> - The time zone data distribution protocol will initially be targeted at
> iCalendar-based clients, but should be flexible enough to deliver
> time zone data in other formats.
>
> - The time zone data will be based on the Time Zone Database
> (http://www.iana.org/time-zones) but must be able to include any source
> of time zone data.
>
> - The time zone data distribution protocol should also offer an API to
> allow thin clients to easily make use of time zone data by querying for
> UTC offsets, offloading the sometimes complex work of expanding
> recurrence rules to the service. This API should be extensible to
> support other types of time zone operations in the future.
>
> - The time zone data distribution protocol will use current security
> protocols to protect the integrity and confidentiality of the data as
> it is distributed, and may also address these issues with respect
> to retrieval of data from its original source (such as the Time Zone
> Database). Even public time zone data can represent a significant
> privacy exposure when it is associated with the user or endpoint
> that is retrieving it.
>
> The following are Out of scope for the working group:
>
> - Any changes to the Time Zone Database process or infrastructure,
> as documented in RFC 6557. However, the WG may work with IANA
> in order to make integrity checking information, such as public keys,
> readily accessible for protocol use.
>
> - The naming process for time zone identifiers.  The working group can
> consider adding a mechanism, such as a "namespace" prefix, to
> differentiate different time zone sources, but the nature of the time
> zone
> identifiers used will be controlled by the sources themselves.
>
> - Lookup protocols or APIs to map a location to a time zone.
>
> Milestones:
>
> TBD
>
> _______________________________________________
> Tzdist mailing list
> Tzdist@ietf.org
> https://www.ietf.org/mailman/listinfo/tzdist
>

--bcaec51b14dd65274604fee2b455
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<br>I suggest a new simple network protocol for tim=
ezone data distribution without http for use in thin devices and IoT.<br>Be=
st Regards<br>Cristian<div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">
On Fri, Jul 18, 2014 at 9:21 AM, The IESG <span dir=3D"ltr">&lt;<a href=3D"=
mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretary@ietf.org</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">A new IETF working group has been proposed in the Applicat=
ions Area. The<br>

IESG has not made any determination yet. The following draft charter was<br=
>
submitted, and is provided for informational purposes only. Please send<br>
your comments to the IESG mailing list (iesg at <a href=3D"http://ietf.org"=
 target=3D"_blank">ietf.org</a>) by 2014-07-28.<br>
<br>
Time Zone Data Distribution Service (tzdist)<br>
------------------------------------------------<br>
Current Status: Proposed WG<br>
<br>
Assigned Area Director:<br>
=C2=A0 Barry Leiba &lt;<a href=3D"mailto:barryleiba@computer.org" target=3D=
"_blank">barryleiba@computer.org</a>&gt;<br>
<br>
Mailing list<br>
=C2=A0 Address: <a href=3D"mailto:tzdist@ietf.org" target=3D"_blank">tzdist=
@ietf.org</a><br>
=C2=A0 To Subscribe: <a href=3D"https://www.ietf.org/mailman/listinfo/tzdis=
t" target=3D"_blank">https://www.ietf.org/mailman/listinfo/tzdist</a><br>
=C2=A0 Archive: <a href=3D"http://www.ietf.org/mail-archive/web/tzdist/" ta=
rget=3D"_blank">http://www.ietf.org/mail-archive/web/tzdist/</a><br>
<br>
Charter:<br>
<br>
Time Zone Data Distribution Service (tzdist)<br>
<br>
-----------------------------------------------------------<br>
<br>
A time zone is a region that has a uniform local time for legal,<br>
commercial, and social purposes, with some regions using daylight saving<br=
>
time (DST) rules for part of the year. A local time is defined as a<br>
standard offset from Coordinated Universal Time (UTC), and a set of DST<br>
rules. =C2=A0Time zone data represents the history, current, and future loc=
al<br>
time rules for these regions, together with an associated time zone<br>
identifier.<br>
<br>
Time zone data is a critical element of computer systems and devices that<b=
r>
make use of local time. In particular, it is critical to any calendaring<br=
>
and scheduling system, such as iCalendar (RFC 5545). Daylight saving<br>
time rules, which affect local UTC offsets, can change - sometimes at<br>
very short notice (just a few days) - as those rules are typically<br>
defined by political processes. =C2=A0Currently, there is no efficient, fas=
t<br>
way to ensure that time zone data is updated in a timely and reliable<br>
manner on devices that need it. =C2=A0Time zone changes are often delivered=
 as<br>
operating system updates, and are thus tied to release schedules that<br>
can trail the actual time zone changes by a significant period of time. A<b=
r>
service is needed that can provide timely, reliable updates.<br>
<br>
One added benefit of such a service for iCalendar is the ability for<br>
calendaring clients and servers to agree on common, standard definitions<br=
>
of time zone data, removing the need to pass time zone data directly &quot;=
by<br>
value&quot; in iCalendar data. By allowing clients and servers to use<br>
time zones &quot;by reference&quot; significant network bandwidth and stora=
ge<br>
savings can be achieved.<br>
<br>
This working group will:<br>
<br>
- Define a time zone data distribution protocol that allows for<br>
efficient, timely updates of time zone data to be delivered to clients.<br>
This protocol must scale to vast numbers of clients, such as the<br>
potential &quot;internet of things&quot; devices, as well as to today&#39;s=
 desktop<br>
computers and servers.<br>
<br>
- Define an extension to CalDAV (RFC 4791) to allow clients and servers<br>
to use time zones &quot;by reference&quot; to improve the efficiency of the=
 overall<br>
protocol.<br>
<br>
The working group will use the following drafts as initial input for its<br=
>
work:<br>
draft-douglass-timezone-service-11<br>
draft-daboo-caldav-timezone-ref-01<br>
<br>
The working group will work under the following parameters:<br>
<br>
- The time zone data distribution protocol will initially be targeted at<br=
>
iCalendar-based clients, but should be flexible enough to deliver<br>
time zone data in other formats.<br>
<br>
- The time zone data will be based on the Time Zone Database<br>
(<a href=3D"http://www.iana.org/time-zones" target=3D"_blank">http://www.ia=
na.org/time-zones</a>) but must be able to include any source<br>
of time zone data.<br>
<br>
- The time zone data distribution protocol should also offer an API to<br>
allow thin clients to easily make use of time zone data by querying for<br>
UTC offsets, offloading the sometimes complex work of expanding<br>
recurrence rules to the service. This API should be extensible to<br>
support other types of time zone operations in the future.<br>
<br>
- The time zone data distribution protocol will use current security<br>
protocols to protect the integrity and confidentiality of the data as<br>
it is distributed, and may also address these issues with respect<br>
to retrieval of data from its original source (such as the Time Zone<br>
Database). Even public time zone data can represent a significant<br>
privacy exposure when it is associated with the user or endpoint<br>
that is retrieving it.<br>
<br>
The following are Out of scope for the working group:<br>
<br>
- Any changes to the Time Zone Database process or infrastructure,<br>
as documented in RFC 6557. However, the WG may work with IANA<br>
in order to make integrity checking information, such as public keys,<br>
readily accessible for protocol use.<br>
<br>
- The naming process for time zone identifiers. =C2=A0The working group can=
<br>
consider adding a mechanism, such as a &quot;namespace&quot; prefix, to<br>
differentiate different time zone sources, but the nature of the time<br>
zone<br>
identifiers used will be controlled by the sources themselves.<br>
<br>
- Lookup protocols or APIs to map a location to a time zone.<br>
<br>
Milestones:<br>
<br>
TBD<br>
<br>
_______________________________________________<br>
Tzdist mailing list<br>
<a href=3D"mailto:Tzdist@ietf.org" target=3D"_blank">Tzdist@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/tzdist" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tzdist</a><br>
</blockquote></div><br></div></div>

--bcaec51b14dd65274604fee2b455--


From nobody Wed Jul 23 20:52:43 2014
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 4524B1AD62C for <tzdist@ietfa.amsl.com>; Wed, 23 Jul 2014 20:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 0li7dz_WgaMq for <tzdist@ietfa.amsl.com>; Wed, 23 Jul 2014 20:52:39 -0700 (PDT)
Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 392061ADDC7 for <tzdist@ietf.org>; Wed, 23 Jul 2014 20:52:29 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id im17so3830383vcb.31 for <tzdist@ietf.org>; Wed, 23 Jul 2014 20:52:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OIWzrSLPx19jGkpMqnb0unvjTrMYjUA4VgVgQuIPlck=; b=Tt/y94p8oH3xN/oKxMp1TCkW/fiAZCD/1UHq5JBRLtFRn3F5ZROqgUzK62h6zk85Ne skQcyZg+TL/zTcGHBLm0PsMvy5apFW9AbbO4DxXexv5GA6cP52x0R2nC12HaEA5E7Hz+ slqQ3LMsU3Hb+yPVv8AsqPDAJj4rPfx2uUpi8SZ7GT9BDV1bq3Fi9Po+bWWwInvU8oYv q2kOaQqQRcUpq/DtWrIRCwEUBrKN4XAQoSSAs54dxINKreUSSg1gq/ppc3NFrR6X2fUY AAFBQfrFzVprGKiJjxvWjXf7eYaYMniRdaitseBPqkqfhjzacCoFP3BCEj17gWH4z8fm GPgA==
MIME-Version: 1.0
X-Received: by 10.52.9.68 with SMTP id x4mr6897488vda.20.1406173948515; Wed, 23 Jul 2014 20:52:28 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.181.71 with HTTP; Wed, 23 Jul 2014 20:52:28 -0700 (PDT)
In-Reply-To: <CAOj9aUW4+SUGKWTD9f26LqwM1+xzS5wPNJmbk4MdEdVcYB4XgA@mail.gmail.com>
References: <20140718122121.9152.82951.idtracker@ietfa.amsl.com> <CAOj9aUW4+SUGKWTD9f26LqwM1+xzS5wPNJmbk4MdEdVcYB4XgA@mail.gmail.com>
Date: Wed, 23 Jul 2014 23:52:28 -0400
X-Google-Sender-Auth: FuSMe45qtIa5yG5WGy906wdZz3s
Message-ID: <CAC4RtVAuPLBidS0a807xECv4KsFV4MBTyjKe=GtAqXEDCmHoQQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Cristian F. Perez Monte" <cristian.perez@gridtics.frm.utn.edu.ar>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/tzdist/JM_UJviPFbrZEKDhx_HzNL8oRYU
Cc: tzdist@ietf.org
Subject: Re: [Tzdist] WG Review: Time Zone Data Distribution Service (tzdist)
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: <http://www.ietf.org/mail-archive/web/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: Thu, 24 Jul 2014 03:52:40 -0000

> I suggest a new simple network protocol for timezone data distribution
> without http for use in thin devices and IoT.

That might be a good idea for follow-on work for this proposed working
group, after the basic protocol is finished.

Barry

