LNPA Working Group Meeting
February 14-19


San Francisco, CA
Host Pacific Bell

Minutes

LNPA Working Group

Monday February 14 1-5pm

· Integrated FRS Review

The FRS review was led by John Nakamura. Revisions and discussion were recorded in that document.

Tuesday February 15 8:30 – 5:00pm

On Bridge:

Linda Godfrey Airtouch

· Approve minutes of previous meeting

John Malyar indicated that the portion of the meeting dealing with his deliverables needs to be revised. A draft version of that section of the minutes was distributed. The minutes will be revised and re-distributed.

The NANC Participation Certification form was discussed again. It was again stated that each company should review internally and sign and return based on that internal review.

At the last meeting in Chicago the Pooling sub-team developed the proposed rollout strategy for 3.0. This has been presented to the LLCs for discussion at their February meeting. That proposal is as follows:

                    6/30/00 Supplemental Test Plan Certification

REGION 1

7/3/00 Begin Individual SP Testing 35 Days (30 days for R2.0)

*Regression (84)

*New Feature (120)

*One Time only test cases (40 included in new feature)

08/21/00 Begin Group Testing 25 Days (R2.0-15days-included perf.)

*Regression/Round Robin (5)

*New Feature (52)-(2.0 had 4 test cases- 5 days)

9/25/00 Performance 5 Days

10/2/00 Disaster Recovery 5 Days

10/2/00 Moratorium (if applicable) 5 business days

10/7&8 Install R3.0 on production

Produce & load Migration data file 2 Days

10/9/00 General Availability - Live

10/9/00 Moratorium (if applicable) 5 business days

10/13/00 END

11/5/00 Disaster Recovery Test – Production

Super Region

8/21/00 Begin Individual SP Testing 40 Days (30days in Rel.2.0)

*Regression (84 Test Cases)

*New Feature (120 Test Cases)

10/16/00 Begin Group Testing 25 Days (15days in Rel.2.0 includes Perf.)

*Regression/Round Robin (5day)

*New Feature (52 Test Cases) (20day)

Performance 0 Days

Disaster Recovery 0 Days

11/13/00 Moratorium (if applicable) 5 business days

11/18-19 Install R3.0 on production

Produce & load Migration data file 2 Days

11/20/00 General Availability – Region 2

11/20/00 Moratorium (if applicable) 5 business days

12/4/00 GA- Region 3

12/11/00 GA - Region 4

1/15/01 GA - Region 5

12/15/00-1/6/00 Freeze for Christmas and New Years Holiday’s

1/22/01 GA - Region 6

1/29/01 GA- Region 7

POINTS FOR CONSIDERATION

1.) If Region 1 does not have any pooling implemented

      • no Moratorium periods required (schedule not impacted)
      • Soak(post production) period will not shake out production problems with pooling and porting

      2.) Entire test strategy and rollout is predicated that Neustar provides "certification" that supplemental –like functionality has been successfully tested. SPs minimized required testing i.e. supplemental test plan, due to this Neustar commitment.

      3.) Total 38 SPs (LSMS/SOA) national

LSMS SOA
MW – 26 1 5
NE - 19 9 2
MA - 19 8 1
SW - 24 10 3
SE - 24 10 4
W - 23 12 4
WC - 22 11 3

4.) 3.0 Testing will be managed via "2 region" strategy i.e. Region 1 and all others will be in "Super Region". Neustar has committed to provide appropriate testing support.

5.) Rollout dates only covered Thanksgiving, Christmas, and New Year’s. No other holidays were taken into consideration for this proposal.

There will be a moratorium of pooling activity for five days prior to the conversion to 3.0. This is due to a need to stabilize the systems for the conversion. There was discussion regarding the proposal currently before the LLC that would mandate a level of regression testing for all service providers when a new NPAC release becomes available. The LLC has this on their agenda for their meeting in February. The Pooling sub-team still has the ITP review and M&P Review scheduled for next month. Discussion arose regarding the availability of the testing documentation for vendors. Currently the testing information is posted to the secure section of the NPAC web site. Previously the PEs took an action item to request that those documents be posted on the insecure site so that they would be more readily available for review. Action Item: Neustar is to provide final confirmation on where the testing documents will live; secure or insecure side of the website.

 

