The Reliable Signaling Gateway Control Protocol (RSGCP)
draft-rfced-info-holdrege-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Matt Holdrege | ||
| Last updated | 1998-06-17 | ||
| 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 memo describes the Control Protocol used between a Network Access Server (NAS) and a Signaling Gateway (SG). The requirements of this protocol are Call Control, Circuit Maintenance and Resource Management. This protocol must be reliable in nature and support redundant links between the NAS and SG. It's important to note that the NAS could be handling either packetized voice or data for access to the Internet.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)