Re: [dns-privacy] Erik Kline's Yes on draft-ietf-dprive-rfc7626-bis-06: (with COMMENT)

Tim Wicinski <tjw.ietf@gmail.com> Thu, 08 October 2020 12:55 UTC

Return-Path: <tjw.ietf@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 922CA3A0AE0; Thu, 8 Oct 2020 05:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 l-7pvP_Lsvr8; Thu, 8 Oct 2020 05:55:26 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (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 721D83A0AD9; Thu, 8 Oct 2020 05:55:26 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id c13so6149273oiy.6; Thu, 08 Oct 2020 05:55:26 -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=ZC3RzgoEI3nMPufjCAxFo0W7WY8Tvh3sYk4/AFF+0G0=; b=RWRnb5U8d4+VlyeOGRMEBzO0dDlZkE7KyXsl5Tjjk+r3KE3sEbNd8+ze4pfEMVclUh RvpNZMY2RgWrDdVVMM/W2+i3TLQd/2C7i/XDGz/9vECbGl9bYld9KNLDEvFtk4NKnP9P SqYTs1HxUj3KuUFQNW2P0GYZV4We46qjWfHK2X3dCSvdpAtwKCyPnynS/GA3BtC6qDDR irZqkNz2y3U51/VGKHSQpALrWbbwMS4nScGvYJJjwsc3edWEsh8I/yHo+YU3NXbbkQwK IeiHVlJQxo+mwczyo+CBXwAQX16NQBk/AB3BYo0bOUfEf5omHT3kb9zozm9+LSWk4TM4 ZPag==
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=ZC3RzgoEI3nMPufjCAxFo0W7WY8Tvh3sYk4/AFF+0G0=; b=Xxn3m+gvhVvT3AWqIbR5Sk+7kmDR2GgVO3QMQp030a4r+igg7+cx8m2ov77Cbmi52s LL0949DEvcPP5JXM2SC8m1NuaQIZ8h9fUv7nHZpiKgSwScl4Pa6TrSMxfEKre9ZO5AQH v7ac2LCAkDslUCQr0rVmvqajiS8QR0lRwkcR6YDKgd0UUsv8ZtCb6sbyASLoYqGKTwgS Q2DpwfIGg1973AG2cKixz13i7xOb1sHevXOKb7C1rwg79ncay+Lb4I19jvWGURwFmKvo DImk0jiSUds1b0ew8JIfQayw+9IdTSuhwp8UDVsgfkS3/6WU8CXEeAIOX//kPFxtgseQ kXIA==
X-Gm-Message-State: AOAM532LgGNuEb99oWuGvJRZrfcbDGMh+VLNXWglPZW0pC4j/w6TAKEi DuvHQlq2AswA66ZysCEeNmkDA4fG/P5y+9/QLig=
X-Google-Smtp-Source: ABdhPJxHZXsonJwUlcO8lboUV5Y8OpbPraIldzcdNXB6bfHBV4gIYNHqHNt/fVJsDVk4X6Wq+ZPOGQJ0RX3KNKldB58=
X-Received: by 2002:a05:6808:aa7:: with SMTP id r7mr5165387oij.174.1602161725624; Thu, 08 Oct 2020 05:55:25 -0700 (PDT)
MIME-Version: 1.0
References: <160196426178.19491.17560402380844863303@ietfa.amsl.com>
In-Reply-To: <160196426178.19491.17560402380844863303@ietfa.amsl.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 8 Oct 2020 08:55:14 -0400
Message-ID: <CADyWQ+EeYNpTQkZ___jCtNgiH4o-1AHC5YVNK31YBYAkRD30wA@mail.gmail.com>
To: Erik Kline <ek.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-dprive-rfc7626-bis@ietf.org, dprive-chairs@ietf.org, DNS Privacy Working Group <dns-privacy@ietf.org>, Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary="00000000000087576205b1285868"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/AvK2SQwvrNvjWUqHx1I3IN3rznc>
Subject: Re: [dns-privacy] Erik Kline's Yes on draft-ietf-dprive-rfc7626-bis-06: (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: Thu, 08 Oct 2020 12:55:29 -0000

On Tue, Oct 6, 2020 at 2:04 AM Erik Kline via Datatracker <noreply@ietf.org>
wrote:

> Erik Kline has entered the following ballot position for
> draft-ietf-dprive-rfc7626-bis-06: Yes
>
> 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-ietf-dprive-rfc7626-bis/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> [[ questions ]]
>
> [ section 6.1.1.1 ]
>
> * Does "Strict DoT" have a definition somewhere?  I couldn't find one
>   in 8499 nor in 7858.
>
>
Erik

There is not a definition for "Strict DoT", but DNSOP has a CfA out on
updating 8499-bis with
some updates which will include Strict DoT.


> [[ nits ]]
>
> [ section 1 ]
>
> * "sent in clear", consider perhaps: "sent in the clear"
>
> [ section 4.1 ]
>
> * "those transaction" -> "those transactions"
>
> [ section 6.1.1 ]
>
> * "to limited subset" -> "to a limited subset"
>
> [ section 6.1.3 ]
>
> * "know to be used" -> "known to be used"
>
>
> Thanks - updated all of these

tim