Document 2

[Alan Emtage <[e-mail]>]

I've included a copy below of the second document currently on the IAFA
plate.... it's still a bit rough around the edges and will a good proof
read. However, the basic structure is there and hopefully this meeting in
Washington will finish it up.

I have not addressed the ongoing discussion about the file naming
conventions and recently wrote a note about this to the list. At this
point I'm tempted to punt this back to the meeting in November. I don't
see any real hurdles ahead, but a number of people have raised
interesting points about the current suggested method. The actual contents
of the files should not be a major problem from all I can see and that
the only thing that would be needed in the document is a method for the
naming of the files on the major operating systems.

There are no really major changes between this draft and the previous
one. ISBN number and FAX number fields have been added to some of the
templates as well as a few others. A Uniform Resource Identifier field
has been added to several of the templates. For those of you unfamiliar
with the subject, there is a short paragraph describing them in the
document.

This document will be placed on the archive in the next day or do. I look
forward to hearing your comments.

-Alan

-------------

	           	   IAFA-WG

	Publishing Information on the Internet with Anonymous FTP

			(IAFA DOC II)

			DRAFT 92.10.19



Over the past several years, Anonymous FTP has become the primary method
of publishing information in the Internet environment.  Anonymous FTP is
an application-level service that makes use of the File Transfer Protocol
[1], one of the principal protocols of the TCP/IP suite. A well organized
and well maintained Anonymous FTP archive (AFA) can provide a relatively
cheap and simple way to distribute the programs, documents and datasets
that are produced for general availability on the network today.

Those groups wishing to set up an Anonymous FTP Archive should refer to
RFC [* IAFA Doc I *] , "A Guide to Anonymous FTP Site Administration"
which provides details on why one would want to set up such an archive
and what steps are required to have a secure, well maintained system.

This document recommends a set of information that your site may wish to
construct and make available on the Anonymous FTP Archive to the Internet
user community. Automatic archive indexing tools have been created that
gather and index this information, thus making it easier for users to
find and access it. It also may be used by the general user community for
extracting information about the archive itself or about material
contained on the archive.  Although not required, providing such
information will make your archive a more useful resource.

In Part I of this document we make recommendations that are intended to
provide a standardized means for sharing information about the contents
of a specific archive site. These include information concerning such
things as services provided by the institution, document abstracts,
software descriptions as well as administrative contacts, local Timezone
and other site-specific details.

Part II contains a set of encoding procedures for the information
outlined in Part I. These procedures allow the you, the AFA
administrator, to take into account site-specific issues such as whether
your particular operating system offers the capability of creating and
using subdirectories, any limitations on filename length or the inability
to use specific characters in filenames.



Part I: Useful Configuration and Contents Information

In this section we define a recommended set of information that you
could make available as the administrator of an archive site. In doing
so, you would extend the functionality of your archive, as well as the
functionality of the indexing and resource discovery tools that pick up
and redistribute such information.

It is expected that this information will be made available through the
anonymous FTP archive mechanism. The actual encoding method used will be
host and OS specific. Encoding methods for some of the most popular
computing environments are presented in Part II.

Note that this document does not mandate or require that any particular
class of information be offered. However it is recommended that those
sites wishing to offer the information described here adhere to the
formats recommended in Part II.

Collectively the files described in this document will be referred to as
"indexing files".

Uniform Resource Identifiers
----------------------------

Work is currently underway for the construction of what are known as
"Uniform Resource Identifiers". These will be structured strings whose
purpose is to uniquely identify any resource on the Internet to determine
access and identification information for that resource. This not only
includes documents, software packages and the like, but also images,
interactive services and physical resources. This concept has been
integrated into the data templates described below, however no examples
of an actual URI are included.

Site-Specific Configuration Information
---------------------------------------

Information about your archive site itself can often be valuable to
users of your system in order for them to utilize the resource in an
efficient manner.


Description Information
-----------------------

	- You should make available a brief description of the kind of
	  information stored in your anonymous FTP archive. If your
	  site specializes in a particular type of information you
	  should mention this. Examples might include software for a
	  specific machine type, on-line copies of particular types of
	  literature or research papers or information covering a
	  particular branch of science or engineering.

	 - You should also make available a set of suitable keywords
	  appropriate to the above description to aid in the creation
	  of suitable indexes.


