IETF Logo Mail Archive

Re: [dmarc-ietf] Request to accept a new I-D into the WG work items

"John Levine" <johnl@taugh.com> Thu, 08 November 2018 06:16 UTC

Return-Path: <johnl@iecc.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 C72A2130E04 for <dmarc@ietfa.amsl.com>; Wed, 7 Nov 2018 22:16:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=L7VS1s+0; dkim=pass (1536-bit key) header.d=taugh.com header.b=cMFCkkqN
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 LAxCeCYiGY_q for <dmarc@ietfa.amsl.com>; Wed, 7 Nov 2018 22:16:54 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0699912D4ED for <dmarc@ietf.org>; Wed, 7 Nov 2018 22:16:53 -0800 (PST)
Received: (qmail 40784 invoked from network); 8 Nov 2018 06:16:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9f4e.5be3d4d4.k1811; bh=VQ0by21uwP03iorP7EsbcKo52zKZgQogKTK8LcNfaWQ=; b=L7VS1s+0eQtAZHe4WMCAa5eEufb7jI+BImbMXugLzjgLU1eC3pNQMCidsyu938FaW6UERR4TQI4P/9kDK/w8TOfDzNyB5krhFqFNbKd6ZWbK5b2/M8cFQcCb4bjSMrW84FncqHWpaq/uXV3IrReab35fhLitqUMPqz+D1vb7UBSyZN9VhWauLnz1T1PfTndhBGDrOLceKf2pjC2y1vS+vA/R3wStAkrdvHsUFuaVf7GVrVkgvmfx3/c+RUEkk0wc
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9f4e.5be3d4d4.k1811; bh=VQ0by21uwP03iorP7EsbcKo52zKZgQogKTK8LcNfaWQ=; b=cMFCkkqNf/Pf2U+r1JqV2dFVnSPcCrmvdpc13kPTK+zINflM9sUAz/UzY93vw/UvAj225dqcXHwZ3kxDJ7hkxf1upMQoH5ttxoMA9Ii+skn0A1am+3eQiKlgq2ROs5mN+58Cb/qq+L2HI6ktsclyGHkPr6hjgzEeGpGEXm9YffVfZUyj3qET2BtxWihXiHio7L3v9CfkNlV+RO35/jLj5haIDsDfBkT2KqfpUz1NLAv4nt4FoK9nge41POr0d4B3
Received: from dhcp-8071.meeting.ietf.org ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 08 Nov 2018 06:16:51 -0000
Received: by dhcp-8071.meeting.ietf.org (Postfix, from userid 501) id 0AF13200829C06; Thu, 8 Nov 2018 13:16:50 +0700 (+07)
Date: Thu, 08 Nov 2018 13:16:50 +0700
Message-Id: <20181108061651.0AF13200829C06@dhcp-8071.meeting.ietf.org>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: sklist@kitterman.com
In-Reply-To: <0E28DA8C-09A6-4E64-AD5E-3741EFE60569@kitterman.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ceC_lF99czspe8x3JqOB-k_hXpI>
Subject: Re: [dmarc-ietf] Request to accept a new I-D into the WG work items
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: Thu, 08 Nov 2018 06:16:56 -0000

In article <0E28DA8C-09A6-4E64-AD5E-3741EFE60569@kitterman.com> you write:
>Unfortunately, I didn't come up with an idea for how to do this in DNS.  This seems like a legitimate issue
>for the WG to work through.

There were two DNS proposals in DBOUND, a more complex one from Casey
Deccio and a simpler one from me.  Mine would certainly work for identifying
org domains.

R's,
John

v2.23.0 | Report a Bug | By Email