Subject: Re: [Modern] protocols for number management?

From: "Peterson, Jon" <[email-masked]>
Date: Thu, 29 Jan 2015 18:37:56 +0000

The key questions that motivated the creation of this mailing list, anyway, were about how numbering functions might look in the post-transition world, especially when we imagine how a diverse, Internet-based set of applications and services would interface with numbering functions in ways that simply have no precedent in the PSTN.

As such, I don't think we're seeking protocol sophistication for its own sake. We're looking to create tools that could support future ecosystems that enable different trade-offs in how we determine authority, how we provide security, and what sorts of attributes we want to associate with numbering resources in that world. These sorts of principles would lead us to create information models for numbering resources that could be encoded in a variety of ways and extended to support operating environments we only understand imperfectly today.

Not coincidentally, these were, in effect, the motivations behind the TeRQ proposal.

Jon Peterson
Neustar, Inc.

From: <PFAUTZ>, PENN L <[email-masked]<mailto:[email-masked]>>
Date: Thursday, January 29, 2015 at 7:46 AM
To: Erik Chuss <[email-masked]<mailto:[email-masked]>>, "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>
Subject: Re: [Modern] protocols for number management?

Erik:
I would expect much of the functionality to be similar to SMS/800 with some tweaks
The numbering space would be more segmented, e.g. by geography and assignment rules would differ. The users would be SPs not RespOrgs.
Don’t know whether direct query would be supported or not  but the info provided in either case would not include service logic.
I would expect the protocol to differ just because technology has become more sophisticated

Thanks,
Penn

From: Erik Chuss [mailto:[email-masked]]
Sent: Thursday, January 29, 2015 10:32 AM
To: PFAUTZ, PENN L; [email-masked]<mailto:[email-masked]>
Cc: Erik Chuss
Subject: RE: protocols for number management?

Penn,

In thinking about this, in order to help facilitate the discussion and identify potential test bed solutions, what do you envision the appropriate provisioning information to be used for?  As you know the Toll Free system has supported, what we have called ‘line-level number allocation’, since the early 1900’s.  The number administration of the system piece allows for centralized access to numbering resources and equal access to the resources on a ‘first in/first out’ basis. It keeps track of the numbering lifecycle by storing the status of each number (Spare, Reserved, Working, Transitional, Disconnect, etc.).  It is also used to identify the Responsible Organization (Resp Org) of a number and ensures only updates to provisioning be made by the Resp Org of the number (i.e. provisioning security).  There are, of course, more functions of the number admin piece but I just wanted to mention a few high-level topics.  A distributed solution may present special challenges for these items that would need to be addressed.  The key piece though is the provisioning piece.  How do you or the others foresee the system be used for in terms of provisioning appropriate information in the network?  Would it just be used for validation on a ‘push’ basis where the information is distributed to the service providers automatically who can then use it as they see fit or opening the system up for query on an as needed basis?  Is there some other functionality that could be included?

I hope this helps with the initial discussion and facilities expanded discussion.

Erik J. Chuss
North America Toll Free Number Administrator
DSMI/Ericsson, Inc.
RRC-4A1142
1 Ericsson Drive
Piscataway, NJ 08854
Phone: 1-732-699-3422

From: Modern [mailto:[email-masked]] On Behalf Of PFAUTZ, PENN L
Sent: Wednesday, January 28, 2015 12:12 PM
To: [email-masked]<mailto:[email-masked]>
Subject: [Modern] protocols for number management?

ATIS has a landscape testbed activity assembling various use cases that might be examined in a testbed.
One of them involves inventory-less just-in-time number assignment within the framework of the kind of unfied numbering lifecycle management platform discussed at the FCC Numbering Testbed Workshop back in March of 2014.

The question came up as to what sort of protocols might be appropriate for service providers to interact with the registry provider(s), to find available resources, request assignments, and provision appropriate information for distribution to other SPs once the assignment is made. Mechanisms to accommodate this a distributed registry architecture are also of interest (how to make sure the same number isn’t assigned by two different  registry providers in a race condition)

It occurred to me folks on this list might have some suggestions.

Thanks,
Penn Pfautz
AT&T Global Connection Management
+1-732-420-4962