Re: [Doh] Eric Rescorla's Block on charter-ietf-doh-00-00: (with BLOCK and COMMENT)

Adam Roach <adam@nostrum.com> Mon, 11 September 2017 19:59 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA1B13239C; Mon, 11 Sep 2017 12:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham 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 wvDmzzjPxQrC; Mon, 11 Sep 2017 12:59:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 280CE132339; Mon, 11 Sep 2017 12:59:02 -0700 (PDT)
Received: from Svantevit.roach.at (cpe-70-122-154-80.tx.res.rr.com [70.122.154.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v8BJx0L3070590 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 11 Sep 2017 14:59:01 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-154-80.tx.res.rr.com [70.122.154.80] claimed to be Svantevit.roach.at
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
Cc: doh@ietf.org, doh-chairs@ietf.org
References: <150497915406.8167.17608149948148839208.idtracker@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <e61d8e64-736e-9cc1-f99b-95f5b497af2e@nostrum.com>
Date: Mon, 11 Sep 2017 14:59:00 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150497915406.8167.17608149948148839208.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/k6J2b9MrAiJEnj9Wyx0d3lLaanw>
Subject: Re: [Doh] Eric Rescorla's Block on charter-ietf-doh-00-00: (with BLOCK and COMMENT)
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 19:59:06 -0000

On 9/9/17 12:45 PM, Eric Rescorla wrote:
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
>
> This charter seems oddly agnostic on whether or not we are defining
> use over HTTP or over HTTPS. In 2017, I think its imperative that this
> only be chartered for secure transports (which is, after all, implicit
> in the value proposition).  I agree with Martin Thomson that "HTTPS"
> is the right way to convey this point.

The charter text had used "HTTP" only where it was an adjective (e.g., 
"HTTP semantics"), and "HTTPS" everywhere else.  Although it sounds a 
bit odd to my ear, the latest revision refers to "HTTPS infrastructure," 
"HTTPS clients," "HTTPS semantics," and "HTTPS protocol".

/a