RFC 3419: Textual Conventions for Transport Addresses
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3419
- Published
- December 2002
- Authors
- M. Daniele; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3970A Traffic Engineering (TE) MIBUpdated
January 2005
- RFC 2790Host Resources MIBCurrent
March 2000
- RFC 2786Diffie-Helman USM Key Management Information Base and Textual ConventionCurrent
March 2000
- RFC 2758Definitions of Managed Objects for Service Level Agreements Performance MonitoringCurrent
February 2000
- RFC 2417Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksCurrent
September 1998
- RFC 3415View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)Current
December 2002
- RFC 3414User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)Updated
December 2002
- 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?