Document Action: Basic MGCP Packages to Informational
The IESG <iesg-secretary@ietf.org> Mon, 16 June 2003 20:16 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 QAA29949 for <ietf-announce-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 16:16:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19S0LR-0004Ag-KQ for ietf-announce-list@asgard.ietf.org; Mon, 16 Jun 2003 16:12:49 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19RzzQ-000113-C5 for all-ietf@asgard.ietf.org; Mon, 16 Jun 2003 15:50:04 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28239; Mon, 16 Jun 2003 15:50:02 -0400 (EDT)
Message-Id: <200306161950.PAA28239@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>
From: The IESG <iesg-secretary@ietf.org>
Subject: Document Action: Basic MGCP Packages to Informational
Date: Mon, 16 Jun 2003 15:50:02 -0400
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
The IESG has approved the Internet-Draft 'Basic MGCP Packages' <draft-foster-mgcp-basic-packages-10.txt> as an Informational RFC. This has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact persons are Allison Mankin and Scott Bradner. RFC Editor, replace the IESG Note in draft-foster-mgcp-basic-packages-10.txt. Old: IESG NOTE: This document is being published for the information of the community. It describes a non-IETF protocol that is currently being deployed in a number of products. Implementers should be aware that the IETF Megaco working group and the ITU-T Study Group 16 have produced a standards track RFC "Megaco Protocol Version 1.0" (RFC 3015, also published as ITU recommendation H.248) which addresses the same problem space and are developing extensions to that protocol for functions of this type. New: IESG Note This document is being published for the information of the community. It describes a non-IETF protocol that is currently being deployed in a number of products. Implementers should be aware of RFC 3015, which was developed in the IETF Megaco Working Group and the ITU-T SG16 and which is considered by the IETF and ITU-T to be the standards-based (including reviewed security considerations) way to meet the needs that MGCP was designed to address. The IETF Megaco working group and the ITU-T Study Group 16 are developing extensions to RFC 3015 that for functions of the type in addressed in this document.