smilint output for ./IANA-TUNNELTYPE-MIB

Messages:

IANA-TUNNELTYPE-MIB

   1: -- extracted from draft-thaler-inet-tunnel-mib-00.txt
   2: -- at Fri May 14 06:21:14 2004

   3: 
   4: IANA-TUNNELTYPE-MIB DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:     MODULE-IDENTITY, mib-2           FROM SNMPv2-SMI
   8:     TEXTUAL-CONVENTION               FROM SNMPv2-TC;
   9: 
  10: ianaTunnelTypeMIB MODULE-IDENTITY
  11:     LAST-UPDATED "200310071200Z" -- October 7, 2003
  12:     ORGANIZATION "IANA"
  13:     CONTACT-INFO
  14:             " Internet Assigned Numbers Authority
  15:               Internet Corporation for Assigned Names and Numbers
  16:               4676 Admiralty Way, Suite 330
  17:               Marina del Rey, CA 90292-6601
  18: 
  19:               Phone: +1 310 823 9358
  20:               EMail: iana@iana.org"
  21:     DESCRIPTION
  22:             "This MIB module defines the IANAtunnelType textual
  23:             convention for use in MIBs which need to identify
  24:             types of IP tunnels.
  25: 
  26:             To assign new tunnel type values, IANA should apply
  27:             the same requirements as it applies to IANAifType
  28:             values.  Requests for IANAifType values to be assigned
  29:             for new IP tunnel types should instead result in
  30:             assignments of new tunnel type values."
  31:     REVISION     "200310071200Z" -- October 7, 2003
  32:     DESCRIPTION
  33:             "Initial version."
  34:     ::= { mib-2 xxx } -- TO BE ASSIGNED BY IANA

  35: 
  36: IANAtunnelType ::= TEXTUAL-CONVENTION

  37:     STATUS     current
  38:     DESCRIPTION
  39:             "The encapsulation method used by a tunnel. The value
  40:             direct indicates that a packet is encapsulated
  41:             directly within a normal IP header, with no
  42:             intermediate header, and unicast to the remote tunnel
  43:             endpoint (e.g., an RFC 2003 IP-in-IP tunnel, or an RFC
  44:             1933 IPv6-in-IPv4 tunnel). The value minimal indicates
  45:             that a Minimal Forwarding Header (RFC 2004) is
  46:             inserted between the outer header and the payload
  47:             packet. The value UDP indicates that the payload
  48:             packet is encapsulated within a normal UDP packet
  49:             (e.g., RFC 1234).
  50: 
  51:             The values sixToFour, sixOverFour, and isatap
  52:             indicates that an IPv6 packet is encapsulated directly
  53:             within an IPv4 header, with no intermediate header,
  54:             and unicast to the destination determined by the 6to4,
  55:             6over4, or ISATAP protocol.
  56: 
  57:             The remaining protocol-specific values indicate that a
  58:             header of the protocol of that name is inserted
  59:             between the outer header and the payload header."
  60:     SYNTAX     INTEGER {
  61:                    other(1),        -- none of the following
  62:                    direct(2),       -- no intermediate header
  63:                    gre(3),          -- GRE encapsulation
  64:                    minimal(4),      -- Minimal encapsulation
  65:                    l2tp(5),         -- L2TP encapsulation
  66:                    pptp(6),         -- PPTP encapsulation
  67:                    l2f(7),          -- L2F encapsulation
  68:                    udp(8),          -- UDP encapsulation
  69:                    atmp(9),         -- ATMP encapsulation
  70:                    msdp(10),        -- MSDP encapsulation
  71:                    sixToFour(11),   -- 6to4 encapsulation
  72:                    sixOverFour(12), -- 6over4 encapsulation
  73:                    isatap(13),      -- ISATAP encapsulation
  74:                    teredo(14)       -- Teredo encapsulation
  75:                }
  76: 
  77: END
  78: 
  79: -- 
  80: -- Copyright (C) The Internet Society (2003).  All Rights Reserved.
  81: -- 
  82: -- This document and translations of it may be copied and furnished
  83: -- to others, and derivative works that comment on or otherwise
  84: -- explain it or assist in its implmentation may be prepared, copied,
  85: -- published and distributed, in whole or in part, without
  86: -- restriction of any kind, provided that the above copyright notice
  87: -- and this paragraph are included on all such copies and derivative
  88: -- works.  However, this document itself may not be modified in any
  89: -- way, such as by removing the copyright notice or references to the
  90: -- Internet Society or other Internet organizations, except as needed
  91: -- for the purpose of developing Internet standards in which case the
  92: -- procedures for copyrights defined in the Internet Standards
  93: -- process must be followed, or as required to translate it into
  94: -- languages other than English.
  95: -- 
  96: -- The limited permissions granted above are perpetual and will not
  97: -- be revoked by the Internet Society or its successors or assigns.
  98: -- 
  99: -- This document and the information contained herein is provided on
 100: -- an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
 101: -- ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
 102: -- IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 103: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 104: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 105: -- 
 106: -- 
 107: