Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)

Tony Hansen <tony@att.com> Tue, 23 November 2010 23:55 UTC

Return-Path: <tony@att.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 309B728C110 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 15:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.434
X-Spam-Level:
X-Spam-Status: No, score=-106.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e2jpiG9nI3LQ for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 15:55:00 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 18BBD3A68F5 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:54:59 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-5.tower-161.messagelabs.com!1290556556!19924708!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 21688 invoked from network); 23 Nov 2010 23:55:57 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-5.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Nov 2010 23:55:57 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oANNuF3p012767 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:56:15 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oANNu8fJ012698 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:56:08 -0500
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 oANNtn41023202 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:55:49 -0500
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oANNtk01023107 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:55:46 -0500
Received: from [135.70.10.203] (vpn-135-70-10-203.vpn.west.att.com[135.70.10.203]) by maillennium.att.com (mailgw1) with ESMTP id <20101123235545gw1004lku4e> (Authid: tony); Tue, 23 Nov 2010 23:55:46 +0000
X-Originating-IP: [135.70.10.203]
Message-ID: <4CEC5480.8040801@att.com>
Date: Tue, 23 Nov 2010 18:55:44 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: ftpext@ietf.org
References: <20101123184835.AFC433A69A1@core3.amsl.com> <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>
In-Reply-To: <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
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: Tue, 23 Nov 2010 23:55:01 -0000

On 11/23/2010 4:17 PM, Anthony Bryan wrote:
> so, wow, looks like things are rolling along! :)
>
> as you can see, our WG got approved last Thursday.
>
> I'm very happy to see comments on
> draft-peterson-streamlined-ftp-command-extensions still coming in.
> please chime in if you haven't already.
>
> I'm new to this, so I wonder what the first order of business is?
>
> here are some ideas:
>
> 1) we have 4 drafts on the charter, 3 of which are "active" (John
> hasn't updated draft-klensin-ftp-typeu yet). once these are submitted
> with the string '-ftpext2-' in the
> draft name, they will show up at http://tools.ietf.org/wg/ftpext2/
>
> I think our ID draft-bryan-ftp-hash becomes ietf-ftpext2-hash then? (&
> the others follow in a similar fashion).

When the next update is ready for each draft, each author should upload 
the draft under the WG name. Bryan's naming suggestion is apropos:

draft-bryan-ftp-hash => draft-ietf-ftpext2-hash
draft-hethmon-mcmurray-ftp-hosts => draft-ietf-ftpext2-hosts
draft-klensin-ftp-typeu => draft-ietf-ftpext2-typeu

John, since yours is long expired, it would be useful if you just upload 
it under the new name so people can start commenting on it.

> should this be done now? we should change the WG at the top of our
> drafts I guess. how is this done in xml2rfc? is there anything else
> that needs to be changed?
This is optional: it is done by using the <workgroup> element in the 
<front> matter.

     Tony Hansen
     tony@att.com