IANA Naming Function Contract
E37209
The IANA Naming Function Contract is the formal agreement that defined how the Internet Assigned Numbers Authority’s naming functions—such as management of the DNS root zone—were performed under oversight prior to the IANA stewardship transition.
All labels observed (3)
| Label | Occurrences |
|---|---|
| IANA Functions Contract (historically with the U.S. Department of Commerce) | 1 |
| IANA Naming Function Contract canonical | 1 |
| IANA functions contract | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T287343 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IANA Naming Function Contract Context triple: [Public Technical Identifiers, compliesWith, IANA Naming Function Contract]
-
A.
Domain Name System root zone
The Domain Name System root zone is the top-level, authoritative directory of the internet’s domain name hierarchy, mapping top-level domains to their corresponding name servers.
-
B.
RFC 1035
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
-
C.
RFC 1034
RFC 1034 is an Internet standards document that specifies the concepts and facilities of the Domain Name System (DNS), defining how domain names are structured and resolved on the internet.
-
D.
Internet Corporation for Assigned Names and Numbers
The Internet Corporation for Assigned Names and Numbers (ICANN) is a nonprofit organization that coordinates the global domain name system and IP address allocation to ensure the stable and secure operation of the internet.
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IANA Naming Function Contract Target entity description: The IANA Naming Function Contract is the formal agreement that defined how the Internet Assigned Numbers Authority’s naming functions—such as management of the DNS root zone—were performed under oversight prior to the IANA stewardship transition.
-
A.
Domain Name System root zone
The Domain Name System root zone is the top-level, authoritative directory of the internet’s domain name hierarchy, mapping top-level domains to their corresponding name servers.
-
B.
RFC 1035
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
-
C.
RFC 1034
RFC 1034 is an Internet standards document that specifies the concepts and facilities of the Domain Name System (DNS), defining how domain names are structured and resolved on the internet.
-
D.
Internet Corporation for Assigned Names and Numbers
The Internet Corporation for Assigned Names and Numbers (ICANN) is a nonprofit organization that coordinates the global domain name system and IP address allocation to ensure the stable and secure operation of the internet.
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IANA-related agreement
ⓘ
contract ⓘ formal agreement ⓘ |
| appliesTo |
country-code top-level domains
ⓘ
generic top-level domains ⓘ internationalized domain name top-level domains ⓘ |
| associatedWith |
VeriSign
ⓘ
surface form:
Verisign
root zone maintainer ⓘ root zone management partners ⓘ |
| category | Internet governance document ⓘ |
| defines |
reporting obligations to NTIA
ⓘ
requirements for performance of IANA naming functions ⓘ security and stability requirements for root zone management ⓘ service level expectations for IANA naming functions ⓘ |
| endedWith | completion of the IANA stewardship transition ⓘ |
| ensures |
continuity of DNS root zone management
ⓘ
stability of the domain name system ⓘ |
| excludes |
Internet Assigned Numbers Authority
ⓘ
surface form:
IANA numbering functions
IANA ⓘ
surface form:
IANA protocol parameter functions
|
| governs |
IANA naming functions
ⓘ
management of the DNS root zone ⓘ root zone WHOIS services ⓘ root zone change requests processing ⓘ root zone database maintenance ⓘ |
| hasParty |
Internet Assigned Numbers Authority
ⓘ
Internet Corporation for Assigned Names and Numbers ⓘ National Telecommunications and Information Administration ⓘ U.S. Department of Commerce ⓘ
surface form:
United States Department of Commerce
|
| hasRole |
framework for accountability of IANA naming operations
ⓘ
mechanism for U.S. government oversight of DNS root ⓘ |
| includes |
audit and compliance provisions
ⓘ
performance metrics for IANA naming functions ⓘ statement of work for naming functions ⓘ term and renewal provisions ⓘ |
| legalJurisdiction |
United States of America
ⓘ
surface form:
United States
|
| oversightBy |
National Telecommunications and Information Administration
ⓘ
surface form:
NTIA
United States government ⓘ |
| performedBy |
IANA
ⓘ
surface form:
IANA functions operator
Internet Corporation for Assigned Names and Numbers ⓘ
surface form:
ICANN
|
| precedes | post-transition IANA arrangements ⓘ |
| purpose | to formalize performance of IANA naming functions under NTIA oversight ⓘ |
| relatedTo |
IANA Naming Function Contract
self-linksurface differs
ⓘ
surface form:
IANA functions contract
ICANN-NTIA relationship ⓘ |
| relatesTo | IANA stewardship transition ⓘ |
| scope | naming-related IANA functions only ⓘ |
| subjectOf |
IANA stewardship transition process
ⓘ
Internet governance debates ⓘ multistakeholder community discussions ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: IANA Naming Function Contract Description of subject: The IANA Naming Function Contract is the formal agreement that defined how the Internet Assigned Numbers Authority’s naming functions—such as management of the DNS root zone—were performed under oversight prior to the IANA stewardship transition.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
IANA Naming Function Contract
→
relatedTo
→
IANA Naming Function Contract
self-linksurface differs
ⓘ
this entity surface form:
IANA functions contract
this entity surface form:
IANA Functions Contract (historically with the U.S. Department of Commerce)