Configuration Information
-------------------------


Site configuration information will help users better understand your
wishes on how and when to access your site.  This would include such
information as:

Site Information:

        - The name of the site
	- The name of the person or group responsible for administering 
	  the site
        - The postal address
        - The telephone number (in International format)
	- The FAX number
        - Email address of person or persons responsible for site
          administration.
        - The name of the organization or group owning the site
        - The type of the organization
	- Sponsoring organization
	- The location of the site by city, state (province, etc) , country
        - The geographical (latitude/longitude) location
        - The timezone of the site
	- Record modification information: the person to last modify
	  the record and when
	- The frequency with which the archive site is generally modified
	- A brief description of the kind of information stored at
	  this anonymous FTP archive. If your site is intended to
	  specialize in a particular type of information (examples
	  might include software for a specific machine type, on-line
	  copies of a particular type of literature or research papers
	  and information in a particular branch of science or
	  arts) you should indicate this.
        - A summary of the access policies of this site. This
          should include such information as preferred times of
          usage, conventions or restrictions for uploading files
          to this site etc.


Logical Configuration
---------------------

Note that one physical archive site may possibly contain multiple
"logical" archives. For example, a single archive host may be shared
amongst multiple departments, each responsible for the administration
their own part of the anonymous FTP directory subtree.

Some information (such as a host's location) will remain constant for
the site as a whole. We therefore recommend that you to list Logical
Archive specific and site-specific information separately.

Logical Archive configuration:

	- A summary of the access policies of this logical archive
	- A summary of the type of information that this logical archive may
	  specialize in
	- The name of the organization or group owning logical archive
	- The type of the organization
	- Sponsoring organization
	- The name of the person responsible for administering logical
	  archive
	- The postal address of primary contact
	- The telephone number of primary contact
	- Email address of primary contact
	- Record modification information: the person to last modify
	  the record and when
	- The frequency with which the archive site is generally modified
	- Keywords appropriate for describing this locgical archive

Site-Specific Content Information
---------------------------------

The preceding collections of information make available access and
utilization policies for a site. You could also wish to make available
a selection of information about the actual contents of your archive or
the services available from your organization or institution.

The following categories have been identified.


Services:
	- The archive can offer an overall description of each the
	  various Internet services offered by your organization's
	  systems, along with corresponding contact information. This
	  description would then indicate whether the the parent
	  organization offers such services as:

		- on-line library catalogues
		- Interactive online information services such as WAIS [3],
		  gopher [4], Prospero [5], WWW [6] or archie [7]
		- specialized information servers such as those
		  providing weather, geographic information, newswire
		  feeds etc.
		- Other information services

	  The following information can be made available:

		- Name of service
		- Host providing service
		- A brief description of the service
		- Name(s) of service maintainer(s)
		- Postal address of Service maintainer(s)
		- Telephone number of service maintainer(s)
		  (in International format)
		- FAX number of service maintainer(s)
		- Electronic Mail address of maintainer(s)
		- The required access protocol (telnet, FTP etc)
		- Policies on service use
		- Access times for service
		- Keywords
		- URI

			  
Documents:

	- You might wish to make available a brief description of
	  documents contained in the archive. This might correspond to
	  the actual abstract for each technical report or other
	  document served from this archive site or simply be a brief
	  description created to help potential readers. All such
	  documents offered should have a corresponding abstract made
	  available for it.

		- Filename or directory name of the document
		- Title of the document
		- Filename of the document
		- Name(s) of author(s)
		- Last revision date
		- Category (technical report, conference paper etc)
		- Abstract of the document being referenced
		- Bibliographic entry
		- Format that the document is stored in (ASCII text,
		  PostScript, DVI etc.)
		- Publication status (draft, published etc.)
		- Document size
		- Document language
		- Document character set
		- ISBN Number
		- Copyright and copying policy
		- Appropriate keywords
		- URI 


Datasets:
	- You should offer a description of any datasets stored on the
	  archive. These could include star catalogs, DNA sequences,
	  census statistics etc.
		- Name of the file containing dataset
		- Title
		- Version designation of the dataset
		- Date last revised for dataset
		- Source of data
		- Name of individual or group responsible for compilation
		- Telephone number of primary contact
		- Postal Address of primary contact
		- FAX number of primary contact
		- Electronic mail address of primary contact
		- Information on person(s) or group(s) responsible
		  for compiling this dataset
		- Size of dataset
		- Format of data (special record format name etc.)
		- Programs used to manipulate the data in the set
		- Copyright and copying policy
		- URI

Software Packages:
	- Outlines for each of the program packages offered at this site.
		- Name of file containing the package
		- Title of package
		- Version of the package
		- Full description of the function of package
		- Abstract (short description of package)
		- Name of author
		- Telephone number of author  (in International format)
		- Address of author
		- Email address of author
		- FAX number of author
		- Package maintainer (name)
		- Telephone number of maintainer  (in International format)
		- Address of maintainer
		- Email address of maintainer
		- FAX number of maintainer
		- Package origin (original site or copied)
		- Distribution type (source code or binary)
		- Special considerations or restrictions on
		  the package's use (programming languages needed,
		  hardware restrictions, etc).
		- Copyright and copying policy (Public Domain, Freely
		  Redistributable)
		- Keywords appropriate for the package
		- Last modified (by whom and when)
		- Discussion forums (mailing lists, USENET newsgroups)
		- URI

