2 References

24.1473GPPConferencing 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.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem; Stage 1".

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

[4] 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".

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

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

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

[8] IETF RFC 4353 (February 2006): "A Framework for Conferencing with the Session Initiation Protocol (SIP)".

[9] IETF RFC 4579 ( August 2006): "Session Initiation Protocol Call Control – Conferencing for User Agents".

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

[11] IETF RFC 4575 (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".

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

[13] Void.

[14] Void.

[15] 3GPP TS 29.208: "End to end Quality of Service (QoS) signalling flows".

[16] IETF RFC 2833 (May 2000): "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals".

[17] IETF RFC 3515 (April 2003): "The Session Initiation Protocol (SIP) Refer Method".

[18] Void.

[19] IETF RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".

[20] IETF RFC 3892 (September 2004): "The Session Initiation Protocol (SIP) Referred-By Mechanism".

[21] Void.

[22] Void.

[23] Void.

[24] Void.

[25] Void.

[26] Void.

[27] Void.

[28] IETF RFC 4582 (November 2006): "The Binary Floor Control Protocol (BFCP)".

[29] Void.

[30] Void.

[31] Void.

[32] Void.

[33] IETF RFC 3891 (September 2004): "The Session Inititation Protocol (SIP) "Replaces" Header".

[34] IETF RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)"

[35] IETF RFC 4583 (November 2006): "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams".

[36] IETF RFC 5360 (October 2008): "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)".

[37] IETF RFC 7989 (October 2016): "End-to-End Session Identification in IP-Based Multimedia Communication Networks".

[38] 3GPP TS 24.166: "3GPP IMS Conferencing Management Object (MO)".

[39] IETF RFC 7647 (September 2015): "Clarifications for the use of REFER with RFC6665".

[40] IETF RFC 4796 (February 2007): "The Session Description Protocol (SDP) Content Attribute".