As per Relevance of the word practice, we have this rfc below:
Network Working Group J.
Request for Comments: 1818
BCP: 1 T.
Category: Best Current Practice cisco
Y.
cisco
August 1995
Best Current
Status of this
This document specifies an Internet Best Current Practices for
Internet Community, and requests discussion and suggestions
improvements. Distribution of this memo is unlimited
This document describes a new series of documents which describe
current practices for the Internet community. Documents in
series carry the endorsement of the Internet Engineering
Group (IESG).
The current IETF process has two types of RFCs: standards
documents and other RFCs (e.g., informational, experimental, FYIs
[1]. The intent of the standards track documents is clear,
culminates in an official Internet Standard [2,3].
RFCs can be published on a less formal basis, subject to
reasonable constraints of the RFC editor. Informational RFCs are
subject to peer review and carry no significance whatsoever
the IETF process [4].
The IETF currently has no other mechanism or means of
relevant technical information which it endorses. This
creates a new subseries of RFCs, entitled Best Current
BCPs).
The BCP process is similar to that for proposed standards. The
is submitted to the IESG for review, and the existing review
applies, including a "last call" on the IETF announcement
list. However, once the IESG has approved the document, the
ends and the document is published. The resulting document is
as having the technical approval of the IETF, but it is not,
cannot become an official Internet Standard
Postel, Li & Rekhter Best Current Practice [Page 1]
RFC 1818 Best Current Practices August 1995
Possible examples of technical information to which BCPs could
applied are "OSI NSAP Allocation" [5], and "OSPF
Statement" [6].
[1] IAB, and IESG, "Internet Standards Process -- Revision 2",
1602, IAB and IESG, March 1994.
[2] Postel, J., Editor, "Internet Official Protocol Standards",
1, RFC 1800, IAB, July 1995.
[3] Hinden, R., "Internet Engineering Task Force Internet
Protocol Standardization Criteria", RFC 1264, BBN, October 1991.
[4] Waitzman, D., "Standard for the Transmission of IP Datagrams
Avian Carriers", RFC 1149, BBN, April 1990.
[5] Collela, R., Callon, R., Gardner, E., and Y. Rekhter, "
for OSI NSAP Allocation in the Internet", RFC 1629, NIST
Wellfleet, Mitre, IBM, May 1994.
[6] Chapin, L., "Applicability Statement for OSPF", RFC 1370, IAB
October 1992.
Security
Security issues are not discussed in this memo
Postel, Li & Rekhter Best Current Practice [Page 2]
RFC 1818 Best Current Practices August 1995
Authors'
Jon
USC - ISI, Suite 1001
4676 Admiralty
Marina del Rey, CA 90292-6695
Phone: 310-822-1511
EMail: postel@isi.
Yakov
cisco Systems, Inc
170 West Tasman
San Jose, CA 95134
Phone: 914-528-0090
EMail: yakov@cisco.
Tony
cisco Systems, Inc
1525 O'Brien
Menlo Park, CA 94025
EMail: tli@cisco.
Postel, Li & Rekhter Best Current Practice [Page 3]
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
