Re: [DNSOP] PSD records, was Verifying TLD operator authorisation
Tim Wicinski <tjw.ietf@gmail.com> Sat, 22 June 2019 23:14 UTC
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27F22120047 for <dnsop@ietfa.amsl.com>; Sat, 22 Jun 2019 16:14:23 -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=ham 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 IprFWFbyDAbQ for <dnsop@ietfa.amsl.com>; Sat, 22 Jun 2019 16:14:21 -0700 (PDT)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 2F2E5120019 for <dnsop@ietf.org>; Sat, 22 Jun 2019 16:14:21 -0700 (PDT)
Received: by mail-ot1-x335.google.com with SMTP id l15so9888185otn.9 for <dnsop@ietf.org>; Sat, 22 Jun 2019 16:14:21 -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=fDE2JKfSIyllEC7gsH4ezTtCda3MWqPv0ZpUdE1zJWU=; b=CYiK883XxZywjvtvh4Yzfn4AgsoUfuc+bkrRXenKmRqZ2RTyC+RCsmlem9le7vvhZb 6qJApzfbcTsqCiSJHLkyrm01Hof2u2THH0w78vx0IVaZLQTJdkb7IAgXXsKZepOo4bu7 onE1mwJz9gB6PY2Hyx3r3OATkMpQ8gAfys2lsH+5U7+oBq91oBlOSwyGKDZBNBifmG/H tyZ49Ur9CxQ60wJY1rP2Q/MgTvjiyPOK30ohXV0Cu1HJSzFUcoxaK2jp/3PzeItIkSE+ sutj0OTHaKTE+mofeS5r4jylXhEiSlNN2lDKo6oTsgwRAi+2i0ItheSga2jpgYlWm4PI yhag==
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=fDE2JKfSIyllEC7gsH4ezTtCda3MWqPv0ZpUdE1zJWU=; b=n3p6DHbqaMmz7RdVRgEdmyY88tfkacGYkezdkayAPe8ph4Ivu2Uuz4ikwpc71uBJ6w ZheL6M3MmQSwC/Cdc6RRpplYIwkoPoVv2rDt6JzKr2uIqUOtrMSHot4AqVxJZqJj/BiC fbHJDwoQfuk0zyT/+xJbQvqm23eUFxjMFVM46hleK8P8rPFkv4qAE1QKAk0qjlTyF5iP qJrN0zIoGcdlEEA0D7XcPL0W9OzvXZCJ9VaWJ3vm2m5dMGZC3a62H1sqZdT8iK2rdM2O ItpKfvU+1e6UcOLEmPzc8KwDr0DbliZfBfooOXypYscFDRLtr7fmyJTDvUBCdJzDva7K WSGg==
X-Gm-Message-State: APjAAAX3nPXG5x0RaNeijmiSvfk21ZnAmrmdpPtG5A0xzTHL0NNQsF9J v5aZag+vukw9M+2c5Bqypp3BMV4unDv+3bOplzw=
X-Google-Smtp-Source: APXvYqxNXe/tFrk3502kaSj8byBQ9PJIa/yIDwG/8oqvLC0tMQshzYtz3K24NVTvI7YW+x/YZYZ3r8XOPXahN/WwLoA=
X-Received: by 2002:a9d:7a45:: with SMTP id z5mr6042538otm.197.1561245260457; Sat, 22 Jun 2019 16:14:20 -0700 (PDT)
MIME-Version: 1.0
References: <CADyWQ+HVYAfVE0WSEPAG7Zz_OL+uM4DmHRLn6Y=mAPQZE5M7eQ@mail.gmail.com> <20190622030814.2556D201630FF7@ary.qy>
In-Reply-To: <20190622030814.2556D201630FF7@ary.qy>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sat, 22 Jun 2019 19:14:09 -0400
Message-ID: <CADyWQ+GMNMyMYJd1nKeVzQrviSdwG4=NcAxNcDS0Gr5rRYtxzA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: dnsop <dnsop@ietf.org>, Seth Blank <seth@valimail.com>
Content-Type: multipart/alternative; boundary="000000000000282900058bf1bddf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tcIu9v8NrMWoUAPOw3ab1QMQiGc>
Subject: Re: [DNSOP] PSD records, was Verifying TLD operator authorisation
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2019 23:14:23 -0000
John I totally agree with you we need to Nerd Harder one the problem space, and folks are trying. But one way we Nerd Harder is to do experiments like this and study how it works, and use that moving forward. I've been talking to folks over the past months on this problem space trying to grapple with quantifying what other folks see. Part of this reason is that my employer has this problem, and while my boss and I have noodled on the idea off and of for the past year, my feeling is that our Java developers will decide to solve this problem for their use case, and it will be done in their way makes their life easier and everyone else's life harder. I'd like to be in front of the problem, leading them toward my promised land than chasing them from behind nipping at their heels. Talking as a chair, I see this more of an Application of DNS Problem than a DNS Operations Problem, but I'm willing to be convinced otherwise. This means, the work may be out of scope for DNSOP. I do feel that whatever solution the IETF works we, we have to first accept that it will *not* replace the Public Suffix List initially. The PSL is a W3C entity, and while I feel they will look honestly at what the IETF may create, they are free to adopt or not adopt it for the PSL, and the IETF needs to accept that. We've not only have to solve the problem, we need to make a convincing case for the W3C to adopt. I find the IETF is great at the former, and struggles at times with the latter. Tim (mostly speaking as myself) On Fri, Jun 21, 2019 at 11:08 PM John Levine <johnl@taugh.com> wrote: > In article <CADyWQ+HVYAfVE0WSEPAG7Zz_OL+uM4DmHRLn6Y= > mAPQZE5M7eQ@mail.gmail.com> you write: > >-=-=-=-=-=- > > > >If y'all care what gets published in a TLD, please take a look at > >https://datatracker.ietf.org/doc/draft-ietf-dmarc-psd/ > >which is an experimental draft that will go into WGLC last call soon. > >This was driven by wanting to add _dmarc records > >into TLDs, per ICANN rules it needs to be an RFC. > > I'm not thrilled about it since I would prefer that we nerd harder on > the general domain boundary problems (the ones for which we all use > the PSL), but PSD for its particular use case of name trees seems > pretty harmless. > > R's, > John >
- [DNSOP] Verifying TLD operator authorisation Nick Johnson
- Re: [DNSOP] Verifying TLD operator authorisation Joe Abley
- Re: [DNSOP] Verifying TLD operator authorisation Nick Johnson
- Re: [DNSOP] Verifying TLD operator authorisation Rubens Kuhl
- Re: [DNSOP] Verifying TLD operator authorisation Nick Johnson
- Re: [DNSOP] Verifying TLD operator authorisation Rubens Kuhl
- Re: [DNSOP] Verifying TLD operator authorisation Nick Johnson
- Re: [DNSOP] Verifying TLD operator authorisation Shane Kerr
- Re: [DNSOP] Verifying TLD operator authorisation Jim Reid
- Re: [DNSOP] Verifying TLD operator authorisation Dr Eberhard W Lisse
- Re: [DNSOP] Verifying TLD operator authorisation Jim Reid
- Re: [DNSOP] Verifying TLD operator authorisation Vladimír Čunát
- Re: [DNSOP] Verifying TLD operator authorisation Nick Johnson
- Re: [DNSOP] Verifying TLD operator authorisation Bjarni Rúnar Einarsson
- Re: [DNSOP] Verifying TLD operator authorisation Jim Reid
- Re: [DNSOP] Verifying TLD operator authorisation Jim Reid
- Re: [DNSOP] Verifying TLD operator authorisation Shane Kerr
- Re: [DNSOP] Verifying TLD operator authorisation Nick Johnson
- Re: [DNSOP] Verifying TLD operator authorisation Joe Abley
- Re: [DNSOP] Verifying TLD operator authorisation Mark Andrews
- Re: [DNSOP] Verifying TLD operator authorisation Tim Wicinski
- Re: [DNSOP] Verifying TLD operator authorisation Matthew Pounsett
- Re: [DNSOP] PSD records, was Verifying TLD operat… John Levine
- Re: [DNSOP] PSD records, was Verifying TLD operat… Tim Wicinski
- Re: [DNSOP] PSD records, was Verifying TLD operat… John R Levine
- Re: [DNSOP] Verifying TLD operator authorisation Vittorio Bertola