Telecom - Staff Letter addressed to all Telecommunication service providers (TSPs)

Ottawa, 11 October 2023

Our reference : 1011-NOC2019-0404

BY E-MAIL

To all Telecommunication service providers (TSPs)

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 (CETRP 2021-123), the Commission required Canadian carriers and other telecommunications service providers (TSPs) to file, every six months, status reports on their continuing efforts to deploy STIR/SHAKEN. 

The reports should be filed only if you are providing voice communication services, whether you are participating (or have requested to participate) with the Canadian Secure Token Governance Authority (CST-GA) or not. 

For your convenience, the template provided in the annex can be used to file the next of those reports which is due on 30 November 2023. If you are not in position to provide some of the requested information, please provide a brief justification. When appropriate, the mention ‘unchanged since last report’ can be used for an answer.

Please note the change of wording in questions 3.1.4 and 3.2.3 d) i. and the addition of optional question 3.5.

The report can be filed preferably by using a My CRTC Account (CGkey). Alternatively, the report can be sent directly to jean-francois.harbour@crtc.gc.ca.  Note that these reports will become part of the public record and will be published on the CRTC website. As such, before submitting any documents electronically, you may designate as confidential information referred to in paragraphs 39(1)(a) to (c) of the Telecommunications Act and provide an abridged version for the public record.

You will find here more information on how to open an account, submit documents and identify confidential information.

Yours sincerely,

Originally signed by

Alain Garneau
Director, Telecommunications Enforcement

Compliance and Enforcement Sector

c. c. : Steven Harroun, CCEO, CRTC

Annexe

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 :

All TSPs

NOTICE :

• This report concerns STIR/SHAKEN implementation by TSPs operating in Canada, i.e. using token provided by the CST-GA. You should provide a report whether or not you have received such a token.
• This report covers the period from 1 March 2023 to 31 August 2023 and must be filed with the Commission by 30 November 2023.
• If any of the requested statistics cannot be provided (for instance because the data cannot or was not captured), indicate the reason.
• Please provide all responses in (.word) or (.pdf) formats

You ARE NOT required to fill a report if you are not providing voice services or transit voice calls.

1 SITUATION

1.1 General situation (Optional)

Please check the box corresponding to your situation regarding STIR/SHAKEN on the last day of the reporting period

My TSP is:

1.2 Specific situation (Optional) (This section (questions 1.2.1 and 1.2.2) is to be filled only if you have checked boxes ‘D’ in section 1.1. If you have checked “A”,”B” or “C”, you can ignore this section and go to section 2)

1.2.1 Check the box corresponding to your situation regarding STIR/SHAKEN on the last day of the reporting period

1.2.2 Do you have some kind of arrangement with your underlying provider(s) regarding the level of attestation attributed to the calls originating from your network? Please provide details.

Insert answer here

2 NETWORK

2.1 Please provide the following information regarding your network:

2.1.1 (Optional) The approximate percentage of your network that is IP

Insert answer here

3 STIR/SHAKEN implementation status (Section 3 need to be filled only if you have checked boxes “A , “B” or “C” in section 1.1. If you have checked “D” in section 1.1, you do not need to provide any other information)

3.1 Network readiness

3.1.1 Provide a brief description of the state of the STIR/SHAKEN implementation on your network, including for instance a summary of the work done and next steps, problems encountered, the status and results of equipment testing and participation in those tests, etc.

Insert answer here

3.1.2 Provide 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 IP 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 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 answer here

