Asynchronous Transfer Mode (ATM) Package for the Media Gateway Control Protocol (MGCP)
RFC 3441

 
Document Type RFC - Informational (January 2003; No errata)
Was draft-rajeshkumar-mgcp-atm-package (individual in tsv area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3441 (Informational)
Telechat date
Responsible AD Scott Bradner
Send notices to <rajeshk@india.hp.com>

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                           R. Kumar
Request for Comments: 3441                                 Cisco Systems
Category: Informational                                     January 2003

               Asynchronous Transfer Mode (ATM) Package
             for the Media Gateway Control Protocol (MGCP)

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   This document describes an Asynchronous Transfer Mode (ATM) package
   for the Media Gateway Control Protocol (MGCP).  This package includes
   new Local Connection Options, ATM-specific events and signals, and
   ATM connection parameters.  Also included is a description of codec
   and profile negotiation.  It extends the MGCP that is currently being
   deployed in a number of products.  Implementers should be aware of
   developments in the IETF Megaco Working Group and ITU SG16, which are
   currently working on a potential successor to this protocol.

Table of Contents

   1.0  Conventions Used in this Document..............................2
   2.0  Introduction...................................................2
   3.0  Local Connection Options.......................................3
     3.1 ATM Bearer Connection.........................................4
     3.2 ATM Adaptation Layer (AAL)....................................8
     3.3 Service Layer................................................15
     3.4 ATM Bearer Traffic Management................................19
     3.5 AAL Dimensioning.............................................27
   4.0 Signals and Events.............................................30
   5.0 Connection Parameters..........................................35
   6.0 Negotiation of Profiles and Codecs in ATM Applications.........37
     6.1  Consistency of Parameters...................................37
     6.2  Codec/Profile Negotiation in ATM Networks...................38
   7.0  Security Considerations.......................................45
   8.0  IANA Considerations...........................................45
   9.0  References....................................................45
   10.0 Acronyms......................................................48

Kumar                        Informational                      [Page 1]
RFC 3441                    ATM MGCP Package                January 2003

   11.0 Acknowledgements..............................................49
   12.0 Author's Address..............................................49
   13.0 Full Copyright Statement......................................50

1.0  Conventions Used in this Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119.

   MGCP identifiers are case-insensitive.  This includes package names,
   event names, local connection options and other elements of the MGCP
   header.

2.0  Introduction

   The Media Gateway Control Protocol or MGCP [36] is used to control
   voice media gateways from external call control elements.  Even
   though the bearer network might be IP, ATM, TDM or a mix of these,
   MGCP is transported over IP.  Packages such as the MGCP CAS packages
   [38] are modular sets of parameters such as connection options,
   signal, event and statistics definitions that can be used to extend
   it into specific contexts.  A related,  IP-based mechanism for the
   description of ATM connections [18] has been generated by the IETF
   MMUSIC group.  Due to the IP-centric nature of all aspects of the
   MGCP device control protocol, and for consistency with other MGCP
   package definitions, it is desirable to publish the MGCP ATM package
   in an IETF document.

   MGCP [36] allows the auditing of endpoints for package versions
   supported.  The package version for the MGCP ATM package, as
   specified in this document, is 0.  Even if the ATM package is the
   default package for some endpoints, the package prefix "atm" shall
   not be omitted in local connection option names, event names, signal
   names etc.  If the ATM package is the default package for an
   endpoint, it will be listed as the first package in the audit
   response list.  It is not necessary for the MGCP ATM package to be
   the default package for ATM to be supported on an endpoint.

   The ATM package in this document consists of Local Connection Options
Show full document text