Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

R. Shekh-Yusef
M. Barnes

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7082

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7082

Abstract

The Centralized Conferencing Manipulation Protocol (CCMP) document(RFC 6503) defines a way for a client to discover a conference controlserver that supports CCMP. However, it does not define a way for aclient involved in a conference to determine if the conference focussupports CCMP. This information would allow a CCMP-enabled clientthat joins a conference using SIP to also register for theCentralized Conferencing (XCON) conference event package and takeadvantage of CCMP operations on the conference.

This document describes two mechanisms, depending upon the need ofthe User Agent (UA), to address the above limitation. The firstmechanism uses the Call-Info header field, and the second mechanismdefines a new value for the "purpose" header field parameter in the<service-uris> element in the SIP conferencing event package.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.