Skip to main content
  • Working on Post-Quantum Cryptography for Open Source Software from Africa

    During the IETF 122 Hackathon in Bangkok and online last month, the cyberstorm.mu team from Mauritius, the United States, and Kenya participated remotely to implement post-quantum cryptography components currently missing from widely-used open source software such as nmap, zmap, wireshark, and GnuTLS.

    30 Apr 2025
  • IETF 122 post-meeting survey

    IETF 122 Bangkok was held 15-21 March 2025 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

    17 Apr 2025
  • IETF Snapshot 2024

    Want to catch up on IETF activity in 2024? How many RFCs were published? How many Internet-Drafts were submitted? How many Working Groups were chartered or concluded? The IETF Snapshot provides a short summary of IETF activity for the previous year.

    17 Apr 2025
  • Report from RPC Retreat 2025

    In early April 2025, the RFC Production Center (RPC) and IETF LLC senior staff met for the first RPC retreat following the contract change that now has the RPC reporting directly to the IETF Executive Director. This was a high-level retreat, the first of its kind for the RPC, looking at community requirements and the RPC internal processes that deliver those.

    16 Apr 2025
  • New IRTF Chair Dirk Kutscher: Advancing Global Collaboration and Innovation in Internet Research

    The IETF Blog recently chatted with new Internet Research Task Force chair Dirk Kutscher about his views of where the IRTF is now and what the path ahead looks like.

    10 Apr 2025

Filter by topic and date

Filter by topic and date

STIR into Action

6 Jan 2020

Providers of voice over IP in the United States will be required to implement the IETF’s Secure Telephony Identity Revisited (STIR) protocol as a result of recently enacted legislation to address some of the root causes of illegal robocalling on the telephone network.

As part of a broader package of reforms aimed at curbing the explosive growth of robocalls, providers of Session Initiation Protocol (SIP)-based services will be required to implement STIR, the base specification of which was published as RFC 8224 together, with extensions in RFCs 8225, 8226, and 8588. A recent IETF blog post by Jon Peterson provides additional details and background about how the STIR working group approached the problem of authenticating callers using SIP-based services.

The same legislation will require providers of voice services to “take reasonable measures to implement an effective call authentication framework in the non-Internet protocol networks of the provider of voice service.” The STIR working group has been considering this issue as well. Its “STIR Out-of-Band Architecture and Use Cases” document was submitted last month to the Internet Engineering Steering Group for consideration to be published as an IETF RFC. You can find more information about the STIR working group and its work via the IETF Datatracker.


Share this page