1 / 10

Session Establishment Data Registry Requirements and Use Cases

Explore the provisioning and distribution mechanisms of Session Establishment Data (SED) in address server components, emphasizing on separation and facilitation of data management. Learn about lookup keys and number portability scenarios.

pillan
Télécharger la présentation

Session Establishment Data Registry Requirements and Use Cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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 1. Provision SED 2. Distribute SED Local Data Repository Local Data Repository

  3. Introduction • The latest I-D revision can be found at: • 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. 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. 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. Snapshot of Use Cases (2/4) • SED Exchange and Discovery Models • Unified LUF/LRF • Using LUF's Domain Name • Using LUF’s Administrative Domain Identifier • Co-existent SED Exchange and Discovery Models • SED Record Content • SED Record Content • Time-To-Live (TTL)

  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. Snapshot of Use Cases (4/4) • Number Portability • Misc • Data Recipient Offer and Accept • Open numbering plans

  9. Data Model Data Recipient ROUTING GROUP SED Record 0..n 0..n 1 0..n 0..n 0..n 1 0..1 DESTINATION GROUP 1 0..n 0..n 0..n Public Identity RN TN Range

  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? 

More Related