RFC 4706: Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)
In plain English — editorial summary, not part of the RFC
This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing parameters of the "Asymmetric Digital Subscriber Line" family of interface types: ADSL, ADSL2, ADSL2+, and their variants. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4706
- Published
- November 2006
- Authors
- M. Morgenstern; M. Dodge; S. Baillie; U. Bonollo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 167
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4560Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsCurrent
June 2006
- RFC 4363Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN ExtensionsCurrent
January 2006
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- 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 4188Definitions of Managed Objects for BridgesCurrent
September 2005
- RFC 4149Definition of Managed Objects for Synthetic Sources for Performance Monitoring AlgorithmsCurrent
August 2005
- RFC 4070Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line CodingCurrent
May 2005
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?