MIBs Depot

T11-FC-SP-TC-MIB

Registered at
1.3.6.1.2.1.175
Last updated
2008-08-20 00:00
Organization
This MIB module was developed through the coordinated effort of two organizations: T11 began the development and the IETF (in the IMSS Working Group) finished it.
Revisions
2008-08-20 00:00
Namespace
standard
Source file
T11-FC-SP-TC-MIB
Digest
sha256:72db8dcc65cc92e3dee2d15c6f484c07d4c7bf1a614ae9a23f0e736451548493

Description

This MIB module defines Textual Conventions for use in the multiple MIB modules, which together define the instrumentation for an implementation of the Fibre Channel Security Protocols (FC-SP) specification. This MIB module also defines Object Identities (for use as possible values of MIB objects with syntax AutonomousType), including OIDs for the Cryptographic Algorithms defined in FC-SP. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5324; see the RFC itself for full legal notices.

Contact

Claudio DeSanti Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA EMail: cds@cisco.com Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA Email: kzm@cisco.com

Imports

FromSymbols
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso, mib-2
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

4 module(s) in this corpus import this one.

Load order

Every file a consumer needs in order to load this module, dependencies first.

SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC
T11-FC-SP-TC-MIB

Textual conventions

NameOIDSyntaxAccessStatus
T11FcRoutingControl
TEXTUAL-CONVENTION
A value stored in the R_CTL (Routing Control) 8-bit field of an FC-2 frame containing routing and information bits to categorize the frame function. For FC-2 frames, an R_CTL value typically distinguishes between control versus data frames and/or solicited versus unsolicited frames, and in combination with the TYPE field (see T11FcSpType), identifies a particular link-layer service/protocol using FC-2. For CT_Authentication, the information field in the R_CTL field contains '02'h for Request CT_IUs and '03'h for Response CT_IUs. The comparison of two values having this syntax is done by treating each string as an 8-bit numeric value.
current
T11FcSaDirection
TEXTUAL-CONVENTION
The direction of frame transmission on a Security Association. Note that Security Associations are unidirectional, but they always exist as part of an SA pair of the same type in opposite directions.
current
T11FcSpAlphaNumName
TEXTUAL-CONVENTION
A syntax used when defining Policy Objects for the name of something, where the name is always in the format specified by: T11FcSpPolicyNameType = 'alphaNumericName'
current
T11FcSpAlphaNumNameOrAbsent
TEXTUAL-CONVENTION
An extension of the T11FcSpAlphaNumName TC with one additional possible value: the zero-length string to indicate the absence of a name.
current
T11FcSpAuthRejReasonCodeExp
TEXTUAL-CONVENTION
A reason code explanation contained in an AUTH_Reject message, or in an SW_RJT (rejecting an AUTH_ILS), or in an LS_RJT (rejecting an AUTH-ELS).
current
T11FcSpAuthRejectReasonCode
TEXTUAL-CONVENTION
A reason code contained in an AUTH_Reject message, or in an SW_RJT (rejecting an AUTH_ILS), or in an LS_RJT (rejecting an AUTH-ELS).
current
T11FcSpDhGroups
TEXTUAL-CONVENTION
A set of zero, one, or more DH Groups defined for use in FC-SP.
current
T11FcSpHashCalculationStatus
TEXTUAL-CONVENTION
When some kind of 'database' is defined in a set of read-write MIB objects, it is common that multiple changes in the data need to be made at the same time. So, if hash values are maintained for that data, those hash values are only correct if and when they are re-calculated after every change. In such circumstances, the use of an object with this syntax allows the re-calculation of the hash values to be deferred until all changes have been made, and therefore the calculation need only be done once after all changes, rather than repeatedly/after each individual change. The definition of an object defined using this TC is required to specify which one or more instances of which MIB objects contain the hash values operated upon (or whose status is given) by the value of this TC. When read, the value of an object with this syntax is either: correct -- the identified MIB object instance(s) contain the correct hash values; or stale -- the identified MIB object instance(s) contain stale (possibly incorrect) values. Writing a value of 'calculate' is a request to re-calculate and update the values of the corresponding instances of the identified MIB objects. Writing a value of 'correct' or 'stale' to this object is an error (e.g., 'wrongValue').
current
T11FcSpHashFunctions
TEXTUAL-CONVENTION
A set of zero, one, or more hash functions defined for use in FC-SP.
current
T11FcSpLifetimeLeft
TEXTUAL-CONVENTION
This TC is used for one object of an associated pair of objects. The object with this syntax specifies a remaining lifetime of something, e.g., of an SA, where the lifetime is given in the units specified by the other object of the pair which has T11FcSpLifetimeLeftUnits as its syntax.
current
T11FcSpLifetimeLeftUnits
TEXTUAL-CONVENTION
An object, defined using T11FcSpLifetimeLeft TC as its syntax, is required to be one of an associated pair of objects such that the other object of the pair is defined with this T11FcSpLifetimeLeftUnits TC as its syntax and with its value specifying the units of the remaining lifetime given by the value of the T11FcSpLifetimeLeft object.
current
T11FcSpPolicyHashFormat
TEXTUAL-CONVENTION
Identifies a cryptographic hash function used to create a hash value that summarizes an FC-SP Policy Object. Each definition of an object with this TC as its syntax must be accompanied by a corresponding definition of an object with T11FcSpPolicyHashValue as its syntax, and containing the hash value. The first two cryptographic hash functions are: Hash Type Hash Tag Hash Length (Bytes) SHA-1 '00000001'h 20 SHA-256 '00000002'h 32
current
T11FcSpPolicyHashValue
TEXTUAL-CONVENTION
Represents the value of the cryptographic hash function of an FC-SP Policy Object. Each definition of an object with this TC as its syntax must be accompanied by a corresponding definition of an object with T11FcSpPolicyHashFormat as its syntax. The corresponding object identifies the cryptographic hash function used to create the hash value.
current
T11FcSpPolicyName
TEXTUAL-CONVENTION
A syntax used, when defining Policy Objects, for the name of something. An object that uses this syntax always identifies a companion object with syntax T11FcSpPolicyNameType such that the companion object specifies the format and usage of the object with this syntax. When the companion object has the value 'wildcard' or 'restrictedWildcard', the value of the T11FcSpPolicyName object is: '0000000000000000'h.
current
T11FcSpPolicyNameType
TEXTUAL-CONVENTION
The format and usage of a companion object having T11FcSpPolicyName as its syntax. Six of the values indicate the same format, i.e., they differ only in semantics. That common format is a Fibre Channel 'Name_Identifier', i.e., the same syntax as 'FcNameIdOrZero (SIZE(8))'. These six are three pairs of one restricted and one unrestricted. Each usage of this syntax must specify what the meaning of 'restricted' is for that usage and how the characteristics and behavior of restricted names differ from unrestricted names. The six are: 'nodeName' - a Node_Name, which is the Name_Identifier associated with a Fibre Channel Node. 'restrictedNodeName' - a Restricted Node_Name. 'portName' - the Name_Identifier associated with a Fibre Channel Port. 'restrictedPortName' - a Restricted Port_Name. 'wildcard' - a Wildcard value that is used to identify 'all others' (typically, all other members of a Policy Object, not all other Policy Objects). 'restrictedWildcard' - a Restricted Wildcard value. Other possible values are: 'alphaNumericName' - the value begins with an ASCII letter (upper or lower case) followed by (0 ... 63) characters from the set: lower case letters, upper case letters, digits, and the four symbols: dollar-sign ($), dash (-), caret (^), and underscore (_). 'ipv6AddressRange' - two IPv6 addresses in network byte order, the numerically smallest first and the numerically largest second; total length is 32 bytes. 'ipv4AddressRange' - two IPv4 addresses in network byte order, the numerically smallest first and the numerically largest second; total length is 8 bytes.
current
T11FcSpPolicyObjectType
TEXTUAL-CONVENTION
A value that identifies the type of an FC-SP Policy Object.
current
T11FcSpPrecedence
TEXTUAL-CONVENTION
The precedence of a Traffic Selector. If a frame matches with two or more Traffic Selectors, then the match that takes precedence is the one with the Traffic Selector having the numerically smallest precedence value. Note that precedence values are not necessarily contiguous.
current
T11FcSpSecurityProtocolId
TEXTUAL-CONVENTION
A Security Protocol identifier to identify the protocol by which traffic is to be protected, e.g., ESP_Header or CT_Authentication.
current
T11FcSpSignFunctions
TEXTUAL-CONVENTION
A set of zero, one, or more signature functions defined for signing certificates for use with FCAP in FC-SP.
current
T11FcSpTransforms
TEXTUAL-CONVENTION
A list of the standardized transforms that are defined by FC-SP for use with ESP_Header, CT_Authentication, and/or IKEv2 Support.
current
T11FcSpType
TEXTUAL-CONVENTION
A value, or combination of values, contained in a frame header used in identifying the link layer service/protocol of a frame. The value is always two octets: - for FC-2 frames, the first octet is zero and the second octet contains the Data structure type (TYPE) value defined by FC-FS-2. The TYPE value is used in combination with T11FcRoutingControl to identify a link layer service/protocol. - for Common Transport Information Units (CT_IUs), the first octet contains a GS_Type value and the second octet contains a GS_Subtype value, defined by FC-GS-5. The comparison of two values having this syntax is done by treating each string as the numeric value obtained by numerically combining the individual octet's value as follows: (256 * 1st-octet) + 2nd-octet
current
T11FcSpiIndex
TEXTUAL-CONVENTION
An SPI (Security Parameter Index) value is carried in the SPI field of a frame protected by the ESP_Header. An SPI is also carried in the SAID field of a Common Transport Information Unit (CT_IU) protected by CT_Authentication. An SPI value identifies the Security Association on which the frame is being transmitted.
current

