RFC 2360: Guide for Internet Standards Writers
In plain English — editorial summary, not part of the RFC
This document is a guide for Internet standard writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2360
- Published
- June 1998
- Authors
- G. Scott
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- usv
- Pages
- 20
- Also known as
- BCP22
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2434Guidelines for Writing an IANA Considerations Section in RFCsObsoleted
October 1998
- RFC 2262Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)Obsoleted
January 1998
- RFC 2572Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)Obsoleted
April 1999
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- RFC 1662PPP in HDLC-like FramingCurrent
July 1994
- RFC 1661The Point-to-Point Protocol (PPP)Updated
July 1994
- RFC 3412Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)Updated
December 2002
- RFC 3692Assigning Experimental and Testing Numbers Considered UsefulCurrent
January 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?