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

Messages:

VPN-TC-STD-MIB

   1: -- extracted from rfc4265.txt
   2: -- at Sat Nov 19 06:39:54 2005

  45: 
  46:    VPNId ::= TEXTUAL-CONVENTION

  47:        STATUS current
  48:        DESCRIPTION
  49:            "The purpose of a VPN-ID is to uniquely identify a VPN.
  50:             The Global VPN Identifier format is:
  51:             3 octet VPN Authority, Organizationally Unique Identifier
  52:             followed by 4 octet VPN index identifying VPN according
  53:             to OUI"
  54:        REFERENCE
  55:            "Fox, B. and Gleeson, B., 'Virtual Private Networks
  56:             Identifier', RFC 2685, September 1999."
  57:        SYNTAX    OCTET STRING (SIZE (7))
  58: 
  59:    VPNIdOrZero ::= TEXTUAL-CONVENTION

  60:        STATUS            current
  61:        DESCRIPTION
  62:            "This textual convention is an extension of the
  63:             VPNId textual convention that defines a non-zero-length
  64:             OCTET STRING to identify a physical entity.  This extension
  65:             permits the additional value of a zero-length OCTET STRING.
  66:             The semantics of the value zero-length OCTET STRING are
  67:             object-specific and must therefore be defined
  68:             as part of the description of any object that uses this
  69:             syntax.  Examples of usage of this extension are
  70:             situations where none or all VPN IDs need to be
  71:             referenced."
  72:        SYNTAX    OCTET STRING (SIZE (0 | 7))
  73: 
  74:    END
  75: 
  76: -- 
  77: --    Copyright (C) The Internet Society (2005).
  78: -- 
  79: --    This document is subject to the rights, licenses and restrictions
  80: --    contained in BCP 78, and except as set forth therein, the authors
  81: --    retain all their rights.
  82: -- 
  83: --    This document and the information contained herein are provided on an
  84: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
  85: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
  86: --    ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
  87: --    INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
  88: --    INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
  89: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
  90: -- 
  91: -- Intellectual Property
  92: -- 
  93: --    The IETF takes no position regarding the validity or scope of any
  94: --    Intellectual Property Rights or other rights that might be claimed to
  95: --    pertain to the implementation or use of the technology described in
  96: --    this document or the extent to which any license under such rights
  97: --    might or might not be available; nor does it represent that it has
  98: --    made any independent effort to identify any such rights.  Information
  99: --    on the procedures with respect to rights in RFC documents can be
 100: --    found in BCP 78 and BCP 79.
 101: -- 
 102: --    Copies of IPR disclosures made to the IETF Secretariat and any
 103: --    assurances of licenses to be made available, or the result of an
 104: --    attempt made to obtain a general license or permission for the use of
 105: --    such proprietary rights by implementers or users of this
 106: --    specification can be obtained from the IETF on-line IPR repository at
 107: --    http://www.ietf.org/ipr.
 108: -- 
 109: --    The IETF invites any interested party to bring to its attention any
 110: --    copyrights, patents or patent applications, or other proprietary
 111: --    rights that may cover technology that may be required to implement
 112: --    this standard.  Please address the information to the IETF at ietf-
 113: --    ipr@ietf.org.
 114: -- 
 115: