RFC 4070: Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding
In plain English — editorial summary, not part of the RFC
This document defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing the Line Code Specific parameters of Very High Speed Digital Subscriber Line (VDSL) interfaces using Multiple Carrier Modulation (MCM) Line Coding. It is an optional extension to the VDSL-LINE-MIB, RFC 3728, which handles line code independent objects. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4070
- Published
- May 2005
- Authors
- M. Dodge; B. Ray
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4069Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line CodingCurrent
May 2005
- RFC 4149Definition of Managed Objects for Synthetic Sources for Performance Monitoring AlgorithmsCurrent
August 2005
- RFC 4188Definitions of Managed Objects for BridgesCurrent
September 2005
- RFC 3895Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface TypesObsoleted
September 2004
- RFC 3878Alarm Reporting Control Management Information Base (MIB)Current
September 2004
- RFC 4319Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) LinesCurrent
December 2005
- RFC 4363Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN ExtensionsCurrent
January 2006
- RFC 3747The Differentiated Services Configuration MIBCurrent
April 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?