Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2 review of FTP HOST command?)
SM <sm@resistor.net> Tue, 13 March 2012 16:30 UTC
Return-Path: <sm@resistor.net>
X-Original-To: ftpext@ietfa.amsl.com
Delivered-To: ftpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F40421F8790 for <ftpext@ietfa.amsl.com>; Tue, 13 Mar 2012 09:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.642
X-Spam-Level:
X-Spam-Status: No, score=-102.642 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmQ8pOdz2r+w for <ftpext@ietfa.amsl.com>; Tue, 13 Mar 2012 09:30:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D488F21F86A7 for <ftpext@ietf.org>; Tue, 13 Mar 2012 09:30:48 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q2DGUgWJ003557; Tue, 13 Mar 2012 09:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1331656247; i=@resistor.net; bh=TOGX7uTiI/JKXqu5x4PTDYVW6obGHFNqhB3meAI3c4A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=w8JQ0iFCkS/Pt5e+49rC5rz0WQZYh0ZLFm19djOcI/WN6cQgbChXb0wGt+Ju4h9KW Bzfq3uUt5iiQPz6OEPnZjY5e6ZI9OK6wapKqZY2yHeb3sjXR6Sz1Bcg5K6F28VYpD9 4kQOx40wH8SrvYmh7SEjgNRNFqIdjMeml3pssIEM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1331656247; i=@resistor.net; bh=TOGX7uTiI/JKXqu5x4PTDYVW6obGHFNqhB3meAI3c4A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y1fGkcNaGpivLWnDJkdrMgv9f+vJqNpNdqlqg1q6AbQYbI7kPNoRQIvOjhFiDg4a5 Hz9HNngaurCx/4B2x5EiP1aANU7Q9aPCfoH6cBbbfY/KfXT7WTcRbtB4O021AngCH3 jypJI55hrMJ2KR5dNz6iR5ScjCinKi+Og30I9iBA=
Message-Id: <6.2.5.6.2.20120313090805.08f0d5a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 13 Mar 2012 09:24:58 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
In-Reply-To: <25D7B5EC576CA65951F75AB8@PST.JCK.COM>
References: <8CC6BE90-16F4-41DB-835B-B8BC9722156A@frobbit.se> <4F5E0B4F.2080401@att.com> <8050883FA9D9EB809D8E848C@PST.JCK.COM> <alpine.DEB.2.00.1203121734130.18227@tvnag.unkk.fr> <25D7B5EC576CA65951F75AB8@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ftpext@ietf.org
Subject: Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2 review of FTP HOST command?)
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 13 Mar 2012 16:30:51 -0000
Hi John, At 07:10 13-03-2012, John C Klensin wrote: >Let me say something slightly more optimistic than the above, >even though I don't think it helps the WG very much. I think we >have several implementers out there, each with a client/customer >base. While those clusters of customers probably overlap enough >in their properties and needs to be different from a >niche-per-implementer/ vendor, they are different. The result >is that vendor X wants extensions A, B, and C (which they may >have developed, implemented, and deployed in some form). Vendor >Y wants extensions D, E, and C', where C' is functionally more >or less like C but not identical. Maybe we could get them >together to work on a common C-approximation (although there >hasn't been evidence of that so far). But X sees no commercial >value in working on, or even reviewing D or E and Y sees no >commercial value in working on A or B. > >Worse from our point of view, X's main interest, as a server >vendor, in bringing A and B to the IETF is to get them >standardized so they can beat up client vendors who haven't >implemented what would otherwise be a perfectly good proprietary >feature. That not only gives them no incentive to invest energy >on D or E, it gives them significant incentive to push back on >any changes to their already-implemented versions of A and B >(using "running code" as an excuse). It's up to X and Y to figure out what's in their mutual interest. Otherwise, one ends up with the classic scenario of a non-working group. >p.s. On looking at the charter, I discovered that one of the >things the WG committed to do was > > "* Review and confirm or reject errata of current FTP > RFCs" > >Circa 18 months after we got serious about chartering the group >(longer than that if one uses other criteria), that task hasn't >been started. Another entry in the "not a good sign" list, IMO. The WG doesn't have any RFC to show since it was chartered in November 2010. That's not a good sign. Regards, -sm
- [ftpext] Fwd: Re: ftpext2 review of FTP HOST comm… Tony Hansen
- [ftpext] WG Status (was: Re: Fwd: Re: ftpext2 rev… John C Klensin
- Re: [ftpext] WG Status Tony Hansen
- Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2… Daniel Stenberg
- Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2… John C Klensin
- Re: [ftpext] WG Status TJ Saunders
- Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2… SM
- Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2… Anthony Bryan
- Re: [ftpext] WG Status Anthony Bryan
- Re: [ftpext] WG Status (was: Re: Fwd: Re: ftpext2… Anthony Bryan
- Re: [ftpext] WG Status Pete Resnick
- Re: [ftpext] WG Status Tony Hansen
- [ftpext] draft-ietf-ftpext2-typeu is now draft-kl… John C Klensin