Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
Anthony Bryan <anthonybryan@gmail.com> Tue, 23 November 2010 21:16 UTC
Return-Path: <anthonybryan@gmail.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 0670728C0DB for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 13:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.817
X-Spam-Level:
X-Spam-Status: No, score=-2.817 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599]
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 ilGuBLQW9iiF for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 13:16:27 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 34C1128C15D for <ftpext@ietf.org>; Tue, 23 Nov 2010 13:16:27 -0800 (PST)
Received: by ewy8 with SMTP id 8so4693406ewy.31 for <ftpext@ietf.org>; Tue, 23 Nov 2010 13:17:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=YlS2FDpTO6bF3PcaD9k4UFOIHMjiCBXJ5b1R6tlMedg=; b=HPVP7OuAwhu4vJBexi72J1QHh6VZMJL5u96i5202uNiKBusbeiLQs5FfvrDXh6rHK9 SQvU8L/aAGs3Ap/oazaMh+FkrBu5Icjih0bgIZcUYloeeLCV741EQurALSgrvA5rJh0P mtGcUesYMu1yKyvCFZmA0mHD8K50iQ0Qkx2aM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=sUlLWV2NBWPym3FZDiYOXjgZvXrfdVkwbumo1QiJBeThk8DbwdhpcDFUNuaBhVLHJs Pfezr80gP4eSCUdJsKUcUtP8oLSDe+HlNw4Nb8blbvDmzHsA2GW0N7XbayV9JB1JbynQ CtXLjdimRTtKHVC5J+RXqhd/u37BIv9WuHVzw=
MIME-Version: 1.0
Received: by 10.213.15.209 with SMTP id l17mr7576720eba.63.1290547044577; Tue, 23 Nov 2010 13:17:24 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Tue, 23 Nov 2010 13:17:24 -0800 (PST)
In-Reply-To: <20101123184835.AFC433A69A1@core3.amsl.com>
References: <20101123184835.AFC433A69A1@core3.amsl.com>
Date: Tue, 23 Nov 2010 16:17:24 -0500
Message-ID: <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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 21:16:29 -0000
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). 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? 2) making sure everyone who would be interested in this WG knows about it's existence. now that it's official, I hope more people will hear about it. Alun mentioned inviting members of the old WG. I think think we can get a subscriber list, but the archives are at http://www.ietf.org/mail-archive/text/ftpext/ if anyone could go through & invite them... is there anyone else that should be invited? thanks for being here & helping us to improve FTP! -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads On Tue, Nov 23, 2010 at 1:48 PM, IESG Secretary <iesg-secretary@ietf.org> wrote: > A new IETF working group has been formed in the Applications Area. For > additional information, please contact the Area Directors or the WG > Chairs. > > FTP Extensions, 2nd edition (ftpext2) > --------------------------------------------------- > Current Status: Active Working Group > > Chair(s): > Anthony Bryan <anthonybryan@gmail.com> > Tony Hansen <tony@att.com> > > Applications Area Directors: > Alexey Melnikov <alexey.melnikov@isode.com> > Peter Saint-Andre <stpeter@stpeter.im> > > Applications Area Advisor: > Alexey Melnikov <alexey.melnikov@isode.com> > > Mailing Lists: > General Discussion: ftpext@ietf.org > To subscribe: https://www.ietf.org/mailman/listinfo/ftpext > Archive: http://www.ietf.org/mail-archive/web/ftpext/ > > Description of Working Group: > > The Standard File Transfer Protocol specification in RFC 959 > has been updated several times with command extensions of one > sort or another, including those based on the extension > mechanism of RFC 2389 (a complete list appears in RFC 5797 and > the corresponding IANA registry at > http://www.iana.org/assignments/ftp-commands-extensions). > > The following are active FTP related drafts: > > draft-bryan-ftp-hash > draft-hethmon-mcmurray-ftp-hosts > FTP extensions to support IPv4/IPv6 translation scenario > draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text > > The Working Group will: > * Review and finalize drafts listed above. > * Review and confirm or reject errata of current FTP RFCs. > * Investigate the differences between FTP in theory > (current RFCs) and practice, and recommend future work to align them. > Any future work would require rechartering of the WG. > > The Working Group's specification deliverables are: > * A document that specifies the HOST command (Proposed Standard). > * A document that specifies the HASH command (Proposed Standard). > * A document that specifies FTP extensions to support IPv4/IPv6 > translation scenario. > * A document that specifies FTP extensions for Internationalized Text. > > The Working Group must not introduce a new version of FTP, e.g. > an incompatible FTP 2.0. > > Goals and Milestones: > > Nov 2010 Submit 'File Transfer Protocol HOST Command for Virtual > Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts > will be used as a starting point) > Nov 2010 Submit 'File Transfer Protocol HASH Command for > Cryptographic Hashes' as working group item (draft-bryan-ftp- > hash will be used as a starting point) > Nov 2010 Submit 'FTP extensions to support IPv4/IPv6 translation' > as working group item (draft-liu-ftp64-extension will be used > as a starting point) > Dec 2010 Working group Last Call of HOST document > Jan 2011 Submit 'File Transfer Protocol HOST Command for Virtual > Hosts' to the IESG for consideration as a Proposed Standard > Jan 2011 Working group Last Call of HASH document > Feb 2011 Submit 'File Transfer Protocol HASH Command for > Cryptographic Hashes' to the IESG for consideration as a > Proposed Standard > Mar 2011 Working group Last Call of 'FTP extensions to support > IPv4/IPv6 translation' document > Apr 2011 Submit 'FTP Extension for Internationalized Text' > as working group item > May 2011 Submit 'FTP extensions to support IPv4/IPv6 translation' > to the IESG for consideration as Proposed Standard > Jul 2011 Working group Last Call of 'FTP Extension for > Internationalized Text' > Aug 2011 Submit 'FTP Extension for Internationalized Text' > to the IESG for consideration as Proposed Standard > Sep 2011 Close or recharter >
- [ftpext] WG Action: FTP Extensions, 2nd edition (… IESG Secretary
- Re: [ftpext] WG Action: FTP Extensions, 2nd editi… Anthony Bryan
- Re: [ftpext] WG Action: FTP Extensions, 2nd editi… Tony Hansen
- Re: [ftpext] WG Action: FTP Extensions, 2nd editi… Anthony Bryan
- Re: [ftpext] WG Action: FTP Extensions, 2nd editi… Tony Hansen