RFC 2856: Textual Conventions for Additional High Capacity Data Types
In plain English — editorial summary, not part of the RFC
This memo specifies new textual conventions for additional high capacity data types, intended for SNMP implementations which already support the Counter64 data type. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2856
- Published
- June 2000
- Authors
- A. Bierman; K. McCloghrie; R. Presuhn
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2578Structure of Management Information Version 2 (SMIv2)Current
April 1999
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 2741Agent Extensibility (AgentX) Protocol Version 1Current
January 2000
- RFC 3159Structure of Policy Provisioning Information (SPPI)Current
August 2001
- RFC 3430Simple Network Management Protocol Over Transmission Control Protocol Transport MappingCurrent
December 2002
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3440Definitions of Extension Managed Objects for Asymmetric Digital Subscriber LinesCurrent
January 2003
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?