ldap objectclass
AKBK Home :: LDAP
:: ObjectClasses ::
Object Class: bootableDevice
ID: nisSchema.2.12
A device with boot parameters; device SHOULD be used as a structural class
BNC Syntax: nisSchema.2.12 NAME 'bootableDevice'
SUP top
AUXILARY
MAY ( bootFile $ bootParameter )
rfc2307
Extends objectClass:
Attributes:
Description: Boot image name
BNC Syntax: nisSchema.1.24 NAME 'bootFile'
EQUALITY caseExactIA5Match
ID : 1.3.6.1.4.1.1466.115.121.1.26
The encoding of a value in this syntax is the string value itself.
BNC Syntax:
Description:
Servers SHOULD be capable of performing the following matching rules.
For all these rules, the assertion syntax is the same as the value
syntax.
When performing the caseIgnoreMatch, caseIgnoreListMatch,
telephoneNumberMatch, caseExactIA5Match and caseIgnoreIA5Match,
multiple adjoining whitespace characters are treated the same as an
individual space, and leading and trailing whitespace is ignored.
Clients MUST NOT assume that servers are capable of transliteration
of Unicode values.
BNC Syntax:
Description: rpc.bootparamd parameter
BNC Syntax: nisSchema.1.23 NAME 'bootParameter'
ID : nisSchema.0.1
The bootParameterSyntax syntax represents boot parameters:
where:
bootparameter = key "=" server ":" path
key = keystring
server = keystring
path = keystring
X.500 servers may use the following representation of the above syntax:
bootParameterSyntax ::= SEQUENCE {
key IA5String,
server IA5String,
path IA5String
}
Values adhering to these syntaxes are encoded as strings by LDAP servers.
BNC Syntax:
Description:
An LDAP server implementation SHOULD recognize the attribute types described in this section. The values of the objectClass attribute describe the kind of object which an entry represents. The objectClass attribute is present in every entry, with at least two values. One of the values is either "top" or "alias".
BNC Syntax: 2.5.4.0 NAME 'objectClass'
EQUALITY objectIdentifierMatch
Syntax: OID
ID : 1.3.6.1.4.1.1466.115.121.1.38
Values in the Object Identifier syntax are encoded according to the BNF in section 4.1 for "oid".
Example:
1.2.3.4
cn
BNC Syntax:
Description:
Servers SHOULD be capable of performing the following matching rules.
For all these rules, the assertion syntax is the same as the value
syntax.
If the client supplies a filter using an objectIdentifierMatch whose
matchValue oid is in the "descr" form, and the oid is not recognized
by the server, then the filter is Undefined.
BNC Syntax:
|
