.us

Canonical .us referent

Record the canonical label, classification and evidence connecting vr.tr.us to the root delegation.

1. What registry or delegation evidence establishes that vr.tr.us denotes the .us country-code top-level domain? definition
2. Does the observed identifier denote .us itself, a descendant name or a non-DNS use of US? boundary

Dated authority mandates

Record responsible organisations, the evidence for their roles and the dates over which those roles apply.

1. Which current delegation record and governing instruments establish the operator and oversight roles for .us? provenance
2. Whose authorisation is required for the proposed registry-policy or root-delegation change? action

Branch and manager resolution

Record branch classification and the responsible manager without treating every descendant as independently registrable.

1. Is the candidate in the direct-registration namespace, a state or locality hierarchy, or another specially governed branch? boundary
2. Which current source identifies the registration boundary and manager for that branch? provenance

Branch lifecycle status

Record whether a branch accepts new names and what operations remain available for existing names, including the status of kids.us.

1. What dated evidence establishes the present status of this locality-based or specially governed branch? provenance
2. Which creation, renewal, transfer or delegation operations remain permitted for this branch? action

Nexus evidence and review

Record the applicable nexus policy, claimed eligibility category and evidence needed to resolve uncertainty.

1. Which nexus category under the applicable policy could qualify this applicant? definition
2. What evidence and verification steps are required before the agent can treat that qualification as established? action

Registration preconditions

Record syntax, reservation, applicant restrictions and data-policy prerequisites for the selected registration route.

1. Does the proposed label meet current syntax rules and avoid applicable reserved or restricted categories? boundary
2. What registration-data, disclosure and privacy or proxy conditions must the applicant satisfy? action

Delegation and validation observations

Record observed root delegation, authoritative responses and DNSSEC validation results with timestamps.

1. Do observed root delegation records and .us authoritative responses agree on the relevant service configuration? measurement
2. What result does root-to-.us DNSSEC validation produce, and which observations support it? measurement

Namespace versus child fault

Record whether failures affect .us authoritative service, a delegated branch, an individual domain or only a resolver path.

1. What query success rates and response times are observed across .us authoritative servers and independent vantage points? measurement
2. Does the evidence locate the failure at .us, below a child delegation or within the observing network? boundary

Permitted operation and prerequisites

Record the requested operation, actor mandate, responsible service and blocking conditions.

1. Is the request a registration-level operation, branch-delegation change or change to .us itself? boundary
2. Which authority, credentials and policy prerequisites must be established before submitting it? action

Issue-specific remedy

Record whether a case concerns nexus, registration data, naming rights, abuse or DNS operation, and link it to the appropriate process.

1. Which .us policy and evidence establish the appropriate process for this reported issue? provenance
2. Who may submit the request, what outcomes can the recipient authorise, and what review route applies? action

Kinds and varieties

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these kinds and varieties hold for the sense of .us this model covers, and on what evidence? provenance

Identifiers and schemes

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these identifiers and schemes hold for the sense of .us this model covers, and on what evidence? provenance

Standards and regulation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these standards and regulation hold for the sense of .us this model covers, and on what evidence? provenance

Real-world use

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these real-world use hold for the sense of .us this model covers, and on what evidence? provenance

Typical measurements

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these typical measurements hold for the sense of .us this model covers, and on what evidence? provenance

Failure modes and hazards

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these failure modes and hazards hold for the sense of .us this model covers, and on what evidence? provenance

Regional variation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these regional variation hold for the sense of .us this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these neighbouring kinds and how to tell them apart hold for the sense of .us this model covers, and on what evidence? provenance