smilint output for ./TSM-MIB

Messages:

TSM-MIB

   1: -- extracted from draft-ietf-isms-transport-security-model-00.txt
   2: -- at Fri Oct 20 06:07:19 2006

   3: 
   4: TSM-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:     TransportAddressSSH, transportDomainSSH

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

  71: -- RFC Ed.: replace xxxx with IANA-assigned number and
  72: --          remove this note
  73: 
  74: -- ---------------------------------------------------------- --
  75: -- subtrees in the TSM-MIB
  76: -- ---------------------------------------------------------- --
  77: 
  78: tsmNotifications OBJECT IDENTIFIER ::= { tsmMIB 0 }
  79: tsmMIBObjects       OBJECT IDENTIFIER ::= { tsmMIB 1 }
  80: tsmConformance   OBJECT IDENTIFIER ::= { tsmMIB 2 }
  81: 
  82: -- -------------------------------------------------------------
  83: -- Objects
  84: -- -------------------------------------------------------------
  85: 
  86: -- Statistics for the Transport Security Model
  87: 
  88: 
  89: tsmStats         OBJECT IDENTIFIER ::= { tsmMIBObjects 1 }
  90: 
  91: -- [todo] do we need any stats?
  92: 
  93: -- The tsmUser Group ************************************************
  94: 
  95: tsmUser          OBJECT IDENTIFIER ::= { tsmMIBObjects 2 }
  96: 
  97: tsmUserSpinLock  OBJECT-TYPE

  98:     SYNTAX       TestAndIncr
  99:     MAX-ACCESS   read-write
 100:     STATUS       current
 101:     DESCRIPTION "An advisory lock used to allow several cooperating
 102:                  Command Generator Applications to coordinate their
 103:                  use of facilities to alter the tsmUserTable.
 104:                 "
 105:     ::= { tsmUser 1 }
 106: 
 107: -- The table of valid users for the SSH Transport Model ********
 108: tsmUserTable     OBJECT-TYPE
 109:     SYNTAX       SEQUENCE OF tsmUserEntry

 110:     MAX-ACCESS   not-accessible
 111:     STATUS       current
 112:     DESCRIPTION "The table of users configured in the SNMP engine's
 113:                  Local Configuration Datastore (LCD).
 114: 
 115:                  To create a new user (i.e., to instantiate a new
 116:                  conceptual row in this table), it is recommended to
 117:                  follow this procedure:
 118: 
 119:                    1)  GET(tsmUserSpinLock.0) and save in sValue.
 120:                    2)  SET(tsmUserSpinLock.0=sValue,
 121:                            tsmUserStatus=createAndWait)
 122: 
 123:                  Finally, activate the new user:
 124: 
 125:                    3) SET(tsmUserStatus=active)
 126: 
 127:                  The new user should now be available and ready to be
 128:                  used for SNMPv3 communication.
 129: 
 130:                  The use of tsmUserSpinlock is to avoid conflicts with
 131:                  another SNMP command generator application which may
 132:                  also be acting on the tsmUserTable.
 133:                 "
 134:     ::= { tsmUser 2 }

 135: 
 136: tsmUserEntry     OBJECT-TYPE
 137:     SYNTAX       tsmUserEntry

 138:     MAX-ACCESS   not-accessible
 139:     STATUS       current
 140:     DESCRIPTION "A user configured in the SNMP engine's Local
 141:                  Configuration Datastore (LCD) for the Session
 142:                  Security Model.
 143:                 "
 144:     INDEX       { tsmUserSecurityName }

 145:     ::= { tsmUserTable 1 }

 146: 
 147: tsmUserEntry ::= SEQUENCE

 148:     {
 149:         tsmUserSecurityName     SnmpAdminString,
 150:         tsmUserStorageType      StorageType,
 151:         tsmUserStatus           RowStatus
 152:     }

 153: 
 154: 
 155: tsmUserSecurityName OBJECT-TYPE

 156:     SYNTAX       SnmpAdminString
 157:     MAX-ACCESS   read-only
 158:     STATUS       current
 159:     DESCRIPTION "A human readable string representing the user in
 160:                  Security Model independent format.
 161: 
 162:                  [todo: Wehn used with transport models that perform
 163:                  authentication, the tsmUserSecurityName is the
 164:                  securityName passed in tmStateReference.
 165:                 "
 166:     ::= { tsmUserEntry 1 }

 167: 
 168: 
 169: tsmUserStorageType OBJECT-TYPE

 170:     SYNTAX       StorageType
 171:     MAX-ACCESS   read-create

 172:     STATUS       current
 173:     DESCRIPTION "The storage type for this conceptual row.
 174: 
 175:                  It is an implementation issue to decide if a SET for
 176:                  a readOnly or permanent row is accepted at all. In some
 177:                  contexts this may make sense, in others it may not. If
 178:                  a SET for a readOnly or permanent row is not accepted
 179:                  at all, then a 'wrongValue' error must be returned.
 180:                 "
 181:     DEFVAL      { nonVolatile }

 182:     ::= { tsmUserEntry 4 }

 183: 
 184: tsmUserStatus    OBJECT-TYPE

 185:     SYNTAX       RowStatus
 186:     MAX-ACCESS   read-create

 187:     STATUS       current
 188:     DESCRIPTION "The status of this conceptual row.
 189: 
 190:                  Until instances of all corresponding columns are
 191:                  appropriately configured, the value of the
 192:                  corresponding instance of the tsmUserStatus column
 193:                  is 'notReady'.
 194: 
 195:                  The RowStatus TC [RFC2579] requires that this
 196:                  DESCRIPTION clause states under which circumstances
 197:                  other objects in this row can be modified:
 198: 
 199:                  The value of this object has no effect on whether
 200:                  other objects in this conceptual row can be modified.
 201:                  "
 202:     ::= { tsmUserEntry 5 }

 203: 
 204: -- -------------------------------------------------------------
 205: -- tsmMIB - Conformance Information
 206: -- -------------------------------------------------------------
 207: 
 208: tsmGroups OBJECT IDENTIFIER ::= { tsmConformance 1 }
 209: 
 210: tsmCompliances OBJECT IDENTIFIER ::= { tsmConformance 2 }
 211: 
 212: -- -------------------------------------------------------------
 213: -- Units of conformance
 214: -- -------------------------------------------------------------
 215: tsmGroup OBJECT-GROUP
 216:     OBJECTS {
 217: 
 218:     }

 219:     STATUS      current

 220:     DESCRIPTION "A collection of objects for maintaining
 221:                  information of an SNMP engine which implements the
 222:                  SNMP Transport Security Model.
 223:                 "
 224: 
 225:     ::= { tsmGroups 2 }

 226: 
 227: -- -------------------------------------------------------------
 228: -- Compliance statements
 229: -- -------------------------------------------------------------
 230: 
 231: tsmCompliance MODULE-COMPLIANCE
 232:     STATUS      current
 233:     DESCRIPTION
 234:         "The compliance statement for SNMP engines that support the
 235:         TSM-MIB"
 236:     MODULE
 237:         MANDATORY-GROUPS { tsmGroup }

 238:     ::= { tsmCompliances 1 }
 239: 
 240: END
 241: 
 242: -- 
 243: --    Copyright (C) The Internet Society (2006).
 244: -- 
 245: --    This document is subject to the rights, licenses and restrictions
 246: --    contained in BCP 78, and except as set forth therein, the authors
 247: --    retain all their rights.
 248: -- 
 249: --    This document and the information contained herein are provided on an
 250: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
 251: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
 252: --    ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
 253: --    INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 254: --    INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 255: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 256: -- 
 257: -- Intellectual Property
 258: -- 
 259: --    The IETF takes no position regarding the validity or scope of any
 260: --    Intellectual Property Rights or other rights that might be claimed to
 261: --    pertain to the implementation or use of the technology described in
 262: --    this document or the extent to which any license under such rights
 263: --    might or might not be available; nor does it represent that it has
 264: --    made any independent effort to identify any such rights.  Information
 265: --    on the procedures with respect to rights in RFC documents can be
 266: --    found in BCP 78 and BCP 79.
 267: -- 
 268: --    Copies of IPR disclosures made to the IETF Secretariat and any
 269: --    assurances of licenses to be made available, or the result of an
 270: --    attempt made to obtain a general license or permission for the use of
 271: --    such proprietary rights by implementers or users of this
 272: --    specification can be obtained from the IETF on-line IPR repository at
 273: --    http://www.ietf.org/ipr.
 274: -- 
 275: --    The IETF invites any interested party to bring to its attention any
 276: --    copyrights, patents or patent applications, or other proprietary
 277: --    rights that may cover technology that may be required to implement
 278: --    this standard.  Please address the information to the IETF at
 279: --    ietf-ipr@ietf.org.
 280: -- 
 281: