A Gateway Location Protocol
draft-ietf-iptel-glp-00
Document | Type |
Expired Internet-Draft
(iptel WG)
Expired & archived
|
|
---|---|---|---|
Author | Dr. Matt Squire | ||
Last updated | 1999-02-17 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
Given a gateway and a (possibly empty) list of gateway attributes, the 'gateway location problem' is to find a gateway serving the given phone number that satisfies the attribute set. This problem has also been referred to as the 'call routing problem' as the answer returned may not be an IP-PSTN gateway but an intermediate signaling server. Part of the solution to this problem is the maintenance and distribution of the call routing tables. This document describes a protocol for maintaining a distributed call routing database across multiple administrative domains. The protocol uses the Server Cache Synchronization Protocol (SCSP) to maintain the distributed database. This document describes the problem of gateway location and a potential solution that uses SCSP as the foundation for distributing the call routing tables.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)