[Search] [pdfized|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: 01 02 03 04 05 rfc3419                         Standards Track
A new Request for Comments is now available in online RFC libraries.

        RFC 3419

        Title:      Textual Conventions for Transport Addresses
        Author(s):  M. Daniele, J. Schoenwaelder
        Status:     Standards Track
        Date:       December 2002
        Mailbox:    md@world.std.com, schoenw@ibr.cs.tu-bs.de
        Pages:      18
        Characters: 37466
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ops-taddress-mib-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3419.txt

This document introduces a Management Information Base (MIB) module
that defines textual conventions to represent commonly used
transport-layer addressing information.  The definitions are
compatible with the concept of TAddress/TDomain pairs introduced by
the Structure of Management Information version 2 (SMIv2) and support
the Internet transport protocols over IPv4 and IPv6.

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.