<?xml version="1.0" encoding="UTF-8"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     version="3"
     category="info"
     ipr="trust200902"
     submissionType="IETF"
     docName="draft-meta-layer-overview-00">

  <front>
    <title abbrev="Meta-layer Overview">The Meta-Layer: A Coordination Substrate for Presence, Annotation, and Governance on the Web</title>

    <author fullname="Karim ATTOUMANI MOHAMED" initials="K." surname="ATTOUMANI MOHAMED">
      <organization>Meta-Layer Initiative</organization>
      <address>
        <postal>
          <country>Comoros</country>
        </postal>
        <email>karimattoumanimohamed@gmail.com</email>
      </address>
    </author>

    <author fullname="Daveed BENJAMIN" initials="D." surname="BENJAMIN">
      <organization>Meta-Layer Initiative</organization>
      <address>
        <postal>
          <country>USA</country>
        </postal>
        <email>daveed@bridgit.io</email>
      </address>
    </author>

    <date year="2025" month="October"/>

    <area>Applications and Real-Time</area>
    <workgroup>GEN-Dispatch</workgroup>
    <keyword>Meta-layer</keyword>
    <keyword>annotation</keyword>
    <keyword>provenance</keyword>
    <keyword>governance</keyword>
    <keyword>overlay</keyword>
    <keyword>presence</keyword>

    <abstract>
      <t>This document introduces the concept of a Meta-layer: a programmable coordination substrate that operates above content layers on the Internet. The Meta-layer enables communities, individuals, and agents to appear, annotate, and govern together in shared digital space, independent of underlying platforms. It is not a replacement for existing web or transport protocols, but a complementary infrastructure that integrates with them. The draft outlines the motivation, terminology, use cases, implementation model, risks, security considerations, and potential IANA registries for future work.</t>
    </abstract>

    <note title="Status of This Memo">
      <t>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</t>
      <t>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/.</t>
      <t>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."</t>
    </note>

    <note title="Copyright Notice">
      <t>Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.</t>
      <t>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.</t>
    </note>
  </front>

  <middle>

    <section anchor="intro" numbered="true" title="Introduction">
      <t>The Internet has evolved from a document-sharing network into a global application substrate. However, it has never included a shared layer for presence, annotation, provenance, and contextual governance across domains. These functions remain fragmented, implemented in proprietary platforms or plugins, without interoperability or transparency.</t>
      <t>The idea of a higher-level coordination or annotation layer above content is not new:</t>
      <dl>
        <dt>Vannevar Bush (1945)</dt>
        <dd>“As We May Think,” <em>The Atlantic Monthly</em>, introduced associative trails—linked paths of thought that presaged hypertext and the idea of connecting knowledge above documents.</dd>
        <dt>Ted Nelson (1965)</dt>
        <dd>“Complex information processing: a file structure for the complex, the changing and the indeterminate” introduced hypertext as a precursor to a cross-page meta-layer.</dd>
        <dt>Douglas Engelbart (1968)</dt>
        <dd>“The Mother of All Demos” (FJCC, San Francisco) publicly demonstrated NLS with hypertext, on-screen overlays, and view controls—effectively a layer above documents.</dd>
        <dt>Tim Berners-Lee (2001)</dt>
        <dd>“The Semantic Web,” <em>Scientific American</em>, framed a data/meaning layer on top of the Web, i.e., machine-understandable metadata layered over pages.</dd>
        <dt>Marc Andreessen (2012)</dt>
        <dd>“Why Andreessen Horowitz Is Investing in Rap Genius,” describing widespread web annotation as the “missing layer of the Internet.”</dd>
      </dl>
      <t>The Meta-layer Initiative seeks to translate these longstanding conceptual foundations into open, interoperable infrastructure under IETF stewardship—turning decades of vision into a standard that integrates presence, annotation, provenance, and governance as native Internet functions.</t>
    </section>

    <section anchor="problem" numbered="true" title="Problem Statement">
      <t>Current IETF protocols provide robust foundations for transport (TCP, QUIC), security (TLS), and identity (OAuth, OIDC, SCIM). However, the Internet still lacks standardized primitives for:</t>
      <ul>
        <li>Presence: expressing who is here, under what rules, and with what visibility.</li>
        <li>Annotation: attaching structured meaning (claims, challenges, polls, bridges) to content across domains.</li>
        <li>Provenance: cryptographically linking contributions to identity and context.</li>
        <li>Governance: enabling communities to compose and enforce rules transparently.</li>
        <li>Agent Containment: running AI and automated processes inside bounded, verifiable execution environments.</li>
      </ul>
      <t>Today, these behaviors exist only as fragmented features inside proprietary platforms. This results in interoperability gaps, inconsistent privacy guarantees, lack of portability, and absence of shared governance mechanisms.</t>
      <t>While the W3C Web Annotation Data Model (2017) has defined a standard format for content-level annotations, it does not address cross-domain interoperability, provenance, or rule-based governance. The Meta-layer complements W3C’s work by proposing a protocol-level substrate—capable of operating across applications and domains—where annotations, presence, and governance can interoperate securely and transparently.</t>
      <t>The absence of such a substrate has long been recognized: the ability to annotate and govern content was described as a “missing feature” of the web browser, and calls to explore a “meta-environment above the page” have been made by early Internet pioneers. As Marc Andreessen noted in “Why Andreessen Horowitz Is Investing in Rap Genius” (2012), this “missing layer” reflects a longstanding need for interoperable annotation infrastructure.</t>
      <t>These concepts build on the architectural vision outlined in “The Metaweb: The Next Level of the Internet” (Bridgit DAO, CRC Press/Taylor &amp; Francis, 2023), which introduced the concept of a “meta-layer above the webpage” as a civic and computational trust substrate. This draft operationalizes that vision for standardization within the IETF context.</t>
    </section>

    <section anchor="relevance" numbered="true" title="Relevance to the IETF">
      <t>This work aligns with several ongoing activities across IETF Areas and external web-standard bodies.</t>

      <section title="Applications and Real-Time (ART) Area">
        <t>Defines application-layer primitives for presence, annotation, and overlays, complementing ongoing work such as MIMI (Messaging Interoperability) and HTTP APIs. The Meta-layer’s semantic and contextual overlay model complements W3C’s Web Annotation work by introducing interoperable signaling, provenance, and governance primitives at the Internet protocol layer.</t>
      </section>

      <section title="Security (SEC) Area">
        <t>The Meta-layer depends on secure identity, accountability, cryptographic provenance, and trusted execution environments (TEEs). It builds upon and extends existing work in OAuth, OIDC, Privacy Pass, and SCIM for federated identity and access control; RATS (Remote ATtestation ProcedureS) and EAT (Entity Attestation Token) for verifying trustworthiness of execution environments; COSE (CBOR Object Signing and Encryption) and CFRG for cryptographic signing and post-quantum resilience; and SUIT (Software Updates for IoT) for maintaining verified code integrity within TEEs. TEEs are thus positioned as security primitives within the IETF SEC Area, ensuring that agents in the Meta-layer execute in verifiable, policy-constrained, and auditable contexts.</t>
      </section>

      <section title="IRTF Research Groups">
        <t>The governance and AI-containment aspects of the Meta-layer overlap with ongoing research in PEARG (Privacy Enhancements and Assessments RG) and RASPRG (Research and Analysis of Standard-Setting Processes RG). The initiative can also contribute to IRTF and IAB workshops on AI accountability, provenance, and sustainable governance models.</t>
      </section>

      <section title="General Area (GEN)">
        <t>Since the Meta-layer crosses multiple areas (ART, SEC, OPS, IRTF), GEN-Dispatch is an appropriate venue to discuss scope and determine whether a dedicated Working Group (WG) or Research Group (RG) is warranted.</t>
      </section>

      <section title="Collaboration with W3C and Other Bodies">
        <t>The Meta-layer aims to be complementary to ongoing efforts in W3C (e.g., Web Annotation, ActivityPub, and provenance standards) and ISO/IEC JTC1 AI frameworks, by providing a network-layer and governance substrate that ensures interoperability, accountability, and trust across ecosystems.</t>
      </section>
    </section>

    <section anchor="terminology" numbered="true" title="Terminology">
      <t>(Working definitions)</t>
      <dl>
        <dt>Overlay</dt>
        <dd>Semantic/visual layer rendered above digital content, carrying presence indicators, tags, and interactions; governed by community rule modules.</dd>
        <dt>Smart Tag</dt>
        <dd>Typed, structured annotation (e.g., note, claim, challenge, poll, bridge); signed, timestamped, interactive, filterable.</dd>
        <dt>Bridge</dt>
        <dd>Semantic link connecting two pieces of content (support, challenge, context) across domains.</dd>
        <dt>Presence</dt>
        <dd>Identity expression in digital space, scoped by context and rules (visible, pseudonymous, invisible).</dd>
        <dt>Governance Module</dt>
        <dd>Composable logic defining rules for interaction, moderation, participation, and policy enforcement within an overlay.</dd>
        <dt>Agent</dt>
        <dd>Automated or semi-autonomous process (AI, bot, scripted service) operating within the Meta-layer under policy constraints.</dd>
        <dt>TEE (Trusted Execution Environment)</dt>
        <dd>Secure, attestable runtime container for agent execution, supporting constraints, logging, attestation.</dd>
        <dt>Provenance</dt>
        <dd>Verifiable origin, context, and authorship of tags/actions/agent behaviors via signed metadata and timestamps.</dd>
      </dl>
    </section>

    <section anchor="impl" numbered="true" title="Implementation Model">
      <t>The Meta-layer operates above existing content without requiring fundamental Web changes. Functions are delivered via extensions, SDKs, and open APIs.</t>
      <section title="Browser Extensions &amp; Presence SDKs">
        <t>Lightweight extension or embeddable SDK renders overlays on existing sites. Overlays carry smart tags, presence, governance. Interoperable and governed by open registries (unlike closed annotation tools).</t>
      </section>
      <section title="Embedded Components in Web Applications">
        <t>Sites integrate Meta-layer widgets or frames (e.g., a semantic sidebar in e-learning portals) via web-embed SDK. No browser installation required for end users in these contexts.</t>
      </section>
      <section title="Federation Across Domains">
        <t>Identity, tags, and governance rules are portable. Provenance (signatures, timestamps) ensures authenticity across domains.</t>
      </section>
      <section title="Trusted Execution for Agents">
        <t>Agents operate in bounded execution environments (e.g., TEEs) with policy-defined capabilities, rates, and auditable logs.</t>
      </section>
      <section title="Open APIs &amp; Developer Onramps">
        <t>APIs expose registries for tag types, badge schemas, governance modules. Third parties define new tag types, build overlays, or fork rule modules. Interop via stable identifiers (IANA-registered if standardized).</t>
      </section>
      <section title="Progressive Deployment">
        <t>Early opt-in communities (e.g., research/fact-checking overlays). Later: native integrations once interop/security are proven. No "flag day"—coexists and incrementally extends today’s Internet.</t>
      </section>
    </section>

    <section anchor="usecases" numbered="true" title="Use Cases">
      <section title="Safe Digital Space">
        <t>Federated identity, proof-of-humanity, and contextual filters enable communities to restrict participation (e.g., verified humans; scoped agent permissions) and create bot-resistant, trustable interaction zones.</t>
      </section>
      <section title="Cross-Site Knowledge &amp; Interaction Flow">
        <t>Smart tags and bridges make annotations portable and filterable across sites, building shared knowledge graphs with provenance.</t>
      </section>
      <section title="Agent Containment">
        <t>Agents run in attested TEEs with logged behaviors and community-defined permissions—preventing unbounded automation and interaction while enabling useful collaboration.</t>
      </section>
    </section>

    <section anchor="risks" numbered="true" title="Risks and Mitigation">
      <ul>
        <li>Identity fraud and bots: federated identity, contextual privileges, proof-of-humanity (when needed).</li>
        <li>Governance capture: modular rule modules, open registries, and forkable governance.</li>
        <li>Annotation spam or overload: attention-based rendering, overlay moderation, reputation weighting, rate limits.</li>
        <li>Privacy loss: scoped presence, pseudonymity, user-controlled visibility, data-minimizing defaults.</li>
        <li>Fragmentation: shared registries for tag types, governance modules, and semantic formats, with room for extensions or forks.</li>
      </ul>
    </section>

    <section anchor="security" numbered="true" title="Security Considerations">
      <ul>
        <li>Identity and Authentication: leverage OAuth, OIDC, SCIM, Privacy Pass.</li>
        <li>Cryptographic Provenance: sign and timestamp tags and bridges; consider hybrid/post-quantum algorithms over time.</li>
        <li>Agent Containment: bounded TEEs or verifiable sandboxes with attestation and enforceable policy.</li>
        <li>Privacy: opt-in presence and annotation; scoped visibility; minimize metadata exposure.</li>
        <li>Registries and Extensions: standardized, auditable registries (designated expert review) to prevent identifier squatting or abuse.</li>
      </ul>
    </section>

    <section anchor="iana" numbered="true" title="IANA Considerations">
      <t>No immediate IANA actions requested. If standardized, potential new registries include:</t>
      <ul>
        <li>Meta-layer Smart Tag Types Registry (e.g., note, claim, bridge, poll, challenge).</li>
        <li>Governance Module Registry (reusable rule modules for overlays/participation/moderation).</li>
        <li>Badge and Role Types Registry (moderator, validator, scribe, etc.).</li>
      </ul>
      <t>Registries should balance extensibility with security and interoperability, using clear specification references and designated-expert review.</t>
    </section>

  </middle>

  <back>
    <references>
      <name>Normative References</name>

      <reference anchor="RFC2026" target="https://www.rfc-editor.org/rfc/rfc2026">
        <front>
          <title>The Internet Standards Process -- Revision 3</title>
          <author initials="S." surname="Bradner"/>
          <date year="1996"/>
        </front>
        <seriesInfo name="RFC" value="2026"/>
        <seriesInfo name="DOI" value="10.17487/RFC2026"/>
      </reference>

      <reference anchor="RFC7990" target="https://www.rfc-editor.org/rfc/rfc7990">
        <front>
          <title>RFC Format Framework</title>
          <author initials="H." surname="Flanagan"/>
          <date year="2016"/>
        </front>
        <seriesInfo name="RFC" value="7990"/>
        <seriesInfo name="DOI" value="10.17487/RFC7990"/>
      </reference>

      <reference anchor="RFC9110" target="https://www.rfc-editor.org/rfc/rfc9110">
        <front>
          <title>HTTP Semantics</title>
          <author initials="R." surname="Fielding"/>
          <author initials="M." surname="Nottingham"/>
          <author initials="J." surname="Reschke"/>
          <date year="2022"/>
        </front>
        <seriesInfo name="RFC" value="9110"/>
        <seriesInfo name="DOI" value="10.17487/RFC9110"/>
      </reference>

      <reference anchor="RFC6749" target="https://www.rfc-editor.org/rfc/rfc6749">
        <front>
          <title>The OAuth 2.0 Authorization Framework</title>
          <author initials="D." surname="Hardt"/>
          <date year="2012"/>
        </front>
        <seriesInfo name="RFC" value="6749"/>
        <seriesInfo name="DOI" value="10.17487/RFC6749"/>
      </reference>
    </references>

    <references>
      <name>Informative References</name>

      <reference anchor="W3C-WebAnnotation" target="https://www.w3.org/TR/annotation-model/">
        <front>
          <title>Web Annotation Data Model</title>
          <author fullname="World Wide Web Consortium"/>
          <date year="2017"/>
        </front>
        <seriesInfo name="W3C Recommendation" value="annotation-model"/>
      </reference>

      <reference anchor="MetaLayerWhitePaper" target="https://themetalayer.org/white-paper">
        <front>
          <title>Meta-layer White Paper</title>
          <author fullname="Meta-Layer Initiative"/>
          <date year="2025"/>
        </front>
      </reference>

      <reference anchor="MetawebBook" target="https://www.routledge.com/The-Metaweb-The-Next-Level-of-the-Internet/DAO/p/book/9781032125527">
        <front>
          <title>The Metaweb: The Next Level of the Internet</title>
          <author fullname="Bridgit DAO"/>
          <date year="2023"/>
        </front>
        <seriesInfo name="Publisher" value="Taylor &amp; Francis / CRC Press"/>
      </reference>

      <reference anchor="Bush1945" target="https://www.theatlantic.com/magazine/archive/1945/07/as-we-may-think/303881/">
        <front>
          <title>As We May Think</title>
          <author fullname="Vannevar Bush"/>
          <date year="1945" month="July"/>
        </front>
        <refcontent>The Atlantic Monthly</refcontent>
      </reference>

      <reference anchor="Engelbart1968">
        <front>
          <title>The Mother of All Demos</title>
          <author fullname="Douglas Engelbart"/>
          <date year="1968" month="December" day="9"/>
        </front>
      </reference>

      <reference anchor="Nelson1965" target="https://dl.acm.org/doi/10.1145/800197.806036">
        <front>
          <title>Complex information processing: a file structure for the complex, the changing and the indeterminate</title>
          <author fullname="Theodor Holm Nelson"/>
          <date year="1965"/>
        </front>
      </reference>

      <reference anchor="BernersLee2001" target="https://www-sop.inria.fr/acacia/cours/essi2006/Scientific%20American_%20Feature%20Article_%20The%20Semantic%20Web_%20May%202001.pdf">
        <front>
          <title>The Semantic Web</title>
          <author fullname="Tim Berners-Lee"/>
          <date year="2001" month="May"/>
        </front>
        <refcontent>Scientific American</refcontent>
      </reference>

      <reference anchor="Andreessen2012" target="https://genius.com/Marc-andreessen-why-andreessen-horowitz-is-investing-in-rap-genius-annotated">
        <front>
          <title>Why Andreessen Horowitz Is Investing in Rap Genius</title>
          <author fullname="Marc Andreessen"/>
          <date year="2012" month="October"/>
        </front>
      </reference>

      <reference anchor="CerfRemarks2023">
        <front>
          <title>Review of &quot;The Metaweb: The Next Level of the Internet&quot;</title>
          <author fullname="Vinton G. Cerf"/>
          <date year="2023"/>
        </front>
      </reference>

      <reference anchor="IAB-IRTF-AI-Workshops">
        <front>
          <title>IETF/IAB/IRTF workshop reports on AI governance and provenance</title>
          <author fullname="IAB / IRTF"/>
          <date year="2023"/>
        </front>
      </reference>

    </references>

    <section anchor="authors-addresses" title="Authors' Addresses">
      <t>Karim ATTOUMANI MOHAMED</t>
      <t>Meta-Layer Initiative</t>
      <t>Email: karimattoumanimohamed@gmail.com</t>
      <t></t>
      <t>Daveed Benjamin</t>
      <t>Meta-Layer Initiative</t>
      <t>Email: daveed@bridgit.io</t>
    </section>
  </back>
</rfc>
