IETF Logo Mail Archive

Re: [Last-Call] Last Call: <draft-danyliw-replace-ftp-pointers-03.txt> (Updating References to the IETF FTP Service) to Proposed Standard

Carsten Bormann <cabo@tzi.org> Mon, 06 September 2021 10:00 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA1D3A2971; Mon, 6 Sep 2021 03:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 bFvZqjKJKt9Z; Mon, 6 Sep 2021 03:00:04 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB7E83A296F; Mon, 6 Sep 2021 03:00:03 -0700 (PDT)
Received: from smtpclient.apple (p548dcf6e.dip0.t-ipconnect.de [84.141.207.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4H33mL0g0lz2xYN; Mon, 6 Sep 2021 12:00:02 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <BN1P110MB0939260B2EAF8EA89254A433DCCB9@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
Date: Mon, 06 Sep 2021 12:00:01 +0200
Cc: "last-call@ietf.org" <last-call@ietf.org>, "draft-danyliw-replace-ftp-pointers@ietf.org" <draft-danyliw-replace-ftp-pointers@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <444CF38A-8374-459A-B844-8660999127FB@tzi.org>
References: <163033335342.27373.621708255382630068@ietfa.amsl.com> <B413516C-3458-42BB-9D6D-A35A7B138A0C@tzi.org> <BN1P110MB0939260B2EAF8EA89254A433DCCB9@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
To: Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/yK6uQEhWwZA4zoB_Y0xB1Dfxeys>
Subject: Re: [Last-Call] Last Call: <draft-danyliw-replace-ftp-pointers-03.txt> (Updating References to the IETF FTP Service) to Proposed Standard
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2021 10:00:09 -0000

On 30. Aug 2021, at 17:36, Roman Danyliw <rdd@cert.org> wrote:
> 
> The reasoning that motivated this document being PS was that it was updating other PS documents.  No more nuance than that.

Too lazy to check:
Are there any documents being updated that should not be BCPs in the first place?

Maybe this could be one more element of the “updates” discussion — a BCP can update a standards-track document that only became that way because at the time BCP hadn’t been invented yet.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email