RFC 3661 on Media Gateway Control Protocol (MGCP) Return Code Usage
rfc-editor@rfc-editor.org Wed, 24 December 2003 21:07 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22815 for <ietf-announce-web-archive@odin.ietf.org>; Wed, 24 Dec 2003 16:07:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AZG2S-0001GW-Sp for ietf-announce-list@asgard.ietf.org; Wed, 24 Dec 2003 15:55:28 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AZG0F-0001ER-3w for all-ietf@asgard.ietf.org; Wed, 24 Dec 2003 15:53:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22411 for <all-ietf@ietf.org>; Wed, 24 Dec 2003 15:53:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AZG08-0007h7-00 for all-ietf@ietf.org; Wed, 24 Dec 2003 15:53:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AZFwJ-0007dS-00 for all-ietf@ietf.org; Wed, 24 Dec 2003 15:49:08 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AZFuD-0007aU-00 for all-ietf@ietf.org; Wed, 24 Dec 2003 15:46:57 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBOKkls17590; Wed, 24 Dec 2003 12:46:47 -0800 (PST)
Message-Id: <200312242046.hBOKkls17590@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3661 on Media Gateway Control Protocol (MGCP) Return Code Usage
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 24 Dec 2003 12:46:47 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3661 Title: Media Gateway Control Protocol (MGCP) Return Code Usage Author(s): B. Foster, C. Sivachelvan Status: Informational Date: December 2003 Mailbox: bfoster@cisco.com, chelliah@cisco.com Pages: 24 Characters: 49898 Updates: 3435 I-D Tag: draft-foster-mgcp-returncodes-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3661.txt This document provides implementation guidelines for the use of return codes in RFC 3435, Media Gateway Control Protocol (MGCP) Version 1.0. Return codes in RFC 3435 do not cover all possible specific situations that may ever occur in a gateway. That is not possible and not necessary. What is important is to ensure that the Call Agent that receives a return code behaves appropriately and consistently for the given situation. The purpose of this document is to provide implementation guidelines to ensure that consistency. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.