As per Relevance of the word document, we have this rfc below:











Network Working Group G.
Request for Comments: 1150
FYI: 1 J.

March 1990


F.Y.I. on F.Y.I

Introduction to the F.Y.I.

Status of this

This RFC is the first in a new sub-series of RFCs called FYIs (
Your Information). This memo provides information for the
community. It does not specify any standard. Distribution of
memo is unlimited

1.

The FYI series of notes is designed to provide Internet users with
central repository of information about any topics which relate
the Internet. FYIs topics may range from historical memos on "Why
was was done this way" to answers to commonly asked
questions

The FYIs are intended for a wide audience. Some FYIs will cater
beginners, while others will discuss more advanced topics. An
may be submitted by anyone who has something to contribute and
the time to do so

2. Why

There are several reasons why the FYIs are part of the larger
series of notes. The formost reason is that the
mechanisms for RFCs are tried and true. Anyone who can get an RFC
can automatically get an FYI. More importantly, anyone who knows
the RFC series, can easily find out about the FYIs

Another reason for making FYIs part of the RFC series is that
maintainance mechanisms for RFCs are already in place and funded.
makes sense to maintain similar documents is a similar way.
all, there have been informational RFCs before

Finally, the name RFC has come to carry a meaning with it. There
credibility associated memos carrying the RFC label. FYIs
share that respect




Malkin & Reynolds [Page 1]

RFC 1150 F.Y.I. on F.Y.I. March 1990


3. Format

Since the FYIs are a part of the RFC series, they must conform
RFC-1111 (Request for Comments on Request for Comments:
to RFC Authors) with respect to format. Ideally, they should
submitted in ASCII format, as described by section 2a, of RFC-1111.

4. Status

Each RFC must include on its first page the "Status of this Memo
section which contains a paragraph describing the intention of
RFC. This section is meant to convey the status granted by the
Editor and the Internet Activities Board (IAB). There are
reasons for publishing a memo as an RFC, for example, to
available some information for interested people, or to begin
continue a discussion of an interesting idea, or to make
the specification of a protocol

For example

This RFC is the first in a new sub-series of RFCs called FYIs (
Your Information). This memo provides information for the
community. It does not specify any standard. Distribution of
memo is unlimited

5. Distribution

Each FYI is to also include a "distribution statement". As
purpose of the FYI series is to disseminate information, there is
reason for the distribution to be anything other than "unlimited".

Typically, the distribution statement will simply be the
"Distribution of this memo is unlimited." appended to the "Status
this Memo" section

6. Security

All FYIs must contain a section that discusses the
considerations of the procedures that are the main topic of the RFC

7. Author's

Each FYI must have at the very end a section giving the author'
address, including the name and postal address, the telephone number
and the Internet email address






Malkin & Reynolds [Page 2]

RFC 1150 F.Y.I. on F.Y.I. March 1990


8. Relation to other

Sometimes an FYI adds information on a topic discussed in a
FYI or completely replaces an earlier FYI. There are two terms
for these cases respectively, UPDATES and OBSOLETES. A document
obsoletes an earlier document can stand on its own. A document
merely updates an earlier document cannot stand on its own; it
something that must be added to or inserted into the
document, and has limited usefulness independently



To be used as a reference from a new item that cannot be
alone (i.e., one that supplements a previous document), to
to the previous document. The newer publication is a part
will supplement or be added on to the existing document; e.g.,
addendum, or separate, extra information that is to be added
the original document



To be used to refer to an earlier document that is replaced
this document. This document contains either revised information
or else all of the same information plus some new information
however extensive or brief that new information is; i.e.,
document can be used alone, without reference to the
document

OBSOLETED-

To be used to refer to the newer document that replaces the
document

UPDATED-

To be used to refer to the newer document that adds information
the existing, still useful, document

9. The FYI

All FYIs are submitted to the IETF User Services Working Group
review prior to their submission to the RFC Editor

Submissions may be made to







Malkin & Reynolds [Page 3]

RFC 1150 F.Y.I. on F.Y.I. March 1990


Joyce K.
Chair, User Services Working
USC - Information Sciences
4676 Admiralty
Marina del Rey, California 90292-6695

Phone: (213) 822-1511

Electronic mail: JKREY@ISI.

10. The FYI Announcement

New FYIs are announced to the RFC distribution list maintained by
SRI Network Information Center (NIC). Contact the SRI-NIC to
added or deleted from this mailing list by sending an email
to RFC-REQUEST@NIC.DDN.MIL

11. Obtaining

FYIs can be obtained via FTP from NIC.DDN.MIL, with the
FYI:mm.TXT, or RFC:RFCnnnn.TXT (where "mm" refers to the number
the FYI and "nnnn" refers to the number of the RFC). Login with FTP
username ANONYMOUS and password GUEST. The NIC also provides
automatic mail service for those sites which cannot use FTP.
the request to SERVICE@NIC.DDN.MIL and in the subject field of
message indicate the FYI or RFC number, as in "Subject: FYI mm"
"Subject: RFC nnnn".

Security

Security issues are not discussed in this memo

Authors'

Gary Scott
Proteon, Inc
2 Technology
Westborough, MA 01581-5008
Phone: (508) 898-2800
EMail: gmalkin@proteon.

Joyce K.
USC/Information Sciences
4676 Admiralty
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
EMail: jkrey@isi.




Malkin & Reynolds [Page 4]







if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.




RFC documents can be found at I.E.T.F.



Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX







Spectrum