ARCHIVED - Telecom Commissiom Letter adressed to Paul Cowling (Shaw Communications Inc.) and to the Distribution List
This page has been archived on the Web
Information identified as archived on the Web is for reference, research or recordkeeping purposes. Archived Decisions, Notices and Orders (DNOs) remain in effect except to the extent they are amended or reversed by the Commission, a court, or the government. The text of archived information has not been altered or updated after the date of archiving. Changes to DNOs are published as “dashes” to the original DNO number. Web pages that are archived on the Web are not subject to the Government of Canada Web Standards. As per the Communications Policy of the Government of Canada, you can request alternate formats by contacting us.
Ottawa, 31 May 2019
Our reference: 1011-NOC2018-0242
SVP, Legal and Regulatory Affairs
Shaw Communications Inc.
Re: Shaw request for clarification with respect to the measurement of the jitter threshold established in Telecom Regulatory Policy CRTC 2019-42
On 7 May 2019, the Commission received a letter from Shaw Cablesystems G.P. (Shaw) requesting a formal clarification from the Commission with respect to the measurement of the jitter threshold established in TRP 2019-42.
In Telecom Decision 2018-241Footnote1 (Decision 2018-241), CISC Network Working Group – Non-consensus report on quality of service metrics to define high-quality fixed broadband Internet access service, the Commission established the methodology and thresholds for packet loss and latency quality of service metrics to define high-quality fixed broadband Internet access service to meet the broadband portion of the universal service objective. Subsequently, in Telecom Regulatory Policy 2019-42 (TRP 2019-42), Establishment of an appropriate quality of service metric for jitter to define high-quality fixed broadband Internet access service, the Commission established a jitter threshold of 5 milliseconds (ms).
Specifically, Shaw requested that the Commission issue a letter of clarification identifying that the 5 ms threshold is measured on a unidirectional basis, in other words measured in either the upstream or the downstream traffic flow, and is not intended to represent a “round-trip” measurement.
While latency is typically measured by the industry in a round-trip manner as specified in Decision 2018-241, jitter is typically measured on a one-way basis and in both the upstream and downstream directions. The Commission’s decision defined jitter as being measured in terms of one-way traffic, from a source to a destination. As well, the 5ms jitter threshold established applies to traffic going in either direction between the two measurement points.
Therefore, in accordance with TRP 2019-42, the upstream jitter and the downstream jitter must both be less than 5ms in either direction for a fixed broadband Internet access service to meet the broadband portion of the universal service objective. The upstream jitter or downstream jitter is to be measured between the modem at the customer premises and a server located off-net at the Internet exchange point in a Canadian Tier 1 city.
It should also be noted that the packet loss threshold also applies unidirectionally to the upstream and downstream traffic, and it is only the latency that is to be measured in a roundtrip manner as indicated in CRTC Decision 2018-241.
Original signed by
c.c.: Distribution list
Bell Canada, email@example.com;
Bragg Communications Incorporated (Eastlink), firstname.lastname@example.org;
Canadian Network Operators Consortium Inc., email@example.com;
Cogeco Inc., firstname.lastname@example.org;
Independent Telecommunications Providers Association, email@example.com;
Northwestel Inc., firstname.lastname@example.org;
Quebecor Inc., email@example.com;
Rogers Communications Canada Inc. (Rogers), firstname.lastname@example.org;
Saskatchewan Telecommunications (SaskTel), email@example.com;
TELUS Communications Inc. (TELUS), firstname.lastname@example.org;
Xplornet Communications Inc., email@example.com;
Hyman Glustein, firstname.lastname@example.org;
Fenwick McKelvey, email@example.com;
David Prioriello, firstname.lastname@example.org.
- Date modified: