Requests, notices, and review
The packet contains a common statement of authority and several schedules. Complete the common part, select the filing class, and attach only the schedules and evidence that apply.
Identify the organization, authorized representative, and evidence that the representative may bind it for this request.
State the requested decision in terms precise enough to approve, refuse, and later compare with implementation.
Record the relevant state as it exists, the state requested, and any assumptions on which the transition depends.
State a safe restoration point and who may authorize its use. If no rollback exists, explain the continuity measure that replaces it.
Label each annex and connect it to the factual claim it supports. Volume is not a substitute for relevance.
Identify personal, confidential, or security-sensitive material and provide a redacted public version where one is required.
Write “unknown” where a relevant fact is not yet known and identify who is resolving it. Write “not applicable” only where the condition making it inapplicable is stated. Blank space establishes nothing.
An organization seeking membership must establish its legal or institutional identity, authority over the proposed registry activity, decision contacts, technical capacity, continuity arrangements, and willingness to accept duties of care toward the shared root. Admission does not itself create a delegation.
The filer must establish authority for the requested label, the proposed registry operator, registry policy, authoritative service, DNSSEC state, public registration services, continuity arrangements, intended root data, and rollback state. WCAAN may require consultation where the delegation affects another namespace or partner.
Use this for nameservers, glue, or another published delegation field where registry authority does not change. Give the exact current and proposed resource records, the implementation sequence, validation evidence, and rollback trigger.
Use this for initial DS publication, rollover, algorithm transition, emergency replacement, or removal. State the complete old and new trust material, timing, overlap, observation method, and the condition under which the old state may be removed.
The existing authority and intended successor should state the transfer independently. The filing must cover registrant continuity, registry data, escrow or restoration material where applicable, EPP and RDAP transition, DNS service, DNSSEC custody, effective time, and rollback.
Use this where the public or authenticated representative changes but delegation data does not. Establish the former authority where available, the new representative's authority, the effective time, and the contact records that become obsolete.
An emergency request must identify the active harm, why ordinary notice would make it materially worse, the narrow temporary state required, the maximum duration, the evidence available now, and the restoration state. The change still follows the ordinary authority and implementation channels. If it fails, it is rolled back. Temporary action expires after 14 days unless a public decision confirms the resulting state.
A member NIC may use the packet to confirm that its authority, responsible contacts, registry controls, DNS and DNSSEC operation, recovery arrangements, and disclosed exceptions remain materially accurate. An assurance states what was examined and by whom. It does not prove what was never tested.
An incident notice must distinguish technical cause from institutional cause where they differ. Record the first observed time, affected service or namespace, user effect, containment, restoration, evidence, remaining uncertainty, and corrective work. Later knowledge belongs in a later version. The first account must not be silently rewritten.
Use a correction for a factual, clerical, or technical error in the public record. Identify the exact statement, the evidence that contradicts it, the corrected text, and whether any party relied on the error. The prior text remains recoverable.
Use reconsideration where a decision is said to contain a material error in authority, fact, procedure, conflict handling, or reasoning. Identify the challenged act, the alleged error, the evidence already available or newly obtained, the effect of the error, and the result requested. Disagreement alone is not evidence of error.
A consultation is a required interval for submissions in support, objections, and answers to them, all of which naturally affect the final decision. The notice must identify the proposal, evidence, questions, submission route, publication treatment, and closing time. Unless recorded urgency requires less, consultation remains open for at least 21 days.
WCAAN ordinarily consults before admitting or removing a member NIC, materially changing delegation conditions, changing how the root incorporates another namespace, or adopting a rule that changes ordinary resolution. CETNIC receives direct notice where .cet, .cet.is, or member rights are affected. Tan's Network receives direct notice where publication or signing requirements change.
Emergency changes may proceed before that interval where delay would create significant technical failure or downtime. Naturally, this is extraordinary. The decision must state why notice could not safely precede action, what temporary state was used, when it expires, and how ordinary review will follow.
An accepted channel preserves the received version and assigns a case reference.
WCAAN identifies missing authority, state, evidence, or publication material. Complete means assessment may begin. It does not mean approved.
Legitimacy and technical feasibility are examined separately. Where consultation applies, its submissions become part of the evidence.
The result states the relevant facts, reasons, conditions, effective time, and review route.
Tan's Network applies the exact approved state, refuses it as unsafe, or rolls it back. The outcome is reported to WCAAN.
The public record contains the decision and implementation result after protected material has been removed.
No filing fee or binding general service target has been adopted. Any future target will begin only when the filing is complete, pause while specifically requested evidence is outstanding, and record both the reason and revised date for an extension. Silence is not an extension.