A Framework for Centralized Conferencing
RFC 5239

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    xcon mailing list <xcon@ietf.org>, 
    xcon chair <xcon-chairs@tools.ietf.org>
Subject: Protocol Action: 'A Framework for Centralized 
         Conferencing' to Proposed Standard 

The IESG has approved the following document:

- 'A Framework for Centralized Conferencing '
   <draft-ietf-xcon-framework-12.txt> as a Proposed Standard

This document is the product of the Centralized Conferencing Working 

The IESG contact persons are Cullen Jennings and Jon Peterson.

A URL of this Internet-Draft is:

          Technical Summary

	     This document defines the framework for Centralized
	     Conferencing.  The framework allows participants using
	     various call signaling protocols, such as SIP, H.323,
	     Jabber and various protocols used in the PSTN, to
	     exchange media in a centralized unicast conference.
	     The Centralized Conferencing Framework defines logical
	     entities and naming conventions, along with a high
	     level conferencing data model.  The framework also
	     outlines a set of conferencing protocols, which are
	     complementary to the call signaling protocols, for
	     building advanced conferencing applications.  The
	     framework binds all the defined components together
	     for the benefit of builders of conferencing systems.

          Working Group Summary

             This document is a product of the XCON working group.
             It captures some of the most important consensus decisions
             in the working group's history, and forms the foundation
             of the conference control protocol that XCON will ultimately

          Document Quality

             The document has been reviewed for technical quality
             by Adam Roach.

             The document specifies a framework and important
             concepts, but does not define an implementable protocol
             (which is a separate deliverable of the XCON working
             group). A group of students at Universita' di Napoli
             Federico II (Naples University) have implemented their
             own protocol based on the concepts in the XCON framework;
             however, because no protocol has been formally defined
             by XCON yet, interoperability isn't possible.  See
             https://sourceforge.net/projects/confiance/ for details.

             The document itself underwent a detailed review by assigned
             reviewers in September of 2005. Detailed reviewers included
             David Morgan, Oscar Novo, Roni Even, and Umesh Chandra.

Note to RFC Editor

Today, users often have passwords containing up to 30 bits
Today, users often have passwords containing up to 30 bits of entropy 

 users' visibility (including "anonymous" and "hidden") may be
 users' identity (including "anonymous" and "hidden") may be