May 2025

Committee Reports

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

• AIDC: Automatic Identification & Data Capture Committee
  • Issue: 0043
  • Title: Updates to ATIS-0300038.2023, Product Marking Implementation Guide
  • Statement: It is the understanding that any product that is manufactured requires that the country of where the product was manufactured is to be recorded and available in the form of a bar code in either a 1D or 2D symbol. Current practices are manufacturers are recording the Country of Origin as either a separate bar code found on the physical product and/or included within the 2D product label. Therefore, this is needed to be reflected with the ATIS-0300038 document.
  • Resolution:
  • Status: New Issue

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

• INC: Industry Numbering Committee
  • Issue: 0997
  • Title: Update Section 18 Rate Center Consolidations/Changes of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines with consistency edits and to provide NANPA direction when a rate center consolidation is initiated by the regulator.
  • Statement: Section 18 Rate Center Consolidations/Changes of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines only provides direction when a rate center consolidation is initiated by the Service Provider that files a tariff in regulated states and deregulated states. The Maine Public Utilities Commission has initiated a rate center consolidation, the guidelines currently do not address NANPA’s role in a regulatory initiated consolidation. NANPA suggests adding a new section to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines outlining NANPAs role when a regulator initiates a rate center consolidation. In addition, NANPA suggest consistency edits regarding NANPA’s coordination with iconectiv’s Telecom Routing Administration (TRA).
  • Resolution:
  • Status: New Issue

  • Issue: 0998
  • Title: Update Sections 9.1.9 Thousands-Block Transfer Process of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines thousands-blocks must be protected from further assignment and all intra service provider ports completed prior to transferring the thousands-block
  • Statement: NANPA suggests adding language to Sections 9.1.9 Thousands-Block Transfer Process of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines to specify that the relinquishing company must protect the thousands-block from further assignment and complete all intra service provider ports prior to initiating the thousands-block transfer.
  • Resolution:
  • Status: New Issue

  • Issue: 0999
  • Title: Large-Scale Rate Center Consolidation Reference Document
  • Statement: There are references to rate center consolidation in the 2014 letter/white paper to the FCC regarding Large-Scale Rate Center Consolidation Considerations in the Transition from the PSTN to All-IP. Due to anticipated large-scale rate center consolidation efforts, it may be beneficial for the INC to craft a reference document.
  • Resolution:
  • Status: New Issue

  • Issue: 0988
  • Title: Update various sections of the Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (ATIS-0300119)
  • Statement: During the review of the TBCOCAG (ATIS-0300119) for updates related to the new combined NAS system, several other needed updates were noted that relate to iconectiv terms including but not limited to the use of the following BIRRDS terms: • BCD – BCD is a GUI screen only and is not what is being updated. The BCR record is being updated. Using the term “BCD” limits the method of updating a BCR record to only using the online GUI screens and does not allow for other means of updating the BCR records such as any future mechanized/automated method. • Screen – similar to above, use of the term Screen instead of Record in reference to updating or entering data into BIRRDS limits the method for updating records to the online GUI screen noted in the guidelines. In the case of the guidelines noting a specific screen in BIRRDS also limits the guidelines to the use of a particular screen when BIRRDS includes alternate screen options for entry of data into particular records to expedite the data entry. This issue is a general issue for updating the TBCOCAG and open for any and all contributions for modifications. iconectiv will submit a contribution for updates throughout the TBCOCAG related to iconectiv terms, definitions, clarity, TRA/CIGRR processes and any identified trademarking changes. Resolution: INC agreed to update the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines references related to TRA terms and updated “regulatory bodies” for consistency as referenced in INC-2024-00126R000, INC-2024-00161R001, INC-2025-00002R000, and INC-2025-00046R001.
  • Resolution:
  • Status: Initial Closure

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

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0074
  • Title: Revisions to ATIS-0300106 (Intercarrier Call Completion/Call Termination Handbook) and ATIS-0300116 (NGN Interoperability for SHAKEN)
  • Statement: As the SHAKEN framework evolves to incorporate new identity authentication mechanisms, including the use of delegate certificates defined in ATIS-1000092, it is important to ensure consistency and interoperability across all relevant NGIIF ATIS best practices. Currently, key ATIS documents – ATIS-0300106 (Intercarrier Call Completion/Call Termination Handbook) and ATIS-0300116 (NGN Interoperability for SHAKEN) – do not reference or account for delegate certificate guidance. To support accurate call validation, fraud mitigation, and seamless call termination across networks, these documents should be updated to acknowledge and align with the expanded SHAKEN delegate certificate procedures. This ensures that service providers can appropriately hand identity assertions, enhance trust, and maintain compliance as SHAKEN use cases broaden.
  • Resolution:
  • Status: New Issue

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0166
  • Title: Update ATIS-1000094, “Calling Name and Rich Call Data Handling Procedures (SHAKEN)” to align with IETF/STIR
  • Statement: The current v001 version of ATIS-1000094 was published back in 4/15/2021. Since then, the IETF/STIR standards on which it is based have evolved, creating a gap between ATIS and IETF in the mechanisms to support rich call data. For example, ATIS-1000094 does not support the following IETF/STIR capabilities related to rich call data: - draft-ietf-stir-passport-rcd o The "apn" and "icn" keys of the "rcd" claim. o The JSON pointer mechanism used by the "rcdi" claim to create digests over individual elements within an "rcd" claim. o 3rd-party signing of rcd PASSporT (including the "iss" claim). - RFC 9118 -- Enhanced JWT Claim Constraints o Extends the JWT Claim Constraints defined in RFC 8226 to enable the PASSporT credentials to specify claims that must not be included in the PASSporT. Resolution: This Issue was placed into Initial Pending with the closure of PTSC-LB-300. Publication of this document will be put on hold until publication of [Ref 6] draft-ietf-sipcore-callinfo-rcd, SIP Call-Info Parameters for Rich Call Data, and [Ref 7] draft-ietf-stir-passport-rcd, PASSporT Extension for Rich Call Data, and those references are updated with (published) RFC numbers.
  • Resolution:
  • Status: Initial Pending

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

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 0100
  • Title: Support of Location-Aware Map with Alert Presentation
  • Statement: The FCC's WEA Third Report and Order requires the support of integrating location-aware maps into the presentation of alerts. From the final rules: "For Alert Messages with a target area specified by a circle or polygon, when a device has location services enabled and has granted location permissions to its native mapping application, Participating CMS Providers must support the presentation of a map along with an emergency alert message that includes at least (1) the shape of the target area, (2) the user's location relative to the target area, and (3) a geographical representation of a target area in which both the targeted area and user are located."
  • Resolution: This Issue was placed into Final Closure with the publication of ATIS-0700036.v004, Wireless Emergency Alert (WEA) 3.0 Mobile Device Behavior (MDB) Specification.
  • Status: Final Closure

  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.