Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht
Alexey Melnikov <alexey.melnikov@isode.com> Tue, 14 September 2010 11:19 UTC
Return-Path: <alexey.melnikov@isode.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 9002F3A69AF for <ftpext@core3.amsl.com>; Tue, 14 Sep 2010 04:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.37
X-Spam-Level:
X-Spam-Status: No, score=-102.37 tagged_above=-999 required=5 tests=[AWL=0.229, BAYES_00=-2.599, 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 hemaOaP9TreW for <ftpext@core3.amsl.com>; Tue, 14 Sep 2010 04:19:23 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id DAAFD3A695A for <ftpext@ietf.org>; Tue, 14 Sep 2010 04:19:22 -0700 (PDT)
Received: from [172.16.2.164] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TI9aUABIEIpi@rufus.isode.com>; Tue, 14 Sep 2010 12:19:47 +0100
Message-ID: <4C8F5A42.5000601@isode.com>
Date: Tue, 14 Sep 2010 12:19:30 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Anthony Bryan <anthonybryan@gmail.com>
References: <4C8743B4.4030101@isode.com> <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com> <AANLkTikL+QYbzr3BJG2XeYjP0Wep6SgKdDZ_Sa4W1XNJ@mail.gmail.com> <AANLkTimZ2i79onC93eL=6LF--3M4kQp2z65367ttZChD@mail.gmail.com>
In-Reply-To: <AANLkTimZ2i79onC93eL=6LF--3M4kQp2z65367ttZChD@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht
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, 14 Sep 2010 11:19:24 -0000
Anthony Bryan wrote: >On Sun, Sep 12, 2010 at 11:30 PM, liu dapeng <maxpassion@gmail.com> wrote: > > >>Hi Anthony, >> >>For the draft: draft-ietf-behave-ftp64, during last IETF meeting, >>people are agreed to split the draft to two separate ones, ALG related >>wrok goes to Behave WG, FTP protocol related work goes to FTPEXT. >>Shall we include this work item to the charter? >> >>Following text for your refernece: >>Deliverables: FTP extensions to support IPv4/IPv6 transiation scenario. >> >> >hi, > >thanks for the info. should I remove draft-ietf-behave-ftp64 from the >list? > I think listing a draft from another WG is confusing, so I would say yes. But note that it is Ok to have a Charter listing deliverables for which there is no draft. >does the FTP related draft exist yet, so I can list it? > > >FTP Extensions, 2nd edition (ftpext2) Charter > >Chair(s): > ? > >IETF Area: > Applications Area > >Applications Area Directors: > Alexey Melnikov <alexey.melnikov@isode.com> > Peter Saint-Andre <stpeter@stpeter.im> > >Responsible Area Director: > Alexey Melnikov <alexey.melnikov@isode.com> > >Mailing list: > General Discussion: ftpext@ietf.org > Archive: http://www.ietf.org/mail-archive/web/ftpext/current/maillist.html > >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 RFCs 2389 (a complete list appears in RFC 5797 and >the corresponding IANA registry at >http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xhtml >). > >The following are active FTP related drafts: > > draft-bryan-ftp-hash > draft-hethmon-mcmurray-ftp-hosts > draft-ietf-behave-ftp64 > draft-peterson-streamlined-ftp-command-extensions > draft-preston-ftpext-deflate > >The Working Group will: >* Review and finalize drafts listed above. >* Continue work on other drafts that are already in progress. >* 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. > >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. > >The Working Group must not introduce a new version of FTP, e.g. >an incompatible FTP 2.0. > >Goals and Milestones >Sep 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) >Sep 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) >??? 2010 Working group Last Call of HOST document >??? 2010 Submit 'File Transfer Protocol HOST Command for Virtual >Hosts' to the IESG for consideration as a Proposed Standard >??? 2011 Working group Last Call of HASH document >??? 2011 Submit 'File Transfer Protocol HASH Command for >Cryptographic Hashes' to the IESG for consideration as a Proposed >Standard >??? 2011 Close or recharter > > > > -- IETF Application Area Director, <http://www.ietf.org/iesg/members.html> Internet Messaging Team Lead, <http://www.isode.com> JID: same as my email address
- [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht liu dapeng
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht liu dapeng
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alfred Hönes
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht John C Klensin
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alfred Hönes
- [ftpext] RFC 959Re: Followup on FTPEXT2 BOF in Ma… John C Klensin
- Re: [ftpext] RFC 959Re: Followup on FTPEXT2 BOF i… Anthony Bryan