IETF Logo Mail Archive

Re: [Add] meeting hum: should the IETF take up this work?

Rob Sayre <sayrer@gmail.com> Sat, 27 July 2019 02:05 UTC

Return-Path: <sayrer@gmail.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 905941201FA for <add@ietfa.amsl.com>; Fri, 26 Jul 2019 19:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 y4LM4G1iRzaR for <add@ietfa.amsl.com>; Fri, 26 Jul 2019 19:05:39 -0700 (PDT)
Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com [IPv6:2607:f8b0:4864:20::d41]) (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 E7CE11201D9 for <add@ietf.org>; Fri, 26 Jul 2019 19:05:38 -0700 (PDT)
Received: by mail-io1-xd41.google.com with SMTP id s7so108468946iob.11 for <add@ietf.org>; Fri, 26 Jul 2019 19:05:38 -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=N2sog6SkjlBxiJNljV9osBZaxwnQ+I8RqhVBBIWw3Dg=; b=LXJvV+quPblHkKERI4NLeFZJ1Z8l6scFP8dKyiGt74xQ9vqKIWvpeotb1kvW3HyGJ3 al2TjMx4J4bQA64ddvy7OJLdCiWOa3r7OtFtm8TvcyToq5Hj0fPaR2OFc0re9T5DpKfc fHZ1RIpLj4EjYSMQmLggE8/ZBT7MSoD8+wTj/0FOYPgrbEqc38sjRuZ78qmuM/jtIO02 Lk5CQc7oGBRm9apFn1czdaTQbzdCBFUOmdrUoNC05ab3mvATmjBPtELhbUTtpsUDS167 1MIRqRLlNI73h36r/M2A4369fh89jymvM6i3zPbmD1Dh/RpZdMtfK/D1Gh5s7Ypj9J6I nT9w==
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=N2sog6SkjlBxiJNljV9osBZaxwnQ+I8RqhVBBIWw3Dg=; b=awGvcWqDOkocg0bHO0wJzZm205BoC4M5i32SMvZa/92GzjOqKRRgfOTee2LYaPXwft ZXKYsjG+qa6ooeUyAx6ICRHrLbEoPtbxxpF4QmKPGNHiJrzJrv5jMZBPvbUnuDxWt8wS iRcgi5b4S7mM3niMg2V/UxmCSx5V3/0Jb7q4bIo9Qo9uihAXOsFw06VnuuszIzMtWFeS 013qLk1FDN8YC9bRyykfUK8pX3Zv8r+qe4yTw9Iy/x3CmYmzt9dOdNRBCL+ecU1MIqlK u07XJ+njhdKm5EYN2g/sajNpqfLmzuRd5J1V65rxotU3wwLHMSO1aegY40YrvfSfh/C7 pmVw==
X-Gm-Message-State: APjAAAUe4bJTW12p4H4zPOn8neGGYMFPfT/xIBCPleUVTMYXOS6KJg3G x6oJqWb66GqJsGi7ShANa+OGXE0wgRYTlEWBhYE=
X-Google-Smtp-Source: APXvYqzYUWI7Vly6V2bvtSicqdTueghAdCMqGJTlhtaznMmAivh66UUuCiN2vN+HEAi/FCGp9sc5valDXGe1jWH1Qa4=
X-Received: by 2002:a05:6602:98:: with SMTP id h24mr27644508iob.49.1564193138149; Fri, 26 Jul 2019 19:05:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <AAEA003A-58DB-4FEE-81B2-BBFE9BBB2A37@rfc1035.com> <CAChr6SwA+HM4u5-xpUxQXPH8G8k7sfm6AETJJ019HE=bsq+OXA@mail.gmail.com> <8F094057-DFBC-4732-9DA4-BE46E7914C8A@rfc1035.com> <20190724165951.GB29051@laperouse.bortzmeyer.org> <821B448B-F7EA-46A5-837D-DA0E8C60643A@open-xchange.com> <d653d422-4a71-9fab-fd2e-b8ddaa476f91@nostrum.com> <25583.1564181379@dooku.sandelman.ca> <CAHbrMsCd_0xAsFYAVyO=Jo-t_Zw0WE9j=fNphQsAkL-_TwVf1w@mail.gmail.com>
In-Reply-To: <CAHbrMsCd_0xAsFYAVyO=Jo-t_Zw0WE9j=fNphQsAkL-_TwVf1w@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 26 Jul 2019 19:05:26 -0700
Message-ID: <CAChr6SwPue5VO8mP1YhZ_5jcbUBuQKK9rWTJsf7bWRpAQN9hGg@mail.gmail.com>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, add@ietf.org, Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="0000000000005c0d2d058ea01878"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/H-ElEju8K9oQYv38W1Z5xNsH_40>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
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: Sat, 27 Jul 2019 02:05:42 -0000

On Fri, Jul 26, 2019 at 5:20 PM Ben Schwartz <bemasc=
40google.com@dmarc.ietf.org> wrote:

> On Fri, Jul 26, 2019 at 6:49 PM Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>> Does Mozilla have a policy/proceedure to vet the privacy policy
>> of DoT/DoH providers?  Maybe Mozilla is considering this?
>>
>
> Yes, they've published their minimum criteria here:
> https://wiki.mozilla.org/Security/DOH-resolver-policy#Privacy_Requirements
>

Without getting into specifics, many ISPs use their DNS traffic as fuel for
an ad network and/or sell the data on, and thus wouldn't meet those
requirements. Whether that's a good or bad thing is probably outside the
already-vague scope of this mailing list.

That's one reason I don't think the IETF should get involved at the moment,
and why terms like "policy" or "operational requirements" can be
problematic.

thanks,
Rob

v2.23.0 | Report a Bug | By Email