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

Eric Rescorla <ekr@rtfm.com> Sat, 09 September 2017 17:45 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: doh@ietf.org
Delivered-To: doh@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1589613219F; Sat, 9 Sep 2017 10:45:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: The IESG <iesg@ietf.org>
Cc: doh-chairs@ietf.org, doh@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150497915406.8167.17608149948148839208.idtracker@ietfa.amsl.com>
Date: Sat, 09 Sep 2017 10:45:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/SXncQ4AWmyjTTve8PPZ75dmE4hg>
X-Mailman-Approved-At: Mon, 11 Sep 2017 08:37:59 -0700
Subject: [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
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: Sat, 09 Sep 2017 17:45:54 -0000

Eric Rescorla has entered the following ballot position for
charter-ietf-doh-00-00: Block

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.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-doh/



----------------------------------------------------------------------
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.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


I think I agree with MT's point that it would be best if this binding
were agnostic about HTTP/2 over TLS versus HTTPS over QUIC (or
whatever we call it) and to the extent possible, agnostic about HTTP/2
versus HTTP/1.1 (i.e., the binding should be indifferent for the
functionality that don't depend on explicit HTTP/2 features like
push). However, I think we could send the charter out for review
w/o deciding that.