Objects

NameOIDSyntaxAccessStatus
t11FcSpIdentities
OBJECT-IDENTITY
1.3.6.1.2.1.175.1
t11FcSpAlgorithms
OBJECT-IDENTITY
1.3.6.1.2.1.175.1.1
t11FcSpEncryptAlgorithms
OBJECT-IDENTITY
1.3.6.1.2.1.175.1.1.1
t11FcSpEncrNull
OBJECT-IDENTITY
The ENCR_NULL algorithm.
1.3.6.1.2.1.175.1.1.1.1current
t11FcSpEncrAesCbc
OBJECT-IDENTITY
The ENCR_AES_CBC algorithm.
1.3.6.1.2.1.175.1.1.1.2current
t11FcSpEncrAesCtr
OBJECT-IDENTITY
The ENCR_AES_CTR algorithm.
1.3.6.1.2.1.175.1.1.1.3current
t11FcSpEncrAesGcm
OBJECT-IDENTITY
The ENCR_AES_GCM algorithm.
1.3.6.1.2.1.175.1.1.1.4current
t11FcSpEncr3Des
OBJECT-IDENTITY
The ENCR_3DES algorithm.
1.3.6.1.2.1.175.1.1.1.5current
t11FcSpEncrNullAuthAesGmac
OBJECT-IDENTITY
The ENCR_NULL_AUTH_AES_GMAC algorithm.
1.3.6.1.2.1.175.1.1.1.6current
t11FcSpAuthAlgorithms
OBJECT-IDENTITY
1.3.6.1.2.1.175.1.1.2
t11FcSpAuthNull
OBJECT-IDENTITY
The AUTH_NONE algorithm.
1.3.6.1.2.1.175.1.1.2.1current
t11FcSpAuthHmacMd5L96
OBJECT-IDENTITY
The AUTH_HMAC_MD5_96 algorithm.
1.3.6.1.2.1.175.1.1.2.2current
t11FcSpAuthHmacSha1L96
OBJECT-IDENTITY
The AUTH_HMAC_SHA1_96 algorithm.
1.3.6.1.2.1.175.1.1.2.3current
t11FcSpAuthHmacMd5L128
OBJECT-IDENTITY
The AUTH_HMAC_MD5_128 algorithm.
1.3.6.1.2.1.175.1.1.2.4current
t11FcSpAuthHmacSha1L160
OBJECT-IDENTITY
The AUTH_HMAC_SHA1_160 algorithm.
1.3.6.1.2.1.175.1.1.2.5current