Re: [Rfced-future] Alvaro Retana's No Objection on draft-rosen-rfcefdp-update-2026-01: (with COMMENT)
Jean Mahoney <jmahoney@amsl.com> Tue, 08 March 2022 18:54 UTC
Return-Path: <jmahoney@amsl.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE21F3A1026 for <rfced-future@ietfa.amsl.com>; Tue, 8 Mar 2022 10:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 PLvpwgq3KQeW for <rfced-future@ietfa.amsl.com>; Tue, 8 Mar 2022 10:54:37 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F0C43A102E for <rfced-future@iab.org>; Tue, 8 Mar 2022 10:54:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8416E425C195; Tue, 8 Mar 2022 10:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAPjiScgC6K2; Tue, 8 Mar 2022 10:54:36 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 3623F425A344; Tue, 8 Mar 2022 10:54:36 -0800 (PST)
Message-ID: <ab6d8759-03ed-6a8e-166b-e47eaaeaaacf@amsl.com>
Date: Tue, 08 Mar 2022 12:54:35 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: Brian Rosen <br@brianrosen.net>, Alvaro Retana <aretana.ietf@gmail.com>
Cc: rfced-future@iab.org, draft-rosen-rfcefdp-update-2026@ietf.org, The IESG <iesg@ietf.org>
References: <164674251319.17115.13477164655608051849@ietfa.amsl.com> <18FD274D-67A8-46B1-906A-F90E7FF1250A@brianrosen.net>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <18FD274D-67A8-46B1-906A-F90E7FF1250A@brianrosen.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/G2Vza9-MCfPPUOFw725bydDQ2PQ>
Subject: Re: [Rfced-future] Alvaro Retana's No Objection on draft-rosen-rfcefdp-update-2026-01: (with COMMENT)
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2022 18:54:42 -0000
Hi all, On 3/8/22 10:44 AM, Brian Rosen wrote: > <adding rfced-future> > Thank you for your review. > > I will defer to whatever current practice the RFC Editor has with regard to how we indicate that a document updates a BCP. Would someone from the RFC Production center chime in here? The IESG approval message should indicate if the document will be added to BCP 9. The Updates field should say: "Updates: 2026 (if approved)" Best regards, Jean, chiming in from the RPC > > I personally don’t think that the reference to rfc-model should be normative, but I will defer to the wishes of the rfced-future work group. “Must be read to understand” applies to lots of informative references. > > Brian > >> On Mar 8, 2022, at 7:28 AM, Alvaro Retana via Datatracker <noreply@ietf.org> wrote: >> >> Alvaro Retana has entered the following ballot position for >> draft-rosen-rfcefdp-update-2026-01: No Objection >> >> When responding, please keep the subject line intact and reply to all >> email addresses included in the To and CC lines. (Feel free to cut this >> introductory paragraph, however.) >> >> >> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ >> for more information about how to handle DISCUSS and COMMENT positions. >> >> >> The document, along with other ballot positions, can be found here: >> https://datatracker.ietf.org/doc/draft-rosen-rfcefdp-update-2026/ >> >> >> >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> (1) It should be indicated somewhere that this document should be part of BCP >> 9. I prefer an RFC Editor Note in the ballot/IESG Writeup. I did notice that >> the header includes "Updates:...BCP 9", but (trying not to get into the meaning >> of "updates") only RFCs should be listed there. >> >> (2) The reference to draft-iab-rfcefdp-rfced-model should be Normative because >> it must be read to understand the change being made. >> >> >>
- Re: [Rfced-future] Alvaro Retana's No Objection o… Brian Rosen
- Re: [Rfced-future] Alvaro Retana's No Objection o… Jean Mahoney
- Re: [Rfced-future] Alvaro Retana's No Objection o… John C Klensin
- Re: [Rfced-future] Alvaro Retana's No Objection o… Brian E Carpenter