smilint output for ./LANGTAG-MIB

Message Severities
Severity	Count
error	2
warning	1

Message Types
Type	Count
bad-identifier-case (error)	1
object-identifier-not-prefix (error)	1
type-unref (warning)	1

Messages:

LANGTAG-MIB

   1: -- extracted from draft-mcwalter-langtag-mib-01.txt
   2: -- at Mon Nov 27 06:07:28 2006

   3: 
   4: LANGTAG-MIB DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:     MODULE-IDENTITY, mib-2             FROM SNMPv2-SMI
   8:     TEXTUAL-CONVENTION                 FROM SNMPv2-TC;
   9: 
  10: langTagMIB MODULE-IDENTITY
  11:     LAST-UPDATED "200611210000Z" -- 21 November 2006
  12:     ORGANIZATION "IETF Operations and Management Area"
  13:     CONTACT-INFO "EMail: ops-area@ietf.org"
  14:     DESCRIPTION
  15:             "This MIB module defines a textual conventions for
  16:             representing BCP 47 language tags."
  17:     REVISION     "200611210000Z" -- 21 November 2006
  18:     DESCRIPTION
  19:            "Initial revision, published as RFC yyyy.
  20: 
  21:             Copyright (C) The IETF Trust (2006).  The initial version of
  22:             this MIB module was published in RFC yyyy; for full legal
  23:             notices see the RFC itself.  Supplementary information may
  24:             be available at:
  25:             http://www.ietf.org/copyrights/ianamib.html."
  26: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
  27:     ::= { mib-2 XXX }

27: error - `XXX' should start with a lower case letter
27: error - Object identifier element `XXX' name only allowed as first element

  28: -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
  29: 
  30: LanguageTag ::= TEXTUAL-CONVENTION

30: warning - warning: current type `LanguageTag' is not referenced in this module

  31:    DISPLAY-HINT "60a"
  32:    STATUS      current
  33:    DESCRIPTION
  34:             "A language tag, constructed in accordance with BCP 47.
  35: 
  36:             Only lowercase characters are allowed.  The purpose of this
  37:             restriction is to provide unique language tags for use as
  38:             indexes.  BCP 47 recommends case conventions for user
  39:             interfaces, but objects using this textual convention MUST
  40:             use only lowercase.
  41: 
  42:             Values MUST be well-formed language tags, in conformance
  43:             with the definition of well-formed tags in BCP 47.  An
  44:             implementation MAY further limit the values it accepts to
  45:             those permitted by a 'validating' processor, as defined in
  46:             BCP 47.
  47: 
  48:             In theory, BCP 47 language tags are of unlimited length.
  49:             This language tag is of limited length.  The analysis of
  50:             language tag lengths in BCP 47 confirms that this limit
  51:             will not pose a problem in practice.  In particular, this
  52:             length is greater than the minimum requirements set out in
  53:             section 4.3.1."
  54:    REFERENCE "RFC 4646 BCP 47"
  55:    SYNTAX      OCTET STRING (SIZE (0..60))
  56: 
  57: END
  58: 
  59: -- 
  60: --    Copyright (C) The IETF Trust (2006).  This document is subject to the
  61: --    rights, licenses and restrictions contained in BCP 78, and except as
  62: --    set forth therein, the authors retain all their rights.
  63: -- 
  64: -- 
  65: -- Acknowledgment
  66: -- 
  67: --    Funding for the RFC Editor function is currently provided by the
  68: --    Internet Society.
  69: