[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 5239 on A Framework for Centralized Conferencing
A new Request for Comments is now available in online RFC libraries.
RFC 5239
Title: A Framework for Centralized Conferencing
Author: M. Barnes, C. Boulton, O. Levin
Status: Standards Track
Date: June 2008
Mailbox: mary.barnes at nortel.com,
cboulton at avaya.com,
oritl at microsoft.com
Pages: 57
Characters: 146927
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-xcon-framework-11.txt
URL: http://www.rfc-editor.org/rfc/rfc5239.txt
This document defines the framework for Centralized Conferencing.
The framework allows participants using various call signaling
protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part
(ISUP), to exchange media in a centralized unicast conference. The
Centralized Conferencing Framework defines logical entities and
naming conventions. 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. [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 From ietf-announce-bounces at ietf.org Mon Jun 9 15:16:29 2008
Return-Path: <ietf-announce-bounces at ietf.org>
X-Original-To: ietf-announce-archive at megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id B4C8E3A6BA8;
Mon, 9 Jun 2008 15:16:29 -0700 (PDT)
X-Original-To: ietf-announce at core3.amsl.com
Delivered-To: ietf-announce at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 9137E3A6A6A;
Mon, 9 Jun 2008 15:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.718
X-Spam-Level:
X-Spam-Status: No, score=-16.718 tagged_above=-999 required=5
tests=[AWL=0.281, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id QcXVQD5C6n-0; Mon, 9 Jun 2008 15:16:27 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
by core3.amsl.com (Postfix) with ESMTP id AA8E63A68C1;
Mon, 9 Jun 2008 15:16:27 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
id 11BA9135F53; Mon, 9 Jun 2008 15:16:48 -0700 (PDT)
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
Subject: RFC 5239 on A Framework for Centralized Conferencing
From: rfc-editor at rfc-editor.org
Message-Id: <20080609221648.11BA9135F53 at bosco.isi.edu>
Date: Mon, 9 Jun 2008 15:16:48 -0700 (PDT)
Cc: xcon at ietf.org, rfc-editor at rfc-editor.org
X-BeenThere: ietf-announce at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
List-Post: <mailto:ietf-announce at ietf.org>
List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request at ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces at ietf.org
Errors-To: ietf-announce-bounces at ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5239
Title: A Framework for Centralized Conferencing
Author: M. Barnes, C. Boulton, O. Levin
Status: Standards Track
Date: June 2008
Mailbox: mary.barnes at nortel.com,
cboulton at avaya.com,
oritl at microsoft.com
Pages: 57
Characters: 146927
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-xcon-framework-11.txt
URL: http://www.rfc-editor.org/rfc/rfc5239.txt
This document defines the framework for Centralized Conferencing.
The framework allows participants using various call signaling
protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part
(ISUP), to exchange media in a centralized unicast conference. The
Centralized Conferencing Framework defines logical entities and
naming conventions. 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. [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-AnnIETF-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 at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
ounce 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 at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce