<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/7/20 19:43, Tim Parenti wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFpi07xVD6H0tDL=3iOc=QgL3Ey0V6G8Fu1bh0kUR5dUeFsKRA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">A reasonable criterion for inclusion should
probably be whether the service makes the protocol accessible
for arbitrary consumption, whether openly or by authenticated
subscription.
<div><br>
</div>
<div>The phrase "supports TZDIST" can of course mean several
different things, but while there are benefits to using the
protocol internally to a product, I don't think this fulfills
the expectation that it would tend to evoke here. From the
perspective of someone reading tz-link.html, it's much more
important to answer "where are some public tzdist servers I
can point my project to?" rather than "what's something that
happens to speak tzdist to its own clients?" (The latter,
frankly, is of little relevance to consumers of the tz project
data.)</div>
</div>
</blockquote>
<p>We implemented (and use) those servers to provide a starting
point. Having a service requires some infrastructure maintained by
some body or consortium. I believe Ken's server fully supports
tzdist (and beyond). Mine may be a little out of date but supports
pretty much the latest.</p>
<p>However, neither of us can provide the infrastructure - that's
for somebody such as IANA<br>
</p>
<blockquote type="cite"
cite="mid:CAFpi07xVD6H0tDL=3iOc=QgL3Ey0V6G8Fu1bh0kUR5dUeFsKRA@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div><br clear="all">
<div>
<div dir="ltr" data-smartmail="gmail_signature">--<br>
Tim Parenti<br>
</div>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 7 Sep 2020 at 17:24,
Paul Eggert <<a href="mailto:eggert@cs.ucla.edu"
target="_blank" moz-do-not-send="true">eggert@cs.ucla.edu</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
9/7/20 1:23 PM, Brian Inglis wrote:<br>
> If you follow those links and dig into those servers,
they appear to be mail<br>
> server calendar addins, which use vzic to convert tzdata
source into VTIMEZONEs,<br>
> for updating and caching calendar zones, not providing
any kind of service or<br>
> distribution, except to their own mail server calendar
clients.<br>
<br>
Thanks for following those links, which I didn't bother to do.
If they don't <br>
support the TZDIST protocol then I suppose I should revert the
recently-proposed <br>
change to tz-links.html[1] which says they do.<br>
<br>
[1] <a
href="https://github.com/eggert/tz/commit/cb2d288ae0bb3aa5fb7cc94480ea955ff76bd183"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/eggert/tz/commit/cb2d288ae0bb3aa5fb7cc94480ea955ff76bd183</a><br>
</blockquote>
</div>
</blockquote>
</body>
</html>