%% You should probably cite rfc7082 instead of this I-D. @techreport{yusef-dispatch-ccmp-indication-03, number = {draft-yusef-dispatch-ccmp-indication-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-yusef-dispatch-ccmp-indication/03/}, author = {Rifaat Shekh-Yusef and Mary Barnes}, title = {{Conference Focus Indicating CCMP Support}}, pagetotal = 9, year = 2013, month = apr, day = 14, abstract = {The Centralized Conferencing Manipulation Protocol document defines a way for a client to discover a conference control server that supports CCMP. However, it does not define a way for a client involved in a conference to determine if the conference focus supports CCMP. This information would allow a CCMP-enabled client that joins a conference using SIP to also register for the XCON conference event package RFC4575 {[}RFC 4575{]} and take advantage of CCMP operations on the conference. This document describes a few options to address the above limitation with the pros and cons for each approach, and recommends two to be used depending on the need of the UA. The first approach uses the Call-Info header and as a result this document updates RFC3261. The second approach defines a new value for the 'purpose' parameter in the 'service-uris' element in the SIP conferencing event package, and as a result this document update RFC4575 {[}RFC 4575{]}.}, }