[XCON] RFC 6503 on Centralized Conferencing Manipulation Protocol

rfc-editor@rfc-editor.org Sat, 24 March 2012 18:14 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xcon@ietfa.amsl.com
Delivered-To: xcon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313B321F8607; Sat, 24 Mar 2012 11:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.194
X-Spam-Level:
X-Spam-Status: No, score=-104.194 tagged_above=-999 required=5 tests=[AWL=0.883, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkDaOAP0jpv0; Sat, 24 Mar 2012 11:14:52 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 874EC21F85AF; Sat, 24 Mar 2012 11:14:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F38B072ECF5; Sat, 24 Mar 2012 11:13:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120324181340.F38B072ECF5@rfc-editor.org>
Date: Sat, 24 Mar 2012 11:13:40 -0700 (PDT)
Cc: xcon@ietf.org, rfc-editor@rfc-editor.org
Subject: [XCON] RFC 6503 on Centralized Conferencing Manipulation Protocol
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Mar 2012 18:14:53 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6503

        Title:      Centralized Conferencing Manipulation Protocol 
        Author:     M. Barnes, C. Boulton,
                    S. Romano, H. Schulzrinne
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2012
        Mailbox:    mary.ietf.barnes@gmail.com, 
                    chris@ns-technologies.com, 
                    spromano@unina.it,  hgs+xcon@cs.columbia.edu
        Pages:      119
        Characters: 257058
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xcon-ccmp-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6503.txt

The Centralized Conferencing Manipulation Protocol (CCMP) allows a
Centralized Conferencing (XCON) system client to create, retrieve,
change, and delete objects that describe a centralized conference.
CCMP is a means to control basic and advanced conference features
such as conference state and capabilities, participants, relative
roles, and details.  CCMP is a stateless, XML-based, client server
protocol that carries, in its request and response messages,
conference information in the form of XML documents and fragments
conforming to the centralized conferencing data model schema.
[STANDARDS-TRACK]

This document is a product of the Centralized Conferencing Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC