Re: [dmarc-ietf] Mention ICANN/operational limitations was: Re: Working Group Last Call: draft-ietf-dmarc-psd

Scott Kitterman <sklist@kitterman.com> Sat, 13 July 2019 18:42 UTC

Return-Path: <sklist@kitterman.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F17412017E for <dmarc@ietfa.amsl.com>; Sat, 13 Jul 2019 11:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=76ECPtom; dkim=pass (2048-bit key) header.d=kitterman.com header.b=kKaQhhgS
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 UwOslPkUueJu for <dmarc@ietfa.amsl.com>; Sat, 13 Jul 2019 11:42:36 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CEAC120157 for <dmarc@ietf.org>; Sat, 13 Jul 2019 11:42:36 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 2EA88F80689; Sat, 13 Jul 2019 14:42:05 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1563043325; h=date : in-reply-to : references : mime-version : content-type : content-transfer-encoding : subject : to : from : message-id : from; bh=CvqUBauFOBgLCxz1+DsWtNfyz+7s82FN8yuIivY7/ak=; b=76ECPtomW3G29eY+o2pH+yDzuedpIE81usglJYTDbJF4g5eaAip/LERu 84UuWaQDkDVcQD/3ysSt767hByanAw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1563043325; h=date : in-reply-to : references : mime-version : content-type : content-transfer-encoding : subject : to : from : message-id : from; bh=CvqUBauFOBgLCxz1+DsWtNfyz+7s82FN8yuIivY7/ak=; b=kKaQhhgSslE8BwAv8cep+tA6doSwWCGrnmpIjlvZ7KDxfpQgW+u5fAvl uAMhY/TN5/dM1UzvUxvRmtwrV6jLPOtEem8Vuzug+Mr7mKZZG87ZUIvh6f tETMnw4xYWHORbcK/wgKLb9jot3nVTr5ceUfVsBKWCP11gJymxJ3Go4We9 EeOx1AGWR6qAFtfXGneMaBBWUnzvqe7TuZSEiwRyhrhJ/8vmAYl6j6SQ99 /TtJhattYVkVJCmHqyoA4qFX3RiS7G9zcpcgFAnk1wmvpqx8kIcaboJGIt 85xc63UVeobAkTZdIylMWVVTvE/el66km00x6w5HQUu85tNo2HXTkw==
Received: from [192.168.1.184] (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id D6090F80607; Sat, 13 Jul 2019 14:42:04 -0400 (EDT)
Date: Sat, 13 Jul 2019 18:42:03 +0000
In-Reply-To: <0c52a75d-1a67-d095-f5f6-e74a8a4ff958@tana.it>
References: <CAL0qLwbbz_UhBLsURg=eXhRBC2g9OghiN==T9Uq9pFuLtd=b7w@mail.gmail.com> <CAOZAAfN0+nxpN1P_nk3y5f8MTQ=c7DYNvYic2iDMuCK_bNa=qg@mail.gmail.com> <1783751.gHVjF1RMII@l5580> <0c52a75d-1a67-d095-f5f6-e74a8a4ff958@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: dmarc@ietf.org
From: Scott Kitterman <sklist@kitterman.com>
Message-ID: <A453B61B-AE87-4F67-8E52-96B7F7FE518F@kitterman.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tc9R3x8DSIQig7kyivtjcn8tcrs>
Subject: Re: [dmarc-ietf] Mention ICANN/operational limitations was: Re: Working Group Last Call: draft-ietf-dmarc-psd
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jul 2019 18:42:38 -0000


On July 13, 2019 5:21:31 PM UTC, Alessandro Vesely <vesely@tana.it>; wrote:
>On Fri 12/Jul/2019 19:41:17 +0200 Scott Kitterman wrote:
>> How about this instead:
>> 
>> "As of the writing of this document operational and policy
>constraints prevent 
>> this experiment from being deployed globally.  If the experiment
>shows that 
>> PSD solves a real problem and can be used at a large scale, the
>results could 
>> prove to be useful in the development of policies outside of the IETF
>that 
>> would permit broader deployment".
>
>
>I'm not familiar with operating a TLD.  The above text seems to imply
>that TLD operators cannot just edit their zone files as they like.  In
>that case, couldn't that statement be more explicit?  In particular,
>what does allow the experiment to be deployed locally?

Some can, some can't.  It's complicated and it's nothing to do with IETF protocol, so I don't think it's on topic to go into any details.

Scott K