From nobody Thu Aug 13 17:23:25 2020 Return-Path: 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 B483F3A0B67; Thu, 13 Aug 2020 17:23:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 RKBk8sdvCBgA; Thu, 13 Aug 2020 17:23:21 -0700 (PDT) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 15AE93A0B58; Thu, 13 Aug 2020 17:23:21 -0700 (PDT) Received: by mail-vs1-xe2f.google.com with SMTP id j188so3868023vsd.2; Thu, 13 Aug 2020 17:23:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s7OzY07XnWSJlwR8glJYQS6jtOB5EcppD/elEdxOUfg=; b=nyS509yj5s2qplxGczPKnvyVjW1wiF3D0FnDB9DOcQz34d+hQjWnh96mEd2gNL1aYs zIcMss4Nl8LUBR15/Zisd2vuF0F7unPvSvnZkdJrsDbcriDr0CnGAxn26LEIVqS5Nhq3 IaiSnw70K4CuQ/637q7Za95cUvaw65umyR6qtLxf78LM/Q/TxjlkG3QkSnNgS+hY5EpU RhjjoV/uPEd8xh/c8ELX+DU1zaAalHPIn+BFfS4eSCH9wJY/lBWsXeF1FtpC9l9PYNt+ Oy6OtLOK1b3MNEwLbc8TneK02ANuOwjqQLhP3jJqJh0IWkjDek8D0HXPeXzzIykXyvg4 770Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=s7OzY07XnWSJlwR8glJYQS6jtOB5EcppD/elEdxOUfg=; b=KTrIcpE1N51pgM2KCAH8h+9JETbTpYl84sDvHBlV1ugRifK9VLz3utQW2rAWCC/YjG LJ03ZGDuBAncktw5pXwLyhBcx4MOYbNvd/0e+LbkBsG5xpyDvPiKXmtBSvq4tTwHbQLd cwb1oaF4+uK32LjRzBt4wiyojAaYzrlntnOhcLl8T2REfyS30GSvL0z9/08VKntcl8Fy qF6kzIMD2DuXVY3iA1VcUDo6nqkKxsvhxIG8Pq573rbExUwmCOal62BeFq9DRIwE/OpX d7tj0ps3Tqi1CZMkfRBGDbZ1xkc6M+usy0OuwXhzWs/PVDvUDyA62u7urGo2wn9xv5+v Czpw== X-Gm-Message-State: AOAM533Bf2krbmDHgz0lf8CyBA3kK+3iD2ccLWKbDx8/IGYPRSxxHvlJ 3tSra7aV4dTToSLi7UqqiNinyv44OUN0MDsji5K8RQ== X-Google-Smtp-Source: ABdhPJx8gLFLC4TTtVrHEWph2n9ocA49lJndxptILZl0wrT72AXSWV5SsJRfDEaO4Az99tQC8azmdu8Ed1Ob0DSnxX0= X-Received: by 2002:a67:eb91:: with SMTP id e17mr73896vso.7.1597364600136; Thu, 13 Aug 2020 17:23:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Murray S. Kucherawy" Date: Thu, 13 Aug 2020 17:23:07 -0700 Message-ID: To: Tim Wicinski Cc: IETF DMARC WG , dmarc-chairs@ietf.org Content-Type: multipart/alternative; boundary="0000000000009167f405accb6d4d" Archived-At: Subject: Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2020 00:23:23 -0000 --0000000000009167f405accb6d4d Content-Type: text/plain; charset="UTF-8" On Mon, Aug 10, 2020 at 12:05 PM Tim Wicinski wrote: > During IETF 108, the chairs realized that there was interest in Dave's > RFC5322.Sender draft. > > This starts a Call for Adoption for draft-crocker-dmarc-sender > > The draft is available here: > https://datatracker.ietf.org/doc/draft-crocker-dmarc-sender/ > > Currently, the draft is marked as "Standards Track". The chairs feel if > the > working group does adopt this, it should begin as "Experimental". If we > start > to see adoption of this work, this can be changed back to "Standards > Track" before > Working Group Last Call. Of course, we welcome input from the working > group on this. > > Please review this draft to see if you think it is suitable for adoption, > and > send any comments to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > This call for adoption ends: 24 August 2020 > DISCUSS. (just kidding; +1 for adoption) -MSK, participating, except for the joke part, that was with full authority --0000000000009167f405accb6d4d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Aug 10, 2020 at 12:05 PM Tim Wici= nski <tjw.ietf@gmail.com> w= rote:
Duri= ng IETF 108, the chairs realized that there was interest in Dave's
= RFC5322.Sender draft. =C2=A0

This starts a Call for Adoption for dra= ft-crocker-dmarc-sender

The draft is available here: https://datatracker.ietf.org/doc/draft-crocker-dmarc-sender/

Cu= rrently, the draft is marked as "Standards Track".=C2=A0 The chai= rs feel if the
working group does adopt this, it should begin as "E= xperimental".=C2=A0 If we start
to see adoption of this work, this= can be changed back to "Standards Track" before
Working Group= Last Call.=C2=A0 Of course, we welcome input from the working group on thi= s.

Please review this draft to see if you think it is suitable for a= doption, and
send any comments to the list, clearly stating your view.<= br>
Please also indicate if you are willing to contribute text, review, = etc.

This call for adoption ends: 24 August 2020

DISCUSS.

(just kiddin= g; +1 for adoption)

-MSK, participating, except fo= r the joke part, that was with full authority
--0000000000009167f405accb6d4d--