smilint output for ./Transport-Subsystem-MIB

Messages:

Transport-Subsystem-MIB

   1: -- extracted from draft-ietf-isms-tmsm-04.txt
   2: -- at Thu Oct 12 06:07:13 2006

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

   8:       mib-2, Integer32, Unsigned32, Gauge32

   9:         FROM SNMPv2-SMI
  10:       TestAndIncr, StorageType, RowStatus

  11:         FROM SNMPv2-TC
  12:       MODULE-COMPLIANCE, OBJECT-GROUP
  13:         FROM SNMPv2-CONF
  14:       SnmpSecurityModel,

  15:       SnmpAdminString,  SnmpSecurityLevel, SnmpEngineID

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

  18:         FROM TRANSPORT-ADDRESS-MIB
  19:       ;
  20: 
  21:   tmsMIB MODULE-IDENTITY
  22:       LAST-UPDATED "200610060000Z"
  23:       ORGANIZATION "ISMS Working Group"
  24:       CONTACT-INFO "WG-EMail:   isms@lists.ietf.org
  25:                     Subscribe:  isms-request@lists.ietf.org
  26: 
  27:                  Chairs:
  28:                    Juergen Quittek
  29:                    NEC Europe Ltd.
  30:                    Network Laboratories
  31:                    Kurfuersten-Anlage 36
  32:                    69115 Heidelberg
  33:                    Germany
  34:                    +49 6221 90511-15
  35:                     quittek@netlab.nec.de
  36: 
  37:                     Juergen Schoenwaelder
  38:                     International University Bremen
  39:                     Campus Ring 1
  40:                     28725 Bremen
  41:                     Germany
  42:                     +49 421 200-3587
  43:                     j.schoenwaelder@iu-bremen.de
  44: 
  45:                  Editor:
  46:                     David Harrington
  47:                     FutureWei Technologies
  48:                     1700 Alma Drive, Suite 100
  49:                     Plano, Texas 75075
  50:                     USA
  51:                     +1 603-436-8634
  52:                     dharrington@huawei.com
  53:                       "
  54:          DESCRIPTION  "The Transport Subsystem MIB Module
  55: 
  56:                        Copyright (C) The Internet Society (2006). This
  57:                        version of this MIB module is part of RFC XXXX;
  58:                        see the RFC itself for full legal notices.
  59: 
  60:   -- NOTE to RFC editor: replace XXXX with actual RFC number
  61:   --                     for this document and remove this note
  62:                       "
  63: 
  64:          REVISION     "200610060000Z"         -- 20 April 2006
  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 Transport-Subsystem-MIB
  76:   -- ---------------------------------------------------------- --
  77: 
  78:   tmsNotifications OBJECT IDENTIFIER ::= { tmsMIB 0 }
  79:   tmsObjects       OBJECT IDENTIFIER ::= { tmsMIB 1 }
  80:   tmsConformance   OBJECT IDENTIFIER ::= { tmsMIB 2 }
  81: 
  82:   -- -------------------------------------------------------------
  83:   -- Objects
  84:   -- -------------------------------------------------------------
  85: 
  86:   -- Textual Conventions
  87: 
  88:   SnmpTransportModel ::= TEXTUAL-CONVENTION

  89:       STATUS       current
  90:       DESCRIPTION "An identifier that uniquely identifies a
  91:                    Transport Model of the Transport Subsystem within
  92:                    the SNMP Management Architecture.
  93: 
  94:                    The values for transportModel are allocated as
  95:                    follows:
  96: 
  97:                    - The zero value does not identify any particular
  98:                      transport model.
  99: 
 100:                    - Values between 1 and 255, inclusive, are reserved
 101:                      for standards-track Transport Models and are
 102:                      managed by the Internet Assigned Numbers Authority
 103:                      (IANA).
 104:                    - Values greater than 255 are allocated to
 105:                      enterprise-specific Transport Models.  An
 106:                      enterprise-specific transportModel value is defined
 107:                      to be:
 108:                      enterpriseID * 256 + transport model within
 109:                      enterprise
 110: 
 111:                      For example, the fourth Transport Model defined by
 112:                      the enterprise whose enterpriseID is 1 would be
 113:                      260.
 114: 
 115:                    This scheme for allocation of transportModel
 116:                    values allows for a maximum of 255 standards-
 117:                    based Transport Models, and for a maximum of
 118:                    256 Transport Models per enterprise.
 119: 
 120:                    It is believed that the assignment of new
 121:                    transportModel values will be rare in practice
 122:                    because the larger the number of simultaneously
 123:                    utilized Transport Models, the larger the
 124:                    chance that interoperability will suffer.
 125:                    Consequently, it is believed that such a range
 126:                    will be sufficient.  In the unlikely event that
 127:                    the standards committee finds this number to be
 128:                    insufficient over time, an enterprise number
 129:                    can be allocated to obtain an additional 256
 130:                    possible values.
 131: 
 132:                    Note that the most significant bit must be zero;
 133:                    hence, there are 23 bits allocated for various
 134:                    organizations to design and define non-standard
 135:                    transportModels.  This limits the ability to
 136:                    define new proprietary implementations of Transport
 137:                    Models to the first 8,388,608 enterprises.
 138: 
 139:                    It is worthwhile to note that, in its encoded
 140:                    form, the transportModel value will normally
 141:                    require only a single byte since, in practice,
 142:                    the leftmost bits will be zero for most messages
 143:                    and sign extension is suppressed by the encoding
 144:                    rules.
 145: 
 146:                    As of this writing, there are several values
 147:                    of transportModel defined for use with SNMP or
 148:                    reserved for use with supporting MIB objects.
 149:                    They are as follows:
 150: 
 151:                        0  reserved for 'any'
 152:                        1  reserved for UDP
 153:                        2  reserved for TCP
 154:                        3  SSH Transport Model
 155:                   "
 156: 
 157:       SYNTAX       INTEGER(0 .. 2147483647)

 158: 
 159:   -- Notifications for the Transport Subsystem
 160: 
 161:   -- Statistics for the Transport Subsystem
 162: 
 163: 
 164:   tmsStats         OBJECT IDENTIFIER ::= { tmsObjects 1 }
 165: 
 166: 
 167:   -- -------------------------------------------------------------
 168:   -- Conformance Information
 169:   -- -------------------------------------------------------------
 170: 
 171:   tmsGroups OBJECT IDENTIFIER ::= { tmsConformance 1 }
 172: 
 173:   tmsCompliances OBJECT IDENTIFIER ::= { tmsConformance 2 }
 174: 
 175:   -- -------------------------------------------------------------
 176:   -- Units of conformance
 177:   -- -------------------------------------------------------------
 178:   tmsGroup OBJECT-GROUP
 179:       OBJECTS {
 180: 
 181:       }

 182:       STATUS      current

 183:       DESCRIPTION "A collection of objects for maintaining session
 184:                    information of an SNMP engine which implements the
 185:                    Transport subsystem.
 186:                   "
 187: 
 188:       ::= { tmsGroups 2 }

 189: 
 190:   -- -------------------------------------------------------------
 191:   -- Compliance statements
 192:   -- -------------------------------------------------------------
 193: 
 194:   tmsCompliance MODULE-COMPLIANCE
 195:       STATUS      current
 196:       DESCRIPTION
 197:           "The compliance statement for SNMP engines that support the
 198:           Transport-Subsystem-MIB"
 199:       MODULE
 200:           MANDATORY-GROUPS { tmsGroup }

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