smilint output for ./PANA-MIB

Messages:

PANA-MIB

   1: -- extracted from draft-yacine-pana-snmp-01.txt
   2: -- at Tue Feb 17 06:17:15 2004

   3: 
   4:       PANA-MIB DEFINITIONS ::= BEGIN
   5: 
   6:       IMPORTS
   7: 
   8:       MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32
   9:                            FROM SNMPv2-SMI
  10: 
  11:       RowStatus, PhysAddress,  StorageType, TimeStamp
  12:                            FROM SNMPv2-TC
  13: 
  14:       MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP

  15:                            FROM SNMPv2-CONF
  16: 
  17:       SnmpAdminString
  18:                            FROM SNMP-FRAMEWORK-MIB
  19: 
  20: 
  21:       spdMIB, spdActionExecuted, spdIPInterfaceType, spdIPInterfaceAddress,
  22:       spdIPSourceType, spdIPSourceAddress, spdIPDestinationType,
  23:       spdIPDestinationAddress, spdPacketDirection
  24:                                     FROM IPSEC-SPD-MIB;

  25: 
  26:         -- Module identity
  27:       --
  28: 
  29:       panaMIB MODULE-IDENTITY
  30:         LAST-UPDATED
  31:            "200402050000Z"            -- 05 February 2004
  32: 
  33:         ORGANIZATION
  34:            "IETF PANA Working Group"
  35:         CONTACT-INFO
  36:           "Yacine El Mghazli
  37:            Alcatel
  38:            91460 Marcoussis, France
  39:            Phone: +33 1 69 63 41 87
  40:            Email: yacine.el_mghazli@alcatel.fr"
  41:         DESCRIPTION
  42:            "The MIB module for defining additional PANA-specific objects to
  43:             the IPSec SPD MIB. Copyright (C) The Internet Society (2003).
  44:             This version of this MIB module is part of RFC XXXX, see the
  45:             RFC itself for full legal notices."
  46: 
  47:       -- Revision History
  48:         REVISION
  49:            "200402050000Z"            -- 05 February 2004
  50:         DESCRIPTION
  51:            "Version 01, draft-yacine-pana-paa2ep-snmp-01.txt"
  52:         REVISION
  53:            "200310310000Z"            -- 31 October 2003
  54:         DESCRIPTION
  55:            "Initial version, draft-yacine-pana-paa2ep-snmp-00.txt"
  56:       ::= { spdMIB XXX } -- XXX to be assigned by IANA

  57: 
  58:       --
  59:       -- groups of related objects
  60:       --
  61: 
  62:       panaConfigObjects         OBJECT IDENTIFIER
  63:            ::= { panaMIB 1 }
  64:       panaNotificationObjects   OBJECT IDENTIFIER
  65:            ::= { panaMIB 2}
  66:       panaConformanceObjects    OBJECT IDENTIFIER
  67:            ::= { panaMIB 3 }
  68: 
  69:       --
  70:       -- Textual Conventions
  71:       --
  72: 
  73:       -- TBD.
  74: 
  75:       --
  76:       -- PANA Additional Filters Objects
  77:       --
  78: 
  79: 
  80:       --
  81:       -- The IEEE 802 Filter Table
  82:       --
  83: 
  84: 
  85:       pana802FilterTable OBJECT-TYPE
  86:           SYNTAX      SEQUENCE OF Pana802FilterEntry
  87:           MAX-ACCESS  not-accessible
  88:           STATUS      current
  89:           DESCRIPTION
  90:             " IEEE 802-based filter definitions. A class that contains
  91:               attributes of IEEE 802 (e.g., 802.3) traffic that form
  92:               filters that are used to perform traffic classification."
  93:           ::= { panaConfigObjects 1 }
  94: 
  95:       pana802FilterEntry OBJECT-TYPE
  96:           SYNTAX      Pana802FilterEntry
  97:           MAX-ACCESS  not-accessible
  98:           STATUS      current
  99:           DESCRIPTION
 100:             " IEEE 802-based filter definitions.  An entry specifies
 101:               (potentially) several distinct matching components. Each
 102:               component is tested against the data in a frame
 103:               individually. An overall match occurs when all of the
 104:               individual components match the data they are compared
 105:               against in the frame being processed. A failure of any
 106:               one test causes the overall match to fail.
 107:               Wildcards may be specified for those fields that are not
 108:               relevant."
 109:           INDEX       { pana802FilterName }
 110:           ::= { pana802FilterTable 1 }
 111: 
 112:       Pana802FilterEntry ::= SEQUENCE {
 113:               pana802FilterName            SnmpAdminString,
 114:               pana802FilterType              BITS,
 115:               pana802FilterDstAddr         PhysAddress,
 116:               pana802FilterSrcAddr         PhysAddress,
 117:               pana802FilterVlanId          Integer32,
 118:               pana802FilterVlanTagRequired INTEGER,
 119:               pana802FilterEtherType       Integer32,
 120:               pana802FilterUserPriority    BITS,
 121:               pana802FiltLastChanged       TimeStamp,
 122:               pana802FiltStorageType       StorageType,
 123:               pana802FiltRowStatus         RowStatus
 124: 
 125:       }
 126: 
 127:       pana802FilterName OBJECT-TYPE
 128:           SYNTAX         SnmpAdminString (SIZE(1..32))
 129:           MAX-ACCESS     not-accessible
 130:           STATUS         current
 131:           DESCRIPTION
 132:               "The administrative name for this filter. "
 133:           ::= { pana802FilterEntry 1 }
 134: 
 135:       pana802FilterType OBJECT-TYPE

 136:           SYNTAX      BITS { srcAddress(0),
 137:                              dstAddress(1),
 138:                              vlanId(4),
 139:                              etherType(5),
 140:                              userPriority(6) }
 141:           MAX-ACCESS  read-create
 142:           STATUS      current
 143:           DESCRIPTION
 144:               "This defines the various tests that are used when evaluating
 145:                a given filter.  The results of each test are ANDed together
 146:                to produce the result of the entire filter.  When processing
 147:                this filter, it is recommended for efficiency reasons that
 148:                the filter halt processing the instant any of the specified
 149:                tests fail.
 150:                Once a row is 'active', this object's value may not be
 151:                changed unless all the appropriate columns needed by the new
 152:                value to be imposed on this object have been appropriately
 153:                configured. . "
 154:           ::= { pana802FilterEntry 2 }
 155: 
 156:       pana802FilterDstAddr OBJECT-TYPE

 157:           SYNTAX         PhysAddress
 158:           MAX-ACCESS     read-create
 159:           STATUS         current
 160:           DESCRIPTION
 161:               "The 802 address against which the 802 DA of incoming
 162:               traffic streams will be compared. Frames whose 802 DA
 163:               matches the physical address specified by this object,
 164:               taking into account address wildcarding as specified by the
 165:               pana802FilterDstAddrMask object, are potentially subject to
 166:               the processing guidelines that are associated with this
 167:               entry through the related action class."
 168:           ::= { pana802FilterEntry 3 }
 169: 
 170:       pana802FilterSrcAddr OBJECT-TYPE

 171:           SYNTAX         PhysAddress
 172:           MAX-ACCESS     read-create
 173:           STATUS         current
 174:           DESCRIPTION
 175:              "The 802 MAC address against which the 802 MAC SA of
 176:               incoming traffic streams will be compared. Frames whose 802
 177:               MAC SA matches the physical address specified by this
 178:               object, taking into account address wildcarding as specified
 179:               by the pana802FilterSrcAddrMask object, are potentially
 180:               subject to the processing guidelines that are associated
 181:               with this entry through the related action class."
 182:           ::= { pana802FilterEntry 4 }
 183: 
 184:       pana802FilterVlanId OBJECT-TYPE

 185:           SYNTAX         Integer32 (-1 | 1..4094)
 186:           MAX-ACCESS     read-create
 187:           STATUS         current
 188:           DESCRIPTION
 189:               "The VLAN ID (VID) that uniquely identifies a VLAN
 190:               within the device. This VLAN may be known or unknown
 191:               (i.e., traffic associated with this VID has not yet
 192:               been seen by the device) at the time this entry
 193:               is instantiated.
 194:               Setting the pana802FilterVlanId object to -1 indicates that
 195:               VLAN data should not be considered during traffic
 196:               classification."
 197:           ::= { pana802FilterEntry 5 }
 198: 
 199:       pana802FilterVlanTagRequired OBJECT-TYPE

 200:           SYNTAX         INTEGER {
 201:                             taggedOnly(1),
 202:                             priorityTaggedPlus(2),
 203:                             untaggedOnly(3),
 204:                             ignoreTag(4)
 205:                          }
 206:           MAX-ACCESS     read-create
 207:           STATUS         current
 208:           DESCRIPTION
 209:               "This object indicates whether the presence of an
 210:               IEEE 802.1Q VLAN tag in data link layer frames must
 211:               be considered when determining if a given frame
 212:               matches this 802 filter entry.
 213:               A value of 'taggedOnly(1)' means that only frames
 214:               containing a VLAN tag with a non-Null VID (i.e., a
 215:               VID in the range 1..4094) will be considered a match.
 216:               A value of 'priorityTaggedPlus(2)' means that only
 217:               frames containing a VLAN tag, regardless of the value
 218:               of the VID, will be considered a match.
 219:               A value of 'untaggedOnly(3)' indicates that only
 220:               untagged frames will match this filter component.
 221:               The presence of a VLAN tag is not taken into
 222:               consideration in terms of a match if the value is
 223:               'ignoreTag(4)'."
 224:           ::= { pana802FilterEntry 6 }
 225: 
 226:       pana802FilterEtherType OBJECT-TYPE

 227:           SYNTAX         Integer32 (-1 | 0..'ffff'h)
 228:           MAX-ACCESS     read-create
 229:           STATUS         current
 230:           DESCRIPTION
 231:               "This object specifies the value that will be compared
 232:               against the value contained in the EtherType field of an
 233:               IEEE 802 frame. Example settings would include 'IP'
 234:               (0x0800), 'ARP' (0x0806) and 'IPX' (0x8137).
 235:                Setting the pana802FilterEtherTypeMin object to -1 indicates
 236:               that EtherType data should not be considered during traffic
 237:               classification.
 238:               Note that the position of the EtherType field depends on
 239:               the underlying frame format. For Ethernet-II encapsulation,
 240:               the EtherType field follows the 802 MAC source address. For
 241:               802.2 LLC/SNAP encapsulation, the EtherType value follows
 242:               the Organization Code field in the 802.2 SNAP header. The
 243:               value that is tested with regard to this filter component
 244:               therefore depends on the data link layer frame format being
 245:               used. If this 802 filter component is active when there is
 246:               no EtherType field in a frame (e.g., 802.2 LLC), a match is
 247:               implied."
 248:           ::= { pana802FilterEntry 7 }
 249: 
 250:       pana802FilterUserPriority OBJECT-TYPE

 251:           SYNTAX         BITS {
 252:                               matchPriority0(0),
 253:                               matchPriority1(1),
 254:                               matchPriority2(2),
 255:                               matchPriority3(3),
 256:                               matchPriority4(4),
 257:                               matchPriority5(5),
 258:                               matchPriority6(6),
 259:                               matchPriority7(7)
 260:                          }
 261:           MAX-ACCESS     read-create
 262:           STATUS         current
 263:           DESCRIPTION
 264:               "The set of values, representing the potential range
 265:               of user priority values, against which the value contained
 266:               in the user priority field of a tagged 802.1 frame is
 267:               compared. A test for equality is performed when determining
 268:               if a match exists between the data in a data link layer
 269:               frame and the value of this 802 filter component. Multiple
 270:               values may be set at one time such that potentially several
 271:               different user priority values may match this 802 filter
 272:               component.
 273:               Setting all of the bits that are associated with this
 274:               object causes all user priority values to match this
 275:               attribute. This essentially makes any comparisons
 276:               with regard to user priority values unnecessary. Untagged
 277:               frames are treated as an implicit match."
 278:           ::= { pana802FilterEntry 8 }
 279: 
 280:       pana802FiltLastChanged OBJECT-TYPE

 281:           SYNTAX      TimeStamp
 282:           MAX-ACCESS  read-only
 283:           STATUS      current
 284:           DESCRIPTION
 285:             "The value of sysUpTime when this row was last modified or
 286:              created either through SNMP SETs or by some other external
 287:              means."
 288:           ::= { pana802FilterEntry 9 }
 289: 
 290:       pana802FiltStorageType OBJECT-TYPE

 291:           SYNTAX      StorageType
 292:           MAX-ACCESS  read-create
 293:           STATUS      current
 294:           DESCRIPTION
 295:             "The storage type for this row.  Rows in this table which were
 296:              created through an external process may have a storage type
 297:              of readOnly or permanent."
 298:          DEFVAL { nonVolatile }
 299:           ::= { pana802FilterEntry 10 }
 300: 
 301:       pana802FiltRowStatus OBJECT-TYPE

 302:           SYNTAX      RowStatus
 303:           MAX-ACCESS  read-create
 304:           STATUS      current
 305:           DESCRIPTION
 306:             "This object indicates the conceptual status of this row.
 307:              This object may not be set to active if the requirements of
 308:              the pana802FilterType object are not met.  In other words,
 309:              if the associated value columns needed by a particular test
 310:              have not been set, then attempting to change this row to an
 311:              active state will result in an inconsistentValue error.  See
 312:              the pana802FilterType object description for further
 313:              details."
 314:           ::= { pana802FilterEntry 11 }
 315: 
 316: 
 317:       --
 318:       --
 319:       -- Notification objects information
 320: 
 321:       --
 322:       --
 323: 
 324:       panaNotifications OBJECT IDENTIFIER ::=
 325:          { panaNotificationObjects 0 }
 326: 
 327:       panaNewPacNotification NOTIFICATION-TYPE

 328:         OBJECTS { spdActionExecuted, spdIPInterfaceType,

 329:                   spdIPInterfaceAddress,

 330:                   spdIPSourceType, spdIPSourceAddress,
 331:                   spdIPDestinationType,
 332:                   spdIPDestinationAddress,
 333:                   spdPacketDirection }
 334:         STATUS  current
 335:         DESCRIPTION
 336:             "Notification that AP detected traffic coming from an
 337:       unauthorized source. The objects sent must include the
 338:       ipspActionExecuted which will indicate which action was executed
 339:       within the scope of the rule.  Additionally, the ipspIPSourceType,
 340:       ipspIPSourceAddress, ipspIPDestinationType, and
 341:       ipspIPDestinationAddress, objects must be included to indicate the
 342:       packet source and destination of the packet that triggered the
 343:       action.  The ipspIPInterfaceType, ipspIPInterfaceAddress, and
 344:       ipspPacketDirection objects are included to indicate which endpoint
 345:       the packet was associated with."
 346:         ::= { panaNotifications 1 }
 347: 
 348: 
 349:       --
 350:       --
 351:       -- Conformance information
 352:       --
 353:       --
 354: 
 355:       -- TBD.
 356: 
 357:       END
 358: 
 359: -- 
 360: --    Copyright (C) The Internet Society (2004). All Rights Reserved.
 361: -- 
 362: --    This document and translations of it may be copied and furnished to
 363: --    others, and derivative works that comment on or otherwise explain it
 364: --    or assist in its implementation may be prepared, copied, published
 365: --    and distributed, in whole or in part, without restriction of any
 366: --    kind, provided that the above copyright notice and this paragraph are
 367: --    included on all such copies and derivative works. However, this
 368: --    document itself may not be modified in any way, such as by removing
 369: --    the copyright notice or references to the Internet Society or other
 370: --    Internet organizations, except as needed for the purpose of
 371: --    developing Internet standards in which case the procedures for
 372: --    copyrights defined in the Internet Standards process must be
 373: --    followed, or as required to translate it into languages other than
 374: --    English.
 375: -- 
 376: --    The limited permissions granted above are perpetual and will not be
 377: --    revoked by the Internet Society or its successors or assignees.
 378: -- 
 379: --    This document and the information contained herein is provided on an
 380: --    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
 381: --    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
 382: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
 383: --    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
 384: --    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 385: -- 
 386: -- 
 387: -- Acknowledgment
 388: -- 
 389: --    Funding for the RFC Editor function is currently provided by the
 390: --    Internet Society.
 391: