As per Relevance of the word document, we have this rfc below:
Network Working Group Internet Activities
Request for Comments: 1311 J. Postel,
March 1992
Introduction to the STD
Status of this
This RFC describes a new sub-series of RFCs, called STDs (Standards).
Distribution of this memo is unlimited
1.
The STDs are a subseries of notes within the RFC series that are
Internet standards. The intent is to identify clearly for
Internet community those RFCs which document Internet standards
2. The Assignment of STD
There is a need to be very clear about which specifications
completed the full process of standardization in the Internet. To
this an STD number will be assigned to a specification when
reaches the Standard maturity level. Note that specifications may
either Technical Specifications (TS) or Applicability
(AS).
When a specification reaches the final stage of the
process and the IAB has designated it a standard for the Internet,
STD number will be assigned to that specification
The existing standards have been assigned STD numbers (see Appendix).
The standard for a particular protocol will always have the same
number
If at some future time a protocol is reworked and a new
is produced as the specification of that standard and the
specification is designated by the IAB as a standard for
Internet, then the new document will be labeled with the same
number (of course, that new document will have a new RFC number).
Multiple Documents for One Standard
A STD number identifies a standard not a document. A document
identified by its RFC number. If the specification of a
is spread over several documents they will each carry the same
number
Internet Activities Board [Page 1]
RFC 1311 RFC on STD RFCs March 1992
For example, the Domain Name System (DNS) is
specified by the combination of RFCs 1034 and 1035. Both
these documents are now labeled STD-13.
To be completely clear the DNS "Concepts and Facilities
document can be referenced as "STD-13/RFC-1034".
In such cases, whenever possible, the set of documents defining
particular standard will cross reference each other
One Standard or Multiple Standards
One difficult decision is deciding whether a set of
describe one standard or multiple standards. In the Appendix,
can see that there are several cases in which one STD applies
multiple RFCs (see STDs 5, 13, and 20). There is one case
which a family of specifications has multiple STD numbers; that
the Telnet Options
The general rule is that a separate STD number is used when
specification is logically separable. That is,
separable options are assigned distinct STD numbers
amendments and non-optional extensions use the same STD number
the base specification
Multiple Versions or Editions of a Standard
It may occur that the documentation of a standard is updated
replaced with a new document. In such cases, the same STD
will be used to label the standard. No version numbers will
attached to STD numbers. There need be no confusion about
the up-to-date document about STD-9 since each version of
document will have a distinct RFC number (and of course
different date).
The complete identification of a specification and its document
the combination of the STD and the RFC. For example, "STD-13/RFC
1035" completely identifies the current version of the second part
the Domain Name System specification
To completely identify all of the DNS standard the citation
be "STD-13/RFC-1034/RFC-1035".
One way to think of this is that an acronym (like TCP) refers to
concept, which is called a protocol. An RFC number (like RFC-793)
indicates the specific version of the protocol specification. An
number (like STD-7) designates the status of the protocol
Internet Activities Board [Page 2]
RFC 1311 RFC on STD RFCs March 1992
2. Why an RFC Subseries ?
There are several reasons why the STDs are part of the larger
series of notes
The foremost reason is that the distribution mechanisms for RFCs
tried and true. Anyone who can get an RFC, can automatically get
STD. More important, anyone who knows of the RFC series can
find the STDs
Another reason for making STDs part of the RFC series is that
maintenance mechanisms for RFCs are already in place. It makes
to maintain similar documents is a similar way
3. Format
Since the STDs are a part of the RFC series, they must conform
"Request for Comments on Request for Comments: Instructions to
Authors" (RFC-1111) with respect to format
3.1 Status
Each STD 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 approved by
Internet Activities Board (IAB).
3.2. Distribution
Each STD RFC will also include a "distribution statement". As
purpose of the STD 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
3.3. Security
All STD RFCs must contain a section that discusses the
considerations of the procedures that are the main topic of the RFC
3.4. Author's
Each STD RFC 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
Internet Activities Board [Page 3]
RFC 1311 RFC on STD RFCs March 1992
In the case of multiple authors, each of the authors will be listed
In the case of a document produced by a group, the editor of
document will be listed and optionally the chair of the group may
listed
4. The STD
New documents can only become STD RFCs through an action of the IAB
The publication of STDs will be performed by the RFC Editor
5. STD
New STD RFCs are announced to the RFC distribution list maintained
the Network Information Center (NIC). Contact the NIC to be added
deleted from this mailing list by sending an email message to RFC
REQUEST@NIC.DDN.MIL
6. Obtaining
STD RFCs may be obtained in the same way as any RFC
Details on obtaining RFCs via FTP or EMAIL may be obtained by
an EMAIL message to "rfc-info@ISI.EDU" with the message body "help
ways_to_get_rfcs". For example
To: rfc-info@ISI.
Subject: getting
help: ways_to_get_
The current standards are listed in the "IAB Official
Standards" (which is STD-1), whose current edition is RFC-1280.
Security
Security issues are not discussed in this memo
Author's
Jon
USC/Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: 310-822-1511
Fax: 310-823-6714
Email: Postel@ISI.
Internet Activities Board [Page 4]
RFC 1311 RFC on STD RFCs March 1992
APPENDIX -- The Grandfathered
Protocol Name Status RFC
======== ===================================== ======= ===== ====
-------- IAB Official Protocol Standards Req 1280 1
-------- Assigned Numbers Req 1060 2
-------- Host Requirements Req 1122,1123 3
-------- Gateway Requirements Req 1009 4
IP Internet Protocol Req 791 5
as amended by
-------- IP Subnet Extension Req 950 5
-------- IP Broadcast Datagrams Req 919 5
-------- IP Broadcast Datagrams with Subnets Req 922 5
ICMP Internet Control Message Protocol Req 792 5
IGMP Internet Group Multicast Protocol Rec 1112 5
UDP User Datagram Protocol Rec 768 6
TCP Transmission Control Protocol Rec 793 7
TELNET Telnet Protocol Rec 854,855 8
FTP File Transfer Protocol Rec 959 9
SMTP Simple Mail Transfer Protocol Rec 821 10
MAIL Format of Electronic Mail Messages Rec 822 11
CONTENT Content Type Header Field Rec 1049 11
NTP Network Time Protocol Rec 1119 12
DOMAIN Domain Name System Rec 1034,1035 13
DNS-MX Mail Routing and the Domain System Rec 974 14
SNMP Simple Network Management Protocol Rec 1157 15
SMI Structure of Management Information Rec 1155 16
MIB-II Management Information Base-II Rec 1213 17
EGP Exterior Gateway Protocol Rec 904 18
NETBIOS NetBIOS Service Protocols Ele 1001,1002 19
ECHO Echo Protocol Rec 862 20
DISCARD Discard Protocol Ele 863 21
CHARGEN Character Generator Protocol Ele 864 22
QUOTE Quote of the Day Protocol Ele 865 23
USERS Active Users Protocol Ele 866 24
DAYTIME Daytime Protocol Ele 867 25
TIME Time Server Protocol Ele 868 26
Telnet Options Option Status RFC
======== ================================= ====== ======= ===== ====
TOPT-BIN Binary Transmission 0 Rec 856 27
TOPT-ECHO Echo 1 Rec 857 28
TOPT-SUPP Suppress Go Ahead 3 Rec 858 29
TOPT-STAT Status 5 Rec 859 30
TOPT-TIM Timing Mark 6 Rec 860 31
TOPT-EXTOP Extended-Options-List 255 Rec 861 32
Internet Activities Board [Page 5]
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
