RFC 3291: 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 4001.
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. The intent is that these textual conventions (TCs) will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3291
- Published
- May 2002
- Authors
- M. Daniele; B. Haberman; S. Routhier; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
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 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 3287Remote Monitoring MIB Extensions for Differentiated ServicesCurrent
July 2002
- RFC 3273Remote Network Monitoring Management Information Base for High Capacity NetworksUpdated
July 2002
- RFC 3231Definitions of Managed Objects for Scheduling Management OperationsCurrent
January 2002
- RFC 3414User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)Updated
December 2002
- RFC 3415View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)Current
December 2002
- RFC 3165Definitions of Managed Objects for the Delegation of Management ScriptsCurrent
August 2001
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
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?