Trunk Group Use in ENUM
draft-malas-enum-trunk-sip-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daryl Malas , Tom Creighton | ||
| Last updated | 2009-10-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
This document describes a method for incorporating trunk group parameters into an E.164 Number Mapping (ENUM) response for the Session Initiation Protocol (SIP) [RFC3261] service URI. It defines the use of trunk group contexts as defined in [RFC4904] as additional parameters in the E2U+SIP enumservice NAPTR record [RFC3403] URI.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)