[XCON] RFC 6501 on Conference Information Data Model for Centralized Conferencing (XCON)

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 []) by ietfa.amsl.com (Postfix) with ESMTP id 3F1DA21F85C9; Sat, 24 Mar 2012 11:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.161
X-Spam-Status: No, score=-102.161 tagged_above=-999 required=5 tests=[AWL=-0.161, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id frngDAQ2Q+4U; Sat, 24 Mar 2012 11:14:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D5D1B21F8598; Sat, 24 Mar 2012 11:14:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 466DF72ECE8; Sat, 24 Mar 2012 11:13:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120324181309.466DF72ECE8@rfc-editor.org>
Date: Sat, 24 Mar 2012 11:13:09 -0700 (PDT)
Cc: xcon@ietf.org, rfc-editor@rfc-editor.org
Subject: [XCON] RFC 6501 on Conference Information Data Model for Centralized Conferencing (XCON)
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:20 -0000

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

        RFC 6501

        Title:      Conference Information Data Model for 
                    Centralized Conferencing (XCON) 
        Author:     O. Novo, G. Camarillo,
                    D. Morgan, J. Urpalainen
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2012
        Mailbox:    Oscar.Novo@ericsson.com, 
                    Dave.Morgan@fmr.com,  jari.urpalainen@nokia.com
        Pages:      94
        Characters: 180210
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xcon-common-data-model-32.txt

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

RFC 5239 defines centralized conferencing (XCON) as an association of
participants with a central focus.  The state of a conference is
represented by a conference object.  This document defines an XML-
based conference information data model to be used for conference
objects.  A conference information data model is designed to convey
information about the conference and about participation in the
conference.  The conference information data model defined in this
document constitutes an extension of the data format specified in the
Session Initiation Protocol (SIP) event package for conference State.  

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

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