[rfc-dist] RFC 3624 on The Media Gateway Control Protocol (MGCP) Bulk Audit Package
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Tue, 18 November 2003 21:43 UTC
From: rfc-editor@rfc-editor.org
Date: Tue, 18 Nov 2003 13:43:41 -0800
Subject: [rfc-dist] RFC 3624 on The Media Gateway Control Protocol (MGCP) Bulk Audit Package
Message-ID: <200311182143.hAILhgs24430@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3624 Title: The Media Gateway Control Protocol (MGCP) Bulk Audit Package Author(s): B. Foster, D. Auerbach, F. Andreasen Status: Informational Date: November 2003 Mailbox: bfoster@cisco.com, dea@cisco.com, fandreas@cisco.com Pages: 19 Characters: 34391 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-foster-mgcp-bulkaudits-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3624.txt The base Media Gateway Control Protocol (MGCP) includes audit commands that only allow a Call Agent to audit endpoint and/or connection state one endpoint at a time. This document describes a new MGCP package for bulk auditing of a group of gateway endpoints. It allows a Call Agent to determine the endpoint naming convention, the list of instantiated endpoints as well connection and endpoint state for the group of endpoints. 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <031118134226.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3624 --OtherAccess Content-Type: Message/External-body; name="rfc3624.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <031118134226.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3624 on The Media Gateway Control … rfc-editor@rfc-editor.org