2 References

24.1413GPPPresence service using the IP Multimedia (IM) Core Network (CN) subsystemRelease 17Stage 3TS

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

– References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.

– For a specific reference, subsequent revisions do not apply.

– For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 22.141: "Presence Service; Stage 1".

[3] 3GPP TS 23.002: "Network architecture".

[4] 3GPP TS 23.141: "Presence service; Architecture and functional description; Stage 2".

[5] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".

[6] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[7] 3GPP TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details".

[8] 3GPP TS 24.228 Release 5: "Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[9] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[10] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".

[11] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".

[12] IETF RFC 2664 (1999): "FYI on Questions and Answers – Answers to Commonly asked New Internet User Questions".

[13] Void.

[14] IETF RFC 2387 (August 1998): "The MIME Multipart/Related Content-type".

[15] Void.

[15A] Void.

[16] IETF RFC 2778 (2000): "A Model for Presence and Instant Messaging".

[17] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol".

[18] IETF RFC 3263 (June 2002): "Session Initiation Protocol (SIP): Locating SIP Servers".

[19] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification".

[20] IETF RFC 3310 (2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".

[21] IETF RFC 3863 (August 2004): "Presence Information Data Format (PIDF)".

[22] IETF RFC 4662 (August 2006): "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists".

[23] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) for Event State Publication".

[24] IETF RFC 5263 (September 2008): "Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information".

[25] IETF RFC 5196 (September 2008): "Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)".

[26] IETF RFC 4480 (July 2006): "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)".

[27] IETF RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".

[28] IETF RFC 3857 (August 2004): "A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)".

[29] IETF RFC 3858 (August 2004): "An Extensible Markup Language (XML) Based Format for Watcher Information".

[30] IETF RFC 4661 (September 2006): "An Extensible Markup Language (XML) Based Format for Event Notification Filtering".

[31] IETF RFC 4660 (September 2006): "Functional Description of Event Notification Filtering".

[32] IETF RFC 4482 (July 2006): "CIPID: Contact Information for the Presence Information Data Format".

[33] IETF RFC 4825 (May 2007): "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".

[34] IETF RFC 4827 (May 2007): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents".

[35] IETF RFC 5025 (December 2007): "Presence Authorization Rules".

[35A] IETF RFC 4745 (February 2007): "Common Policy: A Document Format for Expressing Privacy Preferences".

[36] IETF RFC 4826 (May 2007): "An Extensible Markup Language (XML) Formats for Representing Resource Lists".

[37] IETF RFC 4119 (December 2005): "A Presence-based GEOPRIV Location Object Format".

[38] IETF RFC 5262 (September 2008): "Presence Information Data Format (PIDF) Extension for Partial Presence".

[39] IETF RFC 5874 (May 2010): "An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources".

[40] IETF RFC 4483 (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".

[41] Void.

[42] Void.

[43] IETF RFC 5875 (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".

[44] IETF RFC 4479 (July 2006): "A Data Model for Presence".

[45] IETF RFC 5264 (September 2008): "Publication of Partial Presence Information".

[46] 3GPP2 X.S0027-004: "Network Presence".

[47] Void

[48] 3GPP2 S.S0109: "Generic bootstrapping architecture"

[49] 3GPP2 S.S0114: "Security mechanisms using GBA"

[50] Void

[51] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".

[52] IETF RFC 7231 (June 2014): "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".

[53] IETF RFC 7616 (September 2015): "HTTP Digest Access Authentication".