Gateway and Server Registration Protocol
draft-roy-iptel-gw-server-registration-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Radhika Roy | ||
| Last updated | 2001-09-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 contribution describes a registration protocol that can be used between gateways (GWs) and severs as well as among servers in intra- ITAD communications environment. The registration protocol is used by a GW just to inform its transport address and reachable alias addresses including telephone numbers through it along with other information (e.g., capacity, cost, traffic, usage, QoS, GoS) to the Server and does not deal with any routes or path attributes. The registration protocol is also used to negotiate capabilities between the peers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)