Re: [dns-privacy] Barry Leiba's No Objection on draft-ietf-dprive-bcp-op-08: (with COMMENT)

Barry Leiba <barryleiba@computer.org> Wed, 04 March 2020 21:33 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEFF43A0974; Wed, 4 Mar 2020 13:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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 IaNiHhmdeOGG; Wed, 4 Mar 2020 13:33:10 -0800 (PST)
Received: from mail-io1-f67.google.com (mail-io1-f67.google.com [209.85.166.67]) (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 69CEC3A0973; Wed, 4 Mar 2020 13:33:10 -0800 (PST)
Received: by mail-io1-f67.google.com with SMTP id z190so4115366iof.1; Wed, 04 Mar 2020 13:33:10 -0800 (PST)
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:content-transfer-encoding; bh=TXEr0wvFOGD4xsrp3qLazZz84O2dXeJC+bxXNsNwxvA=; b=dx3irhKJA2DSuWBFDsP7XB6nw/p0rUFNJ6vrlB+JzT7DWdaxDxG69/va6OnYYsxrvK eIt0f4Vaevm32vNhkXQiVP0kGoyQ1bJWceQD+2YFtNnFmsdsBF2XvWbwp/86KTdwmcuk t8dg7JPYYAmYSgMuyqHrvlXLuwLR4Cm1u04/dmltA++vmVFGctZ5feZTd6PfXrQODgBC J1/2kW8TQG/SibEeOOWN/MpLqJN7sdIMDd4liZjDG+PWL52DHz1C0DBoP/uTw8RCGBlL CzUbW5jaGxiG5aPWx2BmgSKoPZf8WWboKfsboqYbmZ7pHvAcKWBCQB40Z9y7cXmx6AjH z7wg==
X-Gm-Message-State: ANhLgQ3U0xukLDWcbX1kxGinQumnacug/PemhymjnxKKs04sEElf8GMr neEuJ1BdsG8Jt4p5YsYxkl8vbKqMXjusv5kIxMA=
X-Google-Smtp-Source: ADFU+vs6k8wVseCen26nPpk/MkIblJ+H2S5cz5W0SmO/+/+mjxZaWl56rAQrAn8XSSTZGzaVrKq3tBWMMLrRrFks90U=
X-Received: by 2002:a5d:9ed4:: with SMTP id a20mr3678317ioe.187.1583357589553; Wed, 04 Mar 2020 13:33:09 -0800 (PST)
MIME-Version: 1.0
References: <158089142938.12762.6290507656137173098.idtracker@ietfa.amsl.com> <DA73322A-65AC-4D2B-AAAF-701BED3AB7CE@sinodun.com>
In-Reply-To: <DA73322A-65AC-4D2B-AAAF-701BED3AB7CE@sinodun.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 4 Mar 2020 16:32:58 -0500
Message-ID: <CALaySJKf_V46TwZsc41-nQ-N5MG_N-cDXfEpAb-71Bcs2srtsQ@mail.gmail.com>
To: Sara Dickinson <sara@sinodun.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-dprive-bcp-op@ietf.org, Tim Wicinski <tjw.ietf@gmail.com>, dprive-chairs@ietf.org, dns-privacy@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/ABC50jaVJnkZrBJzLcKA-NPa9IM>
Subject: Re: [dns-privacy] Barry Leiba's No Objection on draft-ietf-dprive-bcp-op-08: (with COMMENT)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2020 21:33:12 -0000

Hi, Sara, and thanks for the response.

> > — Section 5.1.1 —
> >
> >   o  DNS-over-TLS [RFC7858] and [RFC8310].
> >   o  DoH [RFC8484].
> >
> > There’s no reason to hyphenate the former, and the latter should also be
> > expanded here:
> >
> > NEW
> >   o  DNS over TLS [RFC7858] and [RFC8310].
> >   o  DNS over HTTPS [RFC8484].
> > END
> >
> > Similarly, take the hyphens out of “DNS over DTLS” in the next paragraph, and
> > out of “DNS over TLS” throughout the document.
>
> Depends which draft you look at :-(
> RFC7858 uses DNS-over-TLS, RFC8484 uses DNS over HTTPS, other drafts also hyphenate….
>
> I happen to find the hyphenated form improves readability but can live with removing it (or using
> only the acronyms throughout) for consistency…..

OK... While I see no justification for hyphens (they're not compound
modifiers or anything like that), it's just a comment, and if you like
the hyphens then please leave them in.  The RPC will weigh in when
they do their edits, and we can let them make the final decision.  :-)

> > — Section 8 —
> > For a document such as this, the Security Considerations sectiin seems very
> > meagre.  As the Sec ADs have not called this out, I’ll presume they think it’s
> > OK, and I won’t press the issue.  Perhaps all relevant information is already
> > elsewhere in the document.
>
> Since this draft is really collecting together a set of existing techniques I think the feeling was that
> the reference for each technique should cover the security issues… If there were any new issues
> from combining specific techniques then they should be called out here but I don’t remember any
> being raised.

OK, and that fits in with the Sec ADs thinking it's OK.  All good, and
nothing to see here.

Barry