[dmarc-ietf] In support of draft-ietf-dmarc-arc-protocol-16

Juan Altmayer Pizzorno <juan@sparkpost.com> Tue, 31 July 2018 23:42 UTC

Return-Path: <juan@sparkpost.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 26BB2128CF3 for <dmarc@ietfa.amsl.com>; Tue, 31 Jul 2018 16:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sparkpost.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 diey6VyvHGDD for <dmarc@ietfa.amsl.com>; Tue, 31 Jul 2018 16:42:50 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 F2014130E96 for <dmarc@ietf.org>; Tue, 31 Jul 2018 16:42:49 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id j143-v6so11981542lfj.12 for <dmarc@ietf.org>; Tue, 31 Jul 2018 16:42:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sparkpost.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=5howskGh3XbVdsR2YN7/vnT56pADaFNimruOwYv7PMw=; b=AlU0lRfYV+OKJdLbDSeiIlOTXaZQGo+ttd5J1RV7NjEoWGW5aZzDyHZ0U1xXUVVCAY +mnJBUHh4N8dBjEd3xZDtXrMVvesrdPfM1nuRbOqJ9tJO4W2jf8f1J3bLGMSISyxeyys 1ipp9WS+EG9xJ3N2SQOE8BCiXS5mkB42EUAwk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5howskGh3XbVdsR2YN7/vnT56pADaFNimruOwYv7PMw=; b=ud+trDqj1XngoG7iAjIBHBZAFFpNXSHa2Jc8y3l+RthjsRm0UW00+DChho6CVZEjuU 9N/jsYMeI84sgfqfQ5HC6EneX949SkREKqtdVMGDZyKmD5UnA1YXh5Cb2RdXnTRR6S2H bi3NULkYlgrbo0BORoP5u20ZN8tD/O4gWAoePkhxyc7Okb0LbwpPVIiljrr4EQtPD8yL BmfdMasg5tV577k1HqsDO7U9iTHaZ3U+AMcczTXOYf0Y/O97e73aJY/4yi3go/GaEEzf kGLrS0+QYK7EaU02YfZKYXGDUp9vtDd/zCUF2jyCm+kptYQX2qcQYNC9bA7pGqv0Ut3w hS5w==
X-Gm-Message-State: AOUpUlGEzyatzbcFzHFi3eyHZ3n98/Yd4ODHuMLfSCUGV5ubDX3OAjIZ tNXQhuyvlckXqCaJDFaQiSx0nkmjX+U21dptZG0tedFA
X-Google-Smtp-Source: AAOMgpenyxikwR+BTy6eEvFbF45QgJUm8+3JI6twyaKYNowu0M4LwaExS34GXLn2r8tlqt4fUIHXzxT4tMDE3m4Z/cw=
X-Received: by 2002:a19:d98f:: with SMTP id s15-v6mr14639719lfi.103.1533080567883; Tue, 31 Jul 2018 16:42:47 -0700 (PDT)
MIME-Version: 1.0
From: Juan Altmayer Pizzorno <juan@sparkpost.com>
Date: Tue, 31 Jul 2018 19:42:35 -0400
Message-ID: <CAFiEdE1RYHT12FxndkWhHq2yo8FzfcL5P0KU6mi7naJz5Pjp1Q@mail.gmail.com>
To: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a9461405725422ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Olz4plVq4Z_iUeHgt00to6h6HCU>
Subject: [dmarc-ietf] In support of draft-ietf-dmarc-arc-protocol-16
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 31 Jul 2018 23:42:52 -0000

Dear WG,

I thought I'd chime in in support of the draft.  Having implemented DKIM,
SPF
and various other email authentication protocols, I've chosen this time to
integrate and contribute to OpenARC instead (power to the community! :)).
So while I didn't implement it directly, I can't help but read it from that
perspective;
I think it reads very well and seems very clear.  I hope the protocol is
successful!

.. Juan
juan@port25.com / juan@sparkpost.com