Network Working Group M. E. Kamga Internet-Draft Aureon Ecosystem Intended status: Standards Track October 13, 2026 Expires: April 16, 2027 The AUREON Database-over-HTTP Protocol and Method Suite draft-kamga-http-aureonsql-00 Abstract This document specifies AUREON, a high-performance database-over-HTTP protocol. AUREON leverages HTTP's extensible method mechanism (RFC 9110) to introduce domain-aware custom tokens for relational database operations, Data Definition Language (DDL) governance, Data Control Language (DCL) permissions, and procedural Data Action Language (DAL) workflows. Furthermore, this document defines the complete IANA registration templates for the AUREON method suite and media type parameters. 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 on April 16, 2027. Copyright Notice 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. \f Table of Contents 1. Introduction 2. Conventions and Terminology 3. Protocol Architecture and Content Negotiation 4. The AUREON Method Suite 5. Augmented Backus-Naur Form (ABNF) Syntax 6. IANA Considerations 6.1. HTTP Method Registrations 6.2. Media Type Registrations 7. Security Considerations 8. Normative References Author's Address 1. Introduction Standard HTTP methods (such as GET, POST, PUT, DELETE) are designed for general resource manipulation. High-performance database-over- HTTP architectures require explicit semantic separation for schema management, transactional data mutations, streaming, and procedural execution logic. AUREON defines a suite of extensible HTTP method tokens to bridge relational database engines directly over HTTP/1.1 and HTTP/2 transport layers. 2. Conventions and 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] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. Protocol Architecture and Content Negotiation AUREON utilizes the custom request MIME type `application/vnd.aureonsql` alongside registered tabular responses like `application/vnd.csv`, leveraging specific control parameters (`ticn`, `fs`, `esc`) to guarantee zero-ambiguity parsing without payload corruption. \f 4. The AUREON Method Suite This specification formally defines seventeen custom HTTP method tokens: o DDL & Governance: SQL_CREATE, SQL_ALTER, SQL_DROP, SQL_TRUNCATE, SQL_GRANT, SQL_REVOKE o Mutations & Queries: SQL_SELECT, SQL_INSERT, SQL_UPDATE, SQL_UPSERT, SQL_MERGE o Procedural DAL: SQL_EXECUTE, SQL_FOREACH, SQL_ASSERT, SQL_SUBSCRIBE_TO o Data Exchange: SQL_DAL_IMPORT, SQL_DAL_EXPORT 5. Augmented Backus-Naur Form (ABNF) Syntax aureon-request = method-token SP request-target SP HTTP-version method-token = "SQL_CREATE" / "SQL_ALTER" / "SQL_DROP" / "SQL_SELECT" / "SQL_INSERT" / "SQL_UPDATE" / "SQL_UPSERT" / "SQL_MERGE" / "SQL_TRUNCATE" / "SQL_GRANT" / "SQL_REVOKE" / "SQL_EXECUTE" / "SQL_FOREACH"/ "SQL_ASSERT" / "SQL_SUBSCRIBE_TO" / "SQL_DAL_IMPORT" / "SQL_DAL_EXPORT" 6. IANA Considerations 6.1. HTTP Method Registrations This document requests the registration of seventeen method tokens in the HTTP Method Registry maintained under RFC 9110. Template Summary: - SQL_SELECT: Safe: Yes, Idempotent: Yes - SQL_INSERT: Safe: No, Idempotent: No - SQL_UPDATE: Safe: No, Idempotent: Yes - SQL_UPSERT: Safe: No, Idempotent: Yes - SQL_MERGE: Safe: No, Idempotent: No - SQL_CREATE: Safe: No, Idempotent: No - SQL_ALTER: Safe: No, Idempotent: No - SQL_DROP: Safe: No, Idempotent: Yes - SQL_TRUNCATE: Safe: No, Idempotent: Yes - SQL_GRANT: Safe: No, Idempotent: No - SQL_REVOKE: Safe: No, Idempotent: No - SQL_EXECUTE: Safe: No, Idempotent: No - SQL_FOREACH: Safe: No, Idempotent: No - SQL_ASSERT: Safe: Yes, Idempotent: Yes - SQL_SUBSCRIBE_TO: Safe: Yes, Idempotent: No - SQL_DAL_IMPORT: Safe: No, Idempotent: No - SQL_DAL_EXPORT: Safe: Yes, Idempotent: Yes 7. Security Considerations Implementations MUST enforce strict TLS transport security and parameter validation to prevent injection attacks across database operations and DAL script blocks. 8. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in BCP 14 RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Author's Address Marc Espérance Kamga Aureon Ecosystem Email: marc.kamga@gmail.com Expires: April 16, 2027 (Draft-kamga-http-aureonsql-00)