smilint output for ./PW-TC-DRAFT05-MIB

Messages:

PW-TC-DRAFT05-MIB

   1: -- extracted from draft-ietf-pwe3-pw-tc-mib-05.txt
   2: -- at Thu Jul  8 06:21:50 2004

   3: 
   4:   PW-TC-DRAFT05-MIB DEFINITIONS ::= BEGIN 
   5:    
   6:   IMPORTS 
   7:      MODULE-IDENTITY, Unsigned32, Integer32, transmission 
   8:         FROM SNMPv2-SMI 
   9:    
  10:      TEXTUAL-CONVENTION 
  11:         FROM SNMPv2-TC; 
  12:    
  13:   pwTCMIB MODULE-IDENTITY 
  14:      LAST-UPDATED "200406141200Z"  -- 14 June 2004 12:00:00 GMT 
  15:      ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 
  16:                    Group" 
  17:      CONTACT-INFO 
  18:      " Thomas D. Nadeau 
  19:        Postal: Cisco Systems, Inc. 
  20:                250 Apollo Drive 
  21:                Chelmsford, MA 01824 
  22:        Tel:    +1-978-497-3051 
  23:        Email:  tnadeau@cisco.com 
  24:    
  25:        Dave Danenberg 
  26:        Email:  dave_danenberg@yahoo.com 
  27:     
  28:                David Zelig 
  29:        Postal: Corrigent Systems. 
  30:                126, Yigal Alon St. 
  31:                Tel Aviv, ISRAEL 
  32:                Phone: +972-3-6945273 
  33:        E-mail: davidz@corrigent.com 
  34:    
  35:                Andrew G. Malis  
  36:        Postal: Tellabs, Inc.  
  37:                2730 Orchard Parkway  
  38:                San Jose, CA 95134  
  39:        Email:  Andy.Malis@tellabs.com 
  40:           
  41:           The PWE3 Working Group (email distribution pwe3@ietf.org, 
  42:           http://www.ietf.org/html.charters/pwe3-charter.html) 
  43:       " 
  44:                              PWE3 TC MIB                    June 2004 

  45: 
  46: 
  47: 
  48:      DESCRIPTION 
  49:          "This MIB Module provides Textual Conventions 
  50:          and OBJECT-IDENTITY Objects to be used in networks 
  51:          implementing PW services. 
  52:    
  53:          Copyright (C) The Internet Society (date).  This version 
  54:          of this MIB module is part of RFC yyyy;  see the RFC 
  55:          itself for full legal notices. 
  56:   -- RFC Ed.: replace yyyy with actual RFC number & remove this note 
  57:          " 
  58:    
  59:    
  60:      -- Revision history. 
  61:    
  62:      REVISION "200406141200Z"  -- 14 June 2004 12:00:00 GMT 
  63:      DESCRIPTION " Changes from previous drafts: 
  64:         - Update PW types based on new IANA draft -04. 
  65:         - FCS Retention status has been updated to include FCS size 
  66:           mismatch. 
  67:        " 
  68:    
  69:      REVISION "200402031200Z"  -- 3 February 2004 12:00:00 GMT 
  70:      DESCRIPTION " Changes from previous drafts: 
  71:         - Change IANA request text. 
  72:         - Change PwVcRemoteCwStatus to PwVcCwStatus and add two 
  73:           enum so the textual convention will indicate the full 
  74:           status of the CW negotiation including the final result. 
  75:        " 
  76:      REVISION "200311301200Z"  -- 30 November 2003 12:00:00 GMT 
  77:      DESCRIPTION " Changes from previous drafts: 
  78:         - Removing non-necessary textual convention. 
  79:         - Adapt description of main clause based on MIB 
  80:           boilerplate. 
  81:        " 
  82:      REVISION "200307281200Z"  -- 28 July 2003 12:00:00 GMT 
  83:      DESCRIPTION "Adding objects to cover new control draft.  
  84:         Adapt VC types for current values in WG documents." 
  85:    
  86:      REVISION "200305011200Z"  -- 1 May 2003 12:00:00 GMT 
  87:      DESCRIPTION "Adding PwVcAttachmentIdentifierType,  
  88:         Adapt VC types for current values in WG documents." 
  89:    
  90:      REVISION "200205281200Z"  -- 28 May 2002 12:00:00 GMT 
  91:      DESCRIPTION "Adding PwVcType, and enhance some descriptions." 
  92:       
  93:      REVISION "200201301200Z"  -- 30 January 2002 12:00:00 GMT 
  94:      DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and  
  95:                   PwOperStatus." 
  96:    
  97:      REVISION "200112201200Z"  -- 20 Dec 2001 12:00:00 GMT 
  98:      DESCRIPTION "Remove PwVcInstance" 
  99:                              PWE3 TC MIB                    June 2004 
 100: 
 101: 
 102: 
 103:    
 104:      REVISION "200107121200Z"  -- 12 July 2001 12:00:00 GMT 
 105:      DESCRIPTION "Initial version." 
 106:    
 107:    
 108:      -- Please see the IANA Considerations Section. 
 109:      -- The requested pwStdMIB subId is 1, e.g. 
 110:      --   ::= { pwStdMIB 1 } 
 111:    
 112:      ::= { pwStdMIB x }  

 113:    
 114:   pwStdMIB OBJECT IDENTIFIER 
 115:    
 116:             -- This object identifier needs to be assigned by IANA. 
 117:          ::= { transmission xxx }  

 118:    
 119:   PwGroupID ::= TEXTUAL-CONVENTION 

 120:      STATUS      current 
 121:      DESCRIPTION 
 122:           "An administrative identification mechanism for grouping a 
 123:            set of service-specific pseudo-wire services. May only 
 124:            have local significance." 
 125:      SYNTAX  Unsigned32 
 126:    
 127:   PwVcIDType ::= TEXTUAL-CONVENTION 

 128:      STATUS      current 
 129:      DESCRIPTION 
 130:           "Pseudo-Wire Identifier. Used to identify the PW  
 131:            (together with some other fields) in the signaling  
 132:            session. Zero if the PW is set-up manually." 
 133:      SYNTAX  Unsigned32 
 134:    
 135:   PwVcIndexType ::= TEXTUAL-CONVENTION 

 136:      STATUS      current 
 137:      DESCRIPTION 
 138:           "Pseudo Wire Index. Locally unique index for indexing 
 139:            several MIB tables associated with a particular PW." 
 140:      SYNTAX  Unsigned32 
 141:    
 142:   PwVcVlanCfg ::= TEXTUAL-CONVENTION 

 143:      STATUS      current 
 144:      DESCRIPTION 
 145:           "VLAN configuration for Ethernet PW.  
 146:            Values between 0 to 4095 indicate the actual VLAN field 
 147:            value.  
 148:            A value of 4096 indicates that the object refer to  
 149:            untagged frames, i.e. frames without 802.1Q field. 
 150:            A value of 4097 indicates that the object is not  
 151:            relevant." 
 152:      SYNTAX  Integer32 (0..4097) 
 153:                              PWE3 TC MIB                    June 2004 

 154: 
 155: 
 156: 
 157:   PwOperStatus ::= TEXTUAL-CONVENTION 
 158:      STATUS      current 
 159:      DESCRIPTION 
 160:         "Indicates the operational status of the PW. 
 161:          
 162:         - up(1):            Ready to pass packets.  
 163:         - down(2):          If PW signaling has not yet finished, or 
 164:                             indications available at the service  
 165:                             level indicate that the VC is not  
 166:                             passing packets. 
 167:         - testing(3):       If AdminStatus at the PW level is set to  
 168:                             test. 
 169:         - dormant(4):       The PW is not available because of the 
 170:                             required resources are occupied PW with  
 171:                             higher priority PWs . 
 172:         - notPresent(5):    Some component is missing to accomplish  
 173:                             the set up of the PW. 
 174:         - lowerLayerDown(6):The underlying PSN or outer tunnel is not 
 175:                             in OperStatus 'up' state.  
 176:         " 
 177:    SYNTAX   INTEGER { 
 178:        up(1), 
 179:        down(2), 
 180:        testing(3), 
 181:        unknown(4), 
 182:        dormant(5), 
 183:        notPresent(6), 
 184:        lowerLayerDown(7) 
 185:        }       

 186:    
 187:   PwVcType ::= TEXTUAL-CONVENTION 
 188:      STATUS      current 
 189:      DESCRIPTION 
 190:         "Indicates the PW type (i.e. the carried service). 
 191:         " 
 192:    SYNTAX   INTEGER { 
 193:       other(0), 
 194:       frameRelayDlci(1), 
 195:       atmAal5SduVcc(2), 
 196:       atmTransparent(3), 
 197:       ethernetTagged(4), 
 198:       ethernet(5), 
 199:       hdlc(6), 
 200:       ppp(7), 
 201:       cem(8),  -- old format 
 202:       atmCellNto1Vcc(9), 
 203:       atmCellNto1Vpc(10), 
 204:       ipLayer2Transport(11), 
 205:       atmCell1to1Vcc(12), 
 206:       atmCell1to1Vpc(13), 
 207:       atmAal5PduVcc(14), 
 208:                              PWE3 TC MIB                    June 2004 

 209: 
 210: 
 211: 
 212:       frameRelayPortMode(15), 
 213:       cep(16), 
 214:       e1Satop(17), 
 215:       t1Satop(18), 
 216:       e3Satop(19), 
 217:       t3Satop(20), 
 218:       basicCesPsn(21), 
 219:       basicTdmIp(22), 
 220:       tdmCasCesPsn(23), 
 221:       tdmCasTdmIp(24) 
 222:        }       

 223:    
 224:   PwVcAttachmentIdentifierType ::= TEXTUAL-CONVENTION 

 225:    
 226:      STATUS      current 
 227:      DESCRIPTION 
 228:         "An octet string used in the generalized FEC element for 
 229:          identifying attachment forwarder and groups. The NULL  
 230:          identifier is of zero length. 
 231:         " 
 232:    SYNTAX    OCTET STRING (SIZE (0..255)) 
 233:    
 234:   PwVcCwStatus ::= TEXTUAL-CONVENTION 

 235:    
 236:      STATUS      current 
 237:      DESCRIPTION 
 238:         "Indicates the status of the control word negotiation based 
 239:          on the local configuration and the indications received from 
 240:          the peer node.   
 241:           
 242:          waitingForNextMsg(1) indicates that the node is waiting for  
 243:          another label mapping from the remote. 
 244:           
 245:          sentWrongBitErrorCode(2) indicates that the local node has  
 246:          notified the peer about mismatch in the C bit. 
 247:           
 248:          rxWithdrawWithWrongBitErrorCode(3) indicates that a withdraw  
 249:          message has been received with the wrong C-bit error code. 
 250:           
 251:          illegalReceivedBit(4) indicates a C bit configuration with 
 252:          the remote which is not compatible with the PW type. 
 253:           
 254:          cwPresent(5) indicates that the CW is present for this PW: 
 255:          if signaling is used - C bit is set and agreed between the 
 256:          peers, and for manual configured PW the local configuration 
 257:          require the use of the CW. 
 258:    
 259:          cwNotPresent(6) indicates that the CW is not present for  
 260:          this PW: if signaling is used - C bit is reset and agreed  
 261:          between the peers, and for manual configured PW the local  
 262:          configuration requires that CW would not be used. 
 263:                              PWE3 TC MIB                    June 2004 
 264: 
 265: 
 266: 
 267:    
 268:          notYetKnown(7) indicate that a label mapping has not yet  
 269:          received from the peer. 
 270:         " 
 271:    SYNTAX    INTEGER { 
 272:                 waitingForNextMsg (1), 
 273:                 sentWrongBitErrorCode (2), 
 274:                 rxWithdrawWithWrongBitErrorCode (3), 
 275:                 illegalReceivedBit (4), 
 276:                 cwPresent (5), 
 277:                 cwNotPresent (6), 
 278:                 notYetKnown(7) 
 279:                 } 
 280:    
 281:   PwVcCapabilities ::= TEXTUAL-CONVENTION 

 282:      STATUS      current 
 283:      DESCRIPTION 
 284:         "Indicates the optional capabilities of the control protocol. 
 285:          A value of zero indicates the basic LDP PW signaling.  
 286:          Values may be added in the future based on new capabilities  
 287:          introduced in IETF documents. 
 288:         " 
 289:    SYNTAX   BITS { 
 290:       pwStatusIndication (0) 
 291:        }       
 292:    
 293:   PwVcStatus ::= TEXTUAL-CONVENTION 

 294:      STATUS      current 
 295:      DESCRIPTION 
 296:         "The status of the PW and the interfaces affecting this PW. 
 297:          If none of the bits are set, it indicate no faults are  
 298:          reported. 
 299:         " 
 300:    SYNTAX   BITS { 
 301:       pwNotForwarding (0), 
 302:       customerFacingPwRxFault (1), 
 303:       customerFacingPwTxFault (2), 
 304:       psnFacingPwRxFault  (3), 
 305:       psnFacingPwTxFault  (4) 
 306:        }       
 307:    
 308:   PwVcFragSize ::= TEXTUAL-CONVENTION 

 309:      STATUS      current 
 310:      DESCRIPTION 
 311:         "If set to value other than zero, it indicates desired  
 312:          fragmentation to the value set. If set to zero,  
 313:          fragmentation is not desired for PSN bound packets.  
 314:         " 
 315:    SYNTAX   Unsigned32  
 316:    
 317:   PwVcFragStatus ::= TEXTUAL-CONVENTION 
 318:                              PWE3 TC MIB                    June 2004 

 319: 
 320: 
 321: 
 322:      STATUS      current 
 323:      DESCRIPTION 
 324:         "The status of the fragmentation process based on local  
 325:          configuration and the remote capability. 
 326:    
 327:          noFrag(0) bit indicates that local configuration is for no  
 328:          fragmentation. 
 329:    
 330:          cfgFragGreaterThanPsnMtu(1) bit indicates the local desire 
 331:          to fragment, but the fragmentation size desired is greater  
 332:          than the MTU available at the PSN between peers.  
 333:          Fragmentation is not done in this case. 
 334:           
 335:          cfgFragButRemoteIncapable(2) bit indicates that the local  
 336:          configuration indicates the desire for fragmentation but  
 337:          the remote is not capable of fragmentation. 
 338:    
 339:          cfgFragFcsLengthMismatch(3) bit indicates that there is a  
 340:          mismatch between the FCS size between the local  
 341:          configuration and the remote configuration. 
 342:    
 343:          fragEnabled(4) bit indicates that both the local was  
 344:          configured for fragmentation and the remote has the  
 345:          cabability to accept fragmented packets, and the FCS size is 
 346:          equal in both peers. 
 347:         " 
 348:    SYNTAX   BITS { 
 349:       noFrag (0), 
 350:       cfgFragGreaterThanPsnMtu (1), 
 351:       cfgFragButRemoteIncapable (2), 
 352:       remoteFragCapable (3), 
 353:       fragEnabled (4) 
 354:        }       

 355:    
 356:   END 

 357: 
 358: -- 
 359: --   Copyright (C) The Internet Society (2000).  All Rights Reserved. 
 360: --   This document and translations of it may be copied and furnished to 
 361: --   others, and derivative works that comment on or otherwise explain 
 362: --   it or assist in its implementation may be prepared, copied, 
 363: --   published and distributed, in whole or in part, without restriction 
 364: --   of any kind, provided that the above copyright notice and this 
 365: --   paragraph are included on all such copies and derivative works.  
 366: --   However, this document itself may not be modified in any way, such 
 367: --   as by removing the copyright notice or references to the Internet 
 368: --   Society or other Internet organizations, except as needed for the 
 369: --   purpose of developing Internet standards in which case the 
 370: --   procedures for copyrights defined in the Internet Standards process 
 371: --   must be followed, or as required to translate it into languages 
 372: --   other than English. 
 373: --   The limited permissions granted above are perpetual and will not be 
 374: --   revoked by the Internet Society or its successors or assigns. This 
 375: --   document and the information contained herein is provided on an "AS 
 376: --   IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 
 377: --   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 
 378: --   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 
 379: --   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 
 380: --   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 
 381: --    
 382: -- 11 Intellectual Property Notice 
 383: --    
 384: --   The IETF takes no position regarding the validity or scope of any 
 385: --   intellectual property or other rights that might be claimed to 
 386: --   pertain to the implementation or use of the technology described in 
 387: --   this document or the extent to which any license under such rights 
 388: --   might or might not be available; neither does it represent that it 
 389: --   has made any effort to identify any such rights.  Information on 
 390: --   the IETF's procedures with respect to rights in standards-track and 
 391: --   standards-related documentation can be found in BCP-11 [RFC2028]. 
 392: --   Copies of claims of rights made available for publication and any 
 393: --   assurances of licenses to be made available, or the result of an 
 394: --   attempt made to obtain a general license or permission for the use 
 395: --   of such proprietary rights by implementors or users of this 
 396: --   specification can be obtained from the IETF Secretariat. 
 397: --    
 398: --   The IETF invites any interested party to bring to its attention any 
 399: --   copyrights, patents or patent applications, or other proprietary 
 400: --   rights that may cover technology that may be required to practice 
 401: --   this standard.  Please address the information to the IETF 
 402: --   Executive Director. 
 403: