Ms. Balen:
Ms. Connell:
Mr. Sarrazin:

Following are three NPAC Release 4.0 changes discussed during last week’s LNPA
Working Group meeting regarding changes for clarification purposes only.
None of these actually affect any of the functionality, as agreed upon by
the LNPA-WG and documented in the 2/24/00 R4 package, but are designed to remove any
potential ambiguity as well as clarify the desired functional behavior.

1.  NANC 219, NPAC Monitoring of SOA/LSMS Associations
We need to update one of the requirements (words in CAPs indicate the new
text, with the exception of the NPAC and SPID references).
Req 12 - Association Log Report in Summary Format for Individual Service Provider
NPAC SMS shall allow NPAC Personnel, via the NPAC Administrative Interface,
to request ON BEHALF OF AN INDIVIDUAL SERVICE PROVIDER the Association Log
Report on association log data for both types of bind data, recovery
complete data and abort data, in summary format, and shall encode the SPID
value for all other Service Providers.

2.  NANC 240, No cancellation of SVs based on expiration of T2 timer
We need to add a new requirement that says the “Final Create Window” shall
be equal to the applicable “Final Concurrence Window”.  We need this because
we will continue to use the existing tunable windows, but we don’t want to
change the names of the existing ones to match the new notification.

3.  NANC 191, DPC/SSN value edits
We need to update one of the requirements (words in CAPs indicate the new
text, with the exception of the GTT names).

Req 49 - Number Pool Block - Verify All Routing Data When Activating a
Number Pool Block
NPAC SMS shall when SCHEDULING A BLOCK CREATE EVENT OR activating a Number
Pool Block, reject the SCHEDULING OR activate request for any DPC/SSN value
edit inconsistencies for CLASS, LIDB, CNAM, ISVM, or WSMSC, from the new
Service Provider in an SCHEDULING OR activation for a Number Pool Block.

Please refer any questions to Shelly Shaw or myself.

Thanks,

Charles S. Ryburn
Co-Chair LNPA Working Group