MGCP, MEGACO, and SIP VoIP Signaling Protocol Security Requirements
draft-jacobs-signaling-security-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Henrik Nielsen | ||
| Last updated | 2002-11-04 | ||
| 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
This document specifies the requirements that the MGCP, MEGACO, and SIP VoIP Signaling Protocols must satisfy in order to meet the needs for VoIP deployment in carrier class and large geographically distributed organization networks. These requirements were developed with a specific focus on network address translation (NAT), network through application layer packet filtering, signaling across multiple trust domains, and redundancy of call/controllers, media gateways, proxies and registrars.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)