3.1.3 (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 as above, but the denominator is the total number of IP voice trunks (or trunk equivalents) in the TSP’s network

Insert answer here

3.1.4 Interconnection

1. Provide a list and a brief description of the STIR/SHAKEN enabled interconnections with other TSPs.
   Insert answer here
2. (Optional) Provide the number of STIR/SHAKEN enabled interconnections over your total number of IP interconnections.
   Insert answer here
3. (Optional) Provide information about any issues encountered during STIR/SHAKEN enabled IP interconnections with other TSPs (e.g.: refusal from another TSP, delay from other TSP, non-supported interconnection, hardware limitations, etc. )
   Insert answer here

3.2 Attestation and signature

3.2.1 Provide a brief description of your IP voice network capacity to authenticate and transmit the authentication information to the next TSP in the call path when originating a call.

Insert answer here

3.2.2 (Optional) Please indicate whether your network implementation is in line with or how it differs from the recommendation of the STIR/SHAKEN Guidelines Version 1.0, specifically section 1.3 and 1.3.2.

Insert answer here

3.2.3 Provide a brief description of your IP voice network capacity to perform the following functions:

1. Attest intra-network IP calls, either by using tagging as described in section 1.3 of the STIR/SHAKEN Guidelines Version 1.0 or other means.
   Insert answer here
2. (Optional) Do you assign Attestation level according to the recommendation of section 1.2 of the STIR/SHAKEN Guidelines Version 1.0?
   Insert answer here
3. (Optional) Are you able to assign ‘A’ or ‘B’ level attestation to non-IP switched customers in the cases described in section 1.2 of the STIR/SHAKEN Guidelines Version 1.0?
   Insert answer here
4. Provide a brief description of your IP voice network capacity to handle:
   1. Wholesale customers (Specifically, are you singing calls on the behalf of resellers of communication services ? If yes, which level of attestation are attributed to those calls? If different calls received different attestation level, please specify in which circumstances);
      Insert answer here
   2. Enterprise clients, especially when the calls are using a number provided by another TSP (i.e. multi-homing);
      Insert answer here
   3. Authentication of unsigned calls received from an upstream TSP that either terminate on your IP network or are sent to a downstream TSP through an IP interconnection;
      Insert answer here
   4. Legitimate spoofed calls;
      Insert answer here
   5. Diverted calls; and
      Insert answer here
   6. toll-free calls.
      Insert answer here

3.2.4 Provide statistics identifying:

1. The percentage by month of the number of authenticated voice calls in relation to the total number of voice calls.

For each month of the measurement period, 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 voice calls initiated. To calculate the percentage, divide the numerator by the denominator and multiply by 100.

2. (Optional) The percentage by month of the number of authenticated voice calls in relation to the total number of IP voice calls.

Same numerator as 3.2.4 a) but the denominator is the total number of IP voice calls initiated.

3.2.5 (Optional) Provide the percentage of calls, by month, that are assigned each of level of authentication, as set out in the table below.

For each month of the measurement period, the numerator is the sum of calls given one of the attestation levels as set out in the table below. 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. For a given month, the sum of the percentage for ‘’A’’, ‘’B’’, ‘’C’’ and ‘’No Attestation’’ should be equal to 100.  Some infrastructure vendors cannot provide specific statistics on A, B, and C-level attestations. In this case, the TSP should provide the data in its report to the best of its ability and provide reasons.

3.3 Transit

Please provide a brief description of your IP voice network capacity to 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.

Insert answer here

3.4 Verification and Display

3.4.1 Provide a brief description of your IP voice network capacity to receive and verify the caller ID information when terminating a call.

Insert answer here

3.4.2 Provide statistics identifying:

1. The percentage by month of the number of verified voice calls in relation to the total number of voice calls.

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

2. (Optional) Provide the percentage by month of the number of verified voice calls in relation to the total number of IP voice calls received.

Same numerator as 3.4.2 a), but the denominator is the total number of IP voice calls terminated.

3. (Optional) the percentage by month of the number of voice calls for which the “verstat” parameter is send to the End User Device in relation to the total number of voice calls delivered to customers.

For each month of the measurement period, the numerator is the sum of calls delivered to end users with for which the “verstat“parameter is send to the end user. The denominator is the total number of voice calls delivered to customers. To calculate the percentage, divide the numerator by the denominator and multiply by 100.

3.4.3 (If available) Provide the percentage, by month, of calls by level of authentication for calls delivered to customers, as set out in the table below

For each month of the measurement period, the numerator is the counts of voice calls terminated in IP-enabled end offices for each level of authentication as set out in the table below. 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. For a given month, the sum of the percentage for ‘’A’’, ‘’B’’, ‘’C’’ and ‘’Unsuccessful verification’’ should be equal to 100.  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.

3.4.4 Please response to the following questions regarding the display of STIR/SHAKEN to customers.

1. Does the STIR/SHAKEN authentication use an analytic engine or is the verstat parameter sent to the end-user?
   Insert answer here
2. b) (Optional) If the verstat parameter is used, do you follow the recommendations in section 1.5 of the STIR/SHAKEN Guidelines Version 1.0?
   Insert answer here
3. (Optional) If the verstat parameter is used, please comment on the capacity to send it to IP phones and/or smartphones.
   Insert answer here
4. (Optional) Specifically, how many types of smart devices are available to your customers that have the capacity to display the STIR/SHAKEN information?
   Insert answer here
5. (Optional) If you use an analytic engine, please comment about the capacity to send the results to wireline IP phones and/or smartphones.
   Insert answer here

3.5 Issues

Please provides comments on any technical issues that, in your opinion, should be discussed at the CISC?

4 Cost

4.1 (Optional) Could you provide an estimate of the sum of money ($) you have invested so far for the deployment of STIR/SHAKEN on your network?

Insert answer here

4.2 (Optional) Could provide an estimate of the sum of money ($) that still needs to be invested to deploy STIR/SHAKEN on your network?

Insert answer here

4.3 (Optional) Do you have an estimate of your yearly cost ($) of operation for STIR/SHAKEN

Insert answer here

Date modified:

2023-10-11