Internet-Draft                                 G. Tian

Intended status: Experimental 

Expires: April 2027                     CoCa Foundation
                                              24 Oct 2026

   UTXO Domain Name System (UTXO6-DNS): Data RR for Cryptographic Endpoint 
Discovery

Abstract

   This document specifies a new DNS Data Resource Record (RRTYPE 260) 
   for transporting opaque cryptographic pointers. The RDATA contains 
   a CBOR-encoded endpoint identifier and an optional Verifiable Random 
   Function (VRF) proof. This document prohibits apex usage and 
   mandates the _utxo prefix.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the 
   provisions of BCP 78 and BCP 79.

   This document is an Experimental specification. It is not an IETF 
   standard and does not represent IETF consensus.

1. Introduction

   Application-layer protocols require DNS to resolve a domain name to a 
   cryptographic endpoint (e.g., an IPv6 IID). This document defines a 
   lightweight Data RR to act as a pointer.

   The DNS layer only transports the pointer. The CBOR payload is opaque 
   to the resolver. No identity, compliance, or application-layer 
   semantics are defined here.

2. Why Not TXT? 

   TXT was evaluated and rejected due to three engineering constraints:

   1. Binary Overhead: TXT enforces text encoding (Base64/Hex). This 
      inflates the binary payload by ~33%, increasing the risk of 
      reaching the 512-byte UDP limit.

   2. String Reassembly Failures: DNS TXT records are transmitted as 
      255-byte character-strings. Middleboxes (e.g., firewalls, SPF 
      filters) often mangle or drop these strings. This breaks 
      cryptographic proof verification.

   3. Policy Isolation: TXT is a shared space for SPF/DKIM. A dedicated 
      TYPE 260 allows enterprise gateways to filter cryptographic 
      traffic without breaking standard TXT records.

3. RDATA Format

   The UTXO RR has the following RDATA structure:

       +--------------------+-------------------+
       | Endpoint ID (CBOR) | VRF Proof (opt) |
       +--------------------+-------------------+

   Endpoint Identifier: A CBOR-encoded byte string. It typically embeds 
   an IPv6 IID or a short DID reference. The DNS treats this as opaque 
   binary data.

   VRF Proof: OPTIONAL. A byte string containing a proof (RFC 9381) 
   for offline verification.

   Payload Size Constraint: The total RDATA length MUST NOT exceed 
   512 bytes. A typical CBOR endpoint is 16-24 bytes, and a VRF proof 
   is ~80 bytes. Total typical size is ~100 bytes.

4. Naming and Apex Restrictions

4.1. Apex Prohibition

   The UTXO RR MUST NOT be placed at the zone apex. Adding non-standard 
   RRTYPEs at the apex can conflict with CNAME processing.

4.2. Mandatory Prefix and Examples

   All UTXO records MUST be placed under the _utxo prefix.

   Valid Example:
   _utxo.example.test. 3600 IN UTXO \# 24 ( 82A1F6... )

   Valid Example (Agent-specific):
   _utxo.agent01.example.test. 3600 IN UTXO \# 104 ( 82A1F6... 58A0... )

   Invalid Example (Apex):
   example.test. 3600 IN UTXO ...

4.3. Granularity

   Granularity is handled via explicit subdomains (e.g., 
   _utxo.alice.example.test), not wildcard matching. The DNS layer does 
   not interpret subdomain labels as identity.

5. Resolver Behavior and RFC 3597

   Per RFC 3597, resolvers that do not implement this specification MUST 
   treat TYPE 260 as an unknown type. The RDATA is stored and forwarded 
   as unstructured binary data. The UTXO RR introduces no new protocol 
   state, no additional section processing, and no assumptions about 
   wildcards or DNAME.

6. Security Considerations

   Cache Poisoning: Constrained to 512 bytes.

   Middlebox Interference: A dedicated RRTYPE avoids TXT-specific 
   string manipulation.

   Proof Verification: Resolvers do not validate the VRF proof. Clients 
   MUST validate the CBOR structure and VRF proof.

7. IANA Considerations

   Requesting one new Data RRTYPE:

   Mnemonic: UTXO
   Code: 260
   Type: Data RR
   Reference: This document
   Assignment Policy: Expert Review (RFC 6895)

8. Appendix A: Changes from -01

   - Removed PRN compliance and vLEI logic from DNS payload.
   - Added Section 2: Rationale against TXT.
   - Added Section 4.1: Apex prohibition.
   - Updated examples to use _utxo prefix.
   - Hard-capped RDATA at 512 bytes.

Authors' Addresses

   Guorong Tian
   CoCa Foundation
   Email: [email protected]

﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉﹉
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to