Robocalls

Timeline

June 2003: Do not call registry, telemarketing rules
October 2003: DNC enforcement starts
August 2006: RFC 4474: Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
January 2008: RFC 5039: The Session Initiation Protocol (SIP) and Spam
February 2008: Do-Not-Call Improvement Act of 2007
December 2010: Truth in Caller ID Act: 47 USC 227(e): "It shall be unlawful for any person within the United States, in connection with any telecommunications service or IP-enabled voice service, to cause any caller identification service to knowingly transmit misleading or inaccurate caller identification information with the intent to defraud, cause harm, or wrongfully obtain anything of value, ...".
June 22, 2011: FCC report to Congress: Caller Identification Information in Successor or Replacement Technologies
October 18, 2012: FTC workshop: "Robocalls - All the Rage" presentation
April 2, 2013: FTC robocall challenge winner announced
June 2013: IETF STIR effort started
July 2013 (IETF 87): IETF STIR BOF
November 2013: IETF STIR working group formed
September 2014: RFC 7340: Secure Telephone Identity Problem Statement and Requirements
June 10, 2015: Senate Committee on Aging: testimony by H. Schulzrinne
June 2015: FCC 15-72: TCPA Omnibus Declaratory Ruling and Order; "[W]e affirm that nothing in the Communications Act or our rules or orders prohibits carriers or VoIP providers from implementing call-blocking technology that can help consumers503 who choose to use such technology to stop unwanted robocalls. Consumers currently have the choice to use call-blocking technology to block individual numbers or categories of numbers, and may continue to do so."
July 23, 2015: Compliance and Enforcement Notice of Consultation CRTC 2015-333: Empowering Canadians to protect themselves from unsolicited and illegitimate telemarketing calls
The Commission is gathering information from Canadians and the telecommunications industry to enhance the protections for Canadians from unsolicited and illegitimate telemarketing calls delivered on all telephony platforms by telecommunications service providers.
July 26, 2016: FCC blog post: Cutting off Robocalls
August 2016: FCC R&O 16-99: Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991
September 26, 2016: FCC blog post: Tech Impacts on Robocalls and Spoofing
September 30, 2016: FCC CGB: Clarification on blocking unwanted robocalls; "We clarify here that voice service providers may block such calls when requested by the spoofed number's subscriber, e.g., a government agency such as the IRS. Such calls are presumptively spoofed and thus likely to violate the Commission's anti-spoofing rules."
October 26, 2016: Robocall strike force report
November 7, 2016: Compliance and Enforcement and Telecom Regulatory Policy CRTC 2016-442: Empowering Canadians to protect themselves from unwanted unsolicited and illegitimate telecommunications
The Commission finds that the technical solutions available to Canadians to protect themselves from unwanted unsolicited and illegitimate telecommunications are not sufficient. As such, the Commission sets out its findings on technical solutions that Canadians could use to protect themselves from unwanted unsolicited and illegitimate telecommunications and, for the purposes of empowering and informing Canadians, directs telecommunications service providers that provide retail voice services to report to the Commission, within 180 days of the date of this decision, details on the opt-in filtering service(s) they offer or propose to offer to their subscribers.
January 2017: ATIS-1000074: Signature-based Handling of Asserted information using toKENs (SHAKEN)
January 9, 2017: Compliance and Enforcement and Telecom Notice of Consultation CRTC 2017-4: Measures to reduce caller identification spoofing and to determine the origins of nuisance calls
The Commission hereby initiates a proceeding to build on its previous proceeding to enhance protections for Canadians from unwanted unsolicited and illegitimate telecommunications. Specifically, the Commission will further examine the development and implementation of technical solutions to (i) prevent spoofing of caller identification information, and (ii) trace and identify the source of a call. The Commission will also consider establishing associated regulatory measures as appropriate.
February 2017: STIR draft-ietf-stir-rfc4474bis-16 final draft
March 23, 1017: FCC NPRM FCC 17-24: Advanced Methods to Target and Eliminate Unlawful Robocalls
April 28, 2017: Robocal strike force update
May 19, 2017: FCC Consumer Advisory Committee recommendation
July 2017: RFC 8197: A SIP Response Code for Unwanted Calls
July 2017: ATIS-1000080: Signature-based Handling of Asserted information using toKENs (SHAKEN): Governance Model and Certificate Management
November 13, 2017: DOJ: Last Defendant in the United States Pleads Guilty in Multimillion Dollar India-Based Call Center Scam Targeting U.S. Victims victim impact statement
November 16, 2017: Compliance and Enforcement and Telecom Decision CRTC 2018-32: Measures to reduce caller identification spoofing and to determine the origins of nuisance calls
Parties are invited to comment on the Commission's proposal to require that all Canadian telecommunications service providers implement universal call blocking within nine months following the imposition of such requirements.
November 17, 2017: FCC R&O and NPRM 17-151: Advanced Methods to Target and Eliminate Unlawful Robocall; "Specifically, we adopt rules allowing providers to block calls from phone numbers on a Do-Not-Originate (DNO) list and those that purport to be from invalid, unallocated, or unused numbers."
January 25, 2018: CRTC Compliance and Enforcement and Telecom Decision 2018-32: Measures to reduce caller identification spoofing and to determine the origins of nuisance calls:
"In Compliance and Enforcement and Telecom Regulatory Policy 2016-442, the Commission indicated that it would initiate a proceeding to review the progress that is being made on caller identification (ID) authentication. ... Accordingly, the Commission expects, by 31 March 2019, that TSPs will implement measures to authenticate and verify caller ID for all IP-based voice calls; and the telecommunications industry will establish a Canadian certificate administrator. ... TSPs are required to report on their progress. The Commission requests that the CRTC Interconnection Steering Committee (CISC) submit a consolidated industry progress report to the Commission every six months, beginning six months from the date of this decision."
February 2018: RFC 8224 published: Authenticated Identity Management in the Session Initiation Protocol (SIP)
January - April 2018: CATA working group
March 23, 2018: NPRM 18-31: Re-assigned numbers
April 23, 2018: FCC Stop Illegal Robocalls Expo
April 27, 2018: House Energy & Commerce: hearing