RFC 2851: Textual Conventions for Internet Network Addresses
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3291.
Current document in this lineage: RFC 4001 — Textual Conventions for Internet Network Addresses
In plain English — editorial summary, not part of the RFC
This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2851
- Published
- June 2000
- Authors
- M. Daniele; B. Haberman; S. Routhier; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 16
- Also known as
- —
- Obsoleted by:
- RFC 3291
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2851 (2000)
- RFC 3291 (2002)
- RFC 4001 (2005) ✓
Read the full history of Textual Conventions for Internet Network Addresses →
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.
- RFC 2593Script MIB Extensibility Protocol Version 1.0Obsoleted
May 1999
- RFC 3176InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed NetworksCurrent
September 2001
- RFC 2039Applicability of Standards Track MIBs to Management of World Wide Web ServersCurrent
November 1996
- RFC 1792TCP/IPX Connection Mib SpecificationCurrent
April 1995
- RFC 1748IEEE 802.5 MIB using SMIv2Updated
December 1994
- RFC 2837Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardObsoleted
May 2000
- RFC 2896Remote Network Monitoring MIB Protocol Identifier MacrosCurrent
August 2000
- RFC 2922Physical Topology MIBCurrent
September 2000
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?