A. Submission Date: 2026-10-27

B.1 Submission Type:
[X] New RRTYPE
[ ] Modification to RRTYPE

B.2 Kind of RR:
[X] Data RR
[ ] Meta-RR

C. Contact Information for submitter (will be publicly posted):
- Name: Guorong Tian
- Email Address: [email protected]
- International telephone number: [None]
- Other contact handles: github.com/cocafoundation6

D. Motivation for the new RRTYPE application.

Traditional DNS answers only the "where" question—mapping a domain name to an 
IP address. Modern payment scenarios require the same domain name to 
simultaneously answer three additional questions: who is the receiving party 
(identity), what rules apply (compliance), and to which endpoint the value 
should actually be sent (payment endpoint). These are DNS's structural blind 
spots, and no existing RRTYPE is designed to carry this combination of 
verifiable cryptographic pointers and regulatory metadata.

This application requests a Data RRTYPE that functions as a neutral, opaque 
container for DNS. The RDATA is a CBOR-encoded payload containing a blockchain 
UTXO reference, an optional Verifiable Random Function (VRF) proof, a payment 
endpoint identifier, and optional vLEI legal-entity references. The DNS core 
protocol does not parse or interpret this payload; wallets and TEE clients 
decode and verify it locally. The goal is to extend DNS from a one-dimensional 
name-to-IP mapping into a multi-dimensional resolver for identity, compliance, 
and payment endpoints, while leaving DNS resolution semantics entirely 
unchanged.

E. Description of the proposed RR type.

The RDATA is an opaque byte stream, CBOR-encoded per RFC 8949. It carries a 
structured payload that includes a UTXO reference, an endpoint type, a chain 
identifier, an endpoint identifier, an expiry timestamp, an owner public-key 
hash, and optional fields for a VRF proof (per RFC 9381), an IPv6 Interface 
Identifier (per RFC 7217), and a vLEI DID reference. The complete binary 
format, field ordering, and client-side parsing rules are specified in 
draft-guorong-utxo-dns-02, Section 2.3.

From the perspective of DNS servers and resolvers, this RR is indistinguishable 
from any other RFC 3597 Unknown RR: it is stored, cached, and forwarded as 
opaque RDATA. All semantic processing—CBOR decoding, cryptographic 
verification, payment-endpoint extraction—occurs exclusively in wallet and TEE 
client software, outside the DNS resolution path. The proposed type is a Data 
RR, not a Meta-RR, and it may appear anywhere in a zone file without special 
placement restrictions.

F. What existing RRTYPE or RRTYPEs come closest to filling that need and why 
are they unsatisfactory?

TXT (type 16) is the closest existing Data RR for carrying arbitrary data. 
However, TXT is designed for unstructured UTF-8 text; it provides no binary 
container semantics, no type discrimination, and no mechanism to signal that 
the payload must be cryptographically verified by the client. Encoding a CBOR 
structure inside TXT would require an out-of-band convention that is invisible 
to DNS infrastructure and indistinguishable from ordinary text records.

SVCB (type 64) and HTTPS (type 65) are designed for service-binding parameters 
and have a rigid, structured RDATA format oriented toward transport-layer 
connection setup. They do not accommodate UTXO references, VRF proofs, or 
regulatory metadata, and their semantics assume the RDATA will be parsed by the 
resolver or client library according to a defined schema—not treated as an 
opaque container for a separate verification layer.

No existing RRTYPE combines three properties simultaneously: (1) an opaque, 
client-parsed binary container, (2) explicit signalling that the payload is 
intended for cryptographic verification outside DNS, and (3) coexistence with 
RFC 3597 Unknown RR handling without resolver modifications. A new Data RRTYPE 
is required to fill this gap.

G. What mnemonic is requested for the new RRTYPE (optional)?

UTXO

If the Expert determines that this mnemonic conflicts with existing RRTYPE or 
CLASS mnemonics, the applicant accepts any Expert-assigned mnemonic.

H. Does the requested RRTYPE make use of any existing IANA registry or require 
the creation of a new IANA subregistry in DNS Parameters?

[X] No.

The CBOR payload structure is defined entirely within draft-guorong-utxo-dns-02 
and does not depend on any IANA-managed subregistry. No new DNS Parameters 
subregistry is required. The RRTYPE code point itself is requested through the 
Expert Review process described in RFC 6895; no additional registry creation is 
proposed.

I. Does the proposal require/expect any changes in DNS servers/resolvers that 
prevent the new type from being processed as an unknown RRTYPE (see [RFC3597])?

[X] No.

The proposed RR is explicitly designed to be handled as an RFC 3597 Unknown RR 
by any server or resolver that does not implement it. No changes to DNS 
software are required. Servers that do not recognize the type will store, 
cache, and forward the RDATA as opaque bytes without error. The payload is 
never parsed by DNS infrastructure; verification is performed only by 
wallet/TEE clients that explicitly choose to process this type.

J. Comments:

This application follows the Expert Review path specified in RFC 6895. The 
broader architectural context of .utxo namespace resolution was discussed at 
IETF 126 DNSOP DISPATCH, where it was noted that an alternative namespace 
exceeds the scope of IETF DNS standardization. However, the allocation of a new 
RRTYPE code point via Expert Review does not depend on working-group adoption 
or Standards Track status, and this application is submitted independently on 
that basis.

The applicant acknowledges the Expert guidelines in RFC 6895 §3.1.2 and 
confirms that this proposal does not alter or depend on DNS wildcard, CNAME, or 
DNAME processing; does not request an excessive number of RRTYPE values; and 
provides a description sufficient for implementation, with the full 
specification available in draft-guorong-utxo-dns-02.

The applicant also notes that draft-guorong-utxo-dns-02 currently uses TBD1 
(65400) as a placeholder for the RRTYPE code and TBD2 (65000) for an associated 
EDNS0 option. The EDNS0 option is an independent IANA allocation under a 
separate registry and is not part of this RRTYPE application; this template 
requests only the Data RRTYPE code point. Upon approval, the placeholder TBD1 
will be replaced with the assigned decimal value, and IANA is requested to 
update the registry reference to point to the Internet-Draft or its published 
RFC equivalent.

来自阿里邮箱Android客户端
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to