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

Messages:

PCE-TC-STD-MIB

   1: -- extracted from draft-ietf-pce-tc-mib-02.txt
   2: -- at Wed Sep 26 06:09:21 2007

  11: 
  12:    pceTCDraftMIB MODULE-IDENTITY
  13:       LAST-UPDATED "200709250000Z" -- September 25, 2007
  14:       ORGANIZATION "Path Computation Element (PCE) Working Group"
  15:       CONTACT-INFO "
  16:          Stephan Emile
  17:          France Telecom
  18:       Email: emile.stephan@orange-ftgroup.com
  19: 
  20:       Email comments directly to the PCE WG Mailing List at pce@ietf.org
  21:       WG-URL: http://www.ietf.org/html.charters/pce-charter.html"
  22:       DESCRIPTION
  23:          "This memo defines a portion of the Management Information Base
  24:          (MIB) for use with network management protocols in the Internet
  25:          community.  In particular, it defines Textual Conventions to
  26:          represent commonly used Path Computation Element (PCE)
  27:          management information.  The intent is that these TEXTUAL
  28:          CONVENTIONS (TCs) will be imported and used in PCE related MIB
  29:          modules to avoid duplicating conventions."
  30:       ::= { pceStdMIB 1 }

...
  41: 
  42:    PcePcepIdentifier ::= TEXTUAL-CONVENTION

  43:       DISPLAY-HINT "1d.1d.1d.1d:1d:1d"
  44:       STATUS current
  45:       DESCRIPTION
  46:          "The LDP identifier is a six octet quantity which is used to
  47:          identify a PCE client."
  48:       SYNTAX OCTET STRING (SIZE (0..6))
  49: 
  50:    PceRoutingDomainID ::= TEXTUAL-CONVENTION

  51:       STATUS current
  52:       DESCRIPTION
  53:          "A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS
  54:          information element carries the identifier of a routing domain
  55:          (area, as) which type depends on both the routing protocol and
  56:          on the version of Internet protocol in use in this routing
  57:          domain.
  58: 
  59:          This TC defines a common SMI type for the different kinds of
  60:          routing domain identifiers.
  61: 
  62:          A PceRoutingDomainID value is always interpreted within the
  63:          context of an AddressFamilyNumbers value.  Every usage of the
  64:          PceRoutingDomainID textual convention is required to specify
  65:          the AddressFamilyNumbers object which provides the context.
  66: 
  67:          The value of an PceRoutingDomainID object must always be
  68:          consistent with the value of the associated
  69:          AddressFamilyNumbers object.
  70: 
  71:          Following is the mapping between AddressFamilyNumbers type and
  72:          PceRoutingDomainID size:
  73:             ipV4(1):
  74:                PceRoutingDomainID is an InetAddressIPv4 corresponding to
  75:                the name of an OSPF area;
  76:             ipV6(2):
  77:                PceRoutingDomainID is an InetAddressIPv6 corresponding to
  78:                the name of an OSPF area;
  79:             nsap(3):
  80:                PceRoutingDomainID type is OCTET STRING (SIZE (0..20)),
  81:                corresponding to the name of an ISIS area (see RFC 1195);
  82:             asNumber(18)
  83:                PceRoutingDomainID type is OCTET STRING (SIZE (2))
  84:                corresponding to the name of an Autonomous System.
  85:          "
  86:       SYNTAX OCTET STRING (SIZE (0..20))
  87: 
  88:    END
  89: 
  90: -- 
  91: --    Copyright (C) The IETF Trust (2007).
  92: -- 
  93: --    This document is subject to the rights, licenses and restrictions
  94: --    contained in BCP 78, and except as set forth therein, the authors
  95: --    retain all their rights.
  96: -- 
  97: --    This document and the information contained herein are provided on an
  98: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
  99: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
 100: --    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
 101: --    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 102: --    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 103: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 104: -- 
 105: -- 
 106: -- Intellectual Property
 107: -- 
 108: --    The IETF takes no position regarding the validity or scope of any
 109: --    Intellectual Property Rights or other rights that might be claimed to
 110: --    pertain to the implementation or use of the technology described in
 111: --    this document or the extent to which any license under such rights
 112: --    might or might not be available; nor does it represent that it has
 113: --    made any independent effort to identify any such rights.  Information
 114: --    on the procedures with respect to rights in RFC documents can be
 115: --    found in BCP 78 and BCP 79.
 116: -- 
 117: --    Copies of IPR disclosures made to the IETF Secretariat and any
 118: --    assurances of licenses to be made available, or the result of an
 119: --    attempt made to obtain a general license or permission for the use of
 120: --    such proprietary rights by implementers or users of this
 121: --    specification can be obtained from the IETF on-line IPR repository at
 122: --    http://www.ietf.org/ipr.
 123: -- 
 124: --    The IETF invites any interested party to bring to its attention any
 125: --    copyrights, patents or patent applications, or other proprietary
 126: --    rights that may cover technology that may be required to implement
 127: --    this standard.  Please address the information to the IETF at
 128: --    ietf-ipr@ietf.org.
 129: -- 
 130: -- 
 131: -- Acknowledgment
 132: -- 
 133: --    Funding for the RFC Editor function is provided by the IETF
 134: --    Administrative Support Activity (IASA).
 135: