RFC 1591
E162345
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 1591 canonical | 4 |
| RFC 1591 is largely superseded by later IANA and ICANN policies | 1 |
| RFC1591 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1405514 — 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: RFC 1591 Context triple: [.ch, RFCReference, RFC 1591]
-
A.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
B.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
C.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- 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: RFC 1591 Target entity description: RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
A.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
B.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
C.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
DNS policy document
ⓘ
Internet standards document ⓘ Request for Comments ⓘ |
| appliesTo |
country-code top-level domains
ⓘ
generic top-level domains ⓘ |
| area | Domain Name System ⓘ |
| author | Jon Postel ⓘ |
| defines |
administration of top-level domains
ⓘ
concept of trustee role for TLD managers ⓘ criteria for selecting top-level domain managers ⓘ delegation policies for top-level domains ⓘ distinction between generic and country-code top-level domains ⓘ policies for two-letter country-code top-level domains ⓘ procedures for changing TLD managers ⓘ relationship between IANA and TLD managers ⓘ requirement that TLDs serve the local Internet community ⓘ requirements for country-code top-level domains ⓘ responsibilities of top-level domain administrators ⓘ structure of the Domain Name System top-level domains ⓘ use of ISO 3166 country codes for ccTLDs ⓘ |
| definesRole |
IANA as central authority for TLD delegation
ⓘ
TLD manager as public trustee for the Internet community ⓘ |
| focusesOn |
DNS administration
ⓘ
DNS naming structure ⓘ top-level domain delegation ⓘ |
| governs | early DNS top-level domain management practices ⓘ |
| historicalSignificance | foundational document for early DNS and TLD policy ⓘ |
| identifier |
RFC1591
ⓘ
linked to:
RFC 1591
|
| language | English ⓘ |
| mentions |
IANA
ⓘ
ISO 3166 Maintenance Agency ⓘ |
| policyType | DNS delegation policy ⓘ |
| publicationDate | 1994-03 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
RFC Editor ⓘ |
| rfcNumber | 1591 ⓘ |
| series | RFC series ⓘ |
| setsRequirement |
TLD manager must be equitable and just to all groups in the domain
ⓘ
TLD manager must be on the Internet and have mail connectivity ⓘ TLD manager must have technical competence in DNS operations ⓘ TLD must have at least two independent name servers ⓘ |
| status | Informational ⓘ |
| supersededBy |
RFC 1591 is largely superseded by later IANA and ICANN policies
ⓘ
linked to:
RFC 1591
|
| title |
Domain Name System Structure and Delegation
ⓘ
linked to:
Domain Name System
|
| url | https://www.rfc-editor.org/rfc/rfc1591 ⓘ |
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: RFC 1591 Description of subject: RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 1591
linked to: RFC 1591