• IETF 117 Highlights

    IETF 117 is a few weeks behind us and Dhruv Dhody, IAB Member and liaison to the IESG, took the opportunity to report on a few highlights and some impressions.

    • Dhruv DhodyIAB Member and liaison to the IESG
    21 Aug 2023

  • Proposed response to meeting venue consultations and the complex issues raised

    The IETF Administration LLC recently sought feedback from the community on the possibility of holding an IETF Meeting in the cities of Beijing, Istanbul, Kuala Lumpur and Shenzhen, with received feedback including views that were well expressed and well argued but strongly conflicting. The IETF LLC has considered this feedback in-depth and now seeks community feedback on its proposed response.

    • Jay DaleyIETF Executive Director
    21 Aug 2023

  • Submit Birds of a Feather session proposals for IETF 118

    Now's the time to submit Birds of a Feather session (BOFs) ideas for the IETF 118 meeting 4-10 November 2023, with proposals due by 8 September.

      16 Aug 2023

    • Applied Networking Research Workshop 2023 Review

      More than 250 participants gathered online and in person for ANRW 2023, the academic workshop that provides a forum for researchers, vendors, network operators, and the Internet standards community to present and discuss emerging results in applied networking research.

      • Maria ApostolakiANRW Program co-chair
      • Francis YanANRW Program co-chair
      16 Aug 2023

    • IETF 117 post-meeting survey

      IETF 117 San Francisco was held 22-28 July 2023 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

      • Jay DaleyIETF Executive Director
      11 Aug 2023
    • Show all

    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