[dmarc-ietf] DMARC Specific Organizational Boundary Determination

Scott Kitterman <sklist@kitterman.com> Wed, 21 November 2018 07:43 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 37EB3130EE2 for <dmarc@ietfa.amsl.com>; Tue, 20 Nov 2018 23:43:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=0gb0Svg5; dkim=pass (2048-bit key) header.d=kitterman.com header.b=lGKBGAib
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 ealWRsrB-seu for <dmarc@ietfa.amsl.com>; Tue, 20 Nov 2018 23:43:38 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16EC3130EDD for <dmarc@ietf.org>; Tue, 20 Nov 2018 23:43:38 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1542786217; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=JN2Be/4qIOFjsGKO6cqRA6wf5Kxvh7JflOut2FZ2KBY=; b=0gb0Svg5ep8XZq5mFqC3r1NlOv1czJ2kIGWnbgR/GAIDuvKdvOgEGxED SGEvZmYgiqo7phKWzlWhFzUH4LTZBQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1542786217; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=JN2Be/4qIOFjsGKO6cqRA6wf5Kxvh7JflOut2FZ2KBY=; b=lGKBGAibGec6VBXOHXZFfDDs+A7yoz35WeYrT1lj6/7VAQqaE4Y1Bc1p mS7pjjeO8ATbiq/dtWUMb4Cw2EpM2AF+6j6zxpaUxXMbb0n7ofS3CXevw0 IX4dUk8zHoj829tkxXY0utLEvuCpDjloHn2+WZz8UUTMAokfk5dQAH0TJE ZI21rWEaowLfx2w6hQt6PAfmwdqMI3POtXJCATsffeTVnIDG3YPbJWglHW y5wn6oKV/m9hHSV5s9iIP9Y/gAYYsUOFogUco9rQrodNxJdHs6sZHqHarV gwk9tps93oX7fN8RQHvgSYak8NpeWX/Qbj3bjSo2yGCCr3zCNywCwQ==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 4A9C7C40229 for <dmarc@ietf.org>; Wed, 21 Nov 2018 01:43:37 -0600 (CST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Wed, 21 Nov 2018 02:43:37 -0500
Message-ID: <1752433.LPKdqegoTl@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-158-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/F0kP_O3QGVxDdC88SN9BynWZC3A>
Subject: [dmarc-ietf] DMARC Specific Organizational Boundary Determination
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: Wed, 21 Nov 2018 07:43:39 -0000

While we were discussing the Public Suffix Domain DMARC draft, there seemed to 
be a fair amount of juice on this topic.  I'd suggest further discussions in 
this thread.

Scott K