Browse Prior Art Database

Media Resource Brokering (RFC6917)

IP.com Disclosure Number: IPCOM000226521D
Original Publication Date: 2013-Apr-01
Included in the Prior Art Database: 2013-Apr-12

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Boulton: AUTHOR [+3]

Abstract

As IP-based multimedia infrastructures mature, the complexity and demands from deployments increase. Such complexity will result in a wide variety of capabilities from a range of vendors that should all be interoperable using the architecture and protocols produced by the MediaCtrl working group. It should be possible for a controlling entity to be assisted in Media Server selection so that the most appropriate resource is selected for a particular operation. The importance increases when one introduces a flexible level of deployment scenarios, as specified in RFC 5167 [RFC5167] and RFC 5567 [RFC5567]. These documents make statements like "it should be possible to have a many-to-many relationship between Application Servers and Media Servers that use this protocol". This leads to the following deployment architectures being possible when considering media resources, to provide what can be effectively described as media resource brokering.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Internet Engineering Task Force (IETF)                        C. Boulton Request for Comments: 6917                               NS-Technologies Category: Standards Track                                     L. Miniero ISSN: 2070-1721                                                 Meetecho                                                                G. Munson                                                                     AT&T                                                               April 2013

                         Media Resource Brokering

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6917.

Boulton, et al.              Standards Track                    [Page 1]
 RFC 6917                Media Resource Brokering              April 2013

 Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of...