datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

Indication of Conference Focus Support for the Centralized Conferencing Manipulation Protocol (CCMP)
RFC 7082

Document type: RFC - Informational (December 2013; No errata)
Document stream: IETF
Last updated: 2013-12-04
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Yes
Document shepherd: Alan Johnston
Shepherd Write-Up: Last changed 2013-06-18

IESG State: RFC 7082 (Informational)
IANA Review State: IANA OK - Actions Needed
IANA Action State: RFC-Ed-Ack
Responsible AD: Gonzalo Camarillo
Send notices to: rifatyu@avaya.com, mary.ietf.barnes@gmail.com, draft-yusef-dispatch-ccmp-indication@tools.ietf.org, alan.b.johnston@gmail.com

Internet Engineering Task Force (IETF)                    R. Shekh-Yusef
Request for Comments: 7082                                         Avaya
Category: Informational                                        M. Barnes
ISSN: 2070-1721                                                  Polycom
                                                           December 2013

                 Indication of Conference Focus Support
     for the Centralized Conferencing Manipulation Protocol (CCMP)

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
   <service-uris> element in the SIP conferencing event package.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7082.

Shekh-Yusef & Barnes          Informational                     [Page 1]
RFC 7082            Conference Focus Support for CCMP      December 2013

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................2
      1.1. Terminology ................................................3
   2. Solutions .......................................................3
      2.1. Call-Info ..................................................3
      2.2. Service URI Purpose ........................................4
   3. Overall Process .................................................5
   4. Security Considerations .........................................5
   5. IANA Considerations .............................................6
      5.1. Call-Info Purpose Registration .............................6
      5.2. URI Purpose Registration ...................................6
   6. Acknowledgments .................................................6
   7. Normative References ............................................7
   Appendix A. Other Approaches Considered ............................9
      A.1. Feature Tag ................................................9
      A.2. Conference URI Purpose .....................................9

1.  Introduction

   RFC 5239 [RFC5239] defines a framework for Centralized Conferencing
   (XCON), which allows participants to exchange media in a centralized
   unicast conference.  The framework also outlines a set of
   conferencing protocols for building advanced conferencing
   applications.

   The Centralized Conferencing Manipulation Protocol (CCMP) [RFC6503]
   allows authenticated and authorized users to create, manipulate, and
   delete conference objects.  Operations on conferences include adding
   and removing participants and changing their roles, as well as adding
   and removing media streams and associated end points.

Shekh-Yusef & Barnes          Informational                     [Page 2]
RFC 7082            Conference Focus Support for CCMP      December 2013

[include full document text]