smilint output for ./T11-FC-SP-TC-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 1 |
| minor error | 1 |
| warning | 19 |
| Message Types |
|---|
| Type | Count |
|---|
| object-identifier-not-prefix (error) | 1 |
| revision-missing (minor error) | 1 |
| type-unref (warning) | 18 |
| type-without-format (warning) | 1 |
Messages:
T11-FC-SP-TC-MIB
1: -- extracted from draft-ietf-imss-fc-fcsp-mib-00.txt
2: -- at Thu Aug 16 06:08:56 2007
3:
4: T11-FC-SP-TC-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-IDENTITY, mib-2,
8: Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
9: TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
10:
11: t11FcTcMIB MODULE-IDENTITY
12: LAST-UPDATED "200708130000Z"
13: ORGANIZATION "For the initial versions, T11.
14: For later versions, the IETF's IMSS Working Group."
15: CONTACT-INFO
16: " Claudio DeSanti
17: Cisco Systems, Inc.
18: 170 West Tasman Drive
19: San Jose, CA 95134 USA
20: EMail: cds@cisco.com
21:
22: Keith McCloghrie
23: Cisco Systems, Inc.
24: 170 West Tasman Drive
25: San Jose, CA 95134 USA
26: Email: kzm@cisco.com"
27: DESCRIPTION
28: "This MIB module defines Textual Conventions for use in
29: the multiple MIB modules which together define the
30: instrumentation for an implementation of the Fibre Channel
31: Security Protocols (FC-SP) specification.
32:
33: This MIB module also defines Object Identities (for use as
34: possible values of MIB objects with syntax AutonomousType),
35: including OIDs for the Cryptographic Algorithms defined
36: in FC-SP.
37:
38: Copyright (C) The IETF Trust (2007). This version
39: of this MIB module is part of RFC yyyy; see the RFC
40: itself for full legal notices."
41: -- RFC Editor: replace yyyy with actual RFC number & remove this note
42: REVISION "200702190000Z"
43: DESCRIPTION
44: "Initial version of this MIB module, published as RFCyyyy."
45: -- RFC-Editor, replace yyyy with actual RFC number & remove this note
46: ::= { mib-2 nnn } -- to be assigned by IANA
46: minor error -
revision for last update is missing
46: error -
Object identifier element `nnn' name only allowed as first element
47: -- RFC Editor: replace nnn with IANA-assigned number & remove this note
48:
49: t11FcSpIdentities OBJECT IDENTIFIER ::= { t11FcTcMIB 1 }
50: t11FcSpAlgorithms OBJECT IDENTIFIER ::= { t11FcSpIdentities 1 }
51:
52: --
53: -- Textual Conventions
54: --
55:
56: T11FcSpPolicyHashFormat ::= TEXTUAL-CONVENTION
56: warning -
warning: current type `T11FcSpPolicyHashFormat' is not referenced in this module
57: STATUS current
58: DESCRIPTION
59: "Identifies a cryptographic hash function used to create
60: a hash value which summarizes an FC-SP Policy Object.
61:
62: Each definition of an object with this TC as its syntax
63: must be accompanied by a corresponding definition of an
64: object with T11FcSpPolicyHashValue as its syntax, and
65: containing the hash value.
66:
67: The first two cryptographic hash functions are:
68:
69: Hash Type Hash Tag Hash Length (Bytes)
70: SHA-1 '00000001'h 20
71: SHA-256 '00000002'h 32
72: "
73: REFERENCE
74: "- INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
75: Fibre Channel - Security Protocols (FC-SP),
76: 13 June 2006, section 7.1.3.1.
77: - FIPS PUB 180-2."
78: SYNTAX OCTET STRING (SIZE (4))
79:
80: T11FcSpPolicyHashValue ::= TEXTUAL-CONVENTION
80: warning -
warning: current type `T11FcSpPolicyHashValue' is not referenced in this module
81: STATUS current
82: DESCRIPTION
83: "Represents the value of the cryptographic hash function
84: of an FC-SP Policy Object.
85:
86: Each definition of an object with this TC as its syntax
87: must be accompanied by a corresponding definition of an
88: object with T11FcSpPolicyHashFormat as its syntax.
89: The corresponding object identifies the cryptographic
90: hash function used to create the hash value."
91: REFERENCE
92: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
93: Fibre Channel - Security Protocols (FC-SP),
94: 13 June 2006, section 7.1.3.1."
95: SYNTAX OCTET STRING (SIZE (0..64))
96:
97:
98: T11FcSpAuthRejectReasonCode ::= TEXTUAL-CONVENTION
98: warning -
warning: current type `T11FcSpAuthRejectReasonCode' is not referenced in this module
99: STATUS current
100: DESCRIPTION
101: "A reason code contained in an AUTH_Reject message, or
102: in an SW_RJT (rejecting an AUTH_ILS), or in an LS_RJT
103: (rejecting an AUTH-ELS)."
104: REFERENCE
105: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
106: Fibre Channel - Security Protocols (FC-SP),
107: 13 June 2006, Table 17, 48, 52."
108: SYNTAX INTEGER {
109: authFailure(1),
110: logicalError(2),
111: logicalBusy(3),
112: authILSNotSupported(4),
113: authELSNotSupported(5),
114: notLoggedIn(6)
115: }
116:
117: T11FcSpAuthRejReasonCodeExp ::= TEXTUAL-CONVENTION
117: warning -
warning: current type `T11FcSpAuthRejReasonCodeExp' is not referenced in this module
118: STATUS current
119: DESCRIPTION
120: "A reason code explanation contained in an AUTH_Reject
121: message, or in an SW_RJT (rejecting an AUTH_ILS), or in
122: an LS_RJT (rejecting an AUTH-ELS)."
123: REFERENCE
124: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
125: Fibre Channel - Security Protocols (FC-SP),
126: 13 June 2006, Tables 18, 48, 52."
127: SYNTAX INTEGER {
128: authMechanismNotUsable(1),
129: dhGroupNotUsable(2),
130: hashFunctionNotUsable(3),
131: authTransactionAlreadyStarted(4),
132: authenticationFailed(5),
133: incorrectPayload(6),
134: incorrectAuthProtocolMessage(7),
135: restartAuthProtocol(8),
136: authConcatNotSupported(9),
137: unsupportedProtocolVersion(10),
138: logicalBusy(11),
139: authILSNotSupported(12),
140: authELSNotSupported(13),
141: notLoggedIn(14)
142: }
143:
144:
145: T11FcSpHashFunctions ::= TEXTUAL-CONVENTION
145: warning -
warning: current type `T11FcSpHashFunctions' is not referenced in this module
146: STATUS current
147: DESCRIPTION
148: "A set of zero, one or more hash functions defined for
149: use in FC-SP."
150: REFERENCE
151: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
152: Fibre Channel - Security Protocols (FC-SP),
153: 13 June 2006, Table 14."
154: SYNTAX BITS {
155: md5(0),
156: sha1(1)
157: }
158:
159: T11FcSpSignFunctions ::= TEXTUAL-CONVENTION
159: warning -
warning: current type `T11FcSpSignFunctions' is not referenced in this module
160: STATUS current
161: DESCRIPTION
162: "A set of zero, one or more signature functions defined
163: for signing certificates for use with FCAP in FC-SP."
164: REFERENCE
165: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
166: Fibre Channel - Security Protocols (FC-SP),
167: 13 June 2006, tables 38 & 39."
168: SYNTAX BITS {
169: rsaSha1(0)
170: }
171:
172:
173: T11FcSpDhGroups ::= TEXTUAL-CONVENTION
173: warning -
warning: current type `T11FcSpDhGroups' is not referenced in this module
174: STATUS current
175: DESCRIPTION
176: "A set of zero, one or more DH Groups defined for use
177: in FC-SP."
178: REFERENCE
179: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
180: Fibre Channel - Security Protocols (FC-SP),
181: 13 June 2006, Table 15."
182: SYNTAX BITS {
183: null(0),
184: group1024(1),
185: group1280(2),
186: group1536(3),
187: group2048(4),
188: group3072(5),
189: group4096(6),
190: group6144(7),
191: group8192(8)
192: }
193:
194: T11FcSpPolicyObjectType ::= TEXTUAL-CONVENTION
194: warning -
warning: current type `T11FcSpPolicyObjectType' is not referenced in this module
195: STATUS current
196: DESCRIPTION
197: "A value which identifies the type of an FC-SP Policy
198: Object."
199: REFERENCE
200: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
201: Fibre Channel - Security Protocols (FC-SP),
202: 13 June 2006, Table 102."
203: SYNTAX INTEGER {
204: summary(1),
205: switchMemberList(2),
206: nodeMemberList(3),
207: switchConnectivity(4),
208: ipMgmtList(5),
209: attribute(6)
210: }
211:
212:
213: T11FcSpPolicyNameType ::= TEXTUAL-CONVENTION
213: warning -
warning: current type `T11FcSpPolicyNameType' is not referenced in this module
214: STATUS current
215: DESCRIPTION
216: "The format and usage of a companion object having
217: T11FcSpPolicyName as its syntax.
218:
219: Six of the values indicate the same format, i.e., they
220: differ only in semantics. That common format is a Fibre
221: Channel 'Name_Identifier', i.e., the same syntax as
222: 'FcNameIdOrZero (SIZE(8))'.
223:
224: These six are three pairs of one restricted and one
225: unrestricted. Each usage of this syntax must specify
226: whether restricted names are allowed, and if so, how the
227: usage of restricted names differ from unrestricted names.
228:
229: The six are:
230:
231: 'nodeName' - a Node_Name, which is the
232: Name_Identifier associated
233: with a Fibre Channel Node.
234:
235: 'restrictedNodeName' - a Restricted Node_Name.
236:
237: 'portName' - the Name_Identifier associated
238: with a Fibre Channel Port.
239:
240: 'restrictedPortName' - a Restricted Port_Name.
241:
242: 'wildcard' - a Wildcard value which is used to
243: identify 'all others' (typically,
244: all other members of a Policy
245: Object, not all other Policy
246: Objects).
247:
248: 'restrictedWildcard' - a Restricted Wildcard value.
249:
250: Other possible values are:
251:
252: 'alphaNumericName' - the value begins with an ASCII
253: letter (upper or lower case) followed by (0 ... 63)
254: characters from the set: lower case letters, upper case
255: letters, digits, and the four symbols: dollar-sign ($),
256: dash (-), caret (^), and underscore (_).
257:
258: 'ipv6AddressRange' - two IPv6 addresses in network
259: byte order, the numerically smallest first and the
260: numerically largest second; total length is 32 bytes.
261:
262: 'ipv4AddressRange' - two IPv4 addresses in network
263: byte order, the numerically smallest first and the
264: numerically largest second; total length is 8 bytes."
265: REFERENCE
266: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
267: Fibre Channel - Security Protocols (FC-SP),
268: 13 June 2006, Table 103."
269: SYNTAX INTEGER {
270: nodeName(1),
271: restrictedNodeName(2),
272: portName(3),
273: restrictedPortName(4),
274: wildcard(5),
275: restrictedWildcard(6),
276: alphaNumericName(7),
277: ipv6AddressRange(8),
278: ipv4AddressRange(9)
279: }
280:
281: T11FcSpPolicyName ::= TEXTUAL-CONVENTION
281: warning -
warning: current type `T11FcSpPolicyName' is not referenced in this module
282: STATUS current
283: DESCRIPTION
284: "A syntax used, when defining Policy Objects, for the
285: name of something.
286:
287: An object which uses this syntax always identifies a
288: a companion object with syntax T11FcSpPolicyNameType
289: such that the companion object specifies the format
290: and usage of the object with this syntax.
291:
292: When the companion object has the value 'wildcard' or
293: 'restrictedWildcard', the value of the T11FcSpPolicyName
294: object is: '0000000000000000'h."
295: REFERENCE
296: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
297: Fibre Channel - Security Protocols (FC-SP),
298: 13 June 2006, Table 103."
299: SYNTAX OCTET STRING (SIZE (1..64))
300:
301:
302: T11FcSpAlphaNumName ::= TEXTUAL-CONVENTION
302: warning -
warning: current type `T11FcSpAlphaNumName' is not referenced in this module
303: STATUS current
304: DESCRIPTION
305: "A syntax used when defining Policy Objects for the
306: name of something, where the name is always in the format
307: specified by:
308:
309: T11FcSpPolicyNameType = 'alphaNumericName'
310: "
311: REFERENCE
312: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
313: Fibre Channel - Security Protocols (FC-SP),
314: 13 June 2006, Table 103."
315: SYNTAX OCTET STRING (SIZE (1..64))
316:
317: T11FcSpAlphaNumNameOrNull ::= TEXTUAL-CONVENTION
317: warning -
warning: current type `T11FcSpAlphaNumNameOrNull' is not referenced in this module
318: STATUS current
319: DESCRIPTION
320: "An extension of the T11FcSpAlphaNumName TC which
321: one additional possible value: the zero-length string
322: to indicate the absence of a name."
323: SYNTAX OCTET STRING (SIZE (0..64))
324:
325:
326: T11FcSaDirection ::= TEXTUAL-CONVENTION
326: warning -
warning: current type `T11FcSaDirection' is not referenced in this module
327: STATUS current
328: DESCRIPTION
329: "The direction of frame transmission on a Security
330: Association. Note that Security Associations are
331: unidirectional but they always exist as part of an
332: SA pair of the same type in opposite directions."
333: SYNTAX INTEGER { ingress(1), egress(2) }
334:
335:
336: T11FcSpiIndex ::= TEXTUAL-CONVENTION
336: warning -
warning: current type `T11FcSpiIndex' is not referenced in this module
336: warning -
warning: type `T11FcSpiIndex' has no format specification
337: STATUS current
338: DESCRIPTION
339: "An SPI (Security Parameter Index) value is carried in the
340: SPI field of a frame protected by the ESP_Header. An SPI
341: is also carried in the SAID field of a Common Transport
342: Information Unit (CT_IU) protected by CT_Authentication.
343: An SPI value identifies the Security Association on which
344: the frame is being transmitted."
345: REFERENCE
346: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
347: Fibre Channel - Security Protocols (FC-SP),
348: 13 June 2006, section 4.7.2 and 4.7.3."
349: SYNTAX Unsigned32 -- the default range: (0..4294967295)
350:
351: T11FcSpPrecedence ::= TEXTUAL-CONVENTION
351: warning -
warning: current type `T11FcSpPrecedence' is not referenced in this module
352: DISPLAY-HINT "d"
353: STATUS current
354: DESCRIPTION
355: "The precedence of a Traffic Selector. If a frame
356: matches with two or more Traffic Selectors, then the match
357: which takes precedence is the one with the Traffic Selector
358: having the numerically smallest precedence value. Note that
359: precedence values are not necessarily contiguous."
360: SYNTAX Unsigned32 -- the default range: (0..4294967295)
361:
362:
363: T11FcRoutingControl ::= TEXTUAL-CONVENTION
363: warning -
warning: current type `T11FcRoutingControl' is not referenced in this module
364: DISPLAY-HINT "1x"
365: STATUS current
366: DESCRIPTION
367: "A value stored in the R_CTL (Routing Control) 8-bit field
368: of an FC-2 frame containing routing and information bits to
369: categorize the frame function.
370:
371: For FC-2 frames, an R_CTL value typically distinguishes
372: between control versus data frames, and/or solicited versus
373: unsolicited frames, and in combination with the TYPE field
374: (see T11FcSpType) identifies a particular link layer
375: service/protocol using FC-2.
376:
377: For CT_Authentication, the information field in the R_CTL
378: field contains '02'h for Request CT_IUs, and '03'h for
379: Response CT_IUs.
380:
381: The comparison of two values having this syntax is done
382: by treating each string as an 8-bit numeric value."
383: REFERENCE
384: " - Fibre Channel - Framing and Signaling-2 (FC-FS-2),
385: INCITS xxx/200x, Project T11/1619-D Rev 1.01,
386: 8 August 2006, section 9.3.
387: - Fibre Channel - Generic Services-5 (FC-GS-5),
388: ANSI INCITS 427-2006, sections 4.5.2.4.2, 4.5.2.4.3
389: and table 12."
390: SYNTAX OCTET STRING (SIZE(1))
391:
392: T11FcSpType ::= TEXTUAL-CONVENTION
392: warning -
warning: current type `T11FcSpType' is not referenced in this module
393: DISPLAY-HINT "2x"
394: STATUS current
395: DESCRIPTION
396: "A value, or combination of values, contained in a frame
397: header used in identifying the link layer service/protocol
398: of a frame.
399:
400: The value is always two octets:
401:
402: - for FC-2 frames, the first octet is zero and the second
403: octet contains the Data structure type (TYPE) value
404: defined by FC-FS-2. The TYPE value is used in
405: combination with T11FcRoutingControl to identify a link
406: layer service/protocol.
407:
408: - for Common Transport Information Units (CT_IUs), the
409: first octet contains a GS_Type value and the second
410: octet contains a GS_Subtype value, defined by FC-GS-5.
411:
412: The comparison of two values having this syntax is done
413: by treating each string as the numeric value obtained by
414: numerically combining the individual octet's value as
415: follows:
416:
417: (256 * 1st-octet) + 2nd-octet
418: "
419: REFERENCE
420: " - Fibre Channel - Framing and Signaling-2 (FC-FS-2),
421: INCITS xxx/200x, Project T11/1619-D Rev 1.01,
422: 8 August 2006, section 9.6.
423: - Fibre Channel - Generic Services-5 (FC-GS-5),
424: ANSI INCITS 427-2006, sections 4.3.2.4 and 4.3.2.5."
425: SYNTAX OCTET STRING (SIZE(2))
426:
427: T11FcSpTransforms ::= TEXTUAL-CONVENTION
427: warning -
warning: current type `T11FcSpTransforms' is not referenced in this module
428: STATUS current
429: DESCRIPTION
430: "A list of the standardized transforms which are defined
431: by FC-SP for use with ESP_Header, CT_Authentication and/or
432: IKEv2 Support."
433: REFERENCE
434: "INCITS xxx/200x, T11/Project 1570-D/Rev 1.8,
435: Fibre Channel - Security Protocols (FC-SP),
436: 13 June 2006, Appendix A.3.1, tables A.23, A.24, A.25, A.26."
437: SYNTAX BITS {
438: encrNull(0),
439: encrAesCbc(1),
440: encrAesCtr(2),
441: encrAesGcm(3),
442: encr3Des(4),
443: prfHmacMd5(5),
444: prfHmacSha1(6),
445: prfAesCbc(7),
446: authHmacMd5L96(8),
447: authHmacSha1L96(9),
448: authHmacMd5L128(10),
449: authHmacSha1L160(11),
450: encrNullAuthAesGmac(12),
451: dhGroups1024bit(13),
452: dhGroups2048bit(14)
453: }
454:
455: --
456: -- Object Identities to identify the Cryptographic Algorithms
457: -- listed in FC-SP.
458: --
459:
460: t11FcSpEncryptAlgorithms
461: OBJECT IDENTIFIER ::= { t11FcSpAlgorithms 1 }
462:
463: t11FcSpEncrNull OBJECT-IDENTITY
464: STATUS current
465: DESCRIPTION "The ENCR_NULL algorithm."
466: ::= { t11FcSpEncryptAlgorithms 1 }
467: t11FcSpEncrAesCbc OBJECT-IDENTITY
468: STATUS current
469: DESCRIPTION "The ENCR_AES_CBC algorithm."
470: ::= { t11FcSpEncryptAlgorithms 2 }
471: t11FcSpEncrAesCtr OBJECT-IDENTITY
472: STATUS current
473: DESCRIPTION "The ENCR_AES_CTR algorithm."
474: ::= { t11FcSpEncryptAlgorithms 3 }
475: t11FcSpEncrAesGcm OBJECT-IDENTITY
476: STATUS current
477: DESCRIPTION "The ENCR_AES_GCM algorithm."
478: ::= { t11FcSpEncryptAlgorithms 4 }
479: t11FcSpEncr3Des OBJECT-IDENTITY
480: STATUS current
481: DESCRIPTION "The ENCR_3DES algorithm."
482: ::= { t11FcSpEncryptAlgorithms 5 }
483:
484: t11FcSpAuthAlgorithms
485: OBJECT IDENTIFIER ::= { t11FcSpAlgorithms 2 }
486:
487: t11FcSpAuthNull OBJECT-IDENTITY
488: STATUS current
489: DESCRIPTION "The AUTH_NONE algorithm."
490: ::= { t11FcSpAuthAlgorithms 1 }
491: t11FcSpAuthHmacMd5L96 OBJECT-IDENTITY
492: STATUS current
493: DESCRIPTION "The AUTH_HMAC_MD5_96 algorithm."
494: ::= { t11FcSpAuthAlgorithms 2 }
495: t11FcSpAuthHmacSha1L96 OBJECT-IDENTITY
496: STATUS current
497: DESCRIPTION "The AUTH_HMAC_SHA1_96 algorithm."
498: ::= { t11FcSpAuthAlgorithms 3 }
499: t11FcSpAuthHmacMd5L128 OBJECT-IDENTITY
500: STATUS current
501: DESCRIPTION "The AUTH_HMAC_MD5_128 algorithm."
502: ::= { t11FcSpAuthAlgorithms 4 }
503: t11FcSpAuthHmacSha1L160 OBJECT-IDENTITY
504: STATUS current
505: DESCRIPTION "The AUTH_HMAC_SHA1_160 algorithm."
506: ::= { t11FcSpAuthAlgorithms 5 }
507: t11FcSpEncrNullAuthAesGmac OBJECT-IDENTITY
508: STATUS current
509: DESCRIPTION "The ENCR_NULL_AUTH_AES_GMAC algorithm."
510: ::= { t11FcSpEncryptAlgorithms 6 }
511:
512: END
513:
514: --
515: -- Copyright (C) The IETF Trust (2007). This document is subject to the
516: -- rights, licenses and restrictions contained in BCP 78, and except as
517: -- set forth therein, the authors retain all their rights.
518: --
519: -- This document and the information contained herein are provided on an
520: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
521: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
522: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
523: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
524: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
525: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
526: --
527: -- Disclaimer of validity
528: --
529: -- The IETF takes no position regarding the validity or scope of any
530: -- Intellectual Property Rights or other rights that might be claimed to
531: -- pertain to the implementation or use of the technology described in
532: -- this document or the extent to which any license under such rights
533: -- might or might not be available; nor does it represent that it has
534: -- made any independent effort to identify any such rights. Information
535: -- on the procedures with respect to rights in RFC documents can be
536: -- found in BCP 78 and BCP 79.
537: --
538: -- Copies of IPR disclosures made to the IETF Secretariat and any
539: -- assurances of licenses to be made available, or the result of an
540: -- attempt made to obtain a general license or permission for the use of
541: -- such proprietary rights by implementers or users of this
542: -- specification can be obtained from the IETF on-line IPR repository at
543: -- http://www.ietf.org/ipr.
544: --
545: -- The IETF invites any interested party to bring to its attention any
546: -- copyrights, patents or patent applications, or other proprietary
547: -- rights that may cover technology that may be required to implement
548: -- this standard. Please address the information to the IETF at
549: -- ietf-ipr@ietf.org.
550: --
551: -- Acknowledgment
552: --
553: -- Funding for the RFC Editor function is currently provided by the
554: -- Internet Society.
555: