idnits 2.17.1 draft-ietf-megaco-3015corr-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3525 5 Title: Gateway Control Protocol Version 1 6 Author(s): C. Groves, M. Pantaleo, T. Anderson, T. Taylor, 7 Editors 8 Status: Standards Track 9 Date: June 2003 10 Mailbox: Christian.Groves@ericsson.com.au, 11 Marcello.Pantaleo@eed.ericsson.se, 12 tlatla@verizon.net, 13 taylor@nortelnetworks.com 14 Pages: 213 15 Characters: 439674 16 Obsoletes: 3015 18 I-D Tag: draft-ietf-megaco-3015corr-03.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3525.txt 22 This document defines the protocol used between elements of a 23 physically decomposed multimedia gateway, i.e., a Media Gateway and a 24 Media Gateway Controller. The protocol presented in this document 25 meets the requirements for a media gateway control protocol as 26 presented in RFC 2805. 28 This document replaces RFC 3015. It is the result of 29 continued cooperation between the IETF Megaco Working Group and ITU-T 30 Study Group 16. It incorporates the original text of RFC 3015, 31 modified by corrections and clarifications discussed on the Megaco 33 E-mail list and incorporated into the Study Group 16 Implementor's 34 Guide for Recommendation H.248. The present version of this document 35 underwent ITU-T Last Call as Recommendation H.248 Amendment 1. 36 Because of ITU-T renumbering, it was published by the ITU-T as 37 Recommendation H.248.1 (03/2002), Gateway Control Protocol Version 1. 39 Users of this specification are advised to consult the H.248 40 Sub-series Implementors' Guide at 41 http://www.itu.int/itudoc/itu-t/com16/implgd for additional 42 corrections and clarifications. 44 This document is a product of the Media Gateway Control Working Group 45 of the IETF. 47 This is now a Proposed Standard Protocol. 49 This document specifies an Internet standards track protocol for 50 the Internet community, and requests discussion and suggestions 51 for improvements. Please refer to the current edition of the 52 "Internet Official Protocol Standards" (STD 1) for the 53 standardization state and status of this protocol. Distribution 54 of this memo is unlimited. 56 This announcement is sent to the IETF list and the RFC-DIST list. 57 Requests to be added to or deleted from the IETF distribution list 58 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 59 added to or deleted from the RFC-DIST distribution list should 60 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 62 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 63 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 64 help: ways_to_get_rfcs. For example: 66 To: rfc-info@RFC-EDITOR.ORG 67 Subject: getting rfcs 69 help: ways_to_get_rfcs 71 Requests for special distribution should be addressed to either the 72 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 73 specifically noted otherwise on the RFC itself, all RFCs are for 74 unlimited distribution.echo 75 Submissions for Requests for Comments should be sent to 76 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 77 Authors, for further information.