[MEDIACTRL] RFC 6917 on Media Resource Brokering

rfc-editor@rfc-editor.org Thu, 11 April 2013 21:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mediactrl@ietfa.amsl.com
Delivered-To: mediactrl@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6D71721F8712; Thu, 11 Apr 2013 14:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.214
X-Spam-Status: No, score=-102.214 tagged_above=-999 required=5 tests=[AWL=-0.214, 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 UzCcMngln1pg; Thu, 11 Apr 2013 14:44:49 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id DD91C21F86C3; Thu, 11 Apr 2013 14:44:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 51DDEB1E003; Thu, 11 Apr 2013 14:44:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130411214409.51DDEB1E003@rfc-editor.org>
Date: Thu, 11 Apr 2013 14:44:09 -0700 (PDT)
Cc: mediactrl@ietf.org, rfc-editor@rfc-editor.org
Subject: [MEDIACTRL] RFC 6917 on Media Resource Brokering
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: Thu, 11 Apr 2013 21:44:50 -0000

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

        RFC 6917

        Title:      Media Resource Brokering 
        Author:     C. Boulton, L. Miniero,
                    G. Munson
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2013
        Mailbox:    chris@ns-technologies.com, 
        Pages:      136
        Characters: 280399
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mediactrl-mrb-19.txt

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

The MediaCtrl working group in the IETF has proposed an architecture
for controlling media services.  The Session Initiation Protocol
(SIP) is used as the signaling protocol that provides many inherent
capabilities for message routing.  In addition to such signaling
properties, a need exists for intelligent, application-level media
service selection based on non-static signaling properties.  This is
especially true when considered in conjunction with deployment
architectures that include 1:M and M:N combinations of Application
Servers and Media Servers.  This document introduces a Media Resource
Broker (MRB) entity, which manages the availability of Media Servers
and the media resource demands of Application Servers.  The document
includes potential deployment options for an MRB and appropriate
interfaces to Application Servers and Media Servers.

This document is a product of the Media Server Control Working Group of the IETF.

This is now a Proposed Standard.

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