[ftpext] RFC959 update WAS Re: NAT64 client/server document

"William F. Maton" <wmaton@ottix.net> Wed, 28 July 2010 14:31 UTC

Return-Path: <wmaton@ottix.net>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 24C3228C140 for <ftpext@core3.amsl.com>; Wed, 28 Jul 2010 07:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id cw5Yw74KmfaQ for <ftpext@core3.amsl.com>; Wed, 28 Jul 2010 07:31:12 -0700 (PDT)
Received: from iskra.ottix.net (iskra.ottix.net [IPv6:2001:410:90ff::2]) by core3.amsl.com (Postfix) with ESMTP id AF18F3A6902 for <ftpext@ietf.org>; Wed, 28 Jul 2010 07:31:10 -0700 (PDT)
Received: from iskra.ottix.net (localhost []) by iskra.ottix.net (8.14.4/8.14.4) with ESMTP id o6SEVVO5022234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ftpext@ietf.org>; Wed, 28 Jul 2010 10:31:32 -0400
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 iskra.ottix.net o6SEVVO5022234
Received: from localhost (wmaton@localhost) by iskra.ottix.net (8.14.4/8.14.3/Submit) with ESMTP id o6SEVTvU022229 for <ftpext@ietf.org>; Wed, 28 Jul 2010 10:31:31 -0400
Date: Wed, 28 Jul 2010 10:31:29 -0400
From: "William F. Maton" <wmaton@ottix.net>
To: ftpext@ietf.org
In-Reply-To: <40A8C49E-EFF7-482A-B444-81EDFF41449A@muada.com>
Message-ID: <Pine.LNX.4.64.1007281024050.15461@iskra.ottix.net>
References: <40A8C49E-EFF7-482A-B444-81EDFF41449A@muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Subject: [ftpext] RFC959 update WAS Re: NAT64 client/server document
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2010 14:31:15 -0000

On Tue, 27 Jul 2010, Iljitsch van Beijnum wrote:

>not when there is a 229 response. I also worry that an overhaul of RFC 
>959 and rolling in stuff from later FTP RFCs would take quite a long time 
>because all kinds of other stuff would find its way into the document, 

IANAWGCC [*], but in my voyages through the 'heritage' that is the wu-ftpd 
experience, one downside is having to wade through a lot of RFCs to 'get' 
the protocol.  In my mind, there are two approaches to updating RFC959:

a) As you said, update it and allow for creeping featurism;
b) Tightly scope the update to RFC 959 to just being an updated version
    of the protocol as it stands today according to RFCs only (not drafts,
    not even practices out there on the Internet) and look to fixing it
    later...much later.

There is always the third option and that is to do nothing.

[On the BCP vs STD idea]

Given that this is addressing an issue related to the burgeoning 
deployment of IPv6, at the very least it should be a BCP.  Ideally a STD 
but I admit I don't know what weight that would really carry either.


[*] I am Not a Working Group Co-Chair.