Re: [Doh] Benoit Claise's No Objection on charter-ietf-doh-00-12: (with COMMENT)

Benoit Claise <bclaise@cisco.com> Thu, 28 September 2017 21:09 UTC

Return-Path: <bclaise@cisco.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 AB1601349A5; Thu, 28 Sep 2017 14:09:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 NCD3SeB3-U3W; Thu, 28 Sep 2017 14:09:39 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE99613433C; Thu, 28 Sep 2017 14:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2485; q=dns/txt; s=iport; t=1506632979; x=1507842579; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=0GeoyOMZ4QTiOUEuGay++8eNYU0QZtF6pUeXQrmX0sY=; b=XK1WWOQ5IqsHKm6H9RIX+oPJOdG3eeWzKCwzzXKmmFW/hFHeYZTnY/sk hpzFLTeWRKodgblZj7OsuPIgbTr1gylte0f1/QnqW64LtYw9G/VdHxzAB QHioptCvVq1LxJLdnqvzxZZ4+auoBAWNQNKAtqKecolzeXFBvHW5OfHxv I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ByAQDKZM1Z/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhEBuhB+LE5BhljmCBAqFOwKEaBQBAgEBAQEBAQFrKIUZAQUjDwE?= =?us-ascii?q?FMwMLEAkCGAICJgICVwYBDAgBAYotiSidZoIni0MBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEggQ6CHYNTgWorgn2EUQESAYMygmAFh0SZZI8YhUiLW4crjXSHWYE5NiGBAws?= =?us-ascii?q?yIQgdFUmHHz6HBoI0AQEB?=
X-IronPort-AV: E=Sophos;i="5.42,451,1500940800"; d="scan'208";a="657897412"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Sep 2017 21:09:16 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v8SL9GAk019751; Thu, 28 Sep 2017 21:09:16 GMT
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: doh@ietf.org, doh-chairs@ietf.org
References: <150659321397.13780.18221165528947192319.idtracker@ietfa.amsl.com> <4cfa383f-deb3-6a13-6c63-218071454399@nostrum.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <ba813d4d-d6b1-8ea5-6eb0-e341f381e70c@cisco.com>
Date: Thu, 28 Sep 2017 23:09:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <4cfa383f-deb3-6a13-6c63-218071454399@nostrum.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/7rbIf2qsGahO15in6dPv1g7AN78>
Subject: Re: [Doh] Benoit Claise's No Objection on charter-ietf-doh-00-12: (with 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: Thu, 28 Sep 2017 21:09:41 -0000

That would help. Thanks Adam

B.
> On 9/28/17 5:06 AM, Benoit Claise wrote:
>> In my first ballot, I mentioned "What I've been failing to understand 
>> from the
>> charter is the rational for DNS over HTTPS? Can you expand on this." 
>> Because
>> I'm not an Web browser and DNS expert, or most likely because the 
>> concerns were
>> not clear in my head, I could not clearly express my thoughts.
>>
>> So I watched the IETF mailing list with attention.
>> Mark Nottingham's email summarized the situation
>>
>>      It's not a matter of constraining the work; the work isn't 
>> proposing to
>>      operate even remotely in the way that you describe. I think 
>> we're just
>>      having a misunderstanding, because people have multiple use 
>> cases in mind
>>      for this protocol, and properties thereof have been mixed up.
>>
>>      AIUI those use cases are, roughly:
>>
>>      1. Configure your browser/OS to use a DOH service for DNS 
>> resolution (as
>>      above) -- this will affect browser/OS state, because it's being 
>> used for
>>      DNS; however, it's not being done from JS.
>>
>>      2. Call a DOH service from Javascript (for some reason) -- note 
>> this is
>>      just like any other HTTP request; it doesn't affect browser/OS 
>> state
>>      outside of the same origin model. Yes, you can still build a
>>      browser-in-a-browser and mess with things inside that context, 
>> but that's
>>      already true today.
>>
>>      3. Future handwavy things like making DNS updates over HTTP -- very
>>      ill-defined and not important for this discussion
>>
>> Expressing #1 and #2 in the charter would have helped me. #2 is kind 
>> of present
>> now. What about the addition the notion of "browser and/or OS" in the 
>> next
>> sentence?
>>
>> The primary focus of this working group is to develop a mechanism that
>> provides confidentiality and connectivity between DNS Clients and 
>> Iterative
>> Resolvers.
>
>
> I think "browser" is likely to confuse the issue, since people are 
> likely to conflate that with JavaScript. Do you think it would be 
> clear enough to say the following?
>
> "The primary focus of this working group is to develop a mechanism that
> provides confidentiality and connectivity between DNS Clients (e.g., 
> operating
> system stub resolvers) and Iterative Resolvers."
>
> /a
>
> .
>