smilint output for ./SSHSM-MIB

Messages:

SSHSM-MIB

   1: -- extracted from draft-ietf-isms-secshell-04.txt
   2: -- at Wed Jun 28 06:06:35 2006

   3: 
   4:    SSHSM-MIB DEFINITIONS ::= BEGIN
   5: 
   6:    IMPORTS
   7:        MODULE-IDENTITY, OBJECT-TYPE,

   8:        OBJECT-IDENTITY, mib-2, Counter32, Integer32

   9:          FROM SNMPv2-SMI
  10:        TestAndIncr, AutonomousType

  11:          FROM SNMPv2-TC
  12:        MODULE-COMPLIANCE, OBJECT-GROUP
  13:          FROM SNMPv2-CONF
  14:        SnmpAdminString,  SnmpSecurityLevel, SnmpEngineID

  15:           FROM SNMP-FRAMEWORK-MIB
  16:        TransportAddress, TransportAddressType

  17:          FROM TRANSPORT-ADDRESS-MIB
  18:        ;
  19: 
  20:    sshsmMIB MODULE-IDENTITY
  21:        LAST-UPDATED "200509020000Z"
  22:        ORGANIZATION "ISMS Working Group"
  23:        CONTACT-INFO "WG-EMail:   isms@lists.ietf.org
  24:                      Subscribe:  isms-request@lists.ietf.org
  25: 
  26:                   Chairs:
  27:                     Juergen Quittek
  28:                     NEC Europe Ltd.
  29:                     Network Laboratories
  30:                     Kurfuersten-Anlage 36
  31:                     69115 Heidelberg
  32:                     Germany
  33:                     +49 6221 90511-15
  34:                      quittek@netlab.nec.de
  35: 
  36:                      Juergen Schoenwaelder
  37:                      International University Bremen
  38:                      Campus Ring 1
  39:                      28725 Bremen
  40:                      Germany
  41:                      +49 421 200-3587
  42:                      j.schoenwaelder@iu-bremen.de
  43: 
  44:                   Co-editors:
  45:                      David Harrington
  46:                      Effective Software
  47:                      50 Harding Rd
  48:                      Portsmouth, New Hampshire 03801
  49:                      USA
  50:                      +1 603-436-8634
  51:                      ietfdbh@comcast.net
  52: 
  53:                      Joseph Salowey
  54:                      Cisco Systems
  55:                      2901 3rd Ave
  56:                      Seattle, WA 98121
  57:                      USA
  58:                      jsalowey@cisco.com
  59:                        "
  60:           DESCRIPTION  "The Secure Shell Security Model MIB
  61: 
  62:                         Copyright (C) The Internet Society (2006). This
  63:                         version of this MIB module is part of RFC XXXX;
  64:                         see the RFC itself for full legal notices.
  65:    -- NOTE to RFC editor: replace XXXX with actual RFC number
  66:    --                     for this document and remove this note
  67:                        "
  68: 
  69:           REVISION     "200509020000Z"         -- 02 September 2005
  70:           DESCRIPTION  "The initial version, published in RFC XXXX.
  71:    -- NOTE to RFC editor: replace XXXX with actual RFC number
  72:    --                     for this document and remove this note
  73:                        "
  74: 
  75:        ::= { mib-2 xxxx }

  76:    -- RFC Ed.: replace xxxx with IANA-assigned number and
  77:    --          remove this note
  78:    -- ---------------------------------------------------------- --
  79:    -- subtrees in the SSHSM-MIB
  80:    -- ---------------------------------------------------------- --
  81: 
  82:    sshsmNotifications OBJECT IDENTIFIER ::= { sshsmMIB 0 }
  83:    sshsmObjects       OBJECT IDENTIFIER ::= { sshsmMIB 1 }
  84:    sshsmConformance   OBJECT IDENTIFIER ::= { sshsmMIB 2 }
  85: 
  86:    -- -------------------------------------------------------------
  87:    -- Objects
  88:    -- -------------------------------------------------------------
  89: 
  90:    TransportAddressSSH ::= TEXTUAL-CONVENTION

  91:        DISPLAY-HINT "1a"
  92:        STATUS      current
  93:        DESCRIPTION
  94:            "Represents either a hostname encoded in ASCII
  95:            using the IDNA protocol, as specified in RFC3490, followed by
  96:            a colon ':' (ASCII character 0x3A) and a decimal port number
  97:            in ASCII, or an IP address followed by a colon ':'
  98:            (ASCII character 0x3A) and a decimal port number in ASCII.
  99:             The name SHOULD be fully qualified whenever possible.
 100: 
 101:             Values of this textual convention are not directly useable
 102:             as transport-layer addressing information, and require
 103:             runtime resolution. As such, applications that write them
 104:             must be prepared for handling errors if such values are
 105:             not supported, or cannot be resolved (if resolution occurs
 106:             at the time of the management operation).
 107: 
 108:             The DESCRIPTION clause of TransportAddress objects that may
 109:             have TransportAddressSSH values must fully describe how (and
 110:             when) such names are to be resolved to IP addresses and vice
 111:             versa.
 112: 
 113:             This textual convention SHOULD NOT be used directly in
 114:             object definitions since it restricts addresses to a
 115:             specific format. However, if it is used, it MAY be used
 116:             either on its own or in conjunction with
 117:             TransportAddressType or TransportDomain as a pair.
 118: 
 119:             When this textual convention is used as a syntax of an
 120:             index object, there may be issues with the limit of 128
 121:             sub-identifiers specified in SMIv2, STD 58. In this case,
 122:             the OBJECT-TYPE declaration MUST include a 'SIZE' clause
 123:             to limit the number of potential instance sub-identifiers."
 124:        SYNTAX      OCTET STRING (SIZE (1..255))
 125: 
 126:     transportDomainSSH OBJECT-IDENTITY
 127:        STATUS      current
 128:        DESCRIPTION
 129:            "The SSH transport domain. The corresponding transport
 130:            address is of type TransportAddressSSH.
 131: 
 132:            When an SNMP entity uses the transportDomainSSH transport
 133:            mapping, it must be capable of accepting messages up to
 134:            and including 8192 octets in size.  Implementation of
 135:            larger values is encouraged whenever possible."
 136:        ::= { snmpDomains xxxx }

 137:    -- RFC Ed.: replace xxxx with IANA-assigned number and
 138:    --          remove this note
 139: 
 140: 
 141: 
 142:    -- Statistics for the Secure Shell Security Model
 143: 
 144: 
 145:    sshsmStats         OBJECT IDENTIFIER ::= { sshsmObjects 1 }
 146: 
 147:    -- [todo] do we need any stats?
 148: 
 149: 
 150:    -- -------------------------------------------------------------
 151:    -- sshsmMIB - Conformance Information
 152:    -- -------------------------------------------------------------
 153: 
 154:    sshsmGroups OBJECT IDENTIFIER ::= { sshsmConformance 1 }
 155: 
 156:    sshsmCompliances OBJECT IDENTIFIER ::= { sshsmConformance 2 }
 157: 
 158:    -- -------------------------------------------------------------
 159:    -- Units of conformance
 160:    -- -------------------------------------------------------------
 161:    sshsmGroup OBJECT-GROUP
 162:        OBJECTS {
 163: 
 164:        }

 165:        STATUS      current

 166:        DESCRIPTION "A collection of objects for maintaining
 167:                     information of an SNMP engine which implements the
 168:                     SNMP Secure Shell Security Model.
 169:                    "
 170: 
 171:        ::= { sshsmGroups 2 }

 172: 
 173:    -- -------------------------------------------------------------
 174:    -- Compliance statements
 175:    -- -------------------------------------------------------------
 176: 
 177:    sshsmCompliance MODULE-COMPLIANCE
 178:        STATUS      current
 179:        DESCRIPTION
 180:            "The compliance statement for SNMP engines that support the
 181:            SSHSM-MIB"
 182:        MODULE
 183:            MANDATORY-GROUPS { sshsmGroup }

 184:        ::= { sshsmCompliances 1 }
 185: 
 186:    END
 187: 
 188: -- 
 189: --    Copyright (C) The Internet Society (2006).
 190: -- 
 191: --    This document is subject to the rights, licenses and restrictions
 192: --    contained in BCP 78, and except as set forth therein, the authors
 193: --    retain all their rights.
 194: -- 
 195: --    This document and the information contained herein are provided on an
 196: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
 197: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
 198: --    ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
 199: --    INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 200: --    INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 201: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 202: -- 
 203: -- Intellectual Property
 204: -- 
 205: --    The IETF takes no position regarding the validity or scope of any
 206: --    Intellectual Property Rights or other rights that might be claimed to
 207: --    pertain to the implementation or use of the technology described in
 208: --    this document or the extent to which any license under such rights
 209: --    might or might not be available; nor does it represent that it has
 210: --    made any independent effort to identify any such rights.  Information
 211: --    on the procedures with respect to rights in RFC documents can be
 212: --    found in BCP 78 and BCP 79.
 213: -- 
 214: --    Copies of IPR disclosures made to the IETF Secretariat and any
 215: --    assurances of licenses to be made available, or the result of an
 216: --    attempt made to obtain a general license or permission for the use of
 217: --    such proprietary rights by implementers or users of this
 218: --    specification can be obtained from the IETF on-line IPR repository at
 219: --    http://www.ietf.org/ipr.
 220: -- 
 221: --    The IETF invites any interested party to bring to its attention any
 222: --    copyrights, patents or patent applications, or other proprietary
 223: --    rights that may cover technology that may be required to implement
 224: --    this standard.  Please address the information to the IETF at
 225: --    ietf-ipr@ietf.org.
 226: -- 
 227: