Media Control Channel Framework
RFC 6230

Internet Engineering Task Force (IETF)                        C. Boulton
Request for Comments: 6230                               NS-Technologies
Category: Standards Track                                   T. Melanchuk
ISSN: 2070-1721                                               Rainwillow
                                                            S. McGlashan
                                                         Hewlett-Packard
                                                                May 2011

                    Media Control Channel Framework

Abstract

   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.

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/rfc6230.

Boulton, et al.              Standards Track                    [Page 1]
RFC 6230             Media Control Channel Framework            May 2011

Copyright Notice

   Copyright (c) 2011 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
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions and Terminology  . . . . . . . . . . . . . . . . .  4
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Control Channel Setup  . . . . . . . . . . . . . . . . . . . . 10
     4.1.  Control Client SIP UAC Behavior  . . . . . . . . . . . . . 10
     4.2.  Control Server SIP UAS Behavior  . . . . . . . . . . . . . 13
   5.  Establishing Media Streams - Control Client SIP UAC
       Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
   6.  Control Framework Interactions . . . . . . . . . . . . . . . . 15
     6.1.  General Behavior for Constructing Requests . . . . . . . . 17
     6.2.  General Behavior for Constructing Responses  . . . . . . . 17
     6.3.  Transaction Processing . . . . . . . . . . . . . . . . . . 18
       6.3.1.  CONTROL Transactions . . . . . . . . . . . . . . . . . 18
       6.3.2.  REPORT Transactions  . . . . . . . . . . . . . . . . . 19
       6.3.3.  K-ALIVE Transactions . . . . . . . . . . . . . . . . . 21
       6.3.4.  SYNC Transactions  . . . . . . . . . . . . . . . . . . 22
   7.  Response Code Descriptions . . . . . . . . . . . . . . . . . . 24
     7.1.  200 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.2.  202 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.3.  400 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.4.  403 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.5.  405 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.6.  406 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.7.  420 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.8.  421 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.9.  422 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.10. 423 Response Code  . . . . . . . . . . . . . . . . . . . . 25
     7.11. 481 Response Code  . . . . . . . . . . . . . . . . . . . . 26