smilint output for ./GMPLS-TC-STD-MIB

Messages:

GMPLS-TC-STD-MIB

   1: -- extracted from rfc4801.txt
   2: -- at Thu Mar  1 06:08:21 2007

  14: 
  15:    gmplsTCStdMIB MODULE-IDENTITY

  16:      LAST-UPDATED
  17:        "200702280000Z" -- 28 February 2007 00:00:00 GMT
  18:      ORGANIZATION
  19:        "IETF Common Control and Measurement Plane (CCAMP) Working Group"
  20:      CONTACT-INFO
  21:        "       Thomas D. Nadeau
  22:                Cisco Systems, Inc.
  23:         Email: tnadeau@cisco.com
  24: 
  25:                Adrian Farrel
  26:                Old Dog Consulting
  27:         Email: adrian@olddog.co.uk
  28: 
  29:         Comments about this document should be emailed directly to the
  30:         CCAMP working group mailing list at ccamp@ops.ietf.org"
  31:      DESCRIPTION
  32:        "Copyright (C) The IETF Trust (2007).  This version of
  33:         this MIB module is part of RFC 4801; see the RFC itself for
  34:         full legal notices.
  35: 
  36:         This MIB module defines TEXTUAL-CONVENTIONs for concepts used in
  37:         Generalized Multiprotocol Label Switching (GMPLS) networks."
  38:      REVISION
  39:         "200702280000Z" -- 28 February 2007 00:00:00 GMT
  40:      DESCRIPTION
  41:        "Initial version published as part of RFC 4801."
  42:    ::= { mplsStdMIB 12 }
  43: 
  44:    GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION

  45:      STATUS      current
  46:      DESCRIPTION
  47:        "This TEXTUAL-CONVENTION can be used as the syntax of an object
  48:         that contains any GMPLS Label.  Objects with this syntax can be
  49:         used to represent labels that have label types that are not
  50:         defined in any RFCs.  The freeform GMPLS Label may also be used
  51:         by systems that do not wish to represent labels that have
  52:         label types defined in RFCs using type-specific syntaxes."
  53:      REFERENCE
  54:        "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
  55:            Functional Description, RFC 3471, section 3.2."
  56:      SYNTAX OCTET STRING (SIZE (0..64))
  57: 
  58:    GmplsLabelTypeTC ::= TEXTUAL-CONVENTION

  59:      STATUS      current
  60:      DESCRIPTION
  61:        "Determines the interpretation that should be applied to an
  62:         object that encodes a label.  The possible types are:
  63: 
  64:         gmplsMplsLabel(1)           - The label is an MPLS Packet, Cell,
  65:                                       or Frame Label and is encoded as
  66:                                       described for the TEXTUAL-
  67:                                       CONVENTION MplsLabel defined in
  68:                                       RFC 3811.
  69: 
  70:         gmplsPortWavelengthLabel(2) - The label is a Port or Wavelength
  71:                                       Label as defined in RFC 3471.
  72: 
  73:         gmplsFreeformLabel(3)       - The label is any form of label
  74:                                       encoded as an OCTET STRING using
  75:                                       the TEXTUAL-CONVENTION
  76:                                       GmplsFreeformLabel.
  77: 
  78:         gmplsSonetLabel(4)          - The label is a Synchronous Optical
  79:                                       Network (SONET) Label as
  80:                                       defined in RFC 4606.
  81: 
  82:         gmplsSdhLabel(5)            - The label is a Synchronous Digital
  83:                                       Hierarchy (SDH) Label as defined
  84:                                       in RFC 4606.
  85: 
  86:         gmplsWavebandLabel(6)       - The label is a Waveband Label as
  87:                                       defined in RFC 3471."
  88:      REFERENCE
  89:        "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
  90:            Functional Description, RFC 3471, section 3.
  91:         2. Definition of Textual Conventions and for Multiprotocol Label
  92:            Switching (MPLS) Management, RFC 3811, section 3.
  93:         3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
  94:            for Synchronous Optical Network (SONET) and Synchronous
  95:            Digital Hierarchy (SDH) Control, RFC 4606."
  96:       SYNTAX INTEGER {
  97:         gmplsMplsLabel(1),
  98:         gmplsPortWavelengthLabel(2),
  99:         gmplsFreeformGeneralizedLabel(3),
 100:         gmplsSonetLabel(4),
 101:         gmplsSdhLabel(5),
 102:         gmplsWavebandLabel(6)
 103:       }
 104: 
 105:    GmplsSegmentDirectionTC ::= TEXTUAL-CONVENTION

 106:      STATUS      current
 107:      DESCRIPTION
 108:        "The direction of data flow on an Label Switched Path (LSP)
 109:         segment with respect to the head of the LSP.
 110: 
 111:         Where an LSP is signaled using a conventional signaling
 112:         protocol, the 'head' of the LSP is the source of the signaling
 113:         (also known as the ingress) and the 'tail' is the destination
 114:         (also known as the egress).  For unidirectional LSPs, this
 115:         usually matches the direction of flow of data.
 116: 
 117:         For manually configured unidirectional LSPs, the direction of
 118:         the LSP segment matches the direction of flow of data.  For
 119:         manually configured bidirectional LSPs, an arbitrary decision
 120:         must be made about which LER is the 'head'."
 121:      SYNTAX  INTEGER {
 122:        forward(1),   -- data flows from head-end of LSP toward tail-end
 123:        reverse(2)    -- data flows from tail-end of LSP toward head-end
 124:      }
 125: 
 126:    END
 127: 
 128: -- 
 129: --    Copyright (C) The IETF Trust (2007).
 130: -- 
 131: --    This document is subject to the rights, licenses and restrictions
 132: --    contained in BCP 78, and except as set forth therein, the authors
 133: --    retain all their rights.
 134: -- 
 135: --    This document and the information contained herein are provided on an
 136: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
 137: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
 138: --    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
 139: --    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 140: --    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 141: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 142: -- 
 143: -- Intellectual Property
 144: -- 
 145: --    The IETF takes no position regarding the validity or scope of any
 146: --    Intellectual Property Rights or other rights that might be claimed to
 147: --    pertain to the implementation or use of the technology described in
 148: --    this document or the extent to which any license under such rights
 149: --    might or might not be available; nor does it represent that it has
 150: --    made any independent effort to identify any such rights.  Information
 151: --    on the procedures with respect to rights in RFC documents can be
 152: --    found in BCP 78 and BCP 79.
 153: -- 
 154: --    Copies of IPR disclosures made to the IETF Secretariat and any
 155: --    assurances of licenses to be made available, or the result of an
 156: --    attempt made to obtain a general license or permission for the use of
 157: --    such proprietary rights by implementers or users of this
 158: --    specification can be obtained from the IETF on-line IPR repository at
 159: --    http://www.ietf.org/ipr.
 160: -- 
 161: --    The IETF invites any interested party to bring to its attention any
 162: --    copyrights, patents or patent applications, or other proprietary
 163: --    rights that may cover technology that may be required to implement
 164: --    this standard.  Please address the information to the IETF at
 165: --    ietf-ipr@ietf.org.
 166: -- 
 167: