Share via

3.1.1.1 Abstract Data Model

  • Article

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This protocol does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this protocol.

The UAC SHOULD keep the following state:

  • Epid: A string that is a part of the SIP endpoint identifier. The format and generation of Epid are described in [MS-SIPRE] section 3.2.3.1.

  • SIP.INSTANCE: A string that is a part of the SIP endpoint identifier. The format and generation of SIP.INSTANCE are described in [MS-SIPRE] section 3.2.

  • GRUU: A string that is part of the SIP endpoint identifier. It is generated by the SIP registrar and persisted on the client. The format and generation of GRUU are described in [MS-SIPRE] section 3.4.

  • Presence-Service-Available:<142> A Boolean that is generated by the registrar and persisted on the client, and is updated as described in section 3.1.1.5.1.

  • Primary-Cluster-Type:<143> An identifier associated with the UAC that is generated by the registrar and persisted on the client, and is updated as described in section 3.1.1.5.1.

  • Is-Connected-to-Primary:<144> A Boolean flag associated with the UAC that is generated by the registrar and persisted on the client, and is updated as described in section 3.1.1.5.1.