February 2024

Committee Reports

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

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0116
  • Title: In support of FCC’s request to identify and standardize 988 Location Based Routing mechanism
  • Statement: The 988 Suicide and Crisis Lifeline is a national network of more than 200 crisis centers that helps thousands of people overcome crisis situations every day. These centers are supported by local and state resources as well as the U.S. Department of Health and Human Services’ SAMHSA (Substance Abuse and Mental Health Services Administration). Geolocation services are not currently enabled for 988, as they are for calls to 911. A caller’s location information is not transmitted with a 988 call for possible dispatch of emergency services. The Lifeline automatically routes calls by area code to the nearest crisis center. For example, when a caller based in Virginia with a callback number of a 703 area code calls 988, the Lifeline will route the call to a Virginia Lifeline call center regardless of the caller’s actual location at the time of the call.
  • Resolution:
  • Status: New Issue

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

• INC: Industry Numbering Committee
  • Issue: 0963
  • Title: Update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines with invalid COCTYPE and SSC values for Pooled CO Codes
  • Statement: CIGRR gave TRA and NANPA an action item to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines to indicate that Pooled CO Codes shall not have an NXD COCTYPE of PLN, SIC, TST, AIN, BLG, BRD, CDA, CTV, ENP, FGB, HVL, N11, ONA, RTG, UFA, or 700 or an SSC of A (IntraLATA).
  • Resolution: INC agreed to update ATIS-0300119, Thousands Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines with invalid COCTYPE and SSC values for Pooled CO Codes, with the changes reflected in INC-2023-00095R001.
  • Status: Initial Closure

  • Issue: 0966
  • Title: Update language regarding NPAC and NECA notification in Section 12 Abandoned Numbering Resources of the ATIS-0300119 Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines
  • Statement: Section 12 Abandoned Numbering Resources states that NANPA shall provide the NPAC, TRA and NECA written notice that the SP has terminated service when the appropriate regulatory authority approves the reclamation of abandoned resources. Since NANPA cannot confirm the SP has terminated service and is acting on the direction of the appropriate regulatory authority, Section 12 should be updated to state that NANPA shall notify NPAC, TRA and NECA that the appropriate regulatory authority has directed NANPA to reclaim the abandoned resources.
  • Resolution: INC agreed to update the language regarding NPAC and NECA notification in Section 12 Abandoned Numbering Resources of the ATIS-0300119, Thousands Block (NPA-NXX-XX) & Central Office Code (NPA-NXX) Administration Guidelines with the changes reflected in INC-2023-00101R001.
  • Status: Initial Closure

  • Issue: 0967
  • Title: Remove Rate Center in Section 10.2 Mass Modification Pooled and Non-Pooled CO Codes in the ATIS-0300119 Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines
  • Statement: Section 10.2 Mass Modification Pooled and Non-Pooled Central Office (CO) Codes (NPA-NXX) lists Rate Center as a modification that may change over time, however, Rate Center is not a modification option for a mass modification since it requires an NPAC check and either initial documentation or an MTE. To avoid confusion, NANPA suggests removing Rate Center from the list of modification in Section 10.2.
  • Resolution: INC agreed to remove the Rate Center in Section 10.2 Mass Modification Pooled and Non-Pooled CO Codes in the ATIS-0300119 Thousands Block (NPA-NXX-XX) & Central Office Code (NPA-NXX) Administration Guidelines with the changes reflected in INC-2023-00103R001.
  • Status: Initial Closure

  • Issue: 0968
  • Title: Updates to ATIS-0300050 Carrier Identification Code (CIC) Administration Guidelines and forms for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-0300050, Carrier Identification Code (CIC) Assignment Guidelines, the CIC Application Form – Part 1, and the Appendix 1: Annual CIC Report to align with the combined NANP Administration System (NAS): • Update processing times to 7 calendar days • Update form references to new form names • Update Appendix 1: Annual CIC Report with minor changes and for consistency with other guideline forms • Update the CIC Application Form Part 1 to align with other INC forms and streamline information • Update the CIC Administrator Response/Confirmation Part 3 to align with other INC forms • Update the Confirmation of CIC In Service Part 4 to align with other INC forms • Update language associated with Appendix 1: Annual CIC Report to align with language in the p-ANI Guidelines
  • Resolution: INC agreed to update ATIS-0300050, Carrier Identification Code (CIC) Assignment Guidelines, the Appendix 1: Annual CIC Report, the CIC Application Form – Part 1, the CIC Administrator Response/Confirmation – Part 3 and the Confirmation of CIC In Service – Part 4 to align with other INC Guidelines and changes in the combined NANP Administration System (NAS) as reflected in INC-2024-00007R000, INC-2024-00008R000, INC-2024-00009R000, INC-2024-00010R000, and INC-2024-00011R000.
  • Status: Initial Closure

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