The Slow horse meeting was held during the LNPA WG meeting. Steve presented a brief recap of the last meeting regarding the 3x5 timer change. He also discussed his request for input on the information that is being requested from Neustar by the NAPM LLC on behalf of the Slow Horse Subcommittee in regards to peaking of NPAC activity. No responses to the request for input had been received prior to this meeting. The request for information became the first topic of discussion during the Slow Horse section of the meeting. Concern was raised regarding the intent of the request for information and the methodology that Neustar would utilize in providing that information to Slow Horse.

The following is the excerpt from the SOW that was discussed:

    1. What is the TN per second rate during the test period, i.e., the "advertised" NPAC rate?
    2. The current NPAC advertised rate, based on the standard performance test mix is 4.8 TNs/sec.

    3. What is the TN per second rate for broadcast to a single LSMS during the interval that the LSMS broadcasts occur? This will be a deliverable performed under this SOW. The result will be the TN per second rate from the NPAC to a single LSMS based on the Exhibit N TN
    4. activate scenario.

    5. What is the TN per second rate (or notifications/second) for broadcast to a single SOA during the interval that the SOA notifications occur? This is a deliverable performed under this SOW. The result will be the time TN per second rate from the NPAC to a single SOA as a result of the Exhibit N TN activate scenario.
    6. What would be the impact on the results described in questions 1 through 3 of a test involving far larger quantities of numbers, in multiples of the "standard" 336 TN test group?
    7. This will be a deliverable performed under this SOW. The measurements will be the same as in items 1, 2 and 3 but using 2016 activates instead of the 336 in the Exhibit N TN activate scenario. The same size activate requests will be used however, they will be done twenty times.

    8. What would be the impact on the results described in questions 1 through 3 if, instead of the mix described in question 4, substantially larger ranges were used which more closely match current porting patterns? For official NPAC timing purposes, Exhibit N defines the porting pattern. For purposes of this SOW and for determining the load envelope of the LSMS an alternate porting mix (single + range) will be used. Each test scenario defined in items 1-3 above will be run using range sizes of 1000 TNs from seven providers, each sending 2 requests. This equates to an activate scenario of 14,000 TNs.

Due to the discussion that these questions created, Steve again requested that changes and additions be submitted and distributed to the entire Slow horse sub-team by Monday 2/21/00. Beth and Ron will provide verbiage for the proposed question 6. There was considerable concern relating to the focus of the Slow Horse group as to researching only LSMS or also SOA issues. Due to past discussions, the group limited the Slow Horse focus to the LSMS/NPAC interaction. It appeared that the past consensus may be changing. The SOA data will be requested even though it might not be utilized immediately by the Slow Horse under its current focus on the LSMS. It may be used in the future as needed.

There was discussion of the change in the timers and when Neustar would be able to provide information regarding the effectiveness of the change in the 3x5 timer to a 1x15 timer.

Action Item: Marcel will provide a date that that information will be available during this meeting.

 

0001

The OpWest team has committed to having the proposed flows and narratives distributed to the WG prior to the WG’s March meeting.

0002

After discussion and minor textual changes the Maintenance window document was approved. This will be distributed to the WG and through the NPAC to the Cross Regional distribution list. Any changes to this document will require a new PIM issue to be opened.

0005

Donna Navickas presented the WG with further details regarding PIM 5. That information will be distributed prior to March meeting. After discussion, Donna was requested to revise her proposal for review at the next meeting.

Marcel is requesting that Neustar be able to present this at the next cross regional call and the LNPA WG March meeting. He is stating that they are not prepared at this time to give a complete and conclusive report and are requesting additional time to refine the information that they have compiled. Ameritech and most other service providers requested that the minutes reflect that Neustar is failing to meet an agreed upon action item and their concern with Neustar’s failure to meet industry needs.

Prepaid/slamming - Not an integration issue. GTE’s scenario would be wireless only. Refer to WNPSC for review as an integration issue.

There was considerable discussion on the premise of the need for the shortened porting interval. It was based on this need that the three alternatives were developed. It was determined that the group needed additional guidance from NANC to determine the scope of the 3rd report and the necessity of the shortened porting interval. Charles and Shelly were tasked with taking the issues to NANC and requesting clarification

