Subject: Re: [Modern] All-IP telecommunications network or TN identifiers

From: Henning Schulzrinne <[email-masked]>
Date: Wed, 3 Jun 2015 21:47:59 +0000

[Catching up on old email]

The ATIS document is broader; see, for example, Section 5.1.1:

.1.1 Numbering Use Case 1 – JIT/ITN Number Assignment for individual TN & block allocation
Sponsor: AT&T
Objective: Explore allocation of numbering resources on a just-in-time, per customer basis within the
framework of a converged platform for numbering lifecycle management supporting:
 Number allocation to service providers.
 Service Provider Portability.
 Distribution of service provider information and routing information for session establishment and
metadata access.
The Registry would enforce numbering resource policies and provide utilization reports for regulatory authorities.
Although depicted in what follows as a centralized registry it might be implemented in a distributed fashion.
Scope:
 Test Requirements: Some entities would need to provide a registry with interfaces to interact with SPs. SPs would need to interface with the registry.
 Specifications: The Service Providers and Vendors would need to agree on standard interfaces to accommodate the use case. Interfaces would need to be agreed upon once participants developed and agreed to the use case. Different protocols could be tested.
 Basic functionality would have to include maintaining a pool of numbers for allocation and ability to display available inventory based on queries for attributes such as location, making assignments, receiving data from SPs about assigned numbers, and distribution of data to service providers/bureaus. It is not clear if portability needs to be implemented in the initial test cases.
 Duration of Test: Test duration will be up to participating Service Providers and Vendors but could be as short as a few days or last longer than one month.
 Depth of Testing: Test will provide proof of concept and validate provisioning. Output:
 Format – A report will be issued.
 Target Audience –Service Providers, Vendors. Non-proprietary information could be shared
with others if approved by participants.
Indication of Interest: AT&T, CenturyLink, Comcast, iconectiv, JSI, and Sprint. The API capabilities for number management are detailed below.

________________________________________
From: Modern [[email-masked]] on behalf of Eric Burger [[email-masked]]
Sent: Friday, May 01, 2015 3:20 PM
To: [email-masked]
Subject: Re: [Modern] All-IP telecommunications network or TN identifiers

So folks on the list have it, the document is at
https://access.atis.org/apps/group_public/download.php/21727/Testbesds_Landscape_Team.pdf

All of the use cases are for legacy carriers doing legacy number routing. The use cases are around how to do ENUM and whether to use NS records, URIs, centralized vs. distributed NPAC, and how to route 800# (free phone) calls.

What are the problems being solved?

> On May 1, 2015, at 3:08 PM, Henning Schulzrinne <[email-masked]> wrote:
>
> For what it's worth, ATIS has already produced a uses cases document, and even a very rough protocol specification, with many of the same organizations listed that are participating in this discussion (but possibly and probably different individuals). See ATIS-I-0000047.