| CARVIEW |
-
Suggested IETF 123 Sessions for Getting Familiar with New Topics
These IETF 123 meeting sessions are likely to include discussions and proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.
-
Experiences from IGF 2025
At the Internet Governance Forum 2025 in Norway (23-27 June), the presence of the IETF was well-received as part of the broader effort to strengthen the connection between technical and policy discussions, helping to build trust, increase visibility and highlight the role of the technical community in Internet governance.
- Dhruv Dhody IAB Member
-
Progress on AI Preferences
In January, the IETF chartered the AI Preferences (AIPREF) Working Group to make it easier to express how AI models should use Internet content. With a compressed timeline for delivery, it’s a good time to update those who haven't been following the work closely.
- Suresh Krishnan AIPREF Working Group Co-chair
- Mark Nottingham AIPREF Working Group Co-chair
-
IETF LLC Board Retreat 2025
The IETF Administration LLC (IETF LLC) Board met for its annual strategic retreat 6-7 May 2025 in Amsterdam, where it discussed the future strategy of the IETF LLC, as well as high priority operational issues.
- Mirjam Kuehne IETF Administration LLC Board Chair
-
Report from the Tools Team Retreat 2025
The IETF Administration LLC (IETF LLC) development team met along with IETF LLC senior leadership for its annual two-day retreat, and with the IETF Chair able to join remotely for key sessions. This post reviews the key inputs and outputs of that retreat, and how they affect the IETF.
- Jay Daley IETF Executive Director
- Robert Sparks Senior Director of Information Technology
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.