Telecom - Commission Letter addressed to the Distribution List

Ottawa, 23 July 2021

Our reference: 1011-NOC2019-0404

BY E-MAIL

Distribution List

RE: Compliance and Enforcement and Telecom Decision CRTC 2021-123 - STIR/SHAKEN implementation for Internet Protocol-based voice calls

As you know, in Compliance and Enforcement and Telecom Decision CRTC 2021-123 (CETD 2021-123), the Commission required Canadian carriers and other telecommunications service providers (TSPs) to file STIR/SHAKEN implementation readiness assessment reports by 31 August 2021.

For your convenience, a template has been developed and can be used to file the STIR/SHAKEN implementation readiness assessment report. This template is included in the annex of this communication.

The report can be filed by using CGkey or send directly to Jean-Francois.Harbour@crtc.gc.ca.

Yours sincerely,

Originally signed by:

Alain Garneau
Director, Telecommunications Enforcement
Compliance and Enforcement Sector

cc. All Canadian Telecommunication Service Providers

Annex

Please submit as a Microsoft Word Document

DATE:

Fill in Date of Submission

WORKING GROUP:

Network Working Group (NTWG)

TITLE:

TSP Status Report on progress in the implementation of authentication/verification measures for caller ID

SUBJECT:

Status Report on individual TSPs efforts and progress towards implementing authentication/verification measures for caller ID as per Decision 2021-123.

SOURCE:

Company:
Name:
Tel:
E-mail:

DISTRIBUTION:

CRTC

NOTICE:

Analysis

1. Statistics identifying the percentage of authentication/verification-enabled trunks used for IP voice traffic in relation to the total number of voice trunks. 
   • This single metric, represented as a percent (%), is calculated as a fraction and measures the extent of STIR/SHAKEN deployment in the TSP’s network as of the last day of the measurement period.  The numerator is the number of STIR/SHAKEN-enabled SIP voice trunks (or trunk equivalents where a trunk is a DS-0 equivalent) used for voice traffic in the TSP’s network.  The denominator is the total number of voice trunks (or trunk equivalents) in the TSP’s network.  To calculate the percentage, divide the numerator by the denominator and multiply by 100.
   • INSERT ANALYSIS HERE
   1. OPTIONAL Statistics identifying the percentage of authentication/verification-enabled trunks used for IP voice traffic in relation to the number of IP voice trunks. 
      • Same of above, but the denominator is the number of SIP voice trunks (or trunk equivalents) in the TSP’s network
      • INSERT ANALYSIS HERE
2. Statistics identifying the percentage by month of the number of authenticated/verified voice calls in relation to the total number of voice calls.
   • For each month of the measurement period, provide:
   1. The numerator is the sum of calls with an authentication event (i.e., signing by the Authentication Service or tagging (if used as an alternative for intra TSP calls)). The denominator is the total number of IP voice calls initiated. .To calculate the percentage, divide the numerator by the denominator and multiply by 100.

      Month	Percentage by month of the number of signed IP voice calls to the total number of IP voice calls initiated (January 2021 to June 2021)
      January 2021	INSERT PERCENTAGE HERE
      February 2021
      March 2021
      April 2021
      May 2021
      June 2021

   2. The numerator is the sum of calls with an verification event (i.e., verifying an Identity header with the Verification Service) The denominator is the total number of IP voice calls terminated.  To calculate the percentage, divide the numerator by the denominator and multiply by 100

      Month	Percentage by month of the number of verified IP voice calls to the total number of IP voice calls received (January 2021 to June 2021)
      January 2021	INSERT PERCENTAGE HERE
      February 2021
      March 2021
      April 2021
      May 2021
      June 2021

3. Statistics identifying the percentage of authentication/verification-enabled trunks used for IP voice traffic in relation to the total number of voice trunks. 
   • For each month of the measurement period, provide counts of the level of authentication of voice calls terminated in SIP-enabled end offices:
   1. A-level, or full attestation as successfully verified by the Verification Service;
   2. B-level, or partial attestation as successfully verified by the Verification Service;
   3. C-level, or gateway attestation as successfully verified by the Verification Service.
      • Some infrastructure vendors cannot provide specific statistics on A, B, and C-level attestations. However, they may provide statistics on other parameters such as “verstat.”  In this case, the TSP should provide the data in its report to the best of its ability and provide reasons.

        Level of attestation	Percentage of all IP voice calls received by Terminating TSP for their customers. (from 1 January 2021 to 30 June 2021)
        Full Attestation	INSERT PERCENTAGE HERE
        Partial Attestation
        Gateway Attestation
        No attestation

4. Status of implementation readiness
   Please provide the status and result of your STIR/SHAKEN implementation readiness, as of 30 June 2021, including:
   1. i. The status of your STIR/SHAKEN implementation, including the implementation of authentication/verification standards and their subordinate standards, as well as any other related standards; and
      ii. Identification of Canadian-specific requirements and your efforts to implement these requirements.
   2. Provide comments on the following points:
      1. whether your STIR/SHAKEN solution passes along the verstat parameter to the end-user or does your solution interface with an analytic engine?
      2. a brief description of your IP voice network capacity commenting particularly on your ability to:
         1. perform complete intra-network STIR/SHAKEN-compliant calls,
         2. authenticate and transmit the authentication information to the next TSP in the call path when originating a call,
         3. receive and verify the caller ID information when terminating a call,
         4. send the Verstat parameter to wireless and landline end-users when an analytic engine is not used,
         5. transmit the STIR/SHAKEN information when transiting a call received on an IP interconnection from an upstream TSP and sent on an IP interconnection to a downstream TSP,
         6. authenticate unsigned calls received from an upstream TSP that either terminate on the TSP’s IP network or are sent to a downstream TSP through an IP interconnection,
         7. handle diverted calls,
         8. handle toll-free calls,
         9. handle emergency calls, and
         10. handle legitimate spoofed calls;
      3. a brief description of the status of your IP interconnection with other TSPs, including network-to-network interface and user-to-network interface interconnections;
      4. a brief description of the solution adopted to handle enterprise clients; and
      5. the status and results of equipment testing and participation in those tests;
      6. INSERT ANALYSIS HERE

Conclusion

INSERT CONCLUSION HERE

Date modified:

2021-07-23