Name Pattern Package for Megaco
draft-rosen-megaco-namepatterns-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Brian Rosen | ||
| Last updated | 2002-07-02 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
To construct meaningful audits of terminations while controlling the amount of data sent in response to the audits, it would be very helpful if the MGC understood the way terminations were named in the MG. This package provides a method for obtaining the naming pattern for terminations in an MG
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)