July 2020

Committee Reports

Click on a committee name below to display this month's issues.

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0105
  • Title: Expansion of Test Bed Regions and Cities
  • Statement: Business Need: The existing indoor location test bed regions have begun to experience access and usability limitations that impact the overall timeline, budgets and efficacy of testing. There are several factors that individually can be managed by the operational test teams however, when combined with overlapping causes has contributed to an overall strain and limitation of the test bed program. Items currently being experienced include building and tenant fatigue due to overuse of the same buildings stage-to-stage, delayed timelines due to increasing difficulty of procuring access to test points, budgetary increases due to additional incentives needed for accessing private spaces, as well as loss of existing buildings due to the locations being well known to past participants. Additionally, the increasing technical requirements of future planned stages, for example with the proposed combined test methodology, is expected to increase pressure for site acquisition and testing. In general, the existing cities have limited test areas which are nearing exhaustion in search possibilities while allowing sufficient diversity of meeting testing objectives. Needed is the consideration of including new test regions that may allow for additional diversity of test cases and an expanded pool of potential participating properties. Including new test regions would provide several benefits including but not limited to; ability to maintain tighter test timelines, ability to limit and/or reset building access costs, increase the diversity of test cases satisfying both wider building profiles as well as maintaining an adequate level of anonymity of test buildings in the Test Bed. Issue Statement: This issue proposes to create additional allowable test regions to include with the Test Bed program, drawing from the following existing ATIS standards: ATIS-0500031.v002 Test Bed and Monitoring Regions Definition and Methodology ATIS-0500038 Recommendations for Extensions to Indoor Test Methodology This issue can consider either including only the existing cities that are identified in ATIS-0500031.v002 or adding new cities to the overall Test Bed Region Definition.
  • Resolution: Publication of ATIS-0500043, Supplemental Test Areas for E9-1-1 Indoor Location Testing
  • Status: Final Closure

  For more information, visit the ESIF home page or contact .