Mailing Lists:
	- Publicly available mailing lists are maintained by this
	  organization or institution. It is assumed that only lists
	  admitting general subscriptions will be listed.
	  	- Name of mailing list
		- Email address of list
		- Email address of administrative contact
		- Description of list
		- Archives of list
		- Keywords appropriate for describing the function of the
		  list
		- URI
		

[* Some work needs to be done on this next one *]

Complete File listing:
	- A listing of all archive entries at this archive in format
	  appropriate for that environment. Such listings, if properly
	  maintained, reduce network traffic while simplifying the task of
	  archive indexing services.


Usenet Newsgroup Archives
	- Information concerning Usenet newgroups that are archived
	  at your site and relevant contact details.
		- Name of newsgroup
		- Mailinglist gateway
		- Description of newsgroup
		- Location of archive
		- Starting date of archive
		- Language/character set
		- URI
		



Part II: Information Encoding for Specific Environments
-------------------------------------------------------

In this section we offer a recommended encoding format for each of the
standard items of information suggested in Part I. In many cases these
recommendations should be applicable to all environments. Where this is
not true standardized encodings are offered for specific operating
systems.

We offer such a standardized format so that if such information _is_ to
be offered, it is formatted in such a way that it can be utilized by
automated indexing and retrieval tools. The encoding methods proposed
were developed to be extensible, so that additional information can be
offered in a similar format, if the site administrator so wishes.

Developing such recommendations offers several challenges. It is
hoped that the encoding conventions should be applicable to as wide a
variety of operating systems, file structures and encoding schemes as
possible. In addition, the globalization of the Internet requires
attention to constraints such as the language in use at an archive site.

In addition, the encoding methods proposed must be easy to implement and
for the moment, use existing methods of access and retrieval.  We
currently assume that the site language is English. It is assumed that
additional formats for other languages will be developed over time.


Naming conventions
------------------

For the greatest flexibility it is assumed that unless otherwise stated,
each file containing the indexing information may reside anywhere in the
anonymous FTP subtree and in addition, any number of these files may
exist. The intention here is that they may reside in the same location as
the information they are indexing. You, as the administrator are free to
place these files wherever you think appropriate. Note that some files
may carry information from their place in the directory structure and
therefore they may not just be randomly placed in the file structure.


A file of the given name will exist for each category listed in Part I.
For the sake of consistency across operating systems and for the ability
to distinguish them from non-configuration files of the same name, the
filenames will be in all uppercase letters. Because of restrictions on
some systems, filenames will be kept to a maximum of 14 characters.

In order for tools to easily identify an indexing file from the other
data files at the archive site, all indexing filenames should begin with
the five character string "IAFA-".

(1) Files that may contain multiple instances of a given category (Mailing
    Lists for example) will logically be divided into records and each
    record containing multiple fields. Unless otherwise specified, files
    may contain one or multiple records as defined below and multiple
    records are separated by one or more blank lines. The start of each
    field is marked by a special fieldname on a new line in the rightmost
    column followed by a colon (:).

