Internet Anonymous FTP Archives (iafa) Charter Chair(s): Peter Deutsch <> Alan Emtage Mailing lists: General Discussion:iafa@cc.mcgill.ca To Subscribe: iafa-request@cc.mcgill.ca Archive: pub/iafa-archive@archive.cc.mcgill.ca Description of Working Group: The Internet Anonymous FTP Archives Working Group is chartered to define a set of recommended standard procedures for the access and administration of anonymous ftp archive sites on the Internet. Such a set of procedures will provide a framework for: (a) allowing the inexperienced Internet user the ability to more easily navigate the hundreds of publically accessible archive sites; and, (b) allowing users and network-based tools to retrieve specific site information such as access policies, contact information, possible areas of information specialization, archived package descriptions, etc., in a standardized manner. Particular emphasis will be placed on the possible impact of these procedures on the FTP site administrators. Attention will be paid to the impact of newer archive indexing and access tools on the operation of such archive sites. A set of suggestions will be offered to allow archive site administrators to better integrate their offerings with such tools as they are developed. The security of the anonymous FTP site configuration will also be considered to be an integral part of this document. It is expected that remote management of the archives will be adequately handled by existing network management procedures. Goals and Milestones: Mar 91 Review first draft and determine necessary revisions. Follow up discussion will occur on mailing list. Jun 91 Make document an Internet Draft. Continue revisions based on comments at IETF and on the mailing list. Nov 91 First IETF Meeting: review and approve the Charter making any changes deemed necessary. Examine the scope of the recommended procedures and impact on site administrators. Assign writing assignments for the first draft of the documents. Nov 92 Fourth IETF meeting. Review final drafts and if OK, give to IESG for publication as an RFC.