smilint output for ./LANGTAG-TC-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-TC-MIB

   1: -- extracted from draft-mcwalter-langtag-mib-03.txt
   2: -- at Fri Mar 23 06:22:29 2007

   3: 
   4: LANGTAG-TC-MIB DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:     MODULE-IDENTITY, mib-2             FROM SNMPv2-SMI      -- [RFC2578]
   8:     TEXTUAL-CONVENTION                 FROM SNMPv2-TC;      -- [RFC2579]
   9: 
  10: langTagTcMIB MODULE-IDENTITY
  11:     LAST-UPDATED "200703200000Z" -- 20 March 2007
  12:     ORGANIZATION "IETF Operations and Management (OPS) Area"
  13:     CONTACT-INFO "EMail: ops-area@ietf.org
  14:                   Home page: http://www.ops.ietf.org/"
  15:     DESCRIPTION
  16:             "This MIB module defines a textual convention for
  17:             representing BCP 47 language tags."
  18:     REVISION     "200703200000Z" -- 20 March 2007
  19:     DESCRIPTION
  20:            "Initial revision, published as RFC yyyy.
  21: 
  22:             Copyright (C) The IETF Trust (2007).  This version of this
  23:             MIB module is part of RFC yyyy; see the RFC itself for full
  24:             legal notices."
  25: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
  26:     ::= { mib-2 XXX }

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

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

29: warning - warning: current type `LangTag' is not referenced in this module

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