Public correction record

IDNA encoding is not domain operation

Correction

Unicode, IDNA, registry, registration, delegation, resolution, TLS, and hosting remain separate evidence states.

Stable record: COR-K08-006
Claim status: CORRECTED
Last reviewed: 2026-08-16
Research cutoff: 2026-08-16
Source type: PUBLIC CORRECTION
Currentness: Current for release 2.1.0; external sources require periodic revalidation.
Correction state: No unresolved public correction recorded for this release.
Machine record: Static JSON record

Prior record

Technical discussions can conflate an encodable label with a functioning domain.

Reason for correction

Each state has a different authority and operational proof.

Affected record

REP-K08-065. Correction date: 2026-08-15.

Supporting sources

RFC 3492 — Punycode: A Bootstring Encoding of Unicode for IDNA — IETF / RFC Editor; RFC 3492; PROPOSED STANDARD; UPDATED BY RFC 5891. Exact claim-support entries: 1. Revalidated 2026-08-15T23:55:00Z.
RFC 5890 — IDNA Definitions and Document Framework — IETF / RFC Editor; RFC 5890; PROPOSED STANDARD. Exact claim-support entries: 1. Revalidated 2026-08-15T23:55:00Z.
RFC 5891 — Internationalized Domain Names in Applications: Protocol — IETF / RFC Editor; RFC 5891; PROPOSED STANDARD. Exact claim-support entries: 1. Revalidated 2026-08-15T23:55:00Z.

Correction semantics

The prior record remains preserved for history. The corrected record is active for K02. Correction does not erase provenance, create retroactive authority, or prove every adjacent proposition.