DRINKS WG Key Data for a Registry Provisioning Interface

1. DRINKS WGKey Data for a Registry Provisioning Interface draft-guyton-drinks-registry-data-00 IETF 72 – Thursday July 31 2008 Debbie Guyton, Ph.D. – dguyton@telcordia.com IETF DRINKS WG

2. Agenda • Purpose of this Contribution • Key Provisioning Interface Data Concepts • Validation Control of Distribution • Summary of Benefits IETF DRINKS WG

3. Purpose of this Contribution • Key data concepts that should be included in a provisioning interface and Registry • provides additional benefits above and beyond the basic TN and associated routing information • To get consensus that these concepts are beneficial to the industry • To identify other parties interested in contributing to the development of a provisioning WSDL for a Registry database using these concepts IETF DRINKS WG

4. Key Provisioning Interface Data Concepts • Basic TN and associated Routing Information • Dial Code to Destination Association using a Destination Tag (DT) • The DT is the name of a common routing pattern (a combination of destination URIs and Resource Records for various services) with which the Dial Code is being associated • Effective Date/Time to provide the capability to “register” Dial Code and associated routing information in advance of use • Necessary for timely handling of a TN port • Facilitates network planning and re-arrangements • Selective Routing using Recipient Groups • Service Providers may be associated with a group (they share a common route) • Grouped based on level of trust, geographic needs, other • Different groups may be provided different routing information • If no distinction in routing is needed, a default group of “All” may be used • Use concept of Validation to Control the Distribution • From a Registry database to address servers IETF DRINKS WG

5. Validation Control of Distribution • A Dial Code (TN) may be “registered” by multiple service providers • Necessary for timely handling of TN ports • Only one entry can be valid at any given time • A Validation Process run at each date/time of distribution assures that only “valid” Dial Code and Routing Data get distributed to address servers • A TN – to – Assignee Validation can be performed in near real-time upon reaching an effective date/time or as a TN port becomes effective, so that only valid records are distributed • Necessary for most timely handling of a porting process • Drives the delete of old record(s) in each address server and the add of new record(s) for the valid assignee for the TN • Recommendation is to allow a Validation Process to control the distribution of data to address servers driven by change in TN assignee or effective date/time IETF DRINKS WG

6. Summary of Benefits • A Validation process for the TN- to-Assignee relationship allows the most timely distribution of a TN port as it becomes effective and drives the removal of old records • Use of effective date/time allows records to be included in the Registry in advance of use • Data is already defined for TN ports • provides flexibility in pre-defining data for network planning and re-arrangements • Use of Recipient Groups allows the capability of selective routing by providing different entry points to different groups of service providers • Use of a Destination Tag allows multiple TNs to share a routing pattern • Routing Information can be based on the DT, not individual TNs • Simplifies definition and administration of routing data IETF DRINKS WG

7. Thank YouQ&A IETF DRINKS WG