2.3.8.2 EphemeralEntryID

The EphemeralEntryID is a structure that identifies a specific object in the address book. Additionally, it encodes the NSPI server that issued the Ephemeral Entry ID and enough information for a client to make a decision as to how to display the object to an end user.

A server MUST NOT change an object's Ephemeral Entry ID during the lifetime of an NSPI session.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

ID Type

R1

R2

R3

ProviderUID (16 bytes)

...

...

R4

Display Type

MId

ID Type (1 byte): The type of this ID. The value is the constant 0x87. The server uses the presence of this value to identify this Entry ID as an Ephemeral Entry ID rather than a Permanent Entry ID.

R1 (1 byte): Reserved. All clients and servers MUST set this value to the constant 0x00.

R2 (1 byte): Reserved. All clients and servers MUST set this value to the constant 0x00.

R3 (1 byte): Reserved. All clients and servers MUST set this value to the constant 0x00.

ProviderUID (16 bytes): A FlatUID_r value containing the GUID of the server that issued this Ephemeral Entry ID (section 3.1.3). A server MUST treat any value other than its own GUID as an error condition.

R4 (4 bytes): Reserved. All clients and servers MUST set this value to the constant 0x00000001.

Display Type (4 bytes): The display type of the object specified by this Ephemeral Entry ID. This value is expressed in little-endian format. Valid values for this field are specified in 2.2.3. The display type is not considered part of the object's identity; it is set in the EphemeralEntryID by the NSPI server as a convenience to NSPI clients. The NSPI server MUST set this field when this data structure is returned in an output parameter. An NSPI server MUST ignore values of this field on input parameters.

MId (4 bytes): The MId of this object, as specified in section 2.3.8.1. This value is expressed in little-endian format.