RFC 3808: IANA Charset MIB
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This IANA Charset MIB is now an IANA registry. In particular, a single textual convention 'IANACharset' is defined that may be used to specify charset labels in MIB objects. 'IANACharset' was extracted from Printer MIB v2 (RFC 3805). 'IANACharset' was originally defined (and mis-named) as 'CodedCharSet' in Printer MIB v1 (RFC 1759). A tool has been written in C, that may be used by IANA to regenerate this IANA Charset MIB, when future charsets are registered in accordance with the IANA Charset Registration Procedures (RFC 2978). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3808
- Published
- June 2004
- Authors
- I. McDonald
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4498The Managed Object Aggregation MIBCurrent
May 2006
- RFC 3811Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) ManagementUpdated
June 2004
- RFC 3805Printer MIB v2Current
June 2004
- RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current
June 2004
- RFC 3814Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)Current
June 2004
- RFC 3816Definitions of Managed Objects for RObust Header Compression (ROHC)Current
June 2004
- RFC 3826The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security ModelCurrent
June 2004
- 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?