smilint output for ./TRIP-TC-MIB

Messages:

TRIP-TC-MIB

   1: -- extracted from rfc3872.txt
   2: -- at Sat Sep 18 06:23:14 2004

  61: 
  62: TripItad ::= TEXTUAL-CONVENTION

  63:     STATUS current
  64:     DESCRIPTION
  65:        "The values for identifying the IP Telephony
  66:        Administrative Domain (ITAD)."
  67:     SYNTAX Unsigned32 (0..4294967295)
  68: 
  69: TripId ::= TEXTUAL-CONVENTION

  70:     STATUS current
  71:     DESCRIPTION
  72:        "The TRIP Identifier uniquely identifies a LS within its
  73:        ITAD. It is a 4 octet unsigned integer that may, but not
  74:        necessarily, represent the IPv4 address of a Location
  75:        Server.  Where bytes 1-4 of the Unsigned32 represent
  76:        1-4 bytes of the IPv4 address in network-byte order. For
  77:        an IPv6 network, TripId will not represent the IPv6
  78:        address."
  79:     SYNTAX Unsigned32 (0..4294967295)
  80: 
  81: TripAddressFamily ::= TEXTUAL-CONVENTION

  82:     STATUS current
  83:     DESCRIPTION
  84:         "A type of address for a TRIP route. Address families
  85:         defined within this MIB module are:
  86: 
  87:         Code              Address Family
  88:         1                 Decimal Routing Numbers
  89:         2                 PentaDecimal Routing Numbers
  90:         3                 E.164 Numbers
  91:         255               An other type of address family"
  92: 
  93:     SYNTAX INTEGER
  94:         { decimal(1), pentadecimal(2), e164(3), other(255) }
  95: 
  96: TripAppProtocol ::= TEXTUAL-CONVENTION

  97:     STATUS current
  98:     DESCRIPTION
  99:         "The application protocol used for communication with TRIP
 100:         Location Servers. Protocols defined in this MIB Module
 101:         are:
 102: 
 103:         Code              Protocol
 104:         1                 SIP
 105:         2                 H.323-H.225.0-Q.931
 106:         3                 H.323-H.225.0-RAS
 107:         4                 H.323-H.225.0-Annex-G
 108:         255               An other type of application protocol"
 109: 
 110:     SYNTAX INTEGER
 111:         { sip(1), q931(2), ras(3), annexG(4), other(255) }
 112: 
 113: TripCommunityId ::= TEXTUAL-CONVENTION

 114:     STATUS current
 115:     DESCRIPTION
 116:        "The range of legal values for a TRIP Community
 117:        Identifier."
 118:     SYNTAX Unsigned32 (0..4294967295)
 119: 
 120: TripProtocolVersion ::= TEXTUAL-CONVENTION

 121:     STATUS current
 122:     DESCRIPTION
 123:        "The version number of the TRIP protocol."
 124:     SYNTAX Integer32 (1..255)
 125: 
 126: TripSendReceiveMode ::= TEXTUAL-CONVENTION

 127:     STATUS current
 128:     DESCRIPTION
 129:        "The operational mode of the TRIP application. Possible
 130:        values are:
 131:           1 - Send Receive mode
 132:           2 - Send only mode
 133:           3 - Receive Only mode"
 134:     SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) }
 135: 
 136: END
 137: 
 138: -- 
 139: --    Copyright (C) The Internet Society (2004).
 140: -- 
 141: --    This document is subject to the rights, licenses and restrictions
 142: --    contained in BCP 78, and except as set forth therein, the authors
 143: --    retain all their rights.
 144: -- 
 145: --    This document and the information contained herein are provided on an
 146: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
 147: --    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
 148: --    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
 149: --    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 150: --    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 151: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 152: -- 
 153: -- Intellectual Property
 154: -- 
 155: --    The IETF takes no position regarding the validity or scope of any
 156: --    Intellectual Property Rights or other rights that might be claimed to
 157: --    pertain to the implementation or use of the technology described in
 158: --    this document or the extent to which any license under such rights
 159: --    might or might not be available; nor does it represent that it has
 160: --    made any independent effort to identify any such rights.  Information
 161: --    on the IETF's procedures with respect to rights in IETF Documents can
 162: --    be found in BCP 78 and BCP 79.
 163: -- 
 164: --    Copies of IPR disclosures made to the IETF Secretariat and any
 165: --    assurances of licenses to be made available, or the result of an
 166: --    attempt made to obtain a general license or permission for the use of
 167: --    such proprietary rights by implementers or users of this
 168: --    specification can be obtained from the IETF on-line IPR repository at
 169: --    http://www.ietf.org/ipr.
 170: -- 
 171: --    The IETF invites any interested party to bring to its attention any
 172: --    copyrights, patents or patent applications, or other proprietary
 173: --    rights that may cover technology that may be required to implement
 174: --    this standard.  Please address the information to the IETF at ietf-
 175: --    ipr@ietf.org.
 176: -- 
 177: