IANA Charset MIB
RFC 3808

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 02

Network Working Group                                        I. McDonald
Request for Comments: 3808                                    High North
Category: Informational                                        June 2004

                            IANA Charset MIB

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   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).

Table of Contents

   1.  Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   2
       1.1.  Conformance Terminology . . . . . . . . . . . . . . . .   2
       1.2.  Charset Terminology . . . . . . . . . . . . . . . . . .   2
   2.  The Internet-Standard Management Framework. . . . . . . . . .   2
   3.  Generation of IANA Charset MIB. . . . . . . . . . . . . . . .   3
   4.  Definition of IANA Charset MIB. . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Internationalization Considerations . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgements. . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References. . . . . . . . . . . . . . . . . . . . . . . . . .  11
       9.1.  Normative References. . . . . . . . . . . . . . . . . .  11
       9.2.  Informative References. . . . . . . . . . . . . . . . .  12
   10. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . .  13
   11. Full Copyright Statement. . . . . . . . . . . . . . . . . . .  14

McDonald                     Informational                      [Page 1]
RFC 3808                    IANA Charset MIB                   June 2004

1.  Introduction

   This IANA Charset MIB [CHARMIB] module defines the single textual
   convention 'IANACharset'.  Once adopted, all future versions of the
   IANA Charset MIB [CHARMIB] may be machine-generated whenever the IANA
   Charset Registry [CHARSET] is updated by IANA staff according to the
   procedures defined in [RFC2978], using the utility [CHARGEN]
   described in section 3 of this document or any other machine-
   generation method.

   It is strongly recommended that future updates to the IANA Charset
   MIB [CHARMIB] be machine-generated (rather than hand-edited) to avoid
   asynchrony between the IANA Charset Registry [CHARSET] and the IANA
   Charset MIB [CHARMIB].

   Note:  Questions and comments on this IANA Charset MIB [CHARMIB]
   should be sent to the editor (imcdonald@sharplabs.com) and IANA
   (iana@iana.org) with a copy to the IETF Charsets mailing list (ietf-
   charset@iana.org).

1.1.  Conformance Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

1.2.  Charset Terminology

   The following terms are used in this specification, exactly as
   defined in section 1 'Definitions and Notation' of the IANA Charset
   Registration Procedures [RFC2978]:  "character", "charset", "coded
   character set (CCS)", and "character encoding scheme (CES)".

2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580
   [RFC2580].

McDonald                     Informational                      [Page 2]
RFC 3808                    IANA Charset MIB                   June 2004

3.  Generation of IANA Charset MIB

   Intellectual Property:  The C language utility 'ianachar.c' [CHARGEN]
   and the IANA Charset MIB template file [CHARTEMP] are hereby donated