Re: [Add] [EXTERNAL] Re: Firefox DoH behaviour

Erik Kline <ek@loon.com> Tue, 16 July 2019 22:59 UTC

Return-Path: <ek@google.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3694F1200A4 for <add@ietfa.amsl.com>; Tue, 16 Jul 2019 15:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.249
X-Spam-Level:
X-Spam-Status: No, score=-9.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.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 Xv_ALAolswmS for <add@ietfa.amsl.com>; Tue, 16 Jul 2019 15:59:25 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 435C312013E for <add@ietf.org>; Tue, 16 Jul 2019 15:59:25 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id h6so42684735iom.7 for <add@ietf.org>; Tue, 16 Jul 2019 15:59:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.com; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=Bm9sXJS78KPj8f1LkgRs65cNGRTpMogcNGuexrLOllc=; b=blGMEl1oHisOrk3TMOM01dljsSo79YEsM9Wm4cqF2v26/z9G3J/S7LBsl7RncnKYVN e4azYwKd/gmLlmMmkFqn7sPj0rmOdIdchHx9vqpdgVboQenH9s2nkJc9RopjYi9nsY7r pMaBD6//0gytYBwbQTcf93BOVxsE4nt146F/g=
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:reply-to :from:date:message-id:subject:to:cc; bh=Bm9sXJS78KPj8f1LkgRs65cNGRTpMogcNGuexrLOllc=; b=rdvs+CqyWtzFvKBV5RQtA7+FuedfoOPgl50LLBkY01gGOFP7G46oFHG7ysZnvq9bje 58gQJC1xOOoHMdiBtVd6VwnP2AYYWJHgYbT2LfWLWAqONOhXXsdGBDmzBVPatyXH2Ra4 Ym8KCgOYYMjVHnfzG7vTdnBDiR9jODX4LcHBMd1yWSiODdctRnFXmVwPKB5F1W8W+gOQ eUz14fg+pgZ2kmw0fKcGHqjbWR7tds4KpT45E8dTT7gHbfQv9u1VqXtXWjPU6pr2AEBv svmMlYubaVDQGAu1l99BniI7CmukNcb3bvIRGPGxTTxax3KLhTj4YpA9mpT8t35tkRfH 7lYA==
X-Gm-Message-State: APjAAAX9+DRCMMau2OaM/yGzs/7j7dxsDqjL5l6ce5yLXjdvfn7L80RD ZjSUWA6i4ishfmxmvNDP4Lnxxt7YP6youcSWaiun2g==
X-Google-Smtp-Source: APXvYqya2KwUYATWUnbweNDeYVAKBMzTqizJwWmX5xWv+FZqEhSfHuY+SeN3rx7KPCPXiMMtN4hleeYBUXcFaTmdUCc=
X-Received: by 2002:a02:c90d:: with SMTP id t13mr36476194jao.62.1563317964160; Tue, 16 Jul 2019 15:59:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SwEUz9MrdRA0bnv9f-oNi0oUHkfRKjd9-o6jwhuckLXdw@mail.gmail.com> <CAFWeb9LNdT=EYVKTsYDxcBCQKoQFNShKotYtWujt4U9GA-V1mg@mail.gmail.com> <CAFWeb9+eWKSKY9O2JLn9-0+Zq7hrD48F-y+Y4T-iRaaF0vtdOA@mail.gmail.com> <A45F4F74-D6C1-435A-A52F-C2DEA82E2999@sky.uk> <CAFWeb9JVBj+Yehup5q4v9X-7XDY+02frd-04AQGL2HoSLON2qA@mail.gmail.com> <CABcZeBMY9q9vKGse1svzbvXF_dSHA+9q06j4ugDVCZP9VT1koQ@mail.gmail.com> <CAChr6Sz5Rfz=UxOYuPguSvVK2HCX2ZoA1-FytW7+EOUxN8y46Q@mail.gmail.com> <CABcZeBNB7ASu2U3ZMBZ+OOxEhbSnhDXwFN3Lsex1uzVSDv3R=Q@mail.gmail.com> <c9c83673-c12e-0093-3873-0f2c03155fa5@brokendns.net> <CABcZeBP50XudcymGzTJP7XBZzBNw-SsVHFS07wJ++FxoHMHtNw@mail.gmail.com> <A1B73CC9-0A06-4D7D-8AF0-041AE5719B60@rfc1035.com> <CABcZeBPo3Li6BTKzWiK+TCmQDOMs07rOTPuXUxiiofK5xgW8pw@mail.gmail.com> <C587AEA7-E9EF-42D7-95D6-CAD416F1BF56@nbcuni.com> <CABcZeBPEa7Yc6GzYLho5ZmDgN0xeP729iszQ+OhM8+QZNyASXw@mail.gmail.com>
In-Reply-To: <CABcZeBPEa7Yc6GzYLho5ZmDgN0xeP729iszQ+OhM8+QZNyASXw@mail.gmail.com>
Reply-To: ek@loon.com
From: Erik Kline <ek@loon.com>
Date: Tue, 16 Jul 2019 15:59:12 -0700
Message-ID: <CAAedzxq-UxVEPNHQ8Wotgu5fh9F_JWC_MtKgZRVSiHdj1jEW6Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>, Jim Reid <jim@rfc1035.com>, "add@ietf.org" <add@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ed6ce2058dd45357"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/-Bv8CbUcbkEdgxyayyZBmt0SfDU>
Subject: Re: [Add] [EXTERNAL] Re: Firefox DoH behaviour
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2019 22:59:27 -0000

On Tue, 16 Jul 2019 at 12:23, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Tue, Jul 16, 2019 at 11:56 AM Deen, Glenn (NBCUniversal) <
> Glenn.Deen@nbcuni.com> wrote:
>
>> Hi
>>
>> On Jul 16, 2019, at 1:56 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>>
>> Sorry, this was badly written. Here's an attempt to clarify:
>>
>> if there is an enterprise policy that is set and it configures or enables
>> DoH, then when we will respect that. If there is an enterprise policy set
>> and it says nothing about DoH, then our plan is to disable DoH on the
>> theory that with high probability the enterprise would want DoH off.
>>
>> When I refer to enterprise policy I mean:
>> https://support.mozilla.org/en-US/products/firefox-enterprise/policies-customization-enterprise/policies-overview-enterprise
>>
>>
>> Just so I understand, this looks like it only applies to enterprise
>> managed desktops, or to PCs enrolled in a managed AD environment.
>>
>
> Yes.
>
>
>> Is there a general means for the enterprise to communicate it’s policy
>> for any Firefox instance that runs in its network?
>>
>
> Not at present.
> https://tools.ietf..org/html/draft-grover-add-policy-detection-00
> <https://tools.ietf.org/html/draft-grover-add-policy-detection-00> is an
> exploration of one possible avenue, but as has been discussed somewhat
> extensively, it's not a secure signal, so we're not sure how useful it is.
>

I was wondering about the possibility of having a signal in the intarea PVD
additional info
<https://tools.ietf.org/html/draft-ietf-intarea-provisioning-domains-05#section-4>
JSON.

Simplest: a boolean that says "our DNS servers do/do not filter". Compliant
apps/OSes can observe and choose to comply.

Slightly more complicated: a field that contains a list of resolvers that
do filtering.  Again, compliant OSes/apps can know to use those.