Internet-Draft                                             A. Sogomonian
Intended status: Informational                          MyConcept Project
Expires: March 2026                                      September 11, 2025

                 The "ai" URI Scheme for AI Internet Access
                 draft-sogomonian-ai-uri-scheme-00

Abstract

   This document defines the "ai" Uniform Resource Identifier (URI)
   scheme. The "ai" scheme provides a mechanism to identify and access
   AI-native Internet resources using a blockchain-based registry and
   resolver instead of DNS. It enables digital twin domains (for
   example, ai://bank, ai://shop, ai://gov) used by an "AI Button"
   client.

Status of This Memo

   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 in March 2026.

Copyright Notice

   Copyright (c) 2025 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . .   3
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
       Author's Address  . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   The "ai" URI scheme defines a new entry point to the Internet that
   does not depend on DNS. Resources identified by ai:// are resolved by
   a smart-contract registry mapping names (for example, "bank") to a
   domain manifest stored in decentralized storage such as IPFS.

   The general concept of URIs and their components follows the
   conventions defined in [RFC3986].

2.  Terminology

   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] and [RFC8174]) when, and only when, they appear in all
   capitals, as shown here.

3.  Syntax

   The syntax of the ai-scheme URI follows [RFC3986]:

      ai://<name>[/path][?query][#fragment]

   <name> is a registered AI Internet label (letters, digits, hyphen).
   /path, ?query, and #fragment are optional.

4.  Security Considerations

   All ai:// interactions MUST be gated by explicit user consent.
   Registry uniqueness is by hash of the normalized name. Resolver
   content identifiers SHOULD be content-addressed (for example, IPFS
   CIDs). Anti-phishing controls such as homoglyph filtering and
   reserved names are RECOMMENDED.

5.  IANA Considerations

   This document requests the registration of the "ai" URI scheme in the
   IANA URI Schemes Registry with the following template:

      URI Scheme Name: ai
      Status: Provisional
      Applications or protocols: AI Button; blockchain registry and resolver
      Contact: Aram Sogomonian, Waterbottling@icloud.com
      Change controller: MyConcept / AI Internet Project

6.  Normative References

   [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
             Resource Identifier (URI): Generic Syntax", STD 66, RFC
             3986, January 2005.

   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
             Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119
             Key Words", BCP 14, RFC 8174, May 2017.

Author's Address

   Aram Sogomonian
   MyConcept / AI Internet Project
   Email: Waterbottling@icloud.com