[XCON] RFC 6504 on Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples

rfc-editor@rfc-editor.org Sat, 24 March 2012 18:15 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 A251B21F8616; Sat, 24 Mar 2012 11:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.519
X-Spam-Level:
X-Spam-Status: No, score=-104.519 tagged_above=-999 required=5 tests=[AWL=1.158, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, 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 t6pWqPyntnFv; Sat, 24 Mar 2012 11:15:07 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 26C8521F85DB; Sat, 24 Mar 2012 11:15:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7F40BB1E003; Sat, 24 Mar 2012 11:13:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120324181356.7F40BB1E003@rfc-editor.org>
Date: Sat, 24 Mar 2012 11:13:56 -0700 (PDT)
Cc: xcon@ietf.org, rfc-editor@rfc-editor.org
Subject: [XCON] RFC 6504 on Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
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:15:07 -0000

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

        
        RFC 6504

        Title:      Centralized Conferencing Manipulation Protocol (CCMP) 
                    Call Flow Examples 
        Author:     M. Barnes, L. Miniero,
                    R. Presta, S P. Romano
        Status:     Informational
        Stream:     IETF
        Date:       March 2012
        Mailbox:    mary.ietf.barnes@gmail.com, 
                    lorenzo@meetecho.com, 
                    roberta.presta@unina.it,  spromano@unina.it
        Pages:      78
        Characters: 186366
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xcon-examples-10.txt

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

This document provides detailed call flows for the scenarios
documented in the Framework for Centralized Conferencing (XCON) (RFC
5239) and in the XCON scenarios (RFC 4597).  The call flows document
the use of the interface between a conference control client and a
conference control server using the Centralized Conferencing
Manipulation Protocol (CCMP) (RFC 6503).  The objective is to provide
detailed examples for reference by both protocol researchers and
developers.  This document is not an Internet Standards Track
specification; it is published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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