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 will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4001
- Published
- March 2005
- Authors
- M. Daniele; B. Haberman; S. Routhier; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 22
- Also known as
- —
- Obsoletes:
- 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 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4008Definitions of Managed Objects for Network Address Translators (NAT)Obsoleted
March 2005
- RFC 4069Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line CodingCurrent
May 2005
- RFC 4070Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line CodingCurrent
May 2005
- RFC 3895Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface TypesObsoleted
September 2004
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 3878Alarm Reporting Control Management Information Base (MIB)Current
September 2004
- RFC 3873Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)Current
September 2004
- RFC 3872Management Information Base for Telephony Routing over IP (TRIP)Current
September 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?