How ENUM, SIP URIs, TRIP, and Gateways Relate
draft-ymbk-enum-trip-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Randy Bush | ||
| Last updated | 2001-07-13 | ||
| 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
The often tenuous relationships between ENUM [RFC2916], TRIP [RFC2871], SIP [RFC2543], and SIP gateways have been confusing. This document attempts to clarify them somewhat.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)