Re: [ftpext] WG Status

Tony Hansen <tony@att.com> Sat, 31 March 2012 00:41 UTC

Return-Path: <tony@att.com>
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 77C1221F86A8 for <ftpext@ietfa.amsl.com>; Fri, 30 Mar 2012 17:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.007
X-Spam-Level:
X-Spam-Status: No, score=-104.007 tagged_above=-999 required=5 tests=[AWL=-1.409, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Ap0tu39IyGRl for <ftpext@ietfa.amsl.com>; Fri, 30 Mar 2012 17:41:56 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 70AC421F869C for <ftpext@ietf.org>; Fri, 30 Mar 2012 17:41:56 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 4d2567f4.0.2171752.00-275.6075796.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>); Sat, 31 Mar 2012 00:41:56 +0000 (UTC)
X-MXL-Hash: 4f7652d403f7a3c8-f04bacbf5d344429f37c97fbe3cb17fc42c9010e
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q2V0ftE9001959 for <ftpext@ietf.org>; Fri, 30 Mar 2012 20:41:55 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q2V0fonx001924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ftpext@ietf.org>; Fri, 30 Mar 2012 20:41:51 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <ftpext@ietf.org>; Fri, 30 Mar 2012 20:41:27 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q2V0fQN4027442 for <ftpext@ietf.org>; Fri, 30 Mar 2012 20:41:26 -0400
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q2V0fK42027356 for <ftpext@ietf.org>; Fri, 30 Mar 2012 20:41:21 -0400
Received: from [135.70.89.101] (vpn-135-70-89-101.vpn.swst.att.com[135.70.89.101]) by maillennium.att.com (mailgw1) with ESMTP id <20120331003829gw1004ormfe> (Authid: tony); Sat, 31 Mar 2012 00:38:29 +0000
X-Originating-IP: [135.70.89.101]
Message-ID: <4F7652AD.3060201@att.com>
Date: Fri, 30 Mar 2012 20:41:17 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: ftpext@ietf.org
References: <8CC6BE90-16F4-41DB-835B-B8BC9722156A@frobbit.se> <4F5E0B4F.2080401@att.com> <8050883FA9D9EB809D8E848C@PST.JCK.COM> <4F5ED938.7090406@att.com> <4F7580CD.2020802@qualcomm.com>
In-Reply-To: <4F7580CD.2020802@qualcomm.com>
Content-Type: multipart/alternative; boundary="------------050100060402040308020102"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=Q1bhx3XkwJwA:10 a=ftvWwXIVLBAA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=rg]
X-AnalysisOut: [20VTZoIwHZLBIEA7AA:9 a=qHygi_KlYb0reWGHZd4A:7 a=wPNLvfGTeE]
X-AnalysisOut: [IA:10 a=EUspDBNiAAAA:8 a=hHIpBUO25oDvo1Ll_QYA:9 a=RGxOev0W]
X-AnalysisOut: [4maCPxSdSVMA:7 a=_W_S_7VecoQA:10 a=IG2fH9E8heMA:10]
Subject: Re: [ftpext] WG Status
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: Sat, 31 Mar 2012 00:41:57 -0000

Well folks, we've officially shut the working group down. That does 
*not* mean that work on these drafts needs to die.

First off, this mailing list will stay open indefinitely. (After all, 
it's the same list we used for the FTPEXT working group many years ago.)

Second, Anthony and I are not abandoning you. We will continue to be 
available to help shepherd the drafts through the IETF process.

However, the onus is shifting from the working group back to you, the 
individual. It is now *your* responsibility to push your documents forward.

*IF* you care about your particular FTP extension draft, here is a way 
forward:

1) Repost your draft as an individual submission. Please use a name of 
"draft-YOURNAME-ftpext-TOPIC".
2) Please post a note to this mailing list about your updated document.
3) Solicit comments from people, particularly people who you know who 
either have implemented your extension or are willing to implement your 
extension. Also solicit comments from people who are good at looking for 
completeness of the specs and making sure that the nits are taken care of.
4) When you have at least 5 or 6 people who are willing to send an email 
to the mailing list saying that your document is ready to be published 
as an RFC, send an email message to Anthony and the mailing list asking 
for it to be published.
5) Anthony will work with me to fill out the proper shepherding forms to 
get the Area Directory to issue a IETF-wide last call process.

Let the good times roll.

     Your (former) friendly neighborhood FTPEXT2 co-chairs
     Tony Hansen and Anthony Bryan


On 3/30/2012 5:45 AM, Pete Resnick wrote:
>
> Though there was a small burst of posting in the last 2 weeks, there 
> has not been enough participation to convince me that there is energy 
> to sustain a WG effort. I've decided to close the WG. Documents that 
> the WG was working on will be moved to individual documents and will 
> be replaced with renamed documents (without the "draft-ietf-" name) if 
> and when they are updated. If publication of these documents is 
> desired, they will need to be published as individual submissions 
> sponsored by an Area Director. The mailing list shall remain open for 
> discussion of these documents and any other FTP work.
>
> Thanks to everyone (especially the chairs and document editors) for 
> your efforts in getting this work to move forward. I think we may have 
> more luck dealing with these documents in individual efforts.
>
> pr
>