Key Data for a Registry Provisioning Interface draft-guyton-drinks-registry-data-00.txt
draft-guyton-drinks-registry-data-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Debbie Guyton | ||
| Last updated | 2008-07-07 | ||
| 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 defines data that should be included in a provisioning interface for a Registry. The provisioning interface may be used in (near) real time, or periodically, from a service provider's service provisioning system to establish and administer telephone number (TN) and associated routing information in the Registry after necessary validations. Based on 1) effective date/time specified for the data and 2) validation of the TN assignee, these data will be used to define selective routing views for various recipient service providers which would be reflected in ENUM-SIP address servers. In addition, the concept of multiple TNs sharing a common routing pattern simplifies the definition and administration of routing data. D. Guyton Expires 01/07/09 [page 1] Registry Provisioning Interface July 2008
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)