[MEDIACTRL] RFC 6230 on Media Control Channel Framework
rfc-editor@rfc-editor.org Wed, 25 May 2011 05:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mediactrl@ietfa.amsl.com
Delivered-To: mediactrl@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53982E06EF; Tue, 24 May 2011 22:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.012
X-Spam-Level:
X-Spam-Status: No, score=-102.012 tagged_above=-999 required=5 tests=[AWL=-0.012, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J214PudYTChK; Tue, 24 May 2011 22:53:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id D1C56E06BF; Tue, 24 May 2011 22:53:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C059CE077B; Tue, 24 May 2011 22:53:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110525055323.C059CE077B@rfc-editor.org>
Date: Tue, 24 May 2011 22:53:23 -0700
Cc: mediactrl@ietf.org, rfc-editor@rfc-editor.org
Subject: [MEDIACTRL] RFC 6230 on Media Control Channel Framework
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2011 05:53:24 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6230 Title: Media Control Channel Framework Author: C. Boulton, T. Melanchuk, S. McGlashan Status: Standards Track Stream: IETF Date: May 2011 Mailbox: chris@ns-technologies.com, timm@rainwillow.com, smcg.stds01@mcglashan.org Pages: 49 Characters: 112479 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mediactrl-sip-control-framework-12.txt URL: http://www.rfc-editor.org/rfc/rfc6230.txt This document describes a framework and protocol for application deployment where the application programming logic and media processing are distributed. This implies that application programming logic can seamlessly gain access to appropriate resources that are not co-located on the same physical network entity. The framework uses the Session Initiation Protocol (SIP) to establish an application-level control mechanism between application servers and associated external servers such as media servers. The motivation for the creation of this framework is to provide an interface suitable to meet the requirements of a centralized conference system, where the conference system can be distributed, as defined by the XCON working group in the IETF. It is not, however, limited to this scope. [STANDARDS-TRACK] This document is a product of the Media Server Control 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