TRIP Transit Network Selection
draft-walker-iptel-trip-tns-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dave R. Walker | ||
| Last updated | 2001-02-26 | ||
| 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
Conventional telephony signalling commonly uses E.164 addresses to route calls to their destination. However, selection of the signalling and media paths can be influenced by other considerations. Some such considerations may be user specified, and may differ from that which the network operator would normally choose. In some cases, support for such user-specified options may be required by national regulation. The choice of Transit Network (e.g. selection of long distance carrier) is such a case. This draft describes three ways that a Transit Network Selection (or TNS) mechanism can be added to the TRIP protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)