smilint output for ./T11-FC-SP-CERTS-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| object-identifier-not-prefix (error) | 1 |
Messages:
T11-FC-SP-CERTS-MIB
1: -- extracted from draft-kzm-imss-fc-fcsp-mib-00.txt
2: -- at Wed Jun 13 06:08:27 2007
3:
4: T11-FC-SP-CERTS-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: mib-2, Unsigned32
9: FROM SNMPv2-SMI -- [RFC2578]
10: MODULE-COMPLIANCE,
11: OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
12: SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
13: fcmInstanceIndex FROM FC-MGMT-MIB -- [RFC4044]
14: T11FabricIndex FROM T11-TC-MIB -- [RFC4439]
15: t11FcSpAuEntityName FROM T11-FC-SP-AUTHENTICATION-MIB;
16:
17: t11FcSpCertsMIB MODULE-IDENTITY
18: LAST-UPDATED "200702190000Z"
19: ORGANIZATION "T11"
20: CONTACT-INFO
21: " Claudio DeSanti
22: Cisco Systems, Inc.
23: 170 West Tasman Drive
24: San Jose, CA 95134 USA
25: EMail: cds@cisco.com
26:
27: Keith McCloghrie
28: Cisco Systems, Inc.
29: 170 West Tasman Drive
30: San Jose, CA 95134 USA
31: Email: kzm@cisco.com"
32: DESCRIPTION
33: "This MIB module defines management information specific to
34: the use of certificates in conjunction with Fibre Channel's
35: FC-SP specification.
36:
37: Since FC-SP leverages a subset of IPsec and IKEv2 (see RFC
38: 4595), a subset of the management information defined for
39: the use of certificates with IPsec/IKEv2 is also applicable
40: to FC-SP. Thus, this MIB module leverages RFC wwww and
41: RFC xxxx for the management of certificates, CAs and CRLs.
42: -- RFC Editor: replace wwww with actual RFC number for
43: -- [IPSP-IPSEC-ACTION], and replace xxxx with actual RFC number for
44: -- [IPSP-IKE-ACTION] & remove this note
45:
46: Specifically, the information defined in this MIB module
47: consists of a pointer into the IPsec/IKEv2 MIB modules,
48: plus minimal additional item(s) of information which are
49: considered to be important in a Fibre Channel environment.
50:
51: Copyright (C) The IETF Trust (2007). This version
52: of this MIB module is part of RFC yyyy; see the RFC
53: itself for full legal notices."
54: -- RFC Editor: replace yyyy with actual RFC number & remove this note
55: REVISION "200702190000Z"
56: DESCRIPTION
57: "Initial version of this MIB module, published as RFCyyyy."
58: -- RFC-Editor, replace yyyy with actual RFC number & remove this note
59: ::= { mib-2 nnn } -- to be assigned by IANA
59: error -
Object identifier element `nnn' name only allowed as first element
60: -- RFC Editor: replace nnn with IANA-assigned number & remove this note
61:
62: t11FcSpCertsMIBObjects OBJECT IDENTIFIER ::= { t11FcSpCertsMIB 1 }
63: t11FcSpCertsMIBConformance OBJECT IDENTIFIER ::= { t11FcSpCertsMIB 2 }
64: --
65: -- Certificate Information
66: --
67:
68: t11FcSpCertsTable OBJECT-TYPE
69: SYNTAX SEQUENCE OF T11FcSpCertsEntry
70: MAX-ACCESS not-accessible
71: STATUS current
72: DESCRIPTION
73: "A table containing information on the use of certificates
74: in FC-SP, including (but not limited to) the use of
75: certificates with the Fibre Channel Certificate
76: Authentication Protocol (FCAP) defined by FC-SP, or with
77: FC-SP's use of IKEv2."
78: ::= { t11FcSpCertsMIBObjects 1 }
79:
80: t11FcSpCertsEntry OBJECT-TYPE
81: SYNTAX T11FcSpCertsEntry
82: MAX-ACCESS not-accessible
83: STATUS current
84: DESCRIPTION
85: "Each entry contains information related to one certificate
86: for use by the FC-SP Authentication entity identified by
87: t11FcSpAuEntityName, on a particular Fabric, which is managed
88: as part of the Fibre Channel management instance identified
89: by fcmInstanceIndex."
90: INDEX { fcmInstanceIndex, t11FcSpAuEntityName,
91: t11FcSpCertFabricIndex, t11FcSpCertIndex }
92: ::= { t11FcSpCertsTable 1 }
93:
94: T11FcSpCertsEntry ::= SEQUENCE {
95: t11FcSpCertFabricIndex T11FabricIndex,
96: t11FcSpCertIndex Unsigned32,
97: t11FcSpCertPointer SnmpAdminString,
98: t11FcSpCertUsage INTEGER
99: }
100:
101: t11FcSpCertFabricIndex OBJECT-TYPE
102: SYNTAX T11FabricIndex
103: MAX-ACCESS not-accessible
104: STATUS current
105: DESCRIPTION
106: "An index value which uniquely identifies a particular
107: Fabric where the certificate is available for use."
108: ::= { t11FcSpCertsEntry 1 }
109:
110: t11FcSpCertIndex OBJECT-TYPE
111: SYNTAX Unsigned32
112: MAX-ACCESS not-accessible
113: STATUS current
114: DESCRIPTION
115: "This object distinguishes between the multiple certificates
116: available for use with FC-SP on a particular Fabric."
117: ::= { t11FcSpCertsEntry 2 }
118:
119: t11FcSpCertPointer OBJECT-TYPE
120: SYNTAX SnmpAdminString (SIZE(0..32))
121: MAX-ACCESS read-only
122: STATUS current
123: DESCRIPTION
124: "This object contains the 'name' of a row in the
125: ipsaCredentialTable, i.e., it points to the certificate which
126: is represented by the row of the ipsaCredentialTable for
127: which the value of ipsaCredName has the same value as the
128: value of this object. Further information about the
129: certificate is available in that row.
130:
131: If and when there is no row in the psaCredentialTable for
132: this certificate, the value of this object is the zero-length
133: string."
134: ::= { t11FcSpCertsEntry 3 }
135:
136: t11FcSpCertUsage OBJECT-TYPE
137: SYNTAX INTEGER {
138: other(1),
139: ownDefaultCert(2),
140: ownCert(3),
141: rootCert(4)
142: }
143: MAX-ACCESS read-only
144: STATUS current
145: DESCRIPTION
146: "This object identifies how this certificate can be used:
147:
148: other -- none of the below;
149:
150: ownDefaultCert -- the certificate which the local entity
151: uses as its default certificate; the local entity
152: has at most one default certificate;
153:
154: ownCert -- a certificate which the local entity can use
155: for itself, but which is not its default
156: certificate;
157:
158: rootCert -- a root certificate.
159: "
160: ::= { t11FcSpCertsEntry 4 }
161:
162: --
163: -- Conformance
164: --
165:
166: t11FcSpCertMIBCompliances
167: OBJECT IDENTIFIER ::= { t11FcSpCertsMIBConformance 1 }
168: t11FcSpCertMIBGroups
169: OBJECT IDENTIFIER ::= { t11FcSpCertsMIBConformance 2 }
170:
171: t11FcSpCertMIBCompliance MODULE-COMPLIANCE
172: STATUS current
173: DESCRIPTION
174: "The compliance statement for entities which use
175: certificates with FC-SP."
176:
177: MODULE -- this module
178: MANDATORY-GROUPS
179: { t11FcSpCertInfoGroup }
180:
181: ::= { t11FcSpCertMIBCompliances 1 }
182:
183: -- Units of Conformance
184:
185: t11FcSpCertInfoGroup OBJECT-GROUP
186: OBJECTS {
187: t11FcSpCertPointer,
188: t11FcSpCertUsage
189: }
190: STATUS current
191: DESCRIPTION
192: "A collection of objects containing information
193: related to certificates available for use with FC-SP."
194: ::= { t11FcSpCertMIBGroups 1 }
195:
196: END
197:
198: --
199: -- Copyright (C) The IETF Trust (2007). This document is subject to the
200: -- rights, licenses and restrictions contained in BCP 78, and except as
201: -- set forth therein, the authors retain all their rights.
202: --
203: -- This document and the information contained herein are provided on an
204: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
205: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
206: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
207: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
208: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
209: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
210: --
211: -- Disclaimer of validity
212: --
213: -- The IETF takes no position regarding the validity or scope of any
214: -- Intellectual Property Rights or other rights that might be claimed to
215: -- pertain to the implementation or use of the technology described in
216: -- this document or the extent to which any license under such rights
217: -- might or might not be available; nor does it represent that it has
218: -- made any independent effort to identify any such rights. Information
219: -- on the procedures with respect to rights in RFC documents can be
220: -- found in BCP 78 and BCP 79.
221: --
222: -- Copies of IPR disclosures made to the IETF Secretariat and any
223: -- assurances of licenses to be made available, or the result of an
224: -- attempt made to obtain a general license or permission for the use of
225: -- such proprietary rights by implementers or users of this
226: -- specification can be obtained from the IETF on-line IPR repository at
227: -- http://www.ietf.org/ipr.
228: --
229: -- The IETF invites any interested party to bring to its attention any
230: -- copyrights, patents or patent applications, or other proprietary
231: -- rights that may cover technology that may be required to implement
232: -- this standard. Please address the information to the IETF at
233: -- ietf-ipr@ietf.org.
234: --
235: -- Acknowledgment
236: --
237: -- Funding for the RFC Editor function is currently provided by the
238: -- Internet Society.
239: