Re: [Add] Mozilla's DoH resolver policy
Adam Roach <adam@nostrum.com> Fri, 19 April 2019 15:54 UTC
Return-Path: <adam@nostrum.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 ADBBD120167 for <add@ietfa.amsl.com>; Fri, 19 Apr 2019 08:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 Fd-uLxECOI-s for <add@ietfa.amsl.com>; Fri, 19 Apr 2019 08:54:52 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 EB100120170 for <add@ietf.org>; Fri, 19 Apr 2019 08:54:51 -0700 (PDT)
Received: from Orochi.local (rrcs-24-173-40-58.sw.biz.rr.com [24.173.40.58]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x3JFsbo5093955 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 19 Apr 2019 10:54:39 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1555689284; bh=BJS/62sL2oP17e8FG1LB1Vd6KZBPql0hV5tI/QzNrPs=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=vJyBrxhTh+5l8GyCHaONdBoUViIRjXdHq5oUMCjqCiKod6QaHdWGdD+JvC3j4jsyB i8i1bapqSATZmkpOfgcdaCPTJ8wKiojNxs+RLYzXHssgCOwQ8YRYzdmleIjBlkLFOr 4BJKq2nA6Eka5DcGlR1A0YPfjJBlhdsbjfNAWINI=
X-Authentication-Warning: raven.nostrum.com: Host rrcs-24-173-40-58.sw.biz.rr.com [24.173.40.58] claimed to be Orochi.local
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "vladimir.cunat+ietf@nic.cz" <vladimir.cunat+ietf@nic.cz>, "dns@fl1ger.de" <dns@fl1ger.de>, "daniel@haxx.se" <daniel@haxx.se>
Cc: "add@ietf.org" <add@ietf.org>
References: <297C80CE-F017-4F4A-80E2-79941E8B9E02@icann.org> <b64761dc-dfab-e4e1-4bfb-82d607efa590@riseup.net> <alpine.LRH.2.21.1904101324530.9940@bofh.nohats.ca> <64aeff58-6d68-4c4f-b991-2b2f62d193a0@www.fastmail.com> <90A5C5C4-373C-4B39-80C2-C115CD23CB4D@fl1ger.de> <CACQYfiJa1i2LVgQDcHi_OknmDDKZiaw=++Y6imn34LcPULP3bQ@mail.gmail.com> <E0CA1520-74D4-4A41-9B44-10946FAB4534@fl1ger.de> <CACQYfiKeh=FgmB9RN=eJ-2tq4jyTg55fep4au9SeGe3U5VkMBQ@mail.gmail.com> <ED802588-CD5D-4F80-914D-CA25EE234424@fl1ger.de> <alpine.DEB.2.20.1904111144200.31156@tvnag.unkk.fr> <792D4346-DE43-4BFC-85D4-FC58366E38B5@fl1ger.de> <945967b1-581f-e603-49f1-b9f173decb39@nic.cz> <9d20eb02-9322-875e-230a-e229f516819d@nostrum.com> <2a877eed406c4746bb6da97e2407aac7@verisign.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <5bf5e4ae-911a-ef96-6dff-2456a6583db3@nostrum.com>
Date: Fri, 19 Apr 2019 10:54:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <2a877eed406c4746bb6da97e2407aac7@verisign.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/add/_A-2OYURUzRy1xpistcRhw2ljdc>
Subject: Re: [Add] Mozilla's DoH resolver policy
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: Fri, 19 Apr 2019 15:54:54 -0000
On 4/19/19 14:02, Hollenbeck, Scott wrote: >> -----Original Message----- >> From: Add <add-bounces@ietf.org> On Behalf Of Adam Roach >> Sent: Thursday, April 11, 2019 11:42 AM >> To: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>; Ralf Weber >> <dns@fl1ger.de>; Daniel Stenberg <daniel@haxx.se> >> Cc: add@ietf.org >> Subject: [EXTERNAL] Re: [Add] Mozilla's DoH resolver policy >> >> On 4/11/19 10:18 AM, Vladimír Čunát wrote: >>> If Firefox is to be taken mainly as a real-life example on this >>> mailing-list, is there a suitable Firefox-specific place to discuss >>> related issues? (Assuming Mozilla is actually interested in that.) >>> >> Of course your input is welcome. Mozilla is an opensource project, and >> everyone is invited to participate. >> >> For implementation discussions, DoH is part of our networking stack, called >> Necko. Those are discussed on >> https://groups.google.com/forum/#!forum/mozilla.dev.tech.network >> >> For privacy-related discussions, use >> https://groups.google.com/forum/#!forum/mozilla.dev.privacy > Adam, would discussion of the operational aspects of the TRR program (things like "this is what's expected of participating resolvers") be appropriate for this list or one of the lists described above? Speaking only for myself [and not in any official role] -- My suggestion would be that you decide what you're trying to accomplish and post to one or the other accordingly. If you want to have a conversation with other Mozilla contributors about the specific TRR policy that Mozilla has adopted, I'd use a Mozilla mailing list. If you want to provide input to something that you see the IETF eventually publishing, I'd post it here. In the latter case, I would imagine you'd talk in more general terms about operational guidance for all applications, rather than focusing on suggestions for a single product: the chances that the IETF publishes a document that focuses on guidance for a single product are vanishingly small. /a
- [Add] Mozilla's DoH resolver policy Paul Hoffman
- Re: [Add] Mozilla's DoH resolver policy nusenu
- Re: [Add] Mozilla's DoH resolver policy Paul Wouters
- Re: [Add] Mozilla's DoH resolver policy Martin Thomson
- Re: [Add] Mozilla's DoH resolver policy Ralf Weber
- Re: [Add] Mozilla's DoH resolver policy Valentin Gosu
- Re: [Add] Mozilla's DoH resolver policy Vittorio Bertola
- Re: [Add] Mozilla's DoH resolver policy Jim Reid
- Re: [Add] Mozilla's DoH resolver policy Ralf Weber
- Re: [Add] Mozilla's DoH resolver policy Manabu Sonoda
- Re: [Add] Mozilla's DoH resolver policy Valentin Gosu
- Re: [Add] Mozilla's DoH resolver policy Ray Bellis
- Re: [Add] Mozilla's DoH resolver policy Ralf Weber
- Re: [Add] Mozilla's DoH resolver policy Daniel Stenberg
- Re: [Add] Mozilla's DoH resolver policy Paul Wouters
- Re: [Add] Mozilla's DoH resolver policy Vladimír Čunát
- Re: [Add] Mozilla's DoH resolver policy Ralf Weber
- Re: [Add] Mozilla's DoH resolver policy Vladimír Čunát
- Re: [Add] Mozilla's DoH resolver policy Adam Roach
- Re: [Add] Mozilla's DoH resolver policy Peter Saint-Andre
- Re: [Add] Mozilla's DoH resolver policy Peter Saint-Andre
- Re: [Add] Mozilla's DoH resolver policy nusenu
- Re: [Add] [Ext] Mozilla's DoH resolver policy Paul Hoffman
- Re: [Add] [Ext] Mozilla's DoH resolver policy Peter Saint-Andre
- Re: [Add] [Ext] Mozilla's DoH resolver policy Adam Roach
- Re: [Add] [Ext] Mozilla's DoH resolver policy Brian Dickson
- Re: [Add] [Ext] Mozilla's DoH resolver policy Adam Roach
- Re: [Add] Mozilla's DoH resolver policy Vittorio Bertola
- Re: [Add] Mozilla's DoH resolver policy Wes Hardaker
- Re: [Add] Mozilla's DoH resolver policy Peter Saint-Andre
- Re: [Add] Mozilla's DoH resolver policy Ted Hardie
- Re: [Add] Mozilla's DoH resolver policy Wes Hardaker
- Re: [Add] Mozilla's DoH resolver policy Ted Hardie
- Re: [Add] Mozilla's DoH resolver policy Wes Hardaker
- Re: [Add] Mozilla's DoH resolver policy Christian Huitema
- Re: [Add] Mozilla's DoH resolver policy Mark Andrews
- Re: [Add] Mozilla's DoH resolver policy Wes Hardaker
- Re: [Add] Mozilla's DoH resolver policy Vittorio Bertola
- Re: [Add] Mozilla's DoH resolver policy Vittorio Bertola
- Re: [Add] Mozilla's DoH resolver policy Livingood, Jason
- Re: [Add] Mozilla's DoH resolver policy Livingood, Jason
- Re: [Add] Mozilla's DoH resolver policy Salz, Rich
- Re: [Add] Mozilla's DoH resolver policy Ben Schwartz
- Re: [Add] Mozilla's DoH resolver policy Adam Roach
- [Add] ECS privacy concerns, alternatives? Brian Dickson
- Re: [Add] ECS privacy concerns, alternatives? Brian Dickson
- Re: [Add] ECS privacy concerns, alternatives? Mark Delany
- Re: [Add] ECS privacy concerns, alternatives? Brian Dickson
- Re: [Add] ECS privacy concerns, alternatives? Mark Delany
- Re: [Add] Mozilla's DoH resolver policy Christian Huitema
- Re: [Add] ECS privacy concerns, alternatives? Brian Dickson
- Re: [Add] Mozilla's DoH resolver policy Geoff Huston
- Re: [Add] Mozilla's DoH resolver policy Ralf Weber
- Re: [Add] Mozilla's DoH resolver policy Paul Wouters
- Re: [Add] ECS privacy concerns, alternatives? Erik Nygren
- Re: [Add] ECS privacy concerns, alternatives? Joe Abley
- Re: [Add] ECS privacy concerns, alternatives? Brian Dickson
- Re: [Add] ECS privacy concerns, alternatives? Joe Abley
- Re: [Add] ECS privacy concerns, alternatives? Paul Hoffman
- Re: [Add] ECS privacy concerns, alternatives? Brian Dickson
- Re: [Add] Mozilla's DoH resolver policy Hollenbeck, Scott
- Re: [Add] Mozilla's DoH resolver policy Adam Roach
- Re: [Add] ECS privacy concerns, alternatives? Puneet Sood
- Re: [Add] ECS privacy concerns, alternatives? Erik Kline
- Re: [Add] ECS privacy concerns, alternatives? Brian Dickson