Presentation on theme: "INC Report to the NANC 10/10/2007 1 Industry Numbering Committee (INC) Report to the NANC October 10, 2007 Ken Havens, INC Chair Adam Newman, INC Vice."— Presentation transcript:
INC Report to the NANC 10/10/ Industry Numbering Committee (INC) Report to the NANC October 10, 2007 Ken Havens, INC Chair Adam Newman, INC Vice Chair
INC Report to the NANC 10/10/ INC Meetings: –April 30-May 4, 2007, Minneapolis, MN –June 25-29, 2007, Overland Park, KS –August 13-17, 2007, San Antonio, TX –October 1-4, 2007, Washington, DC Interim VoIP Subcommittee Meetings –18 interim meetings have been held since the last report Next INC Meeting: –December 10-13, 2007, Napa, CA Details on all future meetings can be found at: INC Meetings
INC Report to the NANC 10/10/ CO/NXX Subcommittee Issue 545: Removal of Switch CLLI Information from the NANPA Website Issue 545 Removal of Switch CLLI information from NANPA Website was accepted to address national security concerns documented in NRRIC Issue 0237: Removal of Unnecessary Switching Entity Information from Public Access; as well as other security-oriented governmental bodies Issue 545 directs the NANPA to remove Switch CLLI information from its Public Website; NANPA will continue to provide such information to authorized SPs and Regulators via the NANP Administration System (NAS) With FCC approval of NANPA Change Order 13, implementation was effective October 1, 2007.
INC Report to the NANC 10/10/ LNPA Subcommittee Issue 519: Pool Replenishment At the request of the PA and the NOWG, the INC explored options to ensure that the PA is able to maintain a sufficient quantity of blocks available for assignment to satisfy the anticipated demand while maintaining no more than a six-month inventory, per the Thousands- Block Pooling Contractor Technical Requirements document, section A number of options, including forcing an SP to open a new code, were found to be either unenforceable or could have had negative impacts on end users. INC agreed that PAS should ask SPs via a pop-up box to take a portion of their requested blocks from the existing resources and the remaining blocks from a code opened for pool replenishment. This is intended to encourage SPs to share the burden of pool replenishment and discourage a single SP from taking all the remaining blocks in a pool. The Issue resolution results in changes to the Guidelines and a PA change order will be required.
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability The INC Issue is in response to a NANC Action Item: to take the lead in developing a technical response/recommendation regarding the... VRS [Video Relay Service] interoperability issue raised during the NANC meeting. The NANC transcript defined the matter as follows: In order for VRS to be functionally equivalent to voice telephone services, deaf and hard of hearing individuals, using video broadband communications, need uniform and static end-point numbers linked to the NANP that will remain consistent across all VRS providers, so that they can contact one another and be contacted to the same extent that PSTN and VoIP users are able to identify and call one another... [and] support dialing uniformity for VRS and point-to-point video users. The INC report will focus on both the Number Assignment paradigm and the Number and Routing Database which will be required to support this functionality.
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability Video Relay Service (VRS) VRS allows persons who are deaf or hard-of-hearing to communicate through the telephone system with hearing persons. The VRS caller, using a television or a computer with a video camera device or videophone and a broadband (high speed) Internet connection, contacts a VRS Communications Assistant (CA), who is a qualified sign language interpreter. They communicate with each other in sign language through a video link. The VRS CA then places a telephone call to the party the VRS user wishes to call. The VRS CA relays the conversation between the parties -- in sign language with the VRS user, and by voice with the called party. A voice telephone user can also initiate a VRS call by calling a VRS center, usually through a toll-free number. Photo Courtesy of Sorenson Communications
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability Working Proposal To maintain interoperability and help achieve functional equivalency for VRS, the INC likely will propose that: NANP numbers be assigned to deaf and hard of hearing relay users A Neutral Third Party Administered Central Database to support interoperability among relay providers by linking the relay users NANP number to the necessary Internet address The same approach be applied to other Internet-based relay services
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability Number Assignment Options (Assignment to VRS Deaf or Hard-of-Hearing Relay Users) The INC is considering the following options for number assignments: VRS service providers obtain numbers from existing voice service providers and in turn assign them to VRS users. VRS service providers obtain numbers from a neutral third party and in turn assign them to VRS users. VRS users could obtain numbers directly from voice service providers and arrange for routing to their chosen VRS provider for incoming calls.
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability VRS Number and Routing Database - The INC is considering three major alternatives for implementing a central database: Number Portability Administration Center (NPAC) – The NPAC is the entity that maintains the database of record for local number portability (LNP) in the United States and Canada. It has been proposed that the NPAC could also associate Universal Resource Identifiers (URIs) with deaf relay user telephone numbers so as to meet the database goals required for VRS calls. Dynamic DNS – Dynamic DNS (DDNS) is a standard capability used to link domain names to dynamic IP addresses. The deaf relay users equipment would provide its IP address to the DDNS Server where it would be associated with the relay users telephone number. DNS with Delegation to VRS Service Provider – This option is similar to DDNS, except the VRS users IP Address is held in a DNS server maintained by the called deaf relay users designated VRS provider. Standard DNS delegation procedures make the IP Address available to other VRS providers.
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability The INC Report: Status The draft report currently contains over 50 pages comprised of 7 sections and 4 appendices based on over 100 contributions towards the development of the report. The report is expected to contain a section that identifies components determined to be outside the scope of INC, but items that need to be considered in the overall design and implementation to achieve VRS Interoperability. The collective membership of the INC, including subject matter experts from the VRS Industry, has invested over 2,500 member/staff hours to date assembling and editing the VRS Interoperability Report. INC has been and will continue to meet twice a week until this report is finalized.
INC Report to the NANC 10/10/ INC VoIP Subcommittee Issue 510: Internet-Based Relay Services and Interoperability Additional Points The INC believes the use of NANP resources will facilitate the provision of E911 service to relay users. The INC believes the Number and Routing Database should be operated by a Neutral Third Party with the appropriate Privacy & Security Considerations. The INC Report does not address how, or for which aspects of this service, Service Providers will be reimbursed by the TRS fund.
INC Report to the NANC 10/10/ Issue 407: Treatment of Dedicated Codes for Single Customers in a Pooling Environment Issue 534: Development of p-ANI Guidelines Issue 526: Edit COCAG regarding disconnect for NXXs in Telcordia BIRRDS Issue 539: Clarification to Section regarding block assignments created/activated in the NPAC Issues Remaining in Initial Pending
INC Report to the NANC 10/10/ Issues in Final Closure Issue 544: Exchange of an NPA/NXX Issue 540: Extend the Use of the Remarks Field on the Part 1A Issue 521: Resolve Gap Between INC Guidelines and TMOC Standards Issue 533: 500 NPA Exhaust Issue 542: Update Part 2 Forms Issue 545: Removal of the Switch CLLI Information from NANPA Website Issue 509: Abandoned CIC Assignments Issue 538: Rate Center Updates/Changes That are not Part of a Consolidation of Formal State Issue 541: Assigned and then Ported Numbers from Thousands Blocks Donated to the Pool
INC Report to the NANC 10/10/ Issues in Final Closure (cont) Issue 532: Kinsale Mobile, Inc. Application for ERC Issue 546: Modification of requirements for request of an ERC Issue 548: PCS N00 Relief Clarifications Issue 528: Testing and Code Opening Guidelines for NPA-NXX-X Blocks
INC Report to the NANC 10/10/ Issue 552: Pooled Code Allocation when Jeopardy is Declared Issue 551: Amend Section of the COCAG to address treatment of CO code requests that come from the Pooling Administrator Issue 519: Pool Replenishment Issue 554: Amendment to Section 6.5 of the 900 NXX Code Assignment Guidelines Issue 547: Revise NPA Relief Planning Guidelines for Revised Timeframes and General Updates Issue 550: Modifications to NPA Allocation Plan Section 13 (to mirror changes made in section 12 Issue 553: Update the PAR document to include Administrative Functions Issues in Initial Closure
INC Report to the NANC 10/10/ INC Homepage (front page to all INC links): INC Calendar (future meeting logistics/agendas): INC Issues (historical and active): INC Meeting Records: INC Published Documents: Relevant INC Web Pages