This topic presents the additional directory attribute type that DME uses. Each attribute type has an object identifier, which is the value of the OM attribute DS_ATTRIBUTE_TYPE. These object identifiers are represented in the interface by constants with the same name as the directory attribute, and they are prefixed by DSX_A_ so that they can be easily identified.
This topic contains two tables that are used to indicate the object identifier for the DME attribute type (see the first following table), and the values for the DME attribute type (see the second following table), respectively. Following these two tables is a brief description of the attribute. (See Basic Directory Contents Package for information on general matching rules.)
The following table shows the name of the DME attribute type, together with the BER encoding of the associated object identifier.
Note: The second column of the following table contains the contents octets of the BER encoding of the object identifier in hexadecimal. This object identifier stems from the root {iso(1) identified-organization(3) osf(0022) dme(2) components(1) nmo(2) dmeNmoAttributeType(1)}.
Object Identifier for DME Attribute Type
Attribute Type |
Object Identifier BER Hexadecimal |
DSX_A_ALTERNATE_ADDRESS | \x2B\x16\x02\x01\x02\x01\x01 |
Representation of Values for DME Attribute Types
Attribute Type |
OM Value Syntax |
Value Length | Multi- Valued | Matching Rules |
DSX_A_ ALTERNATE_ ADDRESS |
String(OM_S OCTET_STRING) |
1800 | yes | E |
· DSX_A_ALTERNATE_ADDRESS
This attribute is used by DME to store opaque address formats. In the following table, it can be seen that the AlternateAddress attribute is stored internally by GDS as an octet string. The application expects the following syntax:
AlternateAddress ::= SEQUENCE {
address OCTET STRING,
protocol SET OF OBJECT IDENTIFIER }
For conversion between octet string and a C structure corresponding to this definition, two functions are provided: gds_encode_alt_addr (3xds) and gds_decode_alt_addr (3xds).