idnits 2.17.1 draft-mcdonald-iana-charset-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Unrecognized Status in '[Target Category: Informational RFC - IANA Registry]', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (10 February 2003) is 7718 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2779' is mentioned on line 494, but not defined == Unused Reference: 'RFC2279' is defined on line 538, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'CHARGEN' -- Possible downref: Non-RFC (?) normative reference: ref. 'CHARMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'CHARSET' -- Possible downref: Non-RFC (?) normative reference: ref. 'CHARTEMP' ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) -- Obsolete informational reference (is this intentional?): RFC 1759 (Obsoleted by RFC 3805) -- Duplicate reference: RFC1759, mentioned in 'RFC1759bis', was also mentioned in 'RFC1759'. -- Obsolete informational reference (is this intentional?): RFC 1759 (Obsoleted by RFC 3805) Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Ira McDonald 3 INTERNET DRAFT High North 4 10 February 2003 5 [Target Category: Informational RFC - IANA Registry] 6 Expires: 10 August 2003 8 IANA Charset MIB 9 11 Copyright (C) The Internet Society (2003). All Rights Reserved. 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC 2026. Internet-Drafts are 17 working documents of the Internet Engineering Task Force (IETF), its 18 areas, and its working groups. Note that other groups may also 19 distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 To view the list of Internet-Draft Shadow Directories, see 27 http://www.ietf.org/shadow.html. 29 Abstract 31 This memo defines a portion of the Management Information Base (MIB) 32 for use with network management protocols in the Internet community. 33 This IANA Charset MIB is [intended to become] an IANA registry. In 34 particular, a single textual convention 'IANACharset' is defined that 35 may be used to specify charset labels in MIB objects. 'IANACharset' 36 was extracted from Printer MIB v2 (work-in-progress). 'IANACharset' 37 was originally defined (and mis-named) as 'CodedCharSet' in Printer 38 MIB v1 (RFC 1759). A tool has been written in C, that may be used by 39 IANA to regenerate this IANA Charset MIB, when future charsets are in 40 accordance with the IANA Charset Registration Procedures (RFC 2978). 42 Table of Contents 44 1. Introduction ............................................... 2 45 1.1. Conformance Terminology ................................ 2 46 1.2. Charset Terminology .................................... 3 47 2. The Internet-Standard Management Framework ................. 3 48 3. Generation of IANA Charset MIB ............................. 4 49 4. Definition of IANA Charset MIB ............................. 5 50 5. IANA Considerations ........................................ 12 51 6. Intellectual Property ...................................... 12 52 7. Internationalization Considerations ........................ 12 53 8. Security Considerations .................................... 13 54 9. Acknowledgements ........................................... 13 55 10. Normative References ...................................... 13 56 11. Informative References .................................... 14 57 12. Authors Addresses ......................................... 14 58 13. Full Copyright Statement .................................. 15 59 14. Appendix X - Change Log ................................... 16 61 1. Introduction 63 This IANA Charset MIB [CHARMIB] module defines the single textual 64 convention 'IANACharset'. Once adopted, all future versions of the 65 IANA Charset MIB [CHARMIB] may be machine-generated, whenever the 66 IANA Charset Registry [CHARSET] is updated by IANA staff according to 67 the procedures defined in [RFC2978], using the utility [CHARGEN] 68 described in section 3 of this document or any other 69 machine-generation method. 71 It is strongly recommended that future updates to the IANA Charset 72 MIB [CHARMIB] be machine generated (rather than hand-edited) to avoid 73 asynchrony between the IANA Charset Registry [CHARSET] and the IANA 74 Charset MIB [CHARMIB]. 76 Note: Questions and comments on this IANA Charset MIB [CHARMIB] 77 should be sent to the editor (imcdonald@sharplabs.com) and IANA 78 (iana@iana.org) with a copy to the IETF Charsets mailing list 79 (ietf-charset@iana.org). 81 1.1. Conformance Terminology 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 85 document are to be interpreted as described in RFC 2119 [RFC2119]. 87 1.2. Charset Terminology 89 The following terms are used in this specification, exactly as 90 defined in section 1 'Definitions and Notation' of the IANA Charset 91 Registration Procedures [RFC2978]: "character", "charset", "coded 92 character set (CCS)", and "character encoding scheme (CES)". 94 2. The Internet-Standard Management Framework 96 For a detailed overview of the documents that describe the current 97 Internet-Standard Management Framework, please refer to section 7 of 98 RFC 3410 [RFC3410]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. MIB objects are generally 102 accessed through the Simple Network Management Protocol (SNMP). 103 Objects in the MIB are defined using the mechanisms defined in the 104 Structure of Management Information (SMI). This memo specifies a MIB 105 module that is compliant to the SMIv2, which is described in STD 58, 106 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 107 [RFC2580]. 109 3. Generation of IANA Charset MIB 111 Intellectual Property: The C language utility 'ianachar.c' [CHARGEN] 112 and the IANA Charset MIB template file [CHARTEMP] are hereby donated 113 by the author (Ira McDonald) to IANA, in perpetuity, free of license 114 or any other restraint. 116 The [CHARGEN] utility may be used to generate an updated version of 117 the 'IANACharset' textual convention by reading and parsing the 118 (currently plaintext) IANA Charset Registry [CHARSET]. 120 This utility parses each charset registration, finding (in order): 122 1) The 'Name' field (which is saved for a fallback - see below); 124 2) The 'MIBenum' field (which contains the IANA-assigned positive 125 decimal enum value); and 127 3) The (usually present) 'Alias' field that begins with 'cs' (that 128 contains the IANA-assigned enum label). If an 'Alias' field is 129 not found, the utility constructs one from the 'Name' field by: 131 - Beginning the enum label with a lowercase 'cs' prefix; 133 - Copying _only_ alpha/numeric characters from the 'Name' field 134 to the enum label (ignoring punctuation, whitespace, etc.). 136 4. Definition of IANA Charset MIB 138 IANA-CHARSET-MIB DEFINITIONS ::= BEGIN 139 -- http://www.iana.org/assignments/ianacharset-mib 141 IMPORTS 142 MODULE-IDENTITY, 143 mib-2 144 FROM SNMPv2-SMI 145 TEXTUAL-CONVENTION 146 FROM SNMPv2-TC; 148 ianaCharsetMIB MODULE-IDENTITY 149 LAST-UPDATED "200302100000Z" 150 ORGANIZATION "IANA" 151 CONTACT-INFO " Internet Assigned Numbers Authority 153 Postal: ICANN 154 4676 Admiralty Way, Suite 330 155 Marina del Rey, CA 90292 157 Tel: +1 310 823 9358 158 E-Mail: iana@iana.org" 160 DESCRIPTION "This MIB module defines the IANACharset Textual 161 Convention. The IANACharset TC is used to specify 162 the encoding of string objects defined in a MIB. 164 Each version of this MIB is machine-generated from 165 the IANA Charset Registry file (see RFC 2978) at 166 http://www.iana.org/assignments/character-sets. 168 Note: The IANACharset TC, originally defined in 169 RFC 1759, was inaccurately named CodedCharSet. 171 Note: Best practice is to define new MIB string 172 objects with invariant UTF-8 (RFC 2279) syntax 173 using the SnmpAdminString TC (defined in RFC 3411) 174 in accordance with IETF Policy on Character Sets and 175 Languages (RFC 2277). 177 Copyright (C) The Internet Society (year). This 178 version of this MIB module is part of RFC xxxx; 179 see the RFC itself for full legal notices." 180 -- RFC Editor should assign xxxx and year above. 182 -- revision history 184 REVISION "200302100000Z" -- February 10, 2003 185 DESCRIPTION "Original version transferred from Printer MIB, 186 generated from the IANA maintained assignments 187 http://www.iana.org/assignments/character-sets." 189 -- RFC Editor should regenerate this MIB module 190 -- (using 'ianachar.c' or some other utility) 191 -- immediately prior to publication as an RFC, 192 -- to align with latest IANA charset assignments. 194 ::= { mib-2 nnn } -- nnnn to be assigned by IANA 196 IANACharset ::= TEXTUAL-CONVENTION 197 STATUS current 198 DESCRIPTION 199 "Specifies an IANA registered 'charset' - coded character set 200 (CCS) plus optional character encoding scheme (CES) - terms 201 defined in 'IANA Charset Registration Procedures' (RFC 2978). 203 Objects of this syntax are used to specify the encoding for 204 string objects defined in one or more MIBs. For example, the 205 prtLocalizationCharacterSet, prtInterpreterDefaultCharSetIn, and 206 prtInterpreterDefaultCharSetOut objects defined in Printer MIB. 208 The current list of 'charset' names and enumerated values 209 is contained in the IANA Character Set Registry at: 211 http://www.iana.org/assignments/character-sets 213 Enum names are derived from the IANA Charset Registry 'Alias' 214 fields that begin with 'cs' (for character set). 215 Enum values are derived from the parallel 'MIBenum' fields." 216 SYNTAX INTEGER { 217 other(1), -- used if the designated 218 -- character set is not currently 219 -- registered by IANA 220 unknown(2), -- used as a default value 221 csASCII(3), 222 csISOLatin1(4), 223 csISOLatin2(5), 224 csISOLatin3(6), 225 csISOLatin4(7), 226 csISOLatinCyrillic(8), 227 csISOLatinArabic(9), 228 csISOLatinGreek(10), 229 csISOLatinHebrew(11), 230 csISOLatin5(12), 231 csISOLatin6(13), 232 csISOTextComm(14), 233 csHalfWidthKatakana(15), 234 csShiftJIS(17), 235 csEUCPkdFmtJapanese(18), 236 csEUCFixWidJapanese(19), 237 csISO4UnitedKingdom(20), 238 csISO11SwedishForNames(21), 239 csISO15Italian(22), 240 csISO17Spanish(23), 241 csISO21German(24), 242 csISO60DanishNorwegian(25), 243 csISO69French(26), 244 csISO10646UTF1(27), 245 csISO646basic1983(28), 246 csINVARIANT(29), 247 csISO2IntlRefVersion(30), 248 csNATSSEFI(31), 249 csNATSSEFIADD(32), 250 csNATSDANO(33), 251 csNATSDANOADD(34), 252 csISO10Swedish(35), 253 csKSC56011987(36), 254 csISO2022KR(37), 255 csEUCKR(38), 256 csISO2022JP(39), 257 csISO2022JP2(40), 258 csISO13JISC6220jp(41), 259 csISO14JISC6220ro(42), 260 csISO16Portuguese(43), 261 csISO18Greek7Old(44), 262 csISO19LatinGreek(45), 263 csISO25French(46), 264 csISO27LatinGreek1(47), 265 csISO5427Cyrillic(48), 266 csISO42JISC62261978(49), 267 csISO47BSViewdata(50), 268 csISO49INIS(51), 269 csISO50INIS8(52), 270 csISO51INISCyrillic(53), 271 csISO54271981(54), 272 csISO57GB1988(56), 273 csISO58GB231280(57), 274 csISO61Norwegian2(58), 275 csISO70VideotexSupp1(59), 276 csISO84Portuguese2(60), 277 csISO85Spanish2(61), 278 csISO86Hungarian(62), 279 csISO87JISX0208(63), 280 csISO88Greek7(64), 281 csISO89ASMO449(65), 282 csISO90(66), 283 csISO91JISC62291984a(67), 284 csISO92JISC62991984b(68), 285 csISO93JIS62291984badd(69), 286 csISO94JIS62291984hand(70), 287 csISO95JIS62291984handadd(71), 288 csISO96JISC62291984kana(72), 289 csISO2033(73), 290 csISO99NAPLPS(74), 291 csISO102T617bit(75), 292 csISO103T618bit(76), 293 csISO111ECMACyrillic(77), 294 csa71(78), 295 csa72(79), 296 csISO123CSAZ24341985gr(80), 297 csISO88596E(81), 298 csISO88596I(82), 299 csISO128T101G2(83), 300 csISO88598E(84), 301 csISO88598I(85), 302 csISO139CSN369103(86), 303 csISO141JUSIB1002(87), 304 csISO143IECP271(88), 305 csISO146Serbian(89), 306 csISO147Macedonian(90), 307 csISO150(91), 308 csISO151Cuba(92), 309 csISO6937Add(93), 310 csISO153GOST1976874(94), 311 csISO8859Supp(95), 312 csISO10367Box(96), 313 csISO158Lap(97), 314 csISO159JISX02121990(98), 315 csISO646Danish(99), 316 csUSDK(100), 317 csDKUS(101), 318 csKSC5636(102), 319 csUnicode11UTF7(103), 320 csISO2022CN(104), 321 csUTF8(106), 322 csISO885914(110), 323 csISO885916(112), 324 csGB18030(114), 325 csUnicode(1000), 326 csUCS4(1001), 327 csUnicodeASCII(1002), 328 csUnicodeLatin1(1003), 329 csUnicodeIBM1261(1005), 330 csUnicodeIBM1268(1006), 331 csUnicodeIBM1276(1007), 332 csUnicodeIBM1264(1008), 333 csUnicodeIBM1265(1009), 334 csUnicode11(1010), 335 csSCSU(1011), 336 csUTF16BE(1013), 337 csUTF16(1015), 338 csUTF32(1017), 339 csUTF32LE(1019), 340 csWindows30Latin1(2000), 341 csWindows31Latin1(2001), 342 csWindows31Latin2(2002), 343 csWindows31Latin5(2003), 344 csHPRoman8(2004), 345 csAdobeStandardEncoding(2005), 346 csVenturaUS(2006), 347 csVenturaInternational(2007), 348 csDECMCS(2008), 349 csPC850Multilingual(2009), 350 csPCp852(2010), 351 csPC8CodePage437(2011), 352 csPC8DanishNorwegian(2012), 353 csPC862LatinHebrew(2013), 354 csPC8Turkish(2014), 355 csIBMSymbols(2015), 356 csIBMThai(2016), 357 csHPLegal(2017), 358 csHPPiFont(2018), 359 csHPMath8(2019), 360 csHPPSMath(2020), 361 csHPDesktop(2021), 362 csVenturaMath(2022), 363 csMicrosoftPublishing(2023), 364 csWindows31J(2024), 365 csGB2312(2025), 366 csBig5(2026), 367 csMacintosh(2027), 368 csIBM037(2028), 369 csIBM038(2029), 370 csIBM273(2030), 371 csIBM274(2031), 372 csIBM275(2032), 373 csIBM277(2033), 374 csIBM278(2034), 375 csIBM280(2035), 376 csIBM281(2036), 377 csIBM284(2037), 378 csIBM285(2038), 379 csIBM290(2039), 380 csIBM297(2040), 381 csIBM420(2041), 382 csIBM423(2042), 383 csIBM424(2043), 384 csIBM500(2044), 385 csIBM851(2045), 386 csIBM855(2046), 387 csIBM857(2047), 388 csIBM860(2048), 389 csIBM861(2049), 390 csIBM863(2050), 391 csIBM864(2051), 392 csIBM865(2052), 393 csIBM868(2053), 394 csIBM869(2054), 395 csIBM870(2055), 396 csIBM871(2056), 397 csIBM880(2057), 398 csIBM891(2058), 399 csIBM903(2059), 400 csIBBM904(2060), 401 csIBM905(2061), 402 csIBM918(2062), 403 csIBM1026(2063), 404 csIBMEBCDICATDE(2064), 405 csEBCDICATDEA(2065), 406 csEBCDICCAFR(2066), 407 csEBCDICDKNO(2067), 408 csEBCDICDKNOA(2068), 409 csEBCDICFISE(2069), 410 csEBCDICFISEA(2070), 411 csEBCDICFR(2071), 412 csEBCDICIT(2072), 413 csEBCDICPT(2073), 414 csEBCDICES(2074), 415 csEBCDICESA(2075), 416 csEBCDICESS(2076), 417 csEBCDICUK(2077), 418 csEBCDICUS(2078), 419 csUnknown8BiT(2079), 420 csMnemonic(2080), 421 csMnem(2081), 422 csVISCII(2082), 423 csVIQR(2083), 424 csKOI8R(2084), 425 csIBM866(2086), 426 csPC775Baltic(2087), 427 csKOI8U(2088), 428 csIBM00924(2090), 429 csIBM01141(2092), 430 csIBM01143(2094), 431 csIBM01145(2096), 432 csIBM01147(2098), 433 csIBM01149(2100), 434 csIBM1047(2102), 435 cswindows1250(2250), 436 cswindows1252(2252), 437 cswindows1254(2254), 438 cswindows1256(2256), 439 cswindows1258(2258), 440 reserved(3000) 441 } 442 END 443 5. IANA Considerations 445 IANA should assign a base arc in the 'mgmt' (standards track) OID 446 tree for the 'ianaCharset' MODULE-IDENTITY defined in the IANA 447 Charset MIB [CHARMIB]. 449 Whenever any 'charset' is added to the IANA Charset Registry 450 [CHARSET], a new version of the IANA Charset MIB [CHARMIB] should be 451 machine-generated using the C language utility [CHARGEN] described in 452 section 3 of this document or some other utility. 454 6. Intellectual Property 456 The IETF takes no position regarding the validity or scope of any 457 intellectual property or other rights that might be claimed to 458 pertain to the implementation or use of the technology described in 459 this document or the extent to which any license under such rights 460 might or might not be available; neither does it represent that it 461 has made any effort to identify any such rights. Information on the 462 IETF's procedures with respect to rights in standards-track and 463 standards-related documentation can be found in RFC 2028. Copies of 464 claims of rights made available for publication and any assurances of 465 licenses to be made available, or the result of an attempt made to 466 obtain a general license or permission for the use of such 467 proprietary rights by implementors or users of this specification can 468 be obtained from the IETF Secretariat. 470 The IETF invites any interested party to bring to its attention any 471 copyrights, patents or patent applications, or other proprietary 472 rights which may cover technology that may be required to practice 473 this standard. Please address the information to the IETF Executive 474 Director. 476 7. Internationalization Considerations 478 The IANA Charset MIB [CHARMIB] defines the 'IANACharset' textual 479 convention that may be used in a given MIB module to supply explicit 480 character set labels for one or more text string objects defined in 481 that MIB module. 483 For example, the Printer MIB [RFC1759] defines the three character 484 set label objects 'prtLocalizationCharacterSet' (for description and 485 console strings), 'prtInterpreterDefaultCharSetIn' (for received 486 print job input data), and 'prtIntpreterDefaultCharSetOut' (for 487 processed print job output data). 489 The IANA Charset MIB [CHARMIB] supports implementation of the best 490 practices specified in "IETF Policy on Character Sets and Languages" 491 [RFC2277]. 493 Note: The use of the 'SnmpAdminString' textual convention defined in 494 [RFC3411], which has a fixed character set of UTF-8 [RFC2779], is 495 STRONGLY RECOMMENDED in defining new MIB modules. The IANA Charset 496 MIB [CHARMIB] supports locale-specific MIB objects with variable 497 character sets. 499 8. Security Considerations 501 This MIB module does not define any management objects. Instead, it 502 defines a (set of) textual convention(s) which may be used by other 503 MIB modules to define management objects. 505 Meaningful security considerations can only be written in the MIB 506 modules that define management objects. This document has therefore 507 no impact on the security of the Internet. 509 9. Acknowledgements 511 The editor would like to thank: Bert Wijnen (Lucent) for his 512 original suggestion that the 'IANACharset' textual convention should 513 be extracted from Printer MIB v2 (work-in-progress) [RFC1759bis]; Ron 514 Bergman (Hitachi Printing Solutions) and Harry Lewis (IBM) for their 515 many years of effort as editors of Printer MIB v2 (work-in-progress) 516 [RFC1759bis]. 518 10. Normative References 520 [CHARGEN] IANA Charset MIB Generation Utility (archived at): 521 http://www.pwg.org/pub/pwg/pmp/tools/ianachar.c 523 [CHARMIB] IANA Charset MIB (in the future, to be archived at): 524 http://www.iana.org/assignments/ianacharset-mib 526 [CHARSET] IANA Charset Registry (archived at): 527 http://www.iana.org/assignments/character-sets 529 [CHARTEMP] IANA Charset MIB template file (archived at): 530 http://www.pwg.org/pub/pwg/pmp/tools/ianachar.dat 532 [RFC2119] Bradner. "Key words for use in RFCs to Indicate 533 Requirement Levels", RFC 2119, March 1997. 535 [RFC2277] Alvestrand. "IETF Policy on Character Sets and Languages", 536 RFC 2277, January 1998. 538 [RFC2279] Yergeau. "UTF-8, a Transformation of ISO 10646", RFC 2279, 539 January 1998. 541 [RFC2578] McCloghrie, Perkins, Schoenwaelder, Case, Rose, Waldbusser. 542 "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 543 2578, April 1999. 545 [RFC2579] McCloghrie, Perkins, Schoenwaelder, Case, Rose, Waldbusser. 546 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. 548 [RFC2580] McCloghrie, Perkins, Schoenwaelder, Case, Rose, Waldbusser. 549 "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. 551 [RFC2978] Freed, Postel. "IANA Charset Registration Procedures", RFC 552 2978, October 2000. 554 [RFC3411] Wijnen, Harrington, Presuhn. "An Architecture for 555 Describing SNMP Network Management Frameworks", STD 62, RFC 3411, 556 December 2002. 558 11. Informative References 560 [RFC1759] Smith, Wright, Hastings, Zilles, Gyllenskog. "Printer 561 MIB", RFC 1759, March 1995. 563 [RFC1759bis] Bergman, Lewis, McDonald. "Printer MIB v2" 564 (work-in-progress), , February 565 2003. 567 [RFC3410] Case, Mundy, Partain, Stewart. "Introduction and 568 Applicability Statements for Internet-Standard Network Management 569 Framework", RFC 3410, December 2002. 571 12. Authors Addresses 573 Editor: Ira McDonald 574 Postal: High North Inc 575 221 Ridge Ave 576 Grand Marais, MI 49839 577 USA 578 Tel: +1 906 494 2434 579 Email: imcdonald@sharplabs.com 580 IANA: Internet Assigned Numbers Authority 581 Postal: ICANN 582 4676 Admiralty Way, Suite 330 583 Marina del Rey, CA 90292 584 USA 585 Tel: +1 310 823 9358 586 Email: iana@iana.org 588 Note: Questions and comments on this IANA Charset MIB [CHARMIB] 589 should be sent to the editor (imcdonald@sharplabs.com) and IANA 590 (iana@iana.org) with a copy to the IETF Charsets mailing list 591 (ietf-charset@iana.org). 593 13. Full Copyright Statement 595 Copyright (C) The Internet Society (2003). All Rights Reserved. 597 This document and translations of it may be copied and furnished to 598 others, and derivative works that comment on or otherwise explain it 599 or assist in its implementation may be prepared, copied, published 600 and distributed, in whole or in part, without restriction of any 601 kind, provided that the above copyright notice and this paragraph are 602 included on all such copies and derivative works. However, this 603 document itself may not be modified in any way, such as by removing 604 the copyright notice or references to the Internet Society or other 605 Internet organizations, except as needed for the purpose of 606 developing Internet standards in which case the procedures for 607 copyrights defined in the Internet Standards process must be 608 followed, or as required to translate it into languages other than 609 English. 611 The limited permissions granted above are perpetual and will not be 612 revoked by the Internet Society or its successors or assigns. 614 This document and the information contained herein is provided on an 615 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 616 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 617 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 618 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 619 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 621 14. Appendix X - Change Log 623 [[RFC Editor - delete this section before publication as an RFC]] 625 (10 February 2003) 626 * Added section 1.2 'Charset Terminology', for clarity. 627 * Replaced section 2 'The Internet-Standard Management Framework' 628 with new MIB boilerplate, per request of Bert Wijnen. 629 * Revised section 5 'IANA Considerations', to clarify that IANA MAY 630 use the supplied IANA Charset MIB generation tool, or any other 631 method. 632 * Added section 6 'Intellectual Property', per request of Bert 633 Wijnen. 634 * Replaced section 8 'Security Considerations' with new text, written 635 by Bert Wijnen. 636 * Revised section 10 'Normative References' and section 11 637 'Informative References' to correct SNMPv3 references to RFC 638 3410/3411, per request of Bert Wijnen. 639 * Added section 14 'Appendix X - Change Log', to be deleted before 640 publication as an RFC. 641 * Revised MODULE-IDENTITY in IANA Charset MIB template file, renaming 642 from 'ianaCharset' to 'ianaCharsetMIB', revising DESCRIPTION clause 643 to add MIB copyright, revising REVISION clause to state that the 644 MIB was machine generated from the IANA Charset Registry (with 645 durable URL), and changing OID from 'mib-2 999' to 'mib-2 nnn', per 646 request of Bert Wijnen. 648 (8 October 2002) 649 * Revised Abstract and Introduction, to clarify that IANA MAY use the 650 supplied IANA Charset MIB generation tool, or any other method. 651 * Revised MODULE-IDENTITY in IANA Charset MIB template file to add 652 full IANA address to CONTACT-INFO clause and expanded DESCRIPTION 653 clause. 654 * Renamed textual convention from CodedCharSet (an inaccurate name) 655 to IANACharset, per request of David Hopwood. 657 (5 August 2002) 658 * Initial version, extracted from Printer MIB v2, at the suggestion 659 of Bert Wijnen, with the concurrence (by email) of Ned Freed and 660 Patrik Faltstrom. 661 * Released required IANA Charset MIB generation C utility program.