idnits 2.17.1 draft-ietf-megaco-ipphone-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 3054 5 Title: Megaco IP Phone Media Gateway Application Profile 6 Author(s): P. Blatherwick, R. Bell, P. Holland 7 Status: Informational 8 Date: January 2001 9 Mailbox: blather@nortelnetworks.com, rtbell@cisco.com 10 phil.holland@circa.ca 11 Pages: 14 12 Characters: 31971 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-megaco-ipphone-03.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3054.txt 19 This document specifies a particular application of the Megaco/H.248 20 Protocol for control of Internet telephones and similar appliances: 21 the Megaco IP Phone Media Gateway. The telephone itself is a Media 22 Gateway (MG), controlled by the Megaco/H.248 Protocol, with 23 application control intelligence located in the Media Gateway 24 Controller (MGC). To achieve a high degree of interoperability and 25 design efficiency in such end-user devices, a consistent architectural 26 approach, a particular organization of Terminations and Packages, and 27 a Protocol Profile are described. The approach makes use of existing 28 Protocol features and user interface related Packages, and is thus a 29 straight-forward application of the Megaco/H.248 Protocol. 31 This document is a product of the Media Gateway Control Working Group 32 of the IETF. 34 This memo provides information for the Internet community. It does 35 not specify an Internet standard of any kind. Distribution of this 36 memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.