• INC: Industry Numbering Committee
  • Issue: 0879
  • Title: Revisit Assignment of 800-855 line numbers and the 800-855 Assignment Guidelines
  • Statement: The 800-855 Number Assignment Guidelines (ATIS-0300047) were created in 1994 under INC Issue 14, in order to provide guidance to the NANPA in the assignment of line numbers within the 800-855-XXXX resource, called 800-855 numbers. 800-855 numbers are used for the purpose of accessing public services on the Public Switched Telephone Network (PSTN) intended for the deaf, hard of hearing or speech impaired. Services for the deaf, hard of hearing or speech impaired are defined as those which are used generally to benefit this particular user community, e.g., services used by deaf, hard of hearing or speech impaired persons to access a Telecommunications Relay Service (TRS), Message Relay Service (MRS) or any other entity via text telephone service (TTY). A total of ninety-three (93) 800-855 line numbers are assigned, as shown at https://nationalnanpa.com/pdf/800855_Assignments.pdf, and there has not been an assignment made for the past 7 years. The 800-855 Assignment Guidelines were created in 1994, long before the creation of the Interstate Telecommunications Relay Services Database (iTRS Database). Given the fact that very few 800-855 line numbers are being assigned, the INC should consider whether these numbers are still needed. The iTRS database is contracted by the FCC to map 10 digit U.S. telephone numbers to IP addresses or Instant Message screen names using the industry standard ENUM protocol. Video Relay Service and IP Relay users who are deaf or hard of hearing are assigned 10 digit telephone numbers by their chosen default provider. The 10 digit telephone numbers automatically create relay calls when they are called by hearing users. Relay calls which are direct dialed by hearing callers to deaf or hard of hearing persons use the default relay provider to provide interpreting services. Similarly, a call by a deaf or hard of hearing user to a hearing person may be direct dialed on the deaf/HoH user's IP device and will be placed automatically as a relay call using the default provider.
  • Resolution: The intended use for 800-555 numbers to provide services for the deaf, hard of hearing or speech impaired is no longer required due to the FCC’s implementation of a Uniform Ten-Digit Telephone Numbering System for Internet-based TRS in 2008 (FCC 08-151), and the requirement from the 2011 Order (FCC 11-123) that persons holding a toll free number must transition it to a toll free plan associated with a RespOrg. Therefore, INC agreed to sunset the 800-855 Assignment Guidelines and notify the FCC of its decision via a letter dated August 3, 2020. INC agreed to recommend to the FCC that the TFNA assume management of the 800-855 resources. NANPA will also submit a Change Order to remove the application function for the 800-855 line numbers. NANPA will also publish a Planning Letter announcing the sunset of the 800-855 Assignment Guidelines and provide industry notification that these line numbers are strictly assigned for toll free use and no longer are assigned by NANPA.
  • Status: Initial Closure

  • Issue: 0888
  • Title: Add language to the TBCOCAG to address Company Code Reclamation and to direct NANPA/PA to share Reclamation information for Abandoned Numbering Resources
  • Statement: Recently, TMOC and NECA held a call with INC to discuss Company Code Reclamation. Part of the request included NANPA/PA forwarding information to NECA when they receive approval from a regulator to reclaim abandoned numbering resources. In addition, INC needs to determine what actions NANPA/PA should take when NECA notifies them that a Company Code is reclaimed/expired.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), to direct NANPA/PA to share information with NECA when a regulator reclaims abandoned numbering resources as found in INC-2020-00065R001.
  • Status: Initial Closure

  • Issue: 0889
  • Title: Update TBCOCAG TO Clarify Effective Date Intervals for Thousands-Blocks and/or CO Codes
  • Statement: During discussion of Issue 883 where INC clarified language in the TBCOCAG regarding effective dates when an applicant doesnt specify a specific effective date, INC realized that the standard interval of 33 calendar days from the time an applicant requests a block until numbers from the assigned block can be assigned to customers is not clear in the TBCOCAG. INC should review the TBCOCAG language around the 33-day interval, as well as other intervals, to determine if clarifications should be made.
  • Resolution: INC agreed to modify ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), as noted in INC-2020-00074R001, to address the various effective date intervals for thousands-blocks and/or central office codes.
  • Status: Initial Closure

  • Issue: 0892
  • Title: Add language to Sections 11.2.11.1 and 11.3.10.1 of the TBCOCAG that was inadvertently removed during the combining of the TBPAG and COCAG
  • Statement: Recently, we discovered that the following language was inadvertently removed from the Code Return sections of the TBCOCAG during the combining of the TBPAG and COCAG: “If the NPAC report shows an LRN that is not assigned to the code holder returning the code, NANPA will request the NPAC to remove the LRN.” This issue recommends adding the missing text to TBCOCAG Sections 11.2.11.1 and 11.3.10.1
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), to include the missing text as contained in INC-2020-00068R000.
  • Status: Initial Closure

  • Issue: 0872
  • Title: Update guidelines to add minimum aging requirements and other items from FCC 18-177, the Reassigned Number Database order to multiple guidelines
  • Statement: In the Second Report and Order on Advanced Methods to Target and Eliminate Robocalls (FCC 18-177) adopted December 12, 2018, the FCC requires:
    • New minimum aging requirements on NANP telephone numbers of 45 days
    • SP monthly reporting of data on “Permanently Disconnected” Numbers
    • Creation of a “Reassigned Number” Database
    The INC will need to add the new minimum aging requirements in multiple guidelines. INC will also need to review its guidelines for additional updates on the new disconnected number reporting requirement and the “Reassigned Number” database.
  • Resolution: INC made edits to ATIS-0300068, North American Numbering Plan Numbering Resource Utilization/Forecast (NRUF) Reporting Guidelines, and ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), as contained in INC-2019-00010R001. (Note: The TBPAG and COCAG were combined to create the TBCOCAG, and as a result were not addressed.) INC also made updates to ATIS-0300070, Guidelines for the Administration of Telephone Numbers, as contained in the INC-2019-00011R002. These edits were made in order to add language regarding a minimum aging period and requirements as a result of the FCC Report and Order (FCC 18-177) regarding a Reassigned Number Database. The compliance date for the minimum aging period of 45 days becomes effective July 27, 2020. INC agreed to open a separate Issue to address the SP monthly reporting requirements to the Reassigned Number Database and potential new Guidelines for that reporting.
  • Status: Final Closure

  • Issue: 0890
  • Title: Develop Service Provider Guidelines for Reporting Permanently Disconnected Number Data to the Reassigned Numbers Database
  • Statement: FCC Order 18-177 adopted December 12, 2018 requires that a Reassigned Numbers database (RND) be established and that service providers report permanently disconnected number data to it monthly once it is established. INC has agreed that guidelines are needed for service providers in collecting and reporting such data to the RND, and in November 2019 the INC advised the FCC that it would begin developing such guidelines. The Technical Requirements Document (TRD) for the RND were made public in late January 2020, so INC can move forward with developing the guidelines.
  • Resolution: INC developed the new ATIS-0300120, Reassigned Number Database (RND) Guidelines for Service Provider Reporting of Permanently Disconnected Number Data, to assist service providers in maintaining records on and reporting permanently disconnected number data to the RNDA. The Issue closure and publication of these Guidelines were expedited so that these Guidelines would be made available before the record maintenance compliance date of July 27, 2020.
  • Status: Final Closure

  For more information, visit the INC home page or contact .

