The "" URI Scheme for Biometric-First Communication
draft-schur-bcccop-uri-scheme-00

Network Working Group                                           P. Schur
Internet-Draft                                               theCwindLab
Intended status: Informational                              18 June 2026
Expires: 20 December 2026

          The "⚮" URI Scheme for Biometric-First Communication
                    draft-schur-bcccop-uri-scheme-00

Abstract

   This document registers the "⚮" (U+26AE, DIVORCE SYMBOL) Uniform
   Resource Identifier (URI) scheme for the Biometric-First
   Communication Protocol (BCCCOP).  The scheme enables privacy-first,
   biometric-anchored addressing of resources and invocation of peer-to-
   peer operations across ultrasonic, BLE, and Wi-Fi transports.  This
   document follows the URI scheme registration guidelines of RFC 7595.

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 20 December 2026.

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.  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.

Schur                   Expires 20 December 2026                [Page 1]
Internet-Draft             BCCCOP ⚮ URI Scheme                 June 2026

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Format A — Hierarchical Addressing  . . . . . . . . . . .   3
     2.2.  Format B — Command Invocation . . . . . . . . . . . . . .   3
     2.3.  ABNF Grammar  . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Scheme Semantics  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Encoding and Transport  . . . . . . . . . . . . . . . . . . .   4
   5.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  URI Scheme Registration Template  . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Interoperability Considerations . . . . . . . . . . . . . . .   6
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The Biometric-First Communication Protocol (BCCCOP) is a privacy-
   first, zero-trust protocol for peer-to-peer data exchange.  It
   operates across three physical rails: a personal application rail
   (BPa), an ambient sensor rail (BPb), and a cross-device projection
   rail (BPc).

   All resources in BCCCOP are addressed through "closed atoms" —
   identifiers delimited by the Unicode character U+26AE (⚮).  These
   atoms form the basis of a novel URI scheme that this document
   registers per the procedures defined in [RFC7595].

   The scheme character U+26AE (⚮) was selected for its visual
   distinctiveness, its availability in the Unicode Basic Multilingual
   Plane, and its conceptual resonance with the protocol's separation-
   of-concerns architecture: each ⚮-delimited atom represents a
   sovereign, independently addressable resource.

1.1.  Requirements Language

   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.

Schur                   Expires 20 December 2026                [Page 2]
Internet-Draft             BCCCOP ⚮ URI Scheme                 June 2026

2.  URI Scheme Syntax

   The ⚮ URI scheme supports two formats, both of which normalize to a
   common canonical Abstract Syntax Tree (AST).

2.1.  Format A — Hierarchical Addressing

   Format A addresses a resource by stewardness path:

   ⚮atom⚮;key=val;key=val#fragment
   ⚮://secure.trusted/note/BPa.03.01.01/meeting-notes#section-3

2.2.  Format B — Command Invocation

   Format B invokes an operation through a cross-device Trojan window:

   ⚮:@authority!operation(arg)(arg)?key=val#fragment
   ⚮:@alice!stream(content=hello)?security=crypto

2.3.  ABNF Grammar

   The complete ABNF grammar for the ⚮ URI scheme, per [RFC5234], is:

   ; BCCCOP URI — Unified Grammar
   ; Supports Format A (hierarchical) and Format B (command)

   BCCOP-URI     = format-a / format-b

   format-a      = "⚮" atom-id "⚮" [ ";" param *( ";" param ) ] [ "#" fragment ]
   format-b      = "⚮" [":" authority] "!" operation [ "(" arg *( ")" "(" arg ) ")" ]
                    [ "?" query ] [ "#" fragment ]

   atom-id       = 1*( ALPHA / DIGIT / "#" / "-" / "_" / "." )
   authority     = "@" 1*( ALPHA / DIGIT / "-" / "_" )
   operation     = ALPHA *( ALPHA / DIGIT / "-" / "_" )
   arg           = *( ALPHA / DIGIT / "-" / "_" / "=" / "." )
   param         = key "=" value
   key           = ALPHA *( ALPHA / DIGIT / "-" / "_" )
   value         = *( ALPHA / DIGIT / "-" / "_" / "." / ":" )
   query         = param *( "&" / ";" param )
   fragment      = *( ALPHA / DIGIT / "-" / "_" / "." )

   All ABNF productions use the Core Rules from [RFC5234].  The scheme
   delimiter is the single Unicode character U+26AE (⚮), UTF-8 encoded
   as 0xE2 0x9A 0xAE on the wire.  When used in URIs, ⚮ MUST be percent-
   encoded as %E2%9A%AE per [RFC3986] when appearing outside the scheme
   position.

