IETF Logo Mail Archive

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

tjw ietf <tjw.ietf@gmail.com> Thu, 08 November 2018 06:42 UTC

Return-Path: <tjw.ietf@gmail.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 9425D130DE2 for <dmarc@ietfa.amsl.com>; Wed, 7 Nov 2018 22:42:43 -0800 (PST)
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_PASS=-0.001, URIBL_BLOCKED=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 t8r6wR3U5dzn for <dmarc@ietfa.amsl.com>; Wed, 7 Nov 2018 22:42:41 -0800 (PST)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 23A09130DC8 for <dmarc@ietf.org>; Wed, 7 Nov 2018 22:42:41 -0800 (PST)
Received: by mail-pl1-x629.google.com with SMTP id t6-v6so9070176plo.9 for <dmarc@ietf.org>; Wed, 07 Nov 2018 22:42:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Cgcqg5BdbK8bXdqoAPB3zUd0gNT7fkyD9CwxFjqPJ/8=; b=gsFCgmPd//Vo8X1E/tEZOZ8/+I1DhiPIqTtHkyFCug0r0x5+GT5UVww6SVeFXija4p 0wKBPTM+Pe2eewvQL9ZCcd0OgdQGKEhQf9FEujGqHFnX5+2DH7jVmcfpJSa37w6nDI6Y SwQYc0PC1NRTZqsQHJ/VGWlaWmV/HH0nw9b/lnv44k/MEXkXfRjajU3zU4pcn/DuJcX0 KD/HFMVYqLADA1IDy1oS5TNdjWo7KN/VQWM1cUFh1BewQlP/Feaob5cjy2rXdCRkaqQM eo/B1RmunHMpyEbdOmfFl5XoI5qfvhbQmuoEK0ebkarEc251juH3WQfUc2+x5nZXv2/P nHbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Cgcqg5BdbK8bXdqoAPB3zUd0gNT7fkyD9CwxFjqPJ/8=; b=bBq6PKtNVqUM0qFEn2RQoYjyq9uHaubhKA/f5wCHOmmUNYfyKTYav6bOFcmwtshbKU 7WA9fbC/wflEGIKQcbr5peP3D3tAHQwgR/0M93Rva1cVG2qFtixg7P1EIfL/V+OOFLWl oLAS6jh65wjDjQ7Dd/hnn7IeSdmeXW0/1Z+z82InYQrXYCPTo5/jLd3XCX9VKZ+8EdJj Vp5ZyL+u0W1IPsZdTd4tDltZ1iKTgxckyCrfx7cMPkxGoknIzWijaQ5yCkD+W+uUHUDc 0k3/5Itz/D0CN1gW1xa+PyfE3kYJpweTtymltp5cxLTyza7cR+3iA/nXu/G81HKN+8me dvhQ==
X-Gm-Message-State: AGRZ1gIz0dzZsbVCn4KWPVe5ROKqVJeQ9oenOKXKgmWSoIYNTsGa1ZG+ BjvmT0WevRHGPI2F/TlWP8V9PSHibr4=
X-Google-Smtp-Source: AJdET5ei/Tjpb/IFZ+lKa60apoLmCSfNDqbNR1WkjqQi5AuXCzrkUQvdEsWMh8QTM5m++2bE0vtZaw==
X-Received: by 2002:a17:902:6b46:: with SMTP id g6-v6mr3356628plt.33.1541659360495; Wed, 07 Nov 2018 22:42:40 -0800 (PST)
Received: from [192.168.3.225] (static-222-229-224-101.adsl8.svips.gol.ne.jp. [222.229.224.101]) by smtp.gmail.com with ESMTPSA id v20-v6sm2632472pfm.114.2018.11.07.22.42.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Nov 2018 22:42:39 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-CAF209A9-11AB-4E89-8E6C-DFEE85E1057C"
Mime-Version: 1.0 (1.0)
From: tjw ietf <tjw.ietf@gmail.com>
X-Mailer: iPhone Mail (16A404)
In-Reply-To: <CABuGu1r3=Gwv1wRtohPyBqQMpQz-8-MUugZ9CTmZqi_KH3y_9A@mail.gmail.com>
Date: Thu, 08 Nov 2018 15:42:38 +0900
Cc: John Levine <johnl@taugh.com>, "dmarc@ietf.org" <dmarc@ietf.org>, Scott Kitterman <sklist@kitterman.com>
Content-Transfer-Encoding: 7bit
Message-Id: <0B3FC7A0-E811-4800-A5F8-ED9EBA21C79C@gmail.com>
References: <0E28DA8C-09A6-4E64-AD5E-3741EFE60569@kitterman.com> <20181108061651.0AF13200829C06@dhcp-8071.meeting.ietf.org> <CABuGu1r3=Gwv1wRtohPyBqQMpQz-8-MUugZ9CTmZqi_KH3y_9A@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gu1kHLheQy-KX77-p8AKedAXlGs>
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:42:44 -0000

I remember the two hog mentioned but there could of been a third. 



From my high tech gadget

> On Nov 8, 2018, at 15:19, Kurt Andersen (b) <kboth@drkurt.com> wrote:
> 
>> On Thu, Nov 8, 2018 at 1:17 PM John Levine <johnl@taugh.com> wrote:
>> 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.
> 
> I thought that there was a third one from Andrew too, but let's defer getting into the discussion until we get this proposal adopted into the WG.
> 
> --Kurt 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

v2.23.0 | Report a Bug | By Email