• OBF: Ordering and Billing Forum
  • Issue: 3643
  • Title: Update the meet point exchange process defined by Issue 3464, MECOD: Develop a more standardized provider to provider process for the communication of meet point information
  • Statement: Update the industry process used to exchange meet point information between providers.
  • Resolution: Industry process for the exchange of meet point information between providers has been updated to incorporate the use of UOM for record exchange to be effective with ASOG V63, September 18, 2021.
  • Status: Initial Closure

  • Issue: 3651
  • Title: ASOG: Update ASR Practice (001) to add a new field for Variable Term Agreement (VTAI) Indicator
  • Statement: There is a business need to update the ASR Practice (001) to add a new Variable Term Agreement (VTAI) Indicator Field to identify if the information populated in the VTA field is a request for a new term agreement or a recap/retain existing term agreement on a change/Move activity.
  • Resolution: Updated the ASR (Practice 001) to add a new field for Variable Term Agreement Indicator (VTAI) and updated the MEC (Practice 018) to add a new field for Other Exchange Company Variable Term Agreement Indicator (OECVTAI) to identify a request for a new term or recap/retain existing term on change/Move activity.
  • Status: Final Closure

  • Issue: 3652
  • Title: Access Service Ordering Guidelines (ASOG): Modify Site Contact (SITE CON) (Practice 001) to include Access Customer Terminal Location (ACTL)
  • Statement: There is a business need to add ACTL to the SITE CON field description (practice 001).
  • Resolution: Added ACTL to the SITE CON field description.
  • Status: Final Closure

  For more information, visit the OBF home page or contact .

• TMOC: Telecom Management and Operations Committee
  • Issue: 0234
  • Title: Revision of ATIS-0300251.2020, Structure for the Representation of Service Providers for Information Exchange
  • Statement: There is a need to add a new clause to ATIS-0300251.2020, Structure for the Representation of Service Providers for Information Exchange.
  • Resolution:
  • Status: New Issue

  For more information, visit the TMOC home page or contact .

• STEP: Sustainability in Telecom: Energy and Protection Committee
  • Issue: 0176
  • Title: Translation Table of Safety Related Voltages and Currents
  • Statement: There is a need to create a new technical report pertaining to a translation and comparison table of safety related voltage, current and power terminology derived from ATIS Standards, NEC 70, 70E, UL Safety Standards, IEC Safety Standards, GR 1089, etc.
  • Resolution: The translation table will be incorporated into Issue 0179, Revision of ATIS-0600001 Electrical Protection Standards and Reference Documents Associated with Telecommunication Networks.
  • Status: Final Closure

  For more information, visit the STEP home page or contact .

Definitions

• New Issue: Business, operational, or technical needs that a committee has reached consensus to address.
• Issue in Initial Closure: Issues for which a committee has reached consensus on a proposed resolution. The industry has a 21 calendar day period to review and comment on the consensus resolution developed by the committee. The committee's consensus resolution concludes its work on an issue unless new or substantive information is brought forth. During the 21 day review period, comments on a consensus resolution may be provided to the committee contact and committee leaders.
• Issue in Initial Pending: Issues previously in Initial Closure for which new and substantive information impacting the consensus resolution has been received. An issue may also be in Initial Pending if output that may impact the consensus resolution is expected from another industry group, regulatory body or similar organization.
• Issue in Final Closure: Issues for which work is completed and the resolution accepted by the industry.

Recently Approved ATIS Standards

ESIF

• Document Number: ATIS-0500043
• Title: Supplemental Test Areas for E9-1-1 Indoor Location Testing
• Type: New
• View Here

INC

• Document Number: ATIS-0300068(2020-07)
• Title: North American Number Plan Numbering Resource Utilization/Forecast (NRUF) Reporting Guidelines
• Type: Revision
• View Here
• Document Number: ATIS-0300070(2020-07)
• Title: Guidelines for the Administration of Telephone Numbers
• Type: Revision
• View Here
• Document Number: ATIS-0300119(2020-07)
• Title: Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG)
• Type: Revision
• View Here
• Document Number: ATIS-0300120(2020-07)
• Title: Reassigned Number Database (RND) Guidelines for Service Provider Reporting of Permanently Disconnected Number Data
• Type: New
• View Here

PTSC

• Document Number: ATIS-1000090
• Title: National Security Emergency Preparedness Next Generation Network Priority Service (NS/EP NGN-PS): Transport Level Packet Marking and Packet Scheduling in 5GS
• Type: New
• View Here
• Document Number: ATIS-1000091
• Title: Mechanism for International Signature-based Handling of Asserted information using toKENs (SHAKEN)
• Type: New
• View Here

Recent Policy Filings

INC

• Date: July 22, 2020
• Description: Correspondence announcing the completion of the INC Reassigned Number Database (RND) Guidelines for Service Provider Reporting of Permanently Disconnected Number Data (ATIS-0300120)
• View filing

NRSC

• Date: July 20, 2020
• Description: Comments in response to FCC Public Notice proposing changes to the FCC’s Network Outage Reporting System (NORS) and 911 Reliability Certification System
• View filing

SNAC

• Date: July 29, 2020
• Description: Comments in response to FCC Public Notice seeing input on petition to implement a competitive procurement process to select the Toll Free Numbering Administrator (TFNA)
• View filing

SYNC

• Date: July 13, 2020
• Description: Comments in response to the National Institute of Standards and Technology (NIST) Request for Information (RFI) seeking input about public and private sector use of positioning, navigation, and timing (PNT) services, and standards, practices, and technologies used to manage cybersecurity risks, to systems, networks, and assets dependent on PNT services.
• View filing