TFTP Extensions (tftpexts) Charter

NOTE: This charter is accurate as of the 31st IETF Meeting in San Jose. It may now be out-of-date. (Consider this a "snapshot" of the working group from that meeting.) Up-to-date charters for all active working groups can be found elsewhere in this Web server.

Chair(s)

Art Harkin <ash@cup.hp.com>
Gary Malkin <gmalkin@xylogics.com>

Applications Area Director(s):

John Klensin <Klensin@mail1.reston.mci.net>
Erik Huizer <Erik.Huizer@SURFnet.nl>

Area Advisor

John Klensin <Klensin@mail1.reston.mci.net>

Mailing List Information

General Discussion:tftpexts@hpindsh.cup.hp.com
To Subscribe: tftpexts-request@hpindsh.cup.hp.com
Archive: onet2.cup.hp.com:pub/dist/tftpexts/tftpexts_archive

Description of Working Group

The TFTP Extensions Working Group will review, refine as needed, and then make a recommendation on standardization of several recent standards-track proposals to extend TFTP. These proposals include a backward compatible extension mechanism for TFTP and related extension options for this mechanism.

Initial drafts of all of the documents that the working group is expected to review have already been, or will soon be, published. The working group will be starting with documents that have been prepared as individual (or spontaneous design team) contributions. It is not expected to initiate new work. On the other hand, it is expected to make explicit "not ready for standardization" or "inappropriate for standardization" recommendations if appropriate.

The working group will be begin with the following Internet-Drafts or their successors:

- draft-malkin-tftp-option-ext-00.txt

- draft-malkin-tftp-blksize-opt-00.txt

Goals and Milestones

Done: Meet at the San Jose IETF. Review pending Internet-Drafts and decide for each whether it is ready for processing to Proposed, should be published as Experimental or Informational, should be discarded as a working group effort, or should be a candidate for further working group development. Refine the charter and work plan.
Feb 95: Drafts with minor revisions distributed on mailing list for review. Internet-Drafts concluded in Dec 94 refined and sent to IESG for processing.
Mar 95: Concluded Internet-Drafts with minor revisions sent to IESG for processing.
Apr 95: Meet at the Danvers IETF if necessary. Drafts with major revisions since Dec 94 reviewed. Review new additional Internet-Drafts for new options. Review implementation progress.
Jun 95: Remaining revised Internet-Drafts sent to IESG for processing.