IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Sat, 10 November 2018 04:38 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 E46BF130FF0 for <dmarc@ietfa.amsl.com>; Fri, 9 Nov 2018 20:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.752
X-Spam-Level:
X-Spam-Status: No, score=-1.752 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] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=kbJdZYzc; dkim=pass (1536-bit key) header.d=taugh.com header.b=LwXl016e
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 JMWyZ_o5kRVz for <dmarc@ietfa.amsl.com>; Fri, 9 Nov 2018 20:38:53 -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 9E49D130E7F for <dmarc@ietf.org>; Fri, 9 Nov 2018 20:38:53 -0800 (PST)
Received: (qmail 22669 invoked from network); 10 Nov 2018 04:38: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=5889.5be660dc.k1811; bh=rhwx7a/WIA6TrPuNH4ePVAofFZw1eKy79f2w6218KUI=; b=kbJdZYzcGINP0k0hkRUbhL7gwTAe3pyEcAoSafbPibkpwWiVuO26pWw/qE4bn8SuvML2bBHaqohFJPpkiujXhF6GTbETRXciK7a6GZ7nyS2CM1aHpbjwLtSUGEeVEkTr2Zp0zsFlCsOMHiZkv3Zuc45OS4rM+4/qax/2hTHBsAVibN7SEm8GToeBNYcizMi49rW2mizQO+RWOVxUPqBZRhdlGH54kdKsTgWijuDsrXxw/eUIEckbH9UbFCXm1PUA
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=5889.5be660dc.k1811; bh=rhwx7a/WIA6TrPuNH4ePVAofFZw1eKy79f2w6218KUI=; b=LwXl016e52jBn5XVVHrujKcGt06gM0uWOuFaPhG9w7HS0rIxLSZJsjrZKmuaoHH2E+YXJclexYcCDU4iskYVwP25wkAIm7MHfTWqqGyLa+25Jhqd/V0biUc3+RmbjNDZjlUEHUIDBkbQWY5TLs+gfiYkTx+qFK4hzFQjw4xQMF8i/Yr3cgK2D2YdfuUswNyD3eptRphn6jLXoCXSca8Q/16+1ERILo5ByGho9IHgYbWGRmDlrAAypbzRClwpy2hm
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; 10 Nov 2018 04:38:51 -0000
Received: by dhcp-8071.meeting.ietf.org (Postfix, from userid 501) id C0BED200834BFD; Sat, 10 Nov 2018 11:38:50 +0700 (+07)
Date: Sat, 10 Nov 2018 11:38:50 +0700
Message-Id: <20181110043850.C0BED200834BFD@dhcp-8071.meeting.ietf.org>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: tjw.ietf@gmail.com
In-Reply-To: <CADyWQ+EA2wRSU0bxCNu4ez+R2q+0ZK9NF41Zgqpz4CJLNRq17A@mail.gmail.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/6WE5JApNcZHwXwAUN0iETTy7ESE>
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: Sat, 10 Nov 2018 04:38:55 -0000

In article <CADyWQ+EA2wRSU0bxCNu4ez+R2q+0ZK9NF41Zgqpz4CJLNRq17A@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>John's document reminded me of how CAA records are done,  They
>push all the processing outside the DNS servers.
>Like CAA, we should make the RRTYPE require no special resolver processing
>and then we can get the RRTYPE fairly quickly to start.

In my proposal it's just a container, nothing special.

The magic all comes from the closest encloser rule for wildcards, which is
unrelated to rrtype.

R's,
John

v2.23.0 | Report a Bug | By Email