Schur                   Expires 20 December 2026                [Page 3]
Internet-Draft             BCCCOP ⚮ URI Scheme                 June 2026

3.  Scheme Semantics

   The ⚮ URI scheme operates within the BCCCOP protocol stack.  URIs
   resolve to one of 261 Atomic Type Inventory (ATI) elements across 38
   families, classified into three tiers:

   TIER_0 (System-only):  Biometric, Trojan, Gibber-Link, Break-Glass,
      Consent, Witness.  These atoms cannot be authored from the no-code
      user interface.  Emission requires biometric re-authentication and
      generates an audit frame.

   TIER_1 (User flows):  Action, Resource, Sharing, Topology.  These
      atoms form the standard user-facing command surface.

   TIER_2 (Shell):  Tag, Hash, Unit, Country, Language.  Top-level
      navigation and internationalization atoms.

   The canonical ATI catalog (261 atoms, 38 families) is published at
   https://github.com/DrmedPatrickSchur/bubblepress/blob/main/
   assets/0%20ATI_canonical.csv and carries a BLAKE3 content hash pinned
   in the screen manifest.

4.  Encoding and Transport

   BCCCOP URIs are transmitted over three physical carriers, selected by
   the atom's tier classification:

   *  *Ultrasonic (Gibber-Link™):* 4-FSK modulation at
      18.0/19.0/20.0/21.0 kHz, 100 symbols/s, 200 bps.  Used for zero-
      trust device pairing and TIER_0 pre-verification handshakes.

   *  *Bluetooth Low Energy (BLE 5.3):* GATT service with BCCCOP-
      specific characteristics.  Used for TIER_0 data exchange with
      hardware attestation.

   *  *Wi-Fi Direct / QUIC:* Sustained projection streams for TIER_1 and
      TIER_2 content delivery.

   TIER_0 atoms are restricted to BLE and Wi-Fi Direct carriers; they
   MUST NOT be transmitted over ultrasonic (to prevent eavesdropping on
   biometric data).  All other tiers may use any available carrier.

5.  Operations

   The Trojan Window lifecycle drives Format B command execution through
   a 9-state finite state machine:

Schur                   Expires 20 December 2026                [Page 4]
Internet-Draft             BCCCOP ⚮ URI Scheme                 June 2026

Idle → Discovered → PreVerified → Authorized → CoAuth → Live
                                                          ↕
                                          Suspended ← Live → Revoked → Wiped

   Each state transition requires one or more of: biometric re-
   authentication (Face + Voice cascade per [RFC9106]), stewardness
   accordance check, Gibber-Link X25519 3-party key exchange, or memory-
   wipe attestation (BLAKE3 proof).

6.  IANA Considerations

   This document requests the registration of the "⚮" URI scheme in the
   "Uniform Resource Identifier (URI) Schemes" registry, per the
   procedures of [RFC7595].

6.1.  URI Scheme Registration Template

   Scheme name:  ⚮ (Unicode code point U+26AE)

   Status:  Provisional

   Applications/protocols that use this scheme name:  BCCCOP (Biometric-
      First Communication Protocol); BubblePress application; Gibber-
      Link ultrasonic handshake

   Contact:  Patrick Schur <partnerships@theCwindLab.net>

   Change controller:  Patrick Schur (theCwindLab)

   References:  This document (draft-schur-bcccop-uri-scheme-00)

