Re: [ietf-dkim] Intended status (was: Re: [dmarc-ietf] a slightly less kludge alternative to draft-kucherawy-dmarc-rcpts)

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 17 November 2016 18:46 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A12E1294FE for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Thu, 17 Nov 2016 10:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level:
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" 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 LE1PYc6SjLFE for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Thu, 17 Nov 2016 10:46:58 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 4C62F129412 for <ietf-dkim-archive@ietf.org>; Thu, 17 Nov 2016 10:46:58 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id uAHIkshI029970; Thu, 17 Nov 2016 10:46:56 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=gmail.com header.i=@gmail.com header.b=BAArWs0o; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from mail-yb0-f177.google.com (mail-yb0-f177.google.com [209.85.213.177]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id uAHIkpXe029964 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ietf-dkim@mipassoc.org>; Thu, 17 Nov 2016 10:46:52 -0800
Received: by mail-yb0-f177.google.com with SMTP id d59so69336897ybi.1 for <ietf-dkim@mipassoc.org>; Thu, 17 Nov 2016 10:45:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v/OXLcm2MPU5a0eUbjZNrpWxoHjub1CXfKQK/OXVhgA=; b=BAArWs0odlK++5gBpOxFbL+qv60R6bU57BIX0435xEfGSFypZ4UcjUP4gsseX9vpHK QA8lxd7ljdwYcoqsyDn5pxtPXG7T79KBmpuNOY3kDFcUhtXxecsSQr0ZVD0CSC07oY0t mvFQ/yXIZuNIzXdXfWZVI7M7iC3kR1OJXE94aNop4XD4iKihjSrEUQ/UB8jaa+zz4+qL I3UUDAdnze37glgtuVGzeDNUOUWccwkApWNlQlORyiiqefrocFhsVUixEe7AV7rzMWEw /QUK8jxoUQrRGZK9xqNluwWTmNUFwvzTpZB0b9S8+OeHSASvwvLATnsx3nbUlpZTkADo 6XOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v/OXLcm2MPU5a0eUbjZNrpWxoHjub1CXfKQK/OXVhgA=; b=DuBkglQbIL7qHjG4V7/8R34F0RfSgjplL0uw3U7bD6eIZ981Gji+tIBZ8EYy7g8Q3Z 6DPCbi6X5DpIsPmkEndxU4FktlkTw/EsWnlL4HVEffT/L8ccSBAiJ44lHJuLPHv2J5Z6 i26InUUsPr4XBe94VgG9pF+6/yCXfyR9eCsR6vJG+hH1D6BM/oFTnaVE/CC1iIjwmf2U pQFgb58VwAFODu+tKBgFT/u3pKVgbrqlik22VnlQ9wX0oIoXx4K40OtauSRNX8nrPI5N MagrUtg+b4Q4Ip09XR2FcNhwrEdqSkZOERRWql211t3832pk7hz+c784VxP3LH+x1Hdj 9yMg==
X-Gm-Message-State: ABUngvfaktSDInnicMCVdt7HlZ+w3sgJphIgjOqMIrD154D1qsZqcnx/l6JTnElMqJmwJCICH+kH9MK2Ko5ZIA==
X-Received: by 10.129.99.195 with SMTP id x186mr4142054ywb.182.1479408349915; Thu, 17 Nov 2016 10:45:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.111.130 with HTTP; Thu, 17 Nov 2016 10:45:49 -0800 (PST)
In-Reply-To: <234f6b74-cd9a-af64-c7b6-da06a9d76cc5@sonnection.nl>
References: <alpine.OSX.2.11.1611142158000.21738@ary.local> <01Q7ASDZFS6C011WUX@mauve.mrochek.com> <CAL0qLwazAg2UJvGAr+nx8R_xEbc4xV0ttPEWFKUD69u6xXaMhA@mail.gmail.com> <CAL0qLwaMzy=qeW5XYZ_txPaiYE27Oof+C5V1uRANvv-_cayOcQ@mail.gmail.com> <234f6b74-cd9a-af64-c7b6-da06a9d76cc5@sonnection.nl>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 18 Nov 2016 03:45:49 +0900
Message-ID: <CAL0qLwaERr2fAtnfXgKTKpH7Ox8eEtDdP6LhDrvrnErBPAppwA@mail.gmail.com>
To: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Cc: "ietf-dkim@mipassoc.org" <ietf-dkim@mipassoc.org>
Subject: Re: [ietf-dkim] Intended status (was: Re: [dmarc-ietf] a slightly less kludge alternative to draft-kucherawy-dmarc-rcpts)
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3923026093562647713=="
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

On Fri, Nov 18, 2016 at 1:11 AM, Rolf E. Sonneveld <
R.E.Sonneveld@sonnection.nl> wrote:

> Hi, Murray,
>
> On 16-11-16 02:45, Murray S. Kucherawy wrote:
>
>> There's been a lot of great feedback here.  I just cranked out an update
>> based on the discussion so far:
>>
>> https://www.ietf.org/rfcdiff?url2=draft-kucherawy-dkim-rcpts-01
>>
>> I forgot to update the title of Section 3, but other than that I think I
>> captured what's been discussed.  Please let me know what I've missed.
>>
>
> the intended status field is empty, but do you have some intended status
> in mind or not yet?


All of the versions I can see at
https://datatracker.ietf.org/doc/draft-kucherawy-dkim-rcpts/ show
"Standards Track" as the Intended Status field, meaning it would get
"Proposed Standard" on publication.  I think if we get more than one
operator interested in trying this, then that's the right thing.  If we get
no commitment, "Experimental" is fine, if we go ahead with it at all.

If you're talking about the "Intended RFC Status" in the datatracker, which
still says "(None)", that's not set by the document author; it's set by the
working group chair, sponsoring Area Director, or Independent Submission
editor once it formally enters one of the two possible processing streams.

-MSK
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html