]> Cloudflare

mst@cloudflare.com

Cloudflare

lromm@cloudflare.com

Web and Internet Transport AI Preferences AI preferences content signals This Internet Draft proposes three categories that would enable parties to express preferences regarding how digital assets are used by automated processing systems. The proposal is for these categories to nest within the larger category of Automated Processing, currently envisaged in the . About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the AI Preferences Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction This proposal introduces and aims to define a specific set of preferences to address the need for expressing how digital assets can be used by automated systems, particularly in the context of training artificial intelligence (AI) models and generating search results. These preference categories enable clear and explicit communication of preferences regarding the use of digital assets for search indexing and AI training.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. For the purposes of this document, in addition to the definitions in , the following terms are used:

• Search Results: hyperlinks and short excerpts returned from contents of the retrieved asset(s)
• Retrieval-Augmented Generation (RAG): A technique where external content is retrieved at query time and supplied to a model to condition the generated output (B. Silver)

Vocabulary Definition

Search The act of using one or more assets to build a search index and provide Search Results. Search does not include providing AI-generated search summaries. The use of assets for Search is a proper subset of Automated Processing usage.

AI Input The act of inputting an asset or assets into one or more AI models for purposes of retrieval-augmented generation, grounding, or other real-time taking of content for generative AI search answers. The use of assets for AI Input is a proper subset of Automated Processing usage.

AI Training The act of training or fine-tuning AI models. The use of assets for AI Training is a proper subset of Automated Processing usage.

Usage Category Labels Each usage category in is mapped to a short textual label. specifies this mapping. Usage category labels

Category	Label	Reference
Search	search
AI Input	ai-input
AI Training	ai-train

Security Considerations TODO Security

IANA Considerations This document has no IANA actions.

Addendum The definition definition for Search (3.1) provided in this document may be replaced with the Search Category definition proposed in and copied below: Using one or more assets in a search application that directs users to the location from which the assets were retrieved. Search applications can be complex and may serve multiple purposes. Only those parts of applications that direct users to the location of an asset are included in this category of use. This includes the use of titles or excerpts from assets that are used to help users select between multiple candidate options. Preferences for the Search category apply to those parts of applications that provide search capabilities, regardless of what other preferences are stated. Parts of applications that do not direct users to the location of assets, such as summaries, are not covered by this category of use. The use of assets for Search is a proper subset of Automated Processing usage.

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279. Open Future Mozilla

Acknowledgments TODO acknowledge.