7.  Security Considerations

   The ⚮ URI scheme is designed for biometric-first, zero-trust
   environments.  The following security properties apply:

   1.  *Biometric Anchoring:* All TIER_0 atom emission requires a fused
       biometric cascade (Face + Voice + optional Fingerprint).  The
       cascade produces a BLAKE3 hash that anchors iBubbleTag
       identifiers.  Fresh biometric re-authentication is required for
       every TIER_0 operation per [RFC9106].

   2.  *Consent Vault:* Cross-device operations (Format B) require a
       consent record in the Argon2id-encrypted consent vault.  Consent
       is per-purpose, per-recipient, and instantly revocable.

Schur                   Expires 20 December 2026                [Page 5]
Internet-Draft             BCCCOP ⚮ URI Scheme                 June 2026

   3.  *Transport Security:* TIER_0 data is encrypted with AES-256-GCM
       (12-byte randomized nonce, 16-byte authentication tag) per
       [RFC5116].  Transport-layer encryption uses QUIC ([RFC9000]) with
       TLS 1.3 ([RFC8446]).

   4.  *Carrier Restriction:* TIER_0 atoms are restricted to BLE and Wi-
       Fi Direct carriers.  The ultrasonic Gibber-Link channel (4-FSK,
       18-21 kHz) is used only for non-sensitive pre-verification
       handshakes, never for biometric or consent data.

   5.  *Memory Wipe Attestation:* The terminal Wiped state of the Trojan
       Window FSM produces a BLAKE3 attestation proof that the session
       memory was zero-filled.  No sensitive data persists beyond
       session teardown.

   6.  *Audit Trail:* Every TIER_0 operation emits a cryptographically
       signed SES (Screen Element Streaming) audit frame anchored to the
       Hedera Hashgraph consensus service.

   Implementors SHOULD consult the BCCCOP RFC Conformance Audit
   (0RFC/OUTPUTclaude/BCCCOP_RFC_CONFORMANCE_AUDIT.md) for a detailed
   analysis of compliance with referenced IETF standards.

8.  Interoperability Considerations

   The ⚮ URI scheme is consumed by a 41-crate Rust implementation
   (BCCCOP PoC BUILD, v0.1.0-lockin, 4759 passing tests).  The canonical
   ATI catalog of 261 atoms is published as a CSV file with a BLAKE3
   content hash pinned in the screen manifest, enabling independent
   implementations to validate their atom registry against the reference
   implementation.

   Implementations MUST support the complete ABNF grammar defined in
   Section 2.3.  Format B parsers MUST correctly handle the
   ⚮:@authority!operation(arg) pattern with URI query and fragment
   components.

9.  Normative References

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

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

   [RFC5116]  McGrew, D., "An Interface and Algorithms for Authenticated
              Encryption", January 2008.

Schur                   Expires 20 December 2026                [Page 6]
Internet-Draft             BCCCOP ⚮ URI Scheme                 June 2026

   [RFC5234]  Crocker, D. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", January 2008.

   [RFC7595]  Thaler, D., Hansen, T., and T. Hardie, "Guidelines and
              Registration Procedures for URI Schemes", June 2015.

   [RFC8032]  Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital
              Signature Algorithm (EdDSA)", January 2017.

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

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", August 2018.

   [RFC9000]  Iyengar, J. and M. Thomson, "QUIC: A UDP-Based Multiplexed
              and Secure Transport", May 2021.

   [RFC9106]  Biryukov, A., Dinu, D., Khovratovich, D., and S.
              Josefsson, "Argon2 Memory-Hard Function for Password
              Hashing and Proof-of-Work Applications", September 2021.

Author's Address

   Patrick Schur
   theCwindLab
   Email: patrick.schur@theCwind.com
   URI:   http://www.theCwind.com

Schur                   Expires 20 December 2026                [Page 7]