[dmarc-ietf] Other potential work items for the ARC spec

"Kurt Andersen (b)" <kboth@drkurt.com> Thu, 12 May 2016 21:57 UTC

Return-Path: <kurta@drkurt.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 E213912B02F for <dmarc@ietfa.amsl.com>; Thu, 12 May 2016 14:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.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 l1oKisKMtohP for <dmarc@ietfa.amsl.com>; Thu, 12 May 2016 14:56:59 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 E062212D171 for <dmarc@ietf.org>; Thu, 12 May 2016 14:56:58 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id f89so111290813ioi.0 for <dmarc@ietf.org>; Thu, 12 May 2016 14:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:sender:date:message-id:subject:from:to; bh=VQhVXRsu9gQgAa6M4ld4V0RJyDcL4oLjnAyBgJ45xAk=; b=VhrUppSvvm/G82SdTVvOOGjN6nfaVsxIbwh2Pk1EUNVfTiYP1Jb1LP4oi3N2ojet+a +BSdjZVWgDt9evpi3cHiQzQnsSlzPf0Deu0lMYSejhVz7X8DwCkzV+u6FvosT1AWSmJT 6qI0oLXSo6IjPnMGnhJ2D3Hcu4a4+hSIE9ZpY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=VQhVXRsu9gQgAa6M4ld4V0RJyDcL4oLjnAyBgJ45xAk=; b=HPPAbHim7g7RDDFl3i0KdMdl/Pz/0+sUI1U7Q8jDPoc8WZqInE67ygeYiwqfGfoFd8 +Ggt/gfwa6LbpRxRY7REkUGhxyAjFytWWv0oAHlqbJ5iA1ddniZRqbczEIoI6qo5Mf8I lMWiT03QDlL9dVLTGWcY8VTlXf8QWtDQtz+t8lBfN3O4F5pR+WnpkAsrlx2iCgPJ7xxC HzckOPIVZ0T0QuCgoxLragX9JzQ1TNiSxnep8XheMRPckdQjwnZBr4U3ZJr66WOqSCjP EEaM0yd5OI4a0HxJk0wn8hVxfLYIMdm2ig5elwIthSgehGk4YgIMtv8JGuMhSwJB1DaB AO2w==
X-Gm-Message-State: AOPr4FWwv4r4i18l+LZdwKD1TAF4NIJB8ghIEYPDRi1UR5SMFbhSa2M5xa3/lu9FG2jII679uHrm/UaC0/3SGg==
MIME-Version: 1.0
X-Received: by 10.107.10.37 with SMTP id u37mr9346289ioi.92.1463090218313; Thu, 12 May 2016 14:56:58 -0700 (PDT)
Sender: kurta@drkurt.com
Received: by 10.107.20.202 with HTTP; Thu, 12 May 2016 14:56:58 -0700 (PDT)
Date: Thu, 12 May 2016 14:56:58 -0700
X-Google-Sender-Auth: owQ3C8doFx0VDUv38uDMtxyelC0
Message-ID: <CABuGu1pgkBwad-=CL8Sda9S31_Ln4o16SKdpbXNn7NhhVMJTvA@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="001a113de4dcbce7850532ac3c35"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmarc/iQ4BZvfwWYtrAa8x43dlubsjHq8>
Subject: [dmarc-ietf] Other potential work items for the ARC spec
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.17
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, 12 May 2016 21:57:01 -0000

Allessandro Veseley had suggested (on the arc-discuss) list that the
semantics and construction of the ARC sets could be defined in a
generalized DKIM-like recipe.

When I had discussed this with Dave Crocker, he pointed out that such an
idea would align with the (never quite finalized) DOSETA (
https://datatracker.ietf.org/doc/draft-crocker-doseta-base/) idea and that
having both ARC and DKIM as potential instantiations of the abstract
concept could be enough to bring DOSETA to realization.

--Kurt