idnits 2.17.1 draft-rajeshkumar-mgcp-atm-package-07.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 3441 5 Title: Asynchronous Transfer Mode (ATM) Package for the 6 Media Gateway Control Protocol (MGCP) 7 Author(s): R. Kumar 8 Status: Informational 9 Date: January 2003 10 Mailbox: rkumar@cisco.com 11 Pages: 50 12 Characters: 122455 13 Updates/Obsoletes/See Also: None 15 I-D Tag: draft-rajeshkumar-mgcp-atm-package-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3441.txt 19 This document describes an Asynchronous Transfer Mode (ATM) package 20 for the Media Gateway Control Protocol (MGCP). This package includes 21 new Local Connection Options, ATM-specific events and signals, and ATM 22 connection parameters. Also included is a description of codec and 23 profile negotiation. It extends the MGCP that is currently being 24 deployed in a number of products. Implementers should be aware of 25 developments in the IETF Megaco Working Group and ITU SG16, which are 26 currently working on a potential successor to this protocol. 28 This memo provides information for the Internet community. It does 29 not specify an Internet standard of any kind. Distribution of this 30 memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.