RE: Protocol Action: 'Updating References to the IETF FTP Service' to Proposed Standard (draft-danyliw-replace-ftp-pointers-06.txt)

John C Klensin <john-ietf@jck.com> Sat, 23 October 2021 01:01 UTC

Return-Path: <john-ietf@jck.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 0F4E73A0A8D; Fri, 22 Oct 2021 18:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 KXfabh_0O3_C; Fri, 22 Oct 2021 18:01:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5EB83A0859; Fri, 22 Oct 2021 18:01:48 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1me5Pt-000DDk-Rp; Fri, 22 Oct 2021 21:01:45 -0400
Date: Fri, 22 Oct 2021 21:01:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg-secretary@ietf.org>
cc: draft-danyliw-replace-ftp-pointers@ietf.org, The IESG <iesg@ietf.org>, rfc-editor@rfc-editor.org, ietf@ietf.org
Subject: RE: Protocol Action: 'Updating References to the IETF FTP Service' to Proposed Standard (draft-danyliw-replace-ftp-pointers-06.txt)
Message-ID: <2BE110435B7FFB35C3F2FD13@PSB>
In-Reply-To: <BN1P110MB093900922B0475F7EC59DB7ADC809@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
References: <163493224563.32534.14910053039218445700@ietfa.amsl.com> <DE740A8852DD07F5D15015CC@PSB> <BN1P110MB093900922B0475F7EC59DB7ADC809@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mUOaRv9LgBVakw_Y-sTt70LV4-I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 23 Oct 2021 01:01:59 -0000

Roman,

Thanks for the quick reply.  
Given that the answer is the one from the referenced email
transaction (for the benefit of others, 

	"The reasoning that motivated this document being PS was
	that it was updating other PS documents.  No more nuance
	than that."  )

I am really happy about that -- it is, fwiw, the conclusion I
would have reached and the argument I would have made.  I think
a sentence to that effect somewhere in the document (or at least
the datatracker) would have been helpful.  The current Abstract
and Introduction effectively make the point that no technical
changes are involved, but that is not explicit and not bound to
the idea of a standards track document.  However, given that the
IESG has already processed the document, I'm not convinced that
would be worth the trouble now to make that sort of change.

_However_, I do expect the IESG to be consistent.  While it
probably is not worth the trouble to go back and identify and
reclassify earlier examples, I assume we will not see documents
that make substantive technical modifications to, or alter the
requirements of, standards track Technical Specifications
published as BCPs in the future.

thanks again,
   john


--On Friday, October 22, 2021 23:27 +0000 Roman Danyliw
<rdd@cert.org> wrote:

> Hi John!
> 
> Thanks for the review.  More inline ...
> 
>> -----Original Message-----
>> From: John C Klensin <klensin@jck.com>
>> Sent: Friday, October 22, 2021 5:14 PM
>> To: The IESG <iesg-secretary@ietf.org>
>> Cc: draft-danyliw-replace-ftp-pointers@ietf.org; The IESG
>> <iesg@ietf.org>rg>; rfc- editor@rfc-editor.org; ietf@ietf.org
>> Subject: Re: Protocol Action: 'Updating References to the
>> IETF FTP Service' to Proposed Standard
>> (draft-danyliw-replace-ftp-pointers-06.txt)
> 
> [snip]
>  
>> So a quick question: What is the justification for classifying
>> this as a Proposed Standard?
>  
> [snip]
> 
>> At least according to what I see in the datatracker, this
>> question did not come up during the IESG review either.
> 
> [snip]
> 
>> I
>> think an explanation is in order and/or perhaps a
>> pre-publication change to BCP.
> 
> This question came up even earlier than IESG review, in IETF
> Last Call:
> 
> https://mailarchive.ietf.org/arch/msg/last-call/oMhqRigr4nbRSM
> ll5NY4zXpZu20/
> 
> Regards,
> Roman