Re: [Tzdist-bis] Spencer Dawkins' No Objection on draft-murchison-tzdist-tzif-15: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 25 October 2018 03:15 UTC

Return-Path: <spencerdawkins.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 2CC90130DCD; Wed, 24 Oct 2018 20:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level:
X-Spam-Status: No, score=-1.2 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, HTML_MESSAGE=0.001, MIME_BOUND_DIGITS_15=0.798, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 d7nzLVhxFwRZ; Wed, 24 Oct 2018 20:15:57 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 1D58F130DCA; Wed, 24 Oct 2018 20:15:56 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id z21-v6so6769481ljz.0; Wed, 24 Oct 2018 20:15:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GCH+0LJqj5flIHSITYtKBdA5NTSCCGRzr0hdm1aTDi8=; b=WBSeVE3Yf/8YOxqGSs4u7wAZyepC84KHRUMlVo1gQxRU6xZmg66YR2RwXSf+UkQ4W5 WkjdW6bLgoayKK2onzRLv6qQ+HXz1AWw1vJn9N1ZJ6FI8WOymzJfypI3fP8juCgPLq9W SMCxWcmjz5f/KlsSdTDXjt5zbrZ1Ly9Dqg7at3ZtdwDuaoj/eqdXLU1/oztrOraBgSJW soz1YG5Iw26XuXwDrTGZqQ9AacZUlQi2QfosEbze3g9cczzdm+M8WUqL9G1ixogDdNqT jO8m/r1ApvdR+um+Vb9Hc3zjcAHQvMZ4XB0MQ/OkXLws1b+HsUFhb8RU1Vs7/x5dJdmm fQ5w==
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=GCH+0LJqj5flIHSITYtKBdA5NTSCCGRzr0hdm1aTDi8=; b=fELs/MPtjGdXg+ypCo1zSuHoOKFb67Q7VGRsc4qPWnQ3ppWFzEGTO7GqTF/brsSk2u mNdmLXCJ4EUZijvhaz4/A2QHAftRubvcUqF+WuyQKwIS3ic1SfKTkFV2p24OddqiRg7P B2vZ6GtdMUnFz6TAwOaoEc1S4wdIFNdwQVP5kS951ZRpp1WT5PmYJqj4ViJLafpOE+Cf GHIjsAG1kEofUPYvN9cTtl/wkdyiKsKs0ntWm5m6h06tSYI6+MbxBrBvDidfZId1jPo7 MD/Di6Wf8XYb1QWtnzkxwgslrhn3fF4NOIqY+D7v7GI9/RthRlC72YzEu81Ve3ywixZk 5yNA==
X-Gm-Message-State: AGRZ1gJPE+NFdF0bb9j5Ss5GZSwEZSqJBD3ezzBaO00KEB/ZL8qu7iLX FgRhTo8Hj0UtwEKBlwXSfMijFXajj5LoEquAwWw/fQ==
X-Google-Smtp-Source: AJdET5dqoaLF1Z8vQX5hkk5uFr4BCwKdpaslv1ebVClSqB4SJzRvCXhXKBJL3fEIinjCtFOUpyaZg/MwZko6TbIR7kA=
X-Received: by 2002:a2e:908b:: with SMTP id l11-v6mr3323338ljg.25.1540437354945; Wed, 24 Oct 2018 20:15:54 -0700 (PDT)
MIME-Version: 1.0
References: <154035253315.31261.16689737832868120020.idtracker@ietfa.amsl.com> <daf7dff1-3b98-0b0e-eb98-dd680c1f7e5a@ofcourseimright.com>
In-Reply-To: <daf7dff1-3b98-0b0e-eb98-dd680c1f7e5a@ofcourseimright.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 24 Oct 2018 22:15:43 -0500
Message-ID: <CAKKJt-coY9F7uPZYJBygLJnmTBjOP-ny88nu4oxjMU55edq7pQ@mail.gmail.com>
To: Eliot Lear <lear@ofcourseimright.com>
Cc: IESG <iesg@ietf.org>, draft-murchison-tzdist-tzif@ietf.org, tzdist-bis@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005722760579050558"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tzdist-bis/wgGrQXdv2nWbhC5mqjfJgpCyGDs>
Subject: Re: [Tzdist-bis] Spencer Dawkins' No Objection on draft-murchison-tzdist-tzif-15: (with COMMENT)
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: Thu, 25 Oct 2018 03:15:59 -0000

Hi, Eliot,
On Wed, Oct 24, 2018 at 3:32 AM Eliot Lear <lear@ofcourseimright.com> wrote:

> Hi Spencer, Adam, and Ben,
>
> Alexey asked me to shepherd this doc.  Here is my view on the comments
> received thus far:
>
>    - On Adams suggestion for an including an example, within the bounds
>    of readability, it should be included as an appendix.  Paul and Ken are
>    looking for something suitable (they found an error in a zone in the
>    process!).
>    - On Spencer's point on “define”, The authors are documenting an
>    existing format, but are also defining a code point.  I propose the use of
>    the word “specifies”.  Covers all evils.
>
> I wondered (at the non-blocking Comment level) whether the relationship
between what's being documented here and what's deployed in Unix
implementations would be clear to most readers - it was not obvious to me.
ISTM that it would be useful to say "this stuff is currently deployed as
specified in this document" or "this stuff is currently deployed as
specified in this document, except that section NN is new, and section OO
is a significant change from today's deployed implementations".

But I know you'll do the right thing :-)

Spencer

>
>    -
>    - On Adam's point on privacy considerations, I tend to agree, and
>    would suggest that the authors update accordingly to indicate the risk, and
>    that appropriate protections be considered, with perhaps an informational
>    reference to Sections 8 and 9 of RFC 7808.  It is not possible to list all
>    mitigations, of course, because this is a file format and not a protocol.
>
> Eliot
>
> On 24.10.18 05:42, Spencer Dawkins wrote:
>
> Spencer Dawkins has entered the following ballot position for
> draft-murchison-tzdist-tzif-15: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:https://datatracker.ietf.org/doc/draft-murchison-tzdist-tzif/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I'm a little confused on one high-level point. In this text,
>
>    This document defines the Time Zone Information Format (TZif).  It is
>    a binary format used by most UNIX systems to calculate local time.
>    There is a wide variety of interoperable software [tz-link] capable
>    of generating and reading files in this format.
>
> is it correct to say that you're documenting the existing format, or are you
> also defining aspects that are not currently deployed (which would obviously be
> "defining")?
>
>
>
>
>