(2) Field data may be separated from fieldname by whitespace. Any field
    may continue on the next line by whitespace (blank, tab) in the first
    column. Multi-line fields are terminated with the first line not
    to have whitespace in the first column.

(3) Fields in the same record must not contain any blank lines between
    them.


(4) In the following records _all_ Email addresses must be in RFC 822
    format. Names may be included in the Email address.

    For example:

    		"John Doe" <[e-mail]>
            or
	    	[e-mail] (John X. Doe)

    are valid Email addresses.


Encoding for UNIX Systems
-------------------------

Indexing files should be made world readable. It is assumed that
size and last modification times can be obtained through the existing
FTP mechanism.

The advantages to this system are that this information need only be
constructed once with infrequent periodic updates as changes occur.
Several of these files may never change during the lifetime of the host
as an anonymous FTP site. They require no special programs or protocols to
construct: a text editor is all that is needed.

Site Description
----------------

Filename: IAFA-DESCRIPT

This file contains 1 record with the following fields. 

IMPORTANT: There should only be one instance of this file in each archive.


Description:	This file contains text describing any areas of
		specialization for this site. For example,
		if the site contains information related to the filed
		of molecular biology a paragraph or two with the
		keywords "molecular biology" and some further
		description would be in order. It should also mention 
		if this site contains "logical" archives.
Keywords:	Appropriate keywords describing contents of this AFA


Example for IAFA-DESCRIPT file.

Description:	This site contains data relating to DNA sequencing
		particularly Yeast chromosome 1. Datasets are available.
		There is also a selection of programs available for
		manipulating this information.
Keywords:	DNA, sequencing, yeast, genome, chromosome
		


Physical Site Information 
-------------------------

This file contains one (1) record with the following fields.

IMPORTANT: There should only be one instance of this file in each archive.


Filename: IAFA-SITEINFO

Fields for this file.

Name:			Primary DNS (Domain Name System) name

Preferred-Name:		Preferred DNS-registered name (CNAME record) for
			the site

Contact:		Name of person or group responsible for AFA
			administration

Postal-Address:		The postal address of the site

Telephone:		The telephone number of the contact. Should be in
			international format and including the country
			code

Fax:			FAX number of the contact. Should be in
			international format and including the country
			code

Electronic-Address:	Email address in RFC 822 format for the AFA
			administrator

Organization:		Name of institution/organization/individual to
			which the site belongs

Organization-Type:	Type of organization (university, commercial,
			research)

Sponsoring-Organization: The name and contact information for the
			 organization sponsoring this site if different
			 from above

Location:		City, State and Country of the site

Latitude-Longitude:	Latitude and longitude of site (See Note <1>)

Timezone:		Timezone as hours and minutes from UTC (See Note <2>)

Modified-by:		Name of person writing this file (See Note <3>)

Frequency:		Preferred frequency of retrieval of all AFA
			extended configuration information by automated
			retrieval tools (See Note <4>)

Access-times:		Period of preferred times of access to
			anonymous FTP users in UTC. (See Note <5>)

Policy: 		Information such as conventions or restrictions for
			uploading files to this site etc.


Notes for this record.

