IETF Logo Mail Archive

Re: [Add] What to do in this potential working group

"Ralf Weber" <dns@fl1ger.de> Thu, 22 August 2019 11:12 UTC

Return-Path: <dns@fl1ger.de>
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 0B142120832 for <add@ietfa.amsl.com>; Thu, 22 Aug 2019 04:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 vdSdduxoXdgq for <add@ietfa.amsl.com>; Thu, 22 Aug 2019 04:12:14 -0700 (PDT)
Received: from smtp.guxx.net (nyx.guxx.net [85.10.208.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6D97D120837 for <add@ietf.org>; Thu, 22 Aug 2019 04:12:13 -0700 (PDT)
Received: by nyx.guxx.net (Postfix, from userid 107) id D06115F42CA1; Thu, 22 Aug 2019 13:12:12 +0200 (CEST)
Received: from [192.168.2.190] (p54B8ABDF.dip0.t-ipconnect.de [84.184.171.223]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id 028D25F42377; Thu, 22 Aug 2019 13:12:11 +0200 (CEST)
From: Ralf Weber <dns@fl1ger.de>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Ray Bellis <ray@bellis.me.uk>, ADD Mailing list <add@ietf.org>
Date: Thu, 22 Aug 2019 13:12:11 +0200
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <7893F89E-ACB5-42EF-B8B6-5CF460FA5D0E@fl1ger.de>
In-Reply-To: <CABcZeBMmAqsRwA1YwdzCyRT_tNzkHEDe3u916c7KhWWBeKqPkg@mail.gmail.com>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com> <766112E1-F532-4C6B-8CA8-A096671E02EE@piuha.net> <CABcZeBO1nqtSOn8hmcC58Ys5rC9=fXLPQhWStgWL0oSfMQ072g@mail.gmail.com> <a250ce7e-db59-8b74-3ac7-9c5d751b1cb8@bellis.me.uk> <CABcZeBMmAqsRwA1YwdzCyRT_tNzkHEDe3u916c7KhWWBeKqPkg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/30A6jZfXlUT-C3DBX5fa9UK5jIQ>
Subject: Re: [Add] What to do in this potential working group
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: Thu, 22 Aug 2019 11:12:17 -0000

Moin!

On 21 Aug 2019, at 19:01, Eric Rescorla wrote:
> Indeed: this is what I was referring to when I said "ways to minimize
> centralization". Specifically, ISPs could commit to strong privacy policies
> and join our TRR program.
A lot of ISPs have way stronger privacy policies then the TRR program, yet
they can not join because it’s impossible to fulfil the other requirements
and IMHO bad decsisions in the TRR program what to require and what not:
- No DNSSEC
- But qname minimisation that breaks stuff and for larger resolvers adds
not much
- Requirement to publish block lists

So long
-Ralf
---
Ralf Weber

v2.23.0 | Report a Bug | By Email