IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Sat, 27 July 2019 13:09 UTC

Return-Path: <ekr@rtfm.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 E3C4A12027A for <add@ietfa.amsl.com>; Sat, 27 Jul 2019 06:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 X2e3nHRCiWwC for <add@ietfa.amsl.com>; Sat, 27 Jul 2019 06:09:23 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 56C72120140 for <add@ietf.org>; Sat, 27 Jul 2019 06:09:23 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id v24so54196087ljg.13 for <add@ietf.org>; Sat, 27 Jul 2019 06:09:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OrHHFY7ZwAbtTPseyXUea2lyBvZ7vHDz0l4vVCzYggQ=; b=0yXTuKPYCOTwJP2vRmjE80QrBLMg4GG2sJa7H/kRrfBzXjIj6PqxTFcA9HB0mfW4l4 03YTgUnhMKXgae1Ih0FVGWtxG0SFQdCFq+aavbZZKrQM7Rb9bv0XSsD6ViR31nrpS+QJ mR94/0B7TRvltknZoOc+IQG0UzDEDasybo2/oCv9b+YXYoiawUoDizjiAYCHVD5bFUDY iOr8ZDT0v0wyT2O/KFLR1fknAehVLwZG3frqVI5zzgh4xsG+3KNUoIyFk2SQ3apylm+J EB16Fb8NJljuKPaC3xq9zCMMGoQt1aHSwbIyV9FIRI0PMTctwQq5BKuvFI8pYs3fvLWA RYnQ==
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=OrHHFY7ZwAbtTPseyXUea2lyBvZ7vHDz0l4vVCzYggQ=; b=c6zxF6MCp+Bf8ooeT4k3rTy1Bi6Zcoa6l1DfY3IP4t5MpKVvnoXI3v3cfYOg4dktGw +z4nAzu+UWshv8A4iyLDzFHf3BaZ20VMDarjG4yxWVDGS4RcM0zvHkolAupcyZDHp34m Dkspix+vsiMGII0dFeq4G88AaX93MKVa2CPESfASOE0aiLzkqpEbSUso2uphMPrzfuUZ 0wDlrqmfmyBruf5tQzVYF7tGktkGjTLpancUFt0DVRtwwODsnO6smZ4ObHB3PfWPEsOO nfyJu4cV2T6lH71qX/tQo5NCmIZPqP++tuZ6MQB/QMeNTR0KYTNVbTUp56/bIiOtc1Ih LKiA==
X-Gm-Message-State: APjAAAXvLDUL1Ih5D+tdvmTvTPtF8kcA1cb8HiVkXcZ3Mb0HsJjiXJvl ysUUY6HUq3WbBH/SPmFgNSITh8KpMSGgFI1O5d0=
X-Google-Smtp-Source: APXvYqxmI28vPsJimk2sztVVkYVQA7mGK95TksthcX2yrxjWM3csDwFcf5KWaTvBcOL6Ufr1qJU/EGGXbnnycPn+hzY=
X-Received: by 2002:a2e:3008:: with SMTP id w8mr53470039ljw.13.1564232961420; Sat, 27 Jul 2019 06:09:21 -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>
In-Reply-To: <25583.1564181379@dooku.sandelman.ca>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 27 Jul 2019 06:08:44 -0700
Message-ID: <CABcZeBNnajRyEtOdhk2nS7uNgQM_z04FbEyxSFWMQ8ho82dPiQ@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Adam Roach <adam@nostrum.com>, ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000002ffbf058ea95eb0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/6h-CRR8iQA7zovV30mEZvRvgCnM>
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 13:09:26 -0000

On Fri, Jul 26, 2019 at 3:49 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Adam Roach <adam@nostrum.com> wrote:
>     > Since you mention Firefox's TRR list and then mention data mining
> (with an
>     > implied connection), I'd like to point out yet again that one of the
> key
>     > criteria for appearing on that list is an agreement to treat
> resolution
>     > data according to a strict set of privacy-protecting provisions. You
>     > can see, for
>     > example, Cloudflare's associated privacy policy at
>     >
> https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/
>
> Does Mozilla have a policy/proceedure to vet the privacy policy
> of DoT/DoH providers?  Maybe Mozilla is considering this?
>

Yes:
https://wiki.mozilla.org/Security/DOH-resolver-policy


Would it be appropriate for this to go into
> a certificate extension (perhaps signed by a Mozilla CA)?
>

I'm not sure what this would buy us over just having a list.

-Ekr


> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>

v2.23.0 | Report a Bug | By Email