August 2023

Committee Reports

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

• AIDC: Automatic Identification & Data Capture Committee
  • Issue: 0039
  • Title: Review Product Marking Implementation Guide (ATIS-0300038)
  • Statement: There are many linear labels still in use in 2022 and this hinders how reliable bar code labels are for enhanced operations, supply chain, asset tracking/recording, even some PCNs are impacted by non-2D product labels.
  • Resolution: ATIS AIDC updated ATIS-0300038, Product Marking Implementation Guide, placing emphasis as to the standard product label, which is a product bar code label that contains a 2D type symbol, which are a MicroPDF417 or a Data Matrix ECC 200. AIDC also updated label placement considerations, scanner considerations, and label content hierarchy for labels with CLEI Code, GTIN, and USI.
  • Status: Final Closure

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

• INC: Industry Numbering Committee
  • Issue: 0952
  • Title: Update TBCOCAG Section 11 – Reclamation when there is an AOCN of Record
  • Statement: CIGRR documented and agreed to reclamation procedures (CIGRR Issue C285a) for iconectiv TRA and the NANPA to follow when an AOCN has not disconnected the reclaimed NXD seven calendar days after NANPA has notified the SP of the reclamation. The TBCOCAG Section 11 - Reclamation And Return Of Numbering Resources should be updated to be in line with the CIGRR established procedures.
  • Resolution:
  • Status: New Issue

  • Issue: 0953
  • Title: Update TBCOCAG Section 10 – Mass Modifications based on CIGRR Utility Procedures changes
  • Statement: Utility Requests submitted to TRA with Expedited Effective Date Timeframes may not be able to be accommodated due to timeframes for utility processing and auto-reschedule impacts. The Utility Process will fail if auto-reschedule is required and/or effective dates may need to be changed, thus not matching NANPAs records. CIGRR reviewed these scenarios and agreed to modify the Utility Procedures with Expedited Timeframes (CIGRR Issue C291). The TBCOCAG Section 10 Mass Modifications should be updated to align with the CIGRR agreed Utility Procedures.
  • Resolution:
  • Status: New Issue

  • Issue: 0954
  • Title: Update TBCOCAG Section 4.6 Operating Company Number (OCN) with NECA provided language
  • Statement: iconectiv TRA is receiving multiple inquiries regarding numbering resource assignments published in the LERG Routing Guide and/or TPM Data Source with inaccurate type of service. There are two scenarios that were discovered while researching these inquiries: 1.An SP obtained numbering resources using its CLEC OCN. The SP also has a Mobile line of business. Although the CO Code was obtained with the CLEC OCN, the CO Code was being used by the SPs Mobile line of business. 2.An SP only has a CLEC OCN even though it has a Mobile line of business. All of its numbering resources are being obtained under the CLEC OCN. This results in Mobile numbering resources (CO Codes and Thousands Blocks) being identified as landline (End Office) and not being correctly identified as Mobile. The following language has been provided by NECA and is in the NECA North American Company Code Assignment Procedures Section 2.1 Structure/Format: Company Codes are assigned for each type of service a company provides. Separate and distinct codes are required for Incumbent Local Exchange Carriers (ILECs), facilities-based Competitive Local Exchange Carriers (CLECs), Unbundled Local Exchange Carriers (ULECs), Local Exchange Resellers (LRSLs), Competitive Access Providers (CAPs), Interexchange Carriers (ICs), IP Enabled Service (IPES) providers, Ethernet Exchange (ETHX) providers, Wireless Carriers (WIRE), Wireless Reseller (WRSL), Personal Communications Service (PCS) provider and Personal Communication Service Resellers (PCSR). Companies offering more than one type of service are required to obtain multiple codes, regardless if a separate legal entity is created.
  • Resolution:
  • Status: New Issue

  • Issue: 0955
  • Title: Update ATIS-0300061, NPA Code Relief Planning and Notification Guidelines Annex A #17 to remove requirement for a minutes approval call and replace with a process for email edits and approval
  • Statement: ATIS-0300061, NPA Code Relief Planning and Notification Guidelines Annex A #17 states a conference call is to be held to approve minutes. The participants attending recent relief planning meetings have agreed to forego meetings to finalize minutes and have instead agreed to provide edits to the NPA Relief Planners through email.
  • Resolution:
  • Status: New Issue

  • Issue: 0956
  • Title: Update Section 5 of the ATIS-0300061, NPA Code Relief Planning and Notification Guidelines to direct NANPA to wait for regulatory direction if a docket is opened to investigate relief of an NPA
  • Statement: Recently, Missouri and Louisiana approved NPA relief outside of NANPA filing a petition on behalf of the industry. NANPA notified Missouri and Louisiana Commission staff that relief was needed and submitted a letter outlining the relief planning process. The Commission staff opened a docket, on their own motion, and included the NANPA letter stating NPA relief was needed. NANPA suggests updating Section 5 of the ATIS-0300061, NPA Code Relief Planning and Notification Guidelines to state if a docket is opened to investigate relief of an NPA, NANPA will not proceed with preparing relief options and will wait for regulatory direction.
  • Resolution:
  • Status: New Issue

  • Issue: 0961
  • Title: Update TBCOCAG To Require NANPA/PA To Obtain NPAC Reports Each Business Day
  • Statement: Today NANPA submits a request for an ad hoc report from the NPAC to determine contamination and the presence of LRNs when 1) thousands-blocks or CO codes are returned or abandoned, or 2) thousands-blocks available in the pool are identified as being over-contaminated (greater than 10%). The NANPA has been authorized to obtain these ad hoc NPAC reports once a week under permission previously granted by the North American Portability Management LLC (NAPM LLC). The NPAC ad hoc reports contains the following data: 1) the total quantity of ported numbers within the thousands-block or CO code, 2) the total quantity of ported numbers within the thousands-block or CO code subtotaled by Service Provider ID (SPID), and 3) the quantity of Location Routing Numbers (LRNs) contained within the thousands-block or CO code. The volume of situations where NANPA needs to request these ad hoc reports appears to be growing. If NANPA were permitted to request these ad hoc reports each business day (as needed), rather than just once a week, it would simplify NANPAs processes, allow for more timely processing of thousands-block and CO code returns, and potentially add eligible thousands-blocks to the pool more quickly.
  • Resolution:
  • Status: New Issue

  • Issue: 0962
  • Title: Update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines to include a notification to NANPA when an OCN no longer has an AOCN (CIGRR Issue C301)
  • Statement: In an effort to improve numbering resource conservation, NANPA begins reclamation procedures when it becomes aware that a service provider may have gone out of business It may be useful for NANPA to be notified when an OCN in BIRRDS has its AOCN removed (records transferred to EMB1) Providing NANPA with notification (either via email at the time of the transfer or via a monthly report) may be beneficial to NANPA in its activities related to resource reclamation. This item has been accepted as an Issue during the July 2023 meeting as Issue C301.
  • Resolution:
  • Status: New Issue

  • Issue: 0957
  • Title: Additional updates to ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines Part 1 and Part 3 Forms for the combined NAS
  • Statement: NANPA has identified additional updates to the ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines Part 1 and Part 3 forms for the combined NAS. The suggested changes are to align the forms with other INC Guidelines and to remove fields that do not apply.
  • Resolution: INC agreed to update ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines, Part 1 form for the combined NAS, with the updates reflected in INC-2023-00060R001. No additional changes were made to the Part 3 form. These changes will be in addition to the changes to the Part 1 and Part 3 forms associated with Issue 905, reflected in INC-2021-0044R001 and INC-2021-0045R001. This Issue will be placed in Initial Pending until the implementation of the combined NAS system.
  • Status: Initial Closure

  • Issue: 0958
  • Title: Additional updates to ATIS-0300089, p-ANI Administration Guidelines forms for the combined NAS
  • Statement: NANPA has identified additional updates to the ATIS-0300089, p-ANI Administration Guidelines forms for the combined NAS. NANPA suggests changing Other (please specify) on the Part 1 form to 911 Governing Authority as that is the only type of change for which Other (please specify) is used. NANPA made updates to the Part 3 form to align with other INC Guidelines.
  • Resolution: INC agreed to update ATIS-0300089, p-ANI Administration Guidelines, with the updates reflected in INC-2023-00063R001 and INC-2023-00064R001. The change to the Part 1 Form will be in addition to the changes in INC-2021-0041R000 (Issue 904). NANPA made updates to the Part 3 form to align with other INC Guidelines; this change will be in addition to the changes in INC-2021-0042R000 (Issue 904). This issue will be placed in Initial Pending until the implementation of the combined NAS system.
  • Status: Initial Closure

  • Issue: 0959
  • Title: NANPA has identified additional updates to the ATIS-0300055, NPA Allocation Plan and Assignment Guidelines forms for the combined NAS. Since the NPA forms will be part of NAS NANPA suggests removing the statement directing the applicant to email the form on the Part 1 form. NANPA also updated the Part 3 form to align with other INC Guideline forms.
  • Statement: Update ATIS-0300055, NPA Allocation Plan and Assignment Guidelines Part 1 to remove the statement directing the applicant to email the form; this change will be in addition to the changes in INC-2021-0029R001. NANPA also made updates to the Part 3 form to align with other INC Guidelines; this change will be in addition to the changes in INC-2021-00030R001. This issue will be placed in Initial Pending until the implementation of the combined NAS system.
  • Resolution: INC agreed to update ATIS-0300055, NPA Allocation Plan and Assignment Guidelines, Part 1 and Part 3 forms with the updates reflected in INC-2023-00066R000 and INC-2023-00067R000. These changes will be in addition to the Issue 902 changes in INC-2021-00029R001 and INC-2021-00030R001. This Issue will be placed in Initial Pending until the implementation of the combined NAS system.
  • Status: Initial Closure

  • Issue: 0960
  • Title: Additional updates to ATIS-0300119 Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Part 3 and Part 5 forms for the combined NAS
  • Statement: NPAC requested the removal of “SOA” from the ATIS-0300119 Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Part 1B and Part 5. INC Issue 940, Additional Updates to the TBCOCAG forms for the new combined NAS made the update to the Part 1B, however, the update was not made to the Part 5. To align all forms, “SOA” should also be removed from the Part 3 form. Therefore, NANPA suggests removing “SOA” from the Part 3 and Part 5.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), with the updates reflected in INC-2023-00069R000 and INC-2023-00070R000. These changes are made in addition to Issue 897 contributions INC-2021-00007R001 (Part 1), INC-2021-00008R001 (Part 1B), and INC-2021-00009R001 (Part 3). Issue 940, Additional Updates to the TBCOCAG forms for the new combined NAS and the associated contributions INC-2021-00079R001 (Part 1B) and INC-2021-00081R000 (Part 5). This issue will be placed in Initial Pending until the implementation of the combined NAS system.
  • Status: Initial Closure

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

