metasystema.org
ObsoletedHISTORICLegacy stream

RFC 1871: Addendum to RFC 1602 -- Variance Procedure

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2026.

Current document in this lineage: RFC 2026 — The Internet Standards Process -- Revision 3

In plain English — editorial summary, not part of the RFC

This document describes a modification to the IETF procedures to allow an escape from a situation where the existing procedures are not working or do not seem to apply. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC1871
Published
November 1995
Authors
J. Postel
Status
HISTORIC
Stream
Legacy
Area
—
Pages
4
Also known as
—
Obsoleted by:
RFC 2026
Updates:
RFC 1602, RFC 1603

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 1310 (1992)
  2. RFC 1602 (1994)
  3. RFC 1871 (1995)
  4. RFC 2026 (1996) ✓

Read the full history of The Internet Standards Process -- Revision 3 →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/1871-addendum-to-rfc-1602-variance-procedure