INC Report to the NANC May 18, 2004 Ken Havens - INC Chair Adam Newman - INC Vice Chair

1. INC Report to the NANCMay 18, 2004Ken Havens - INC Chair Adam Newman - INC Vice Chair

2. Future INC Meetings • Next Meeting: June 8-11 in Overland Park, KS • Details on all future meetings can be found at: www.atis.org/atis/clc/inc/inccal.htm

3. Issue 436: Revise Section 8.2 of TBPAG for State Authority in Multiple LRN Request Situations Issue addressed March NANC action item for inclusion of “additional” text NANC Chair notified of Initial Closure of the Issue via e-mail per NANC action item, as well as the results of the 4/23/04 INC Interim General Session Conference Call INC respectfully requests that any future NANC communications to the INC be captured in NANC action items and/or communicated to the INC in writing by the NANC Chair Issue 407: Treatment of Dedicated Codes for Single Customers in a Pooling Environment Issue addressed process flows for requesting dedicated codes in a pooling environment The Issue went to Initial Closure but given its policy implications will not become Final until regulatory direction is received Paragraph 14, NRO IV: “In addition, we direct the NANPA to cease assignment of NXX codes to carriers after they are required to participate in pooling. Carriers required to participate in pooling must request and receive numbering resources from the national Pooling Administrator (PA),” INC recommends an operational change that codes dedicated to a single customer in a pooling environment be processed directly through NANPA rather than through the PA LNPA Subcommittee

4. Issue 369: Forecasting In September 2002, INC raised a concern at the NANC regarding SP forecasts in the Pooling Administration System (PAS) The NANC tasked the NOWG with analyzing all aspects of the situation In November, 2002, the NOWG presented its findings to the NANC and the NANC subsequently forwarded this report to the FCC for action INC is still awaiting a response from the NANC in order to conclude its work on this Issue LNPA Subcommittee (cont.)

5. The North American Numbering Plan Numbering Resource Utilization/Forecast Report (NRUF) was designed to provide a reasonable “snapshot” view of number utilization and categorization, not a precise account of every TN. INC participants explained that there are four acceptable ways of reporting on contaminated blocks as stated in the NANPA NRUF Job Aid (see following slide): Donating carrier has the option of reporting on contaminated TNs or not Receiving carrier has the same option of reporting on contaminated TNs or not This may result in both unreported and double reported TNs within contaminated blocks. INC NRUF Guidelines incorporate and reference all FCC Orders as to how carriers must report telephone numbers on NRUF, FCC Form 502. Straw poll of INC members shows individual carriers’ systems have been built per FCC Form 502, NRUF Guidelines, & the NRUF Job Aid. Any changes to NRUF reporting requirements would likely call for system changes. As stated in the INC NRUF Guidelines, “Utilization calculated using NRUF data is distinct from that reported on Months to Exhaust worksheets submitted to NANPA or the PA to qualify for codes or blocks.” Recommendation: NANPA should be asked to provide an analysis on the scope of “double reporting” on the contaminated TNs in donated and received blocks as reported on the NRUF. CO/NXX Subcommittee: Response to NANC Action Item

6. Reporting Utilization on Contaminated Blocks (NRUF Job Aid) It is recommended that carriers report utilization in the case in which a contaminated block has been donated to the pool. In this case, the carrier would mark an “X” in the Donated to Pool Column, and also report on the status of the contaminating TNs. For those reporting using the FTP submission, the carrier should report 1000 in the 11th field, and the carrier should report on the status of the contaminating TNs (U1S or U3S). The carrier should calculate the utilization in the 12th field based on the formula listed in Section IX. Form 502 EFT Submission. It is recognized that many carriers have made efforts to automate their TN administration systems, and so carriers will not be expected to reprogram their systems if they are not currently reporting on contaminated numbers, although the carrier should be prepared to provide evidence on the status of any contaminated TNs as long as the TN is still in the carrier’s inventory. ** March 17, 2004 clarification -- If you are reporting on a contaminated block you have received from the pool (the PA has assigned the block to you), and you are not the LERG Assignee for that thousands-block, you are not required to report the status of the contaminating TNs. CO/NXX Subcommittee: Response to NANC Action Item (cont.)

7. INC Issue Summary Note: • 85 meeting time man-hours were spent on NANC-related issues (65 for the NANC NRUF action item & 20 for the NANC LRN action item) • 15 meeting time man-hours were spent discussing issues relating to FCC Change Orders (both NANPA & PA)

8. Relevant INC Web Sites • INC Homepage (front page to all INC links): http://www.atis.org/atis/clc/inc/inchom.htm • INC Calendar (future meeting logistics/agendas): http://www.atis.org/atis/clc/inc/inccal.htm • INC Issues (historical and active links): http://www.atis.org/atis/clc/inc/incissue.htm • INC Meeting Records: http://www.atis.org/atis/clc/inc/incmtgrc.htm • INC Published Documents: http://www.atis.org/atis/clc/inc/incdocs.htm