Skip to main content
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026
  • IETF email infrastructure transition planned for 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026

Filter by topic and date

Filter by topic and date

IETF setting standards for AI preferences

27 Feb 2025

The newly-chartered AI Preferences (AIPREF) Working Group will work on standardizing building blocks that allow for the expression of preferences about how content is collected and processed for Artificial Intelligence (AI) model development, deployment, and use.

pexels-pixabay-277593

The use of Internet content for training large language models ("AI") has become a contentious topic. Training a model requires voluminous information, and the Internet is readily available as a source of diverse content. However, many publishers and authors object to these new uses of their work without permission or compensation.

While the IETF doesn't take a position on the legal questions in this space, we do track developments, and last September the IAB AI-CONTROL Workshop highlighted a need for clearer communication between content publishers and AI model trainers. 

Right now, AI vendors use a confusing array of non-standard signals in the robots.txt file (defined by RFC 9309) and elsewhere to guide their crawling and training decisions. As a result, authors and publishers lose confidence that their preferences will be adhered to, and resort to measures like blocking their IP addresses.

To address this need, the AIPREF working group has been chartered to define:

  1. a common vocabulary to express authors' and publishers' preferences regarding use of their content for AI training and related tasks, and

  2. means of attaching that vocabulary to content on the Internet, either by embedding it in the content or by formats similar to robots.txt, and a standard mechanism to reconcile multiple expressions of preferences. 

The Working Group will hold its first meeting during IETF 122 Bangkok, where administrative and initial scoping discussions will take place. Shortly thereafter, it will hold an interim meeting from 8-10 April in Brussels, Belgium. This is an open meeting, but registration is required.

If you are interested in monitoring or participating in this work, subscribe to the AIPREF working group mailing list


Share this page