<1> Latitude and longitude are specified in that order as

	DD MM SS C / DD MM SS C

    Where
        DD is in degrees
	MM is in minutes
	SS is in seconds
	C is the direction designator which is 
	  For latitude
		"+"	is north of the equator
		"-"	is south of the equator
	  
	  For longitude
	        "+"	is west of the Greenwich meridian
		"-"	is east of the Greenwich meridian

    The double quotes (") are not part of the designator, but are used
    here to delimit the symbols.


<2> Timezone is specified in hours and minutes from UTC (GMT). Specified
    as

    THHMM

    Where T is one of 
		"+"	is east of the Greenwich meridian
		"-"	is west of the Greenwich meridian


    HH is hours from UTC
    MM is minutes from UTC

<3> Email address and date of document composition may be included in
    this field in free format. This field should be overwritten when the
    information is modified to show the person modifying the record and
    when it was modified.

<4> The period is measured in days. This value should be chosen to
    reflect the turnover of information at the archive.


<5> Times in UTC between which access to this site is preferred. There
    may be multiple entries, each separated by whitespace. Each entry
    takes the format

    HHMM / HHMM

    Where
       HH is in hours
       MM is in minutes

    The first HHMM is starting time, the second the ending time.


An example of a IAFA-SITEINFO file:

Name:			foo.bar.org
Preferred-Name:		ftp.bar.org
Organization:		Beyond All Recognition Foundation
Contact:		John Doe
Electronic-Address:	[e-mail]
Telephone:		[phone]
Fax:			[phone]
Postal-Address:		PO Box. 6977, Marinetown, PA 17602
Location:		Lampeter, PA, USA
Latitude-Longitude:	37 24 43 - / 121 58 54 +
Timezone:		-0400 (North America Eastern Standard Time)
Modified-by:		[e-mail] (John X. Doe); Mon Feb 10 22:43:31 PST 1992
Frequency:		10
Access-Times:		0200 / 1300 1800 / 2100
Policy:			Non-proprietary data may be uploaded to this
			site in the "incoming" directory. Please
			contact site administrators if you do so.
			Proprietary material found in this directory
			will be removed. This site is not to be used
			as a temporary storage area.
		

Logical Archive Info
--------------------

Filename: IAFA-LARCHIVE

IMPORTANT: The placement of this file in the file structure is
significant: It implies that the directory in which this file exists and
all subdirectories are part of the logical archive.

Any number of these files may exist in the archive.


Policy: 		Information such as conventions or restrictions for
			uploading files to this site etc.

Description:		Contains text describing any field or area of
			specialization that the site subscribes to.

Organization:		Name of institution/organization/individual to
			which the site belongs

Organization-Type:	Type of organization (university, commercial,
			research)

Sponsoring-Oranization:	The name and contact information for the
			organization sponsoring this site if different
			from above

Contact:		Name of person or group responsible for AFA
			administration

Postal-Address:		The postal address of the primary contact

Telephone:		The telephone number of the primary contact.
			Should be in international format and including
			the country code

Fax:			The FAX number of the primary contact. Should be
			in international format and including the country
			code

Electronic-Address:	Email address in RFC 822 format for the AFA
			administrator

Modified-by:		Name of person writing this file (See Note <1>)

Frequency:		Preferred frequency of retrieval of all AFA
			extended configuration information by automated
			retrieval tools (See Note <2>)

Keywords:		Appropriate keywords describing contents of this
			logical AFA

Notes for this record.


<1> Email address and date of document composition may be included in
    this field in free format. This field should be overwritten when the
    information is modified to show the person modifying the record and
    when it was modified.

<2> The period is measured in days. This value should be chosen to
    reflect the turnover of information at the archive.

An example of a IAFA-LARCHIVE file:

Organization:		Orymonix Incorporated
Policy:			All material contained in this 
			archive is in the public domain
Description:		This archive contains essays on Military
			Intelligence, Postal Service and Progressive
			Conservatism
Contact:		Ima Admin
Electronic-Address:	[e-mail]
Telephone:		[phone]
Fax:			[phone]
Postal-Address:		555, Marsden Road, London, SE15 4EE
Modified-by:		Yuri Tolstoy <[e-mail]>
			Fri Nov 27 07:00 GMT 1992
Frequency:		20
Access-Times:		0200 / 1300 1800 / 2100
Keywords:		Militarism, Post Office, Conservatism


For the following categories the assumption shouldn't be made that the
information applies to the anonymous FTP host itself. Rather, the group
or organization may publish general information: the specific information
will be contained inside the file describing the category.


Services information
--------------------

Filename: IAFA-SERVICES

This file contains records with the following fields. Each record is
started and delimited by the "Service-Name" field.

Any number of these files may exist in the archive.


Service-Name:		Name of the service (See Note <1>)

Primary-Name:		Primary DNS name of host providing service

Description:		Short description of the service provided

Contact:		Name of person or group responsible for service
			administration (primary contact)

Postal-Address:		The postal address of the primary contact

Telephone:		The telephone number of the primary contact.
			Should be in international format and including
			the country code

Fax:			The FAX number of the primary contact. Should be
			in international format and including the country
			code

Electronic-Address:	Email address in RFC 822 format for the service
			administrator

Modified-by:		Name of person modifying this record and date
			modified

Access-protocol:	Method required to access service (See Note <2>)

Access-Times:		Times for mandatory or preferred access of
			service. See Access-Times field for IAFA-SITEINFO
			record for format

Keywords:		Keywords appropriate for the service

Policy:			Policies for the use of this service

URI:			The Uniform Resource Identifier for this service

Notes on this file.

<1> This can be a generic name such as "NNTP" or "WAIS" or something more
    specific such as "Geographic Name Server"

<2> A description of how the service is to be accessed. This may be as
   simple as "Email" or "telnet to port 201" or more complex such as
   "Prospero protocol on port 5678"


Example of IAFA-SERVICES file.

Service-Name:		Census Bureau information server
Hostname:		census.ispy.gov
Description:		This server provides information from the latest USA
			Census Bureau statistics (1990).
Contact:		Jay Bond
Postal-Address:		PO Box. 42, A street Washington DC, USA 20001
Telephone:		[phone]
Fax:			[phone]
Electronic-Address:	[e-mail]
Access-protocol:	telnet protocol to port 666. A server-specific
			query language is used. Type "help" for more
			information.
Access-Times:		0900 / 1700
Modified-by:		Q <[e-mail]> Jan 1 12:00 GMT 1908
Policy:			This service may not be used by sites in the
			Republic of West Commiedom
Keywords:		census, population, 1990, statistics



Document Abstracts information
------------------------------

Filename: IAFA-ABSTRACTS

This file contains records with the following fields. Each record is
started and the previous record is delimited by the "Document-Name" field.
Any number of these files may exist in the archive.

Any number of these files may exist in the archive.


Document-Name:		Filename containing the document

Title:			Full title of the document

Authors:		Name of authors (See Note <1>)

Revision-Date:		Last date that the document was revised

Category:		Type of document. (See Note <2>)

Abstract:		Summary of the document

Citation:		The official bibliographic entry for the document

Format:			Format or formats in which the document is
			available (See Note <3>)

Publication-Status: 	Current status of document (draft, published etc)

Size:			Length of document in pages or bytes

Language:		The name of the language in which the document is
			written

Character-Set:		The designation of the character set used in
			the document (ASCII, ISO Latin-1 etc)

ISBN:			The ISBN number of the document

Copyright:		The copyright statment. Any additional information
			on the copying policy may be included.

Keywords:		Keywords relevant to the document

URI:			The URI for the document


Notes for this file.

<1> The names of the individuals or group appearing on the document as
    authors. RFC 822 Email address for each author should be included
    where appropriate.  Postal addresses may also be included where
    appropriate. Entries should be separated by a semicolon.

    For example

Authors:     H. Hermithouse <[e-mail]>; Roche German
       	     <[e-mail]> 805 Alpenstrasse, Hamburg, FRG

<2> The intention of this field is to define the category of the document.
    It can be "Technical Report", or the name and date of the conference
    at which the paper was presented. It may also be something like
    "General guide" or "User manual"

<3> Documents are often available in several formats. Examples include
    "PostScript", "ASCII text", "DVI" etc.



Example of IAFA-ABSTRACTS file.

Document-Name:	 	yeast-homeobox.ps, yeast-homeobox.txt
Title:			The function of homeoboxes in Yeast Chromosome 1
Authors:		John Doe [e-mail]; Jane Buck
			[e-mail]
Revision-Date:		25 November 1991
Category:		Yeastcon, January 1992, Mushroom Rock, CA, USA
Abstract:		Homeoboxes have been shown to have a
			significant impact on the expressions of genes
			in Chromosome 1 of bakers yeast.
Format:			PostScript, ASCII (without graphs)
Citation:		J. Doe, J. Buck, The function of homeoboxes in
			Yeast Chromosome 1, Conf. proc. Yeastcon, January
			1992, Mushroom Rock, pp. 33-50
Publication-Status:	Published
Language:		English
Character-Set:		ASCII
Copyright:		The copyright on this document is held by the
			authors. It may be freely copied and quoted as
			long as the authors are cited.
Size:			18 pages
Keywords:		homeobox, yeast, chromosome, DNA, sequencing
			



Datasets Information
--------------------

Filename: IAFA-DATASETS

This file contains records with the following fields. The record is
started and delimited by the "Dataset-Name" field.

Any number of these files may exist in the archive.


Dataset-Name:	Name of the file or directory containing the dataset

Title:		Title of the dataset.

Version:	Version number can be used if one is associated with the
		dataset

Revision-Date:	The date of last revision of the dataset


Contact:	Name of person or group responsible for dataset
		administration (primary contact)

Postal-Address:	The postal address of the primary contact

Telephone:	The telephone number of the primary contact.
		Should be in international format and including
		the country code

Fax:		The FAX number of the primary contact. Should be
		in international format and including the country
		code

Electronic-Address:	Email address in RFC 822 format for the service
			administrator

Source:		The group or organization providing the source for the
		dataset. Email or postal addresses should be included
		where possible

Compiled-by:	The group or organization responsible for compiling the
		dataset into the format for which this description
		applies. Email or postal addresses should be included
		where possible

Size:		Size of the dataset. (See Note <1>)

Format:		The format in which the dataset is distributed. (See Note
		<2>)

Software:	A list of any programs used to manipulate the dataset.
		Contact names and addresses (Email,postal) should be
		included where possible.

Copyright:	Copyright policy for this dataset

URI:		The URI for the dataset

Notes on this file.

<1> This information should be in well-known units such as octets
    (bytes). Alternatively the number of records in the dataset and the
    record size may be given. The units used should be written explicitly.
    
<2> The format may be well-known or specific to a specific dataset.
    Additional information on programs used with this dataset should be
    provided in the "Software" field.


[* Example of the DATASETS file. *]




Software Packages Information
-----------------------------

Filename: IAFA-PACKAGES

This file contains records with the following fields. The record is
started and delimited from other records by the "Package-Name" field.

Any number of these files may exist in the archive.


Package-Name:		Name of the file or directory containing the package

Title:			Title of the package

Version:		This field can be used if a version number or
			string is associated with the package

Description:		Full description of the function of the programs
			in the package

Abstract:		Short description of function of package

Author:			Name address of author(s) if available

Author-Telephone: 	The telephone number of the author

Author-Fax:		FAX number of author

Author-Postal:		Postal address of the author

Author-Email:		Electronic mail address of author

Maintained-by:		The current maintainer of the package

Postal-Address:		The postal address of the primary contact

Telephone:		The telephone number of the primary contact.
			Should be in international format and including
			the country code

Fax:			The FAX number of the primary contact in
			international format and including the country
			code

Electronic-Address:	Email address in RFC 822 format for the primary
			contact

Maintained-At:		Host name of the "home" of the package if known.
			This is the site at which the most uptodate
			version of the package would be expected to be
			found

Distribution-Type: 	Describes if the package is distributed in source
			or binary format. The programming language the
			package is written in should be included for
			source distributions or the architecture for
			binary distributions

Restrictions:		Any requirements or restrictions that the package
			may have in terms of hardware or software (OS)
			platforms.

Discussion-Groups: 	Any groups (mailing lists, USENET newsgroups)
			where discussion of this package would be
			appropriate

Copying-Policy:		The status of the package for copying purposes
			(See note <1>)

Modified-by:		Name of person modifying this record and date modified

Keywords:		Keywords appropriate for users trying to locate
			the package

URI:			The URI for this package


Notes on this record.

<1> The most common entries for this field would be "Public Domain" or
    "Freely Redistributable" or "Voluntary Payment" (shareware). However
    since a record may exist for software packages not resident on the
    AFA, this field may be entered as "Proprietary" or some other form of
    restricted access. A copyright notice should be included here if
    desired.

Example record for the IAFA-PACKAGES file.

Package-Name:		Vfifth.tar.Z
Title:			Beethoven's Fifth Player 
Version:		67
Description:		The program provides the novice to Transitional
			Classical-Romantic music a V-window interface
			to the authors latest composition. 
Abstract:		V-window based music player
Author:			Ludwig Van Beethoven ([e-mail])
Author-Fax:		[phone]
Maintained-At:		dot-dot-dot.dash.at
Distribution-Type:	Source
Discussion-Groups:	USENET rec.music.classical
Restrictions:		Runs on Morse OS version V or greater
Copying-policy:		Freely Redistributable. Copyright held by author.
Keywords:		Classical music, V-windows




Mailing List Information
------------------------

Filename: IAFA-MAILLISTS

This file contains records with the following fields. New records are
marked and delimited by the "Mailinglist-Name" field.

Any number of these files may exist in the archive.


Mailinglist-Name:	The name of the list

Address:		The address (in RFC 822 format) that mail
			intended for this list should be sent to.

Administration: 	The address (in RFC 822 format) of the
			administrative contact for the list. Additions
			and deletions to the list as well as questions
			about the list should be directed to this address.

Description:		A description of the purpose of the list. Any
			special conditions for the list should be
			included.

Keywords:		Keywords useful for anyone looking for the list

Archive:		Location and access method for any archive for
			this mailing list

URI:			The URI for the list

Example of the IAFA-MAILLISTS file.

Mailinglist-Name:	Internet Engineering Task Force (IETF) Internet
			Anonymous FTP Archive working group (IAFA-WG)
			mailing list
Address:		[e-mail]
Administration:		[e-mail]
Description:		Discussion list for the IAFA Working Group
			concerning the administration of anonymous FTP
			archive sites.
Keywords:		IETF, IAFA, anonymous, FTP, archive, Internet
Archive:		The archive for this mailing list is available on
			archive.cc.mcgill.ca via anonymous FTP in the file
			pub/mailing-lists/iafa




Listing Information
-------------------

Filename: IAFA-LISTINGS

Only one instance of this file should exist in the archive.

This file differs from the others in that it has no defined fields.  For
UNIX sites this file should contain a long recursive listing (ls -lR)
from the directory in which the anonymous FTP client would find itself on
initial login. The file may be compressed by the UNIX compress(1) format.
Any anonymous FTP retrieve of this file should be, by default in binary
mode to accommodate the case of the file being compressed.

This file should be automatically generated on a frequent basis,
depending on how often the files at your site change. Compressing the
file lessens the load on the network since less traffic has to flow and it
lessens the load on the anonymous FTP archive host since the
administrators can determine when it is most convenient for the program to
run.
    


USENET News Information
-----------------------

Filename: IAFA-NEWSARCH

This file contains records with the following fields. New records are
marked and delimited by the "Newsgroup-Name" field.


Newsgroup-Name:		The name of the newsgroup

Mailinglist-Gate:	The address (in RFC 822 format) of the mailing list
			this newsgroup is gatewayed to (if any)

Description:		A description of the purpose of the newsgroup as
			found in List_of_Active_Newsgroups regularly posted
			in news.announce.newusers.

Keywords:		Keywords useful for anyone looking for the newsgroup

Archive:		Location and access method for the archive for this
			newsgroup.

Archive-Date:		The date that the archive was started

Language:		Primary language for this newsgroup

Character-Set:		Principal character set for this newsgroup

URI:			The URI for this news archive

Example of the IAFA-NEWSARCH record.

Newsgroup-Name:		comp.windows.x
Mailinglist-Gate:	[e-mail]
Description:		Discussion about the X Window System
Archive:		Selected articles are archived in
			/pub/news/comp.windows.x/volumeYY/NN-MMM,
			where YY is the year (e.g. 91), NN is the number of the
			month (e.g. 03) and MMM is the name of the month
			(e.g. Mar). This gives something like volume91/03-Mar.
Keywords:		X, X11, X Window System, Xlib, Xt, Xaw


Conclusion
----------

This document attempts to provide the foundation for a common set of
recommended cataloging practices which may be used on the Internet to
enhance the utility of Anonymous FTP archives, currently the most widely
used and supported mechanism for general information storage and
retrieval. It is intended that these recommendations be flexible enough
to accomodate a broad spectrum of information classes and it is hoped
that they will be widely used and that automated tools will be developed
to use the valuable information that they make available.

----------------------------------------------------------------------

Bibliography [* To be fixed up *]
------------

[1] RFC 959		Postel, J.B.; Reynolds, J.K. File Transfer
                        Protocol. 1985 October

[2] RFC1296		Lottor, M.  Internet Growth (1981-1991).  1992
                        January;