• OBF: Ordering and Billing Forum
  • Issue: 3663
  • Title: Moving the Ethernet Virtual Connection Quantity (EVC QTY) Field
  • Statement: Requesting a move of the EVC QTY field from the EVC Form to the ASR Form.
  • Resolution: Moved the EVC QTY field from the EVC Form to the ASR Form.
  • Status: Final Closure

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0167
  • Title: Revision of ATIS-1000020, ETS Packet Priority for IP NNI Interfaces – Requirements for a Separate Expedited Forwarding Mechanism
  • Statement: Current requirements and text on pre-emption in ATIS-1000020 are not consistent with FCC Title 47 Appendix B to Part 64—Wireless Priority Service (WPS) for National Security and Emergency Preparedness (NSEP) issued May 2022, which provides clarifications that permit voice, data, text, and video communications from NSEP users to preempt or degrade other in-progress communications, except for public safety emergency (911) communications.
  • Resolution:
  • Status: New Issue

  • Issue: 0168
  • Title: Revision of ATIS-1000049, End-to-End NGN GETS Call Flows
  • Statement: Current requirements and text on pre-emption in ATIS-1000049 are not consistent with FCC Title 47 Appendix B to Part 64—Wireless Priority Service (WPS) for National Security and Emergency Preparedness (NSEP) issued May 2022, which provides clarifications that permit voice, data, text, and video communications from NSEP users to preempt or degrade other in-progress communications, except for public safety emergency (911) communications.
  • Resolution:
  • Status: New Issue

  • Issue: 0169
  • Title: Revision of ATIS-1000059, Emergency Telecommunications Service Wireline Access Requirements
  • Statement: Current requirements and text on pre-emption in ATIS-1000059 are not consistent with FCC Title 47 Appendix B to Part 64—Wireless Priority Service (WPS) for National Security and Emergency Preparedness (NSEP) issued May 2022, which provides clarifications that permit voice, data, text, and video communications from NSEP users to preempt or degrade other in-progress communications, except for public safety emergency (911) communications.
  • Resolution:
  • Status: New Issue

  • Issue: 0170
  • Title: Revision of ATIS-1000065, Emergency Telecommunications Service (ETS) Evolved Packet Core (EPC) Network Element Requirements
  • Statement: Current requirements and text on pre-emption in ATIS-1000065 are not consistent with FCC Title 47 Appendix B to Part 64—Wireless Priority Service (WPS) for National Security and Emergency Preparedness (NSEP) issued May 2022, which provides clarifications that permit voice, data, text, and video communications from NSEP users to preempt or degrade other in-progress communications, except for public safety emergency (911) communications.
  • Resolution:
  • Status: New Issue

  • Issue: 0171
  • Title: Revision of ATIS-1000086, LTE and IMS Parameters for Supporting NS/EP Priority Services in NGN
  • Statement: Current requirements and text on pre-emption in ATIS-1000086 are not consistent with FCC Title 47 Appendix B to Part 64—Wireless Priority Service (WPS) for National Security and Emergency Preparedness (NSEP) issued May 2022, which provides clarifications that permit voice, data, text, and video communications from NSEP users to preempt or degrade other in-progress communications, except for public safety emergency (911) communications.
  • Resolution:
  • Status: New Issue

  For more information, visit the PTSC 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

AIDC

• Document Number: ATIS-0300038
• Title: Product Marking Implementation Guide
• Type: Revision
• View Here

PTSC

• Document Number: ATIS-1000607.2014(R2023)
• Title: Integrated Services Digital Network (ISDN) – Layer 3 Signaling Specification for Circuit Switched Bearer Service for Digital Subscriber Signaling System Number 1 (DSS1)
• Type: Revision
• View Here

Recent Policy Filings

ATIS

• Date: 07/18/2023
• Description: Ex Parte notification regarding HAC Task Force meeting with FCC (CGA, WTB and OET)
• View filing
• Date: 07/24/2023
• Description: Ex Parte notification regarding HAC Task Force meeting with FCC (CGA, WTB and OET)
• View filing
• Date: 08/23/2023
• Description: Ex Parte notification regarding HAC Task Force meeting with FCC (CGA, WTB and OET)
• View filing

ESIF, NRSC

• Date: 08/09/2023
• Description: Comments in response to FCC rulemaking on advancing the transition to NG911
• View filing

WTSC

• Date: 07/21/2023
• Description: Comments in response to FCC rulemaking regarding WEA performance
• View filing
• Date: 08/21/2023
• Description: Reply Comments in response to FCC rulemaking regarding WEA performance
• View filing