Previously the WG had stated that a documentation only change for the GDMO would not require a re -release of the GDMO. Through discussion of the FRS during yesterday’s meeting, a documentation only change was discovered that would impact a service provider who implemented the GDMO without the documentation change. A document will be published that will contain the behavior changes to the GDMO that normally would be published only when a new point release for 3.0 would be issued. This will convey the information to all providers without a 3.2 version of the GDMO.

 

Wednesday 2/16, 8:30 am - 5 pm,

Discussion opened with the prioritization of change orders.

There was extensive discussion of change order 301 and the proposal to have it implemented prior to Release 4.0. The final determination was that 301 should be included in the proposed package for Release 4.0 but should be presented separately by the PEs to the LLCs for implementation prior to the release. It was proposed that the change be sent to the LLCs and then submitted to Neustar where they can either respond that it is a no charge change, or with a SOW. The WG feels that this is a patch and should have a no or low cost.

Letter to LLC about 301 – Have the PEs take it to the LLC. There was more discussion of the NPAC’s ability to test monitoring of SOA and LSMS associations via NPAC TCP level heartbeat (transport layer). Evidently this is something that currently does exist in some form. Testing of this cannot be done because Neustar will not allow this on the test bed unless the LLCs give permission. Marcel is looking for additional information from internal sources to be able to tell the WG what the tunable values should be since they have performed some testing of this already. Beth will write up questions regarding the tunable parameters for Marcel to distribute internally for a response. The WG is looking for suggestions as to best method of testing. Action Item: Marcel to return with Neustar’s opinion as to what the tunables should be and if this requires testing. If testing and validation of the tunable parameters is required, which would have to be handled through the LLCs, a study would need to be commissioned through a SOW process. Neustar will present a white paper on this issue at the March meeting. This will be a fixed start at 9:00 on Wednesday. The Invalid Departure time presentation will be done following the white paper presentation.

Thursday 2/17, 8:30 am – 5 pm,

Final selection of R4 change orders took place. There will be on final conference call on February 22 to discuss last minute requirement changes. The group also signed off on the following definition of backward compatibility furnished by John Malyar of Telcordia.

The NPAC SMS supports Service Provider Flags for the purpose of:

1. Support of optional functionality

2. Support of release backward compatibility flags for the purpose of not

requiring flash cuts across the Industry

The release backward compatibility flags will be defined with a specific life

span known as sunset value. The sunset value will be minimally one major release

(e.g., defined in 2.0 and removed in 3.0). The sunset value will be defined in

the initial release FRS with an end release value. Ongoing language: All FRS

updates for subsequent updates will warn that the flag is pending removal and

the N-1 FRS must indicate that the Flag will removed in the next Release.

 

It was determined that the July meeting would be in Boston hosted by Bell Atlantic.

Friday 2/18, 8:30 am – 12 pm,

On Bridge:

Dennis Robbins – ELI

Beth Watkins – ATT

M&P review was led by Jean Anthony of TSE. Please refer to that document for discussion and changes.

 

The WG appears to be in a position to submit the release package on the 24th provided the conference call on 22 goes well. The notice should go out on the 24th to the LLCs. Marcel wanted to know when the LLCs would submit the SOW request to Neustar. The WG could not determine that since it is the LLCs responsibility to submit the SOW request to Neustar. Neustar is looking at a 6 week turnaround on the SOW after they receive the package request. That would provide a release GA on September 6th, 2001. Testing on April 20th 2001, ITP in March. Rollout (Production) would be July 13 through September 6th. It was determined that during the June Meeting the WG would need to start working on Release 5.

Discussion arose about adding 179 to the proposed package. Since the changes made to 130 and 192 will be distributed on Monday for the discussion on Tuesday, it was decided to add the changes made to 179 for discussion as well. On Tuesday, the package content will be decided. The final determination of the package content will be made and Charles and Shelly will distribute the proposed package to the LLCs on the 22nd. This will enable the LLCs to have the package two days early and potentially discuss during their February meeting. John Nakamura will update the document with all of the changes and distribute.

Release Status

3.0

4.0

Slow Horse

3rd Report to NANC Clarification

Premise of Customer expectation

Slamming/Prepay

Next Meetings … March 6-9 Denver Host ESI


lmclogo_s.gif (1902 bytes)

 

Send mail to Web Content with questions or comments about this web site.

Copyright © 1999 Neustar, Inc.
Last modified: March 10, 2000