Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht

[Alexey Melnikov <[e-mail]>]

Anthony Bryan wrote:

>On Sun, Sep 12, 2010 at 11:30 PM, liu dapeng <[e-mail]> 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 <[e-mail]>
>     Peter Saint-Andre <[e-mail]>
>
>Responsible Area Director:
>     Alexey Melnikov <[e-mail]>
>
>Mailing list:
>     General Discussion: [e-mail]
>     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