Hi IANA Team, DNSOP Chairs, and Community,
Following the recent technical discussions on this thread and the valuable
feedback from the experts (Paul, Stephane, Mukund, and Ray), we have made our
final engineering decision.
To avoid exacerbating public RRTYPE space congestion and to maintain DNS core
neutrality, we are formally withdrawing our request for a dedicated RRTYPE code
point.
Instead, as suggested by the consensus, the UTXO6 protocol will immediately
proceed with production deployment using the RFC 3597 Private-use space (QTYPE
65400), strictly bound to the `_utxo` owner name prefix.
We have just published the final revised Internet-Draft:
https://datatracker.ietf.org/doc/draft-guorong-utxo-dns-03/
Key updates in -03 include:
1. Removed the RRTYPE allocation request (utilizing 65400).
2. Corrected the technical explanations regarding TXT wire format and Apex
prohibition, thanks to Mukund's rigorous review.
3. Solidified the architecture: DNS acts solely as an opaque transport layer,
while all CBOR validation is handled locally by the TEE.
Thank you all for the rigorous review. The community's feedback has made our
specification much more robust. We will now focus on interoperability testing
and commercial deployment.
Best regards,
Guorong Tian
CoCa Foundation
来自阿里邮箱Android客户端
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]