IP Telephony Routing Protocol (ITRP)
draft-roy-iptel-itrp-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 an IP Telephony Routing Protocol (ITRP) for intra-ITAD communications. ITRP is a SINGLE protocol that is used between gateways and servers as well as among servers. It uses discovery, registration, update, keep-alive, confirmation, and error-notification messages. The connectionless (e.g., UDP) transport is used and, if needed, multicasting can be used instead of flooding. The connection-oriented (e.g., TCP) transport can also be utilized. ITRP's operation is independent of any signaling protocol and, can serve as a mechanism to provide the reachability information about alias addresses including telephone numbers. The proposed message formats in ITRP are similar to TRIP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)