smilint output for ./SIP-TC
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| warning | 5 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| module-name-suffix (warning) | 1 |
| object-identifier-not-prefix (error) | 1 |
| type-unref (warning) | 4 |
Messages:
SIP-TC
1: -- extracted from draft-ietf-sip-mib-11.txt
2: -- at Wed Jun 7 06:06:24 2006
3:
4: SIP-TC DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY,
8: mib-2
9: FROM SNMPv2-SMI
10:
11: TEXTUAL-CONVENTION
12: FROM SNMPv2-TC;
13:
14: sipTC MODULE-IDENTITY
15: LAST-UPDATED "200605171700Z"
16: ORGANIZATION "IETF Session Initiation Protocol Working Group"
17: CONTACT-INFO
18: "SIP WG email: sip@ietf.org
19:
20: Co-editor Kevin Lingle
21: Cisco Systems, Inc.
22: postal: 7025 Kit Creek Road
23: P.O. Box 14987
24: Research Triangle Park, NC 27709
25: USA
26: email: klingle@cisco.com
27: phone: +1 919 392 2029
28:
29: Co-editor Joon Maeng
30: email: jmaeng@austin.rr.com
31:
32: Co-editor Jean-Francois Mule
33: CableLabs
34: postal: 858 Coal Creek Circle
35: Louisville, CO 80027
36: USA
37: email: jf.mule@cablelabs.com
38: phone: +1 303 661 9100
39:
40: Co-editor Dave Walker
41: email: drwalker@rogers.com"
42: DESCRIPTION
43: "Session Initiation Protocol (SIP) MIB Textual
44: Conventions module used by other SIP-related
45: MIB Modules.
46:
47: Copyright (C) The Internet Society (2006). This version
48: of this MIB module is part of RFC XXXX; see the RFC
49: itself for full legal notices."
50: -- RFC Ed: replace XXXX with actual RFC number and remove this note
51: REVISION "200605171700Z"
52: DESCRIPTION
53: "Initial version of the IETF SIP-TC module.
54: This version published as part of RFC XXXX."
55: -- RFC Ed: replace XXXX with actual RFC number and remove this note
56: ::= { mib-2 XXX1 }
56: error -
`XXX1' should start with a lower case letter
56: error -
Object identifier element `XXX1' name only allowed as first element
57: -- RFC Ed: replace XXX1 with actual IANA assigned number for this
58: -- sipTC mib module and remove this note
59:
60: --
61: -- Textual Conventions
62: --
63:
64: SipTransportProtocol ::= TEXTUAL-CONVENTION
64: warning -
warning: current type `SipTransportProtocol' is not referenced in this module
65: STATUS current
66: DESCRIPTION
67: "This convention is a bit map. Each bit represents a
68: transport protocol. If a bit has value 1, then that
69: selected transport protocol is in some way dependent
70: on the context of the object using this convention.
71: If a bit has value 0, then that transport protocol
72: is not selected. Combinations of bits can be
73: set when multiple transport protocols are selected.
74:
75: bit 0 : a protocol other than those defined here
76: bit 1 : User Datagram Protocol
77: bit 2 : Transmission Control Protocol
78: bit 3 : Stream Control Transmission Protocol
79: bit 4 : Transport Layer Security Protocol over TCP
80: bit 5 : Transport Layer Security Protocol over SCTP"
81: SYNTAX BITS {
82: other(0), -- none of the following
83: udp(1),
84: tcp(2),
85: sctp(3), -- RFC4168
86: tlsTcp(4),
87: tlsSctp(5) -- RFC 4168
88: }
89: -- REFERENCE "RFC 3261, Section 18"
90: -- REFERENCE "RFC 4168"
91:
92: SipEntityRole ::= TEXTUAL-CONVENTION
92: warning -
warning: current type `SipEntityRole' is not referenced in this module
93: STATUS current
94: DESCRIPTION
95: "This convention defines the role of a SIP entity.
96: Examples of SIP entities are proxies, user agents,
97: redirect servers, registrars or combinations of
98: the above."
99: SYNTAX BITS {
100: other(0),
101: userAgent(1),
102: proxyServer(2),
103: redirectServer(3),
104: registrarServer(4)
105: }
106:
107: SipOptionTagHeaders ::= TEXTUAL-CONVENTION
107: warning -
warning: current type `SipOptionTagHeaders' is not referenced in this module
108: STATUS current
109: DESCRIPTION
110: "This convention defines the header fields that use
111: the option tags per section 19.2 of RFC 3261.
112: These tags are used in Require (Section 20.32),
113: Proxy-Require (Section 20.29), Supported
114: (Section 20.37) and Unsupported (Section 20.40)
115: header fields."
116: SYNTAX BITS {
117: require(0), -- Require header
118: proxyRequire(1), -- Proxy-Require header
119: supported(2), -- Supported header
120: unsupported(3) -- Unsupported header
121: }
122: -- REFERENCE "RFC 3261, Section 19.2"
123:
124: SipMethodName ::= TEXTUAL-CONVENTION
124: warning -
warning: current type `SipMethodName' is not referenced in this module
125: STATUS current
126: DESCRIPTION
127: "This textual convention is a string that uniquely
128: identifies a SIP method. The scope of uniqueness
129: is the context of all defined SIP methods.
130:
131: Experimental support of extension methods is
132: acceptable and expected. Extension methods are
133: those defined in Internet-Draft documents but
134: not yet allocated an official sanctioned by IANA.
135:
136: To support experimental extension methods, any
137: object using this textual convention as syntax
138: MAY return/accept a method identifier value other
139: than those sanctioned by IANA. That system MUST
140: ensure no collisions with officially assigned
141: method names."
142: SYNTAX OCTET STRING (SIZE (1..128))
143:
144: END
144: warning -
warning: module name `SIP-TC' should match `*-MIB'
145:
146: --
147: -- Copyright (C) The Internet Society (2006).
148: --
149: -- This document is subject to the rights, licenses and restrictions
150: -- contained in BCP 78, and except as set forth therein, the authors
151: -- retain all their rights.
152: --
153: -- This document and the information contained herein are provided on an
154: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
155: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
156: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
157: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
158: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
159: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
160: --
161: --
162: -- Intellectual Property
163: --
164: -- The IETF takes no position regarding the validity or scope of any
165: -- Intellectual Property Rights or other rights that might be claimed to
166: -- pertain to the implementation or use of the technology described in
167: -- this document or the extent to which any license under such rights
168: -- might or might not be available; nor does it represent that it has
169: -- made any independent effort to identify any such rights. Information
170: -- on the procedures with respect to rights in RFC documents can be
171: -- found in BCP 78 and BCP 79.
172: --
173: -- Copies of IPR disclosures made to the IETF Secretariat and any
174: -- assurances of licenses to be made available, or the result of an
175: -- attempt made to obtain a general license or permission for the use of
176: -- such proprietary rights by implementers or users of this
177: -- specification can be obtained from the IETF on-line IPR repository at
178: -- http://www.ietf.org/ipr.
179: --
180: -- The IETF invites any interested party to bring to its attention any
181: -- copyrights, patents or patent applications, or other proprietary
182: -- rights that may cover technology that may be required to implement
183: -- this standard. Please address the information to the IETF at
184: -- ietf-ipr@ietf.org.
185: --
186: --
187: -- Acknowledgment
188: --
189: -- Funding for the RFC Editor function is currently provided by the
190: -- Internet Society.
191: