Usage of TRIP in Gateways for Exporting Phone Routes
draft-ietf-iptel-trip-gw-00
| Document | Type |
Replaced Internet-Draft
(iptel WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dhaval Shah , Dr. Hussein F. Salama , Jonathan Rosenberg , Manjunath Bangalore , Rajneesh Kumar | ||
| Last updated | 2015-10-14 (Latest revision 2002-06-07) | ||
| Replaced by | draft-ietf-iptel-tgrep | ||
| 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 | Replaced by draft-ietf-iptel-tgrep | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Scott O. Bradner | ||
| Send notices to | <fluffy@cisco.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a new application of the Telephony Routing over IP (TRIP) protocol. TRIP was engineered as a tool for inter- domain exchange of telephone routing information. However, it can also be used as a means for gateways and soft switches to export their routing information to a Location Server (LS), which may be co-resident with a proxy or gatekeeper. This LS can then manage those gateway resources. We discuss the motivations for this application, and then show how a subset of TRIP is needed for this application.
Authors
Dhaval Shah
Dr. Hussein F. Salama
Jonathan Rosenberg
Manjunath Bangalore
Rajneesh Kumar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)