• NRSC: Network Reliability Steering Committee
  • Issue: 0057
  • Title: 988 Lifeline Designated Points of Contact
  • Statement: FCC 23-57 WC Docket No. 18-336 establishes a requirement to deliver notifications to 988 special facility Designated Point of Contact (DPOC). This contact information must exercise “special diligence” to identify, maintain, and, on an annual basis, confirm current contact information. Three 988 special facilities must be contacted, SAMHSA, the VA, and the 988 Lifeline Administrator. However, the Commission does not provide material guidance on establishing these initial DPOCs, leaving each service provider to search out contact, email, and phone individually. This issue would leverage the NRSC membership to work together on identifying these DPOCs for industry use.
  • Resolution:
  • Status: New Issue

  For more information, visit the NRSC home page or contact Mignot Asefa.

• OBF: Ordering and Billing Forum
  • Issue: 3664
  • Title: ASOG: Expansion of Clarification/Notification Request (CNR) Remarks field
  • Statement: There is a business need to expand the CNR Remarks field from the current 225 characters to 450 characters to allow for additional remarks/information being sent to the customer to better explain the reason for the CNR. Resolution: Expanded the CNR Remarks field to 450 alphanumeric characters on Practice 10 (CNR).
  • Resolution:
  • Status: Final Closure

  • Issue: 3665
  • Title: Removal of SSN/TaxID field
  • Statement: History: In May, 2005, the LNPA WG agreed the SSN/TaxID field would not be required, and the NANC endorsed the position. "It is the position of the LNPA WG that the consumer’s Social Security Number/Tax Identification Number shall not be required on an LSR/WPR to port that consumer’s telephone number if the consumer’s Account Number associated with the Old Local Service Provider is provided on the LSR/WPR for identification." At its May 2005 meeting, the North American Numbering Council (NANC) endorsed the LNPA-WG’s position as stated above, and agreed to send a letter to the FCC with its endorsement of the LNPA-WG position. Today: The world has certainly changed since 2005, and technology has flourished. In light of the current state-of-affairs with fraud and data breaches, T-Mobile appreciates the ATIS OBF committee’s consideration of removing the SSN/TaxID field all-together. Although many service providers ceased using this field in or around 2005, we feel having the field present could lead to unwanted situations for any service providers that may not fully understand that they do not ‘have’ to populate it. This subject came up on a conference call internally, some questioning ‘why’ we should even allow someone to populate a SSN – it seemed to folks on our call that removing the field all together was an organic way to safe and effectively avoid confusion.
  • Resolution:
  • Status: New Issue

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 174
  • Title: Investigate Out-of-Band SHAKEN architecture that uses Secure Telephone Identity Call Placement Service (STI-CPS) discovery
  • Statement: While there are no documented issues with hop-to-hop Out-of-Band (OOB) SHAKEN, an alternative OOB SHAKEN architecture that uses a single Secure Telephone Identity Call Placement Service (STI-CPS) per call with STI-CPS discovery instead of hop-to-hop may be possible.
  • Resolution:
  • Status: New Issue

  For more information, visit the PTSC home page or contact Anna Karditzas.

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 0102
  • Title: Lawful interception for Voice Services in the Visiting Public Land Mobile Network (VPLMN) with home-routed roaming
  • Statement: WTSC-LI previously developed and published a standard ATIS-0700005 titled Lawfully Authorized Electronic Surveillance for 3GPP IMS-based VoIP and other Multimedia Services. When that standard was developed home-routed roaming scenarios were not considered, and accordingly, the focus was only on Local Breakout (LBO) as the roaming architecture. Since then, home-routed roaming is now determined to be the preferred approach over LBO, and 3GPP SA3 LI has developed the stage 2 and stage 3 details to support LI in the VPLMN for home-routed roaming architecture. Updates to the ATIS LI Standards would provide the benefit of clarifying the application of the LI in the VPLMN with home-routed roaming to the US LI requirements per CALEA.
  • Resolution:
  • Status: New Issue

  For more information, visit the WTSC home page or contact Anna Karditzas.

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

No new Standards approved this month.

Recent Policy Filings

WTSC

• Date: 02/05/2024
• Description: Ex Parte notification on behalf of ATIS WTSC WEA providing input to the FCC on timeline estimates associated with WEA enhancements
• View filing