%% You should probably cite rfc7082 instead of this I-D.
@techreport{yusef-dispatch-ccmp-indication-07,
    number =    {draft-yusef-dispatch-ccmp-indication-07},
    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/07/},
    author =    {Rifaat Shekh-Yusef and Mary Barnes},
    title =     {{Indication of Conference Focus Support for the Centralized Conferencing Manipulation Protocol (CCMP)}},
    pagetotal = 10,
    year =      2013,
    month =     oct,
    day =       9,
    abstract =  {The Centralized Conferencing Manipulation Protocol (CCMP) document (RFC 6503) 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 Centralized Conferencing (XCON) conference event package and take advantage of CCMP operations on the conference. This document describes two mechanisms, depending upon the need of the User Agent (UA), to address the above limitation. The first mechanism uses the Call-Info header field, and the second mechanism defines a new value for the "purpose" header field parameter in the \textless{}service-uris\textgreater{} element in the SIP conferencing event package.},
}