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

Messages:

PW-TC-DRAFT04-MIB

   1: -- extracted from draft-ietf-pwe3-pw-tc-mib-04.txt
   2: -- at Tue Feb 17 06:17:14 2004

   3: 
   4:   PW-TC-DRAFT04-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 "200402031200Z"  -- 3 February 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                February 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 "200402031200Z"  -- 3 February 2004 12:00:00 GMT 
  63:      DESCRIPTION " Changes from previous drats: 
  64:         - Change IANA request text. 
  65:         - Change PwVcRemoteCwStatus to PwVcCwStatus and add two 
  66:           enum so the textual convention will indicate the full 
  67:           status of the CW negotiation including the final result. 
  68:        " 
  69:      REVISION "200311301200Z"  -- 30 November 2003 12:00:00 GMT 
  70:      DESCRIPTION " Changes from previous drats: 
  71:         - Removing non-necessary textual convention. 
  72:         - Adapt description of main clause based on MIB 
  73:           boilerplate. 
  74:        " 
  75:      REVISION "200307281200Z"  -- 28 July 2003 12:00:00 GMT 
  76:      DESCRIPTION "Adding objects to cover new control draft.  
  77:         Adapt VC types for current values in WG documents." 
  78:    
  79:      REVISION "200305011200Z"  -- 1 May 2003 12:00:00 GMT 
  80:      DESCRIPTION "Adding PwVcAttachmentIdentifierType,  
  81:         Adapt VC types for current values in WG documents." 
  82:    
  83:      REVISION "200205281200Z"  -- 28 May 2002 12:00:00 GMT 
  84:      DESCRIPTION "Adding PwVcType, and enhance some descriptions." 
  85:       
  86:      REVISION "200201301200Z"  -- 30 January 2002 12:00:00 GMT 
  87:      DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and  
  88:                   PwOperStatus." 
  89:    
  90:      REVISION "200112201200Z"  -- 20 Dec 2001 12:00:00 GMT 
  91:      DESCRIPTION "Remove PwVcInstance" 
  92:    
  93:      REVISION "200107121200Z"  -- 12 July 2001 12:00:00 GMT 
  94:      DESCRIPTION "Initial version." 
  95:    
  96:    
  97:      -- Please see the IANA Considerations Section. 
  98:      -- The requested pwStdMIB subId is 1, e.g. 
  99:                              PWE3 TC MIB                February 2004 
 100: 
 101: 
 102: 
 103:      --   ::= { pwStdMIB 1 } 
 104:    
 105:      ::= { pwStdMIB 1 }  

 106:    
 107:   pwStdMIB OBJECT IDENTIFIER 
 108:             -- This object identifier needs to be assigned by IANA. 
 109:    
 110:          ::= { transmission XXX }  

 111:    
 112:   PwGroupID ::= TEXTUAL-CONVENTION 

 113:      STATUS      current 
 114:      DESCRIPTION 
 115:           "An administrative identification mechanism for grouping a 
 116:            set of service-specific pseudo-wire services. May only 
 117:            have local significance." 
 118:      SYNTAX  Unsigned32 
 119:    
 120:   PwVcIDType ::= TEXTUAL-CONVENTION 

 121:      STATUS      current 
 122:      DESCRIPTION 
 123:           "Pseudo-Wire Identifier. Used to identify the PW  
 124:            (together with some other fields) in the signaling  
 125:            session. Zero if the PW is set-up manually." 
 126:      SYNTAX  Unsigned32 
 127:    
 128:   PwVcIndexType ::= TEXTUAL-CONVENTION 

 129:      STATUS      current 
 130:      DESCRIPTION 
 131:           "Pseudo Wire Index. Locally unique index for indexing 
 132:            several MIB tables associated with a particular PW." 
 133:      SYNTAX  Unsigned32 
 134:    
 135:   PwVcVlanCfg ::= TEXTUAL-CONVENTION 

 136:      STATUS      current 
 137:      DESCRIPTION 
 138:           "VLAN configuration for Ethernet PW.  
 139:            Values between 0 to 4095 indicate the actual VLAN field 
 140:            value.  
 141:            A value of 4096 indicates that the object refer to  
 142:            untagged frames, i.e. frames without 802.1Q field. 
 143:            A value of 4097 indicates that the object is not  
 144:            relevant." 
 145:      SYNTAX  Integer32 (0..4097) 
 146:    
 147:   PwOperStatus ::= TEXTUAL-CONVENTION 

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

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

 210: 
 211: 
 212: 
 213:      DESCRIPTION 
 214:         "An octet string used in the generalized FEC element for 
 215:          identifying attachment forwarder and groups. The NULL  
 216:          identifier is of zero length." 
 217:    SYNTAX    OCTET STRING (SIZE (0..255)) 
 218:    
 219:   PwVcCwStatus ::= TEXTUAL-CONVENTION 
 220:    
 221:      STATUS      current 
 222:      DESCRIPTION 
 223:         "Indicate the status of the control word negotiation based on 
 224:          the local configuration and the remote indications.   
 225:           
 226:          waitingForNextMsg indicate that the node is waiting for  
 227:          another label mapping from the remote. 
 228:           
 229:          sentWrongBitErrorCode indicate that the local node has  
 230:          notified the peer about mismatch in the C bit. 
 231:           
 232:          rxWithdrawWithWrongBitErrorCode indicate that a withdraw  
 233:          message has been received with wrong C-bit error code. 
 234:           
 235:          illegalReceivedBit indicate a C bit configuration with 
 236:          the remote which is not compatible with the PW type. 
 237:           
 238:          cwPresent indicate that the CW is present for this PW: if  
 239:          signaling is used - C bit is set and agreed between the 
 240:          peers, and for manual configured PW the local configuration 
 241:          require the use of the CW. 
 242:    
 243:          cwNotPresent indicate that the CW is not present for this  
 244:          PW: if signaling is used - C bit is reset and agreed between 
 245:          the peers, and for manual configured PW the local  
 246:          configuration requires that CW would not be used. 
 247:    
 248:          notYetKnown indicate that a label mapping has not yet  
 249:          received from the peer. 
 250:         " 
 251:    SYNTAX    INTEGER { 
 252:                 waitingForNextMsg (1), 
 253:                 sentWrongBitErrorCode (2), 
 254:                 rxWithdrawWithWrongBitErrorCode (3), 
 255:                 illegalReceivedBit (4), 
 256:                 cwPresent (5), 
 257:                 cwNotPresent (6), 
 258:                 notYetKnown(7) 
 259:                 } 

 260:    
 261:   PwVcCapabilities ::= TEXTUAL-CONVENTION 
 262:      STATUS      current 
 263:      DESCRIPTION 
 264:                              PWE3 TC MIB                February 2004 

 265: 
 266: 
 267: 
 268:         "Indicate the optional capabilities of the control protocol. 
 269:          A value of zero indicate the basic LDP PW signaling.  
 270:          Values may be added in the future based on  
 271:          new capabilities introduced in IETF documents. 
 272:         " 
 273:    SYNTAX   BITS { 
 274:       pwStatusIndication (0) 
 275:        }       

 276:    
 277:   PwVcStatus ::= TEXTUAL-CONVENTION 

 278:      STATUS      current 
 279:      DESCRIPTION 
 280:         "The status of the PW and the interfaces affecting this PW. 
 281:          If none of the bits are set, it indicate no faults are  
 282:          reported." 
 283:    SYNTAX   BITS { 
 284:       pwNotForwarding (0), 
 285:       customerFacingPwRxFault (1), 
 286:       customerFacingPwTxFault (2), 
 287:       psnFacingPwRxFault  (3), 
 288:       psnFacingPwTxFault  (4) 
 289:        }       
 290:    
 291:   PwVcFragSize ::= TEXTUAL-CONVENTION 

 292:      STATUS      current 
 293:      DESCRIPTION 
 294:         "If set to value other than zero, it indicates desired  
 295:          fragmentation to the value set. If set to zero,  
 296:          fragmentation is not desired for PSN bound packets." 
 297:    SYNTAX   Unsigned32  
 298:    
 299:   PwVcFragStatus ::= TEXTUAL-CONVENTION 

 300:      STATUS      current 
 301:      DESCRIPTION 
 302:         "The status of the fragmentation process based on local  
 303:          configuration and the remote capability. 
 304:    
 305:          noFrag bit indicates that local configuration is for no  
 306:          fragmentation. 
 307:    
 308:          cfgFragGreaterThanPsnMtu bit indicates the local desire to  
 309:          fragment, but the fragmentation size desired is greater  
 310:          than the MTU available at the PSN between peers.  
 311:          Fragmentation is not done in this case. 
 312:    
 313:          cfgFragButRemoteIncapable bit indicates local configuration  
 314:          for fragmentation but the remote is not fragmentation  
 315:          capable. 
 316:    
 317:          remoteFragCapable bit indicates that the remote has  
 318:          advertized it's fragmentation capability. 
 319:                              PWE3 TC MIB                February 2004 
 320: 
 321: 
 322: 
 323:    
 324:          fragEnabled bit indicates that both the local was  
 325:          configured for fragmentation and the remote has the  
 326:          cabability to accept fragmented packets. 
 327:         " 
 328:    SYNTAX   BITS { 
 329:       noFrag (0), 
 330:       cfgFragGreaterThanPsnMtu (1), 
 331:       cfgFragButRemoteIncapable (2), 
 332:       remoteFragCapable (3), 
 333:       fragEnabled (4) 
 334:        }       
 335:    
 336:   END 

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