1. 1 Use Cases & Requirements IETF#78, Maastricht, NL.

2. 2 Re-Recap Registry is the authoritative source for provisioned session establishment data (SED) and related information Local Data Repository is the data store component of an addressing server that provides resolution responses Registry is responsible for distributing SED and related information to the Local Data Repositories Registry Local Data Repository 1. Provision SED 2. Distribute SED Local Data Repository

3. 3 Introduction The latest I-D revision can be found at: – http://tools.ietf.org/html/draft-ietf-drinks-usecases-requirements-03 http://tools.ietf.org/html/draft-ietf-drinks-usecases-requirements-03 There have been two revisions since Anaheim – The first revision (-02, May) incorporated comments and contributions just before the last IETF – The second revision (-03, May) was a result of the discussions at Anaheim and at the interim F2F meeting

4. 4 Use Case Categories Provisioning Mechanisms Interconnect Schemes SED Exchange and Discovery Models SED Record Content Separation and Facilitation of Data Management Lookup Keys Number Portability Misc.

5. 5 Snapshot of Use Cases (1/4) Provisioning – Real-Time – Non-Real-Time Bulk – Multi-request Interconnect Schemes – Inter-SSP SED – Direct v/s Indirect Peering – Intra-SSP SED – Selective Peering – Delegated Name Server

6. 6 Snapshot of Use Cases (2/4) SED Exchange and Discovery Models – Unified LUF/LRF – Using LUF's Domain Name – Using LUFs Administrative Domain Identifier – Co-existent SED Exchange and Discovery Models SED Record Content – SED Record Content – Time-To-Live (TTL)

7. 7 Snapshot of Use Cases (3/4) Separation and Facilitation of Data Management – Separation of Provisioning Responsibility – Destination Groups – Route Groups Lookup Keys – Additions and deletions – Carrier-of-Record vs Transit Lookup Key – Multiplicity of Identical Lookup Keys – Lookup Key Destination Group Modification – Lookup Key Carrier-Of-Record vs Transit Modification – Modification of authority

8. 8 Snapshot of Use Cases (4/4) Number Portability Misc – Data Recipient Offer and Accept – Open numbering plans

9. Data Model 9 0..n 0..1 0..n 1 1 1

10. 10 Next Steps Incorporate any additional use cases (e.g., from our discussions today, as the protocol docs mature) – Any contributions? Discuss and incorporate comments – Otmar provided comments on the list on 7/21 – Any additional review volunteers? Progress to Last Call?