[MEDIACTRL] RFC 6505 on A Mixer Control Package for the Media Control Channel Framework

rfc-editor@rfc-editor.org Sat, 24 March 2012 18:27 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 BCAE321F8528; Sat, 24 Mar 2012 11:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level:
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 3PjPWMQN777x; Sat, 24 Mar 2012 11:27:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 4F1E121F8510; Sat, 24 Mar 2012 11:27:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CB998B1E004; Sat, 24 Mar 2012 11:14:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120324181408.CB998B1E004@rfc-editor.org>
Date: Sat, 24 Mar 2012 11:14:08 -0700
Cc: mediactrl@ietf.org, rfc-editor@rfc-editor.org
Subject: [MEDIACTRL] RFC 6505 on A Mixer Control Package for the 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: Sat, 24 Mar 2012 18:27:38 -0000

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

        
        RFC 6505

        Title:      A Mixer Control Package for 
                    the Media Control Channel Framework 
        Author:     S. McGlashan, T. Melanchuk,
                    C. Boulton
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2012
        Mailbox:    smcg.stds01@mcglashan.org, 
                    timm@rainwillow.com, 
                    chris@ns-technologies.com
        Pages:      89
        Characters: 187038
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mediactrl-mixer-control-package-14.txt

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

This document defines a Media Control Channel Framework Package for
managing mixers for media conferences and connections.  The package
defines request elements for managing conference mixers, managing
mixers between conferences and/or connections, as well as associated
responses and notifications.  The package also defines elements for
auditing package capabilities and mixers  [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