Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
ned+ietf@mauve.mrochek.com Fri, 11 May 2018 22:51 UTC
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C5D12D77E for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 15:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 E-uKWbFpWDf5 for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 15:51:04 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 679F6129C6D for <ietf@ietf.org>; Fri, 11 May 2018 15:51:04 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QSDU0TI08000RU8H@mauve.mrochek.com> for ietf@ietf.org; Fri, 11 May 2018 15:49:23 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QS9HM46G1S000051@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 11 May 2018 15:49:19 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Cc: IETF discussion list <ietf@ietf.org>
Message-id: <01QSDU0RB1QY000051@mauve.mrochek.com>
Date: Fri, 11 May 2018 15:49:02 -0700
Subject: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
In-reply-to: "Your message dated Thu, 10 May 2018 09:13:27 -0400" <CAC4RtVCq-27o7QjVfd8pES0Zi4zHaOs9uWh4eDR+L_Y4Os_JLg@mail.gmail.com>
References: <152588285893.3989.7909763661642193132.idtracker@ietfa.amsl.com> <CAC4RtVCq-27o7QjVfd8pES0Zi4zHaOs9uWh4eDR+L_Y4Os_JLg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WY87Iylcz-op42QUnAI8hDDHFW0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 22:51:06 -0000
Ditto. This change is if anything overdue. Ned > I fully agree with and support this status change. > Barry > On Wed, May 9, 2018 at 12:20 PM, The IESG <iesg-secretary@ietf.org> wrote: > > > > The IESG has received a request from DMARC WG to make the > > following status changes: > > > > - RFC4405 from Experimental to Historic > > (SMTP Service Extension for Indicating the Responsible Submitter of an > > E-Mail Message) > > > > - RFC4406 from Experimental to Historic > > (Sender ID: Authenticating E-Mail) > > > > - RFC4407 from Experimental to Historic > > (Purported Responsible Address in E-Mail Messages) > > > > The supporting document for this request can be found here: > > > > https://datatracker.ietf.org/doc/status-change-change-sender-id-to-historic/ > > > > The IESG plans to make a decision in the next few weeks, and solicits final > > comments on this action. Please send substantive comments to the > > ietf@ietf.org mailing lists by 2018-06-06. Exceptionally, comments may be > > sent to iesg@ietf.org instead. In either case, please retain the beginning of > > the Subject line to allow automated sorting. > > > > The affected documents can be obtained via > > https://datatracker.ietf.org/doc/rfc4405/ > > https://datatracker.ietf.org/doc/rfc4406/ > > https://datatracker.ietf.org/doc/rfc4407/ > > > > IESG discussion of this request can be tracked via > > https://datatracker.ietf.org/doc/status-change-change-sender-id-to-historic/ballot/ > >
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Hector Santos
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John C Klensin
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Alexey Melnikov
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Scott Kitterman
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Alexey Melnikov
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… S Moonesamy
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Barry Leiba
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… ned+ietf
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Kurt Andersen
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Scott O. Bradner
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John Levine
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Kurt Andersen
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John C Klensin
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John R Levine
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John Levine
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Barry Leiba
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John C Klensin
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… Barry Leiba
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 440… John R Levine