| Internet-Draft | AIPREF Vocabulary Parameters | August 2026 |
| Zehta | Expires 7 February 2027 | [Page] |
This document defines how parameters can be added to AI Preferences.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://TimidRobot.github.io/ietf-aipref-parameters/draft-zehta-parameters.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-zehta-aipref-parameters/.¶
Discussion of this document takes place on the AI Preferences Working Group mailing list (mailto:ai-control@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/ai-control/. Subscribe at https://www.ietf.org/mailman/listinfo/ai-control/.¶
Source for this draft and an issue tracker can be found at https://github.com/TimidRobot/ietf-aipref-parameters.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 7 February 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document defines how parameters can be added to AI Preferences [VOCAB].¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
As noted in Section 6 of [VOCAB]:¶
The format relies on the Dictionary type defined in Section 3.2 of [FIELDS].¶
The AI Preferences can be extended with parameters. The parameter syntax is defined in (Section 3.1.2 of [FIELDS]):¶
Parameters are an ordered map of key-value pairs that are associated with an Item (Section 3.3) [...]. The keys are unique within the scope of the Parameters they occur within, and the values are bare items (i.e., they themselves cannot be parameterized; see Section 3.3).¶
If the value of a parameter contains a URI-reference (Section 4.1 of [URI]) and its value is not a valid URI-reference, the parameter MUST be ignored. If its value is a relative reference (Section 4.2 of [URI]), it MUST be resolved (Section 5 of [URI]) before being used.¶
This document has no IANA actions.¶
The following individuals made significant contributions to this document:¶
Sara Lovell¶