Skip to main content

Textual Conventions for Internet Network Addresses

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3291.
Authors Mike Daniele , Jürgen Schönwälder , Brian Haberman , Shawn A. Routhier
Last updated 2013-03-02 (Latest revision 2001-12-17)
RFC stream Internet Engineering Task Force (IETF)
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3291 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3291

        Title:      Textual Conventions for Internet Network Addresses
        Author(s):  M. Daniele, B. Haberman, S. Routhier,
                    J. Schoenwaelder 
        Status:     Standards Track
        Date:       May 2002
        Pages:      20
        Characters: 43564
        Obsoletes:  2851

        I-D Tag:    draft-ietf-ops-rfc2851-update-06.txt


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.

This document obsoletes RFC 2851.

This document is a product of the Operations and Management Open Area
Working Group of the IETF. 

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.