RFC 920
E819964
RFC 920 is an early Internet standards document that defines the procedures and requirements for registering and managing top-level domains in the Domain Name System (DNS).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 920 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T9767725 — 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.
Target entity: RFC 920 Context triple: [.net, technicalStandard, RFC 920]
-
A.
RFC 990
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
-
B.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
C.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
D.
RFC 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
-
E.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 920 Target entity description: RFC 920 is an early Internet standards document that defines the procedures and requirements for registering and managing top-level domains in the Domain Name System (DNS).
-
A.
RFC 990
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
-
B.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
C.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
D.
RFC 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
-
E.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| appliesTo |
DNS
NERFINISHED
ⓘ
Domain Name System NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| concerns |
Internet domain structure
ⓘ
Internet naming architecture NERFINISHED ⓘ |
| defines |
policies for allocation of domain names
ⓘ
policies for management of top-level domains ⓘ procedures for registering top-level domains ⓘ requirements for country-level domains ⓘ requirements for generic domains ⓘ requirements for top-level domains ⓘ roles and responsibilities of domain administrators ⓘ |
| documentType | standards document ⓘ |
| focusesOn |
TLDs
NERFINISHED
ⓘ
top-level domains ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc920 ⓘ |
| historicalRole | one of the earliest documents defining DNS top-level domain policies ⓘ |
| intendedAudience |
Internet protocol designers
ⓘ
domain registries ⓘ network administrators ⓘ |
| language | English ⓘ |
| networkProtocolFamily | Internet NERFINISHED ⓘ |
| partOf | RFC series NERFINISHED ⓘ |
| publicationDate | 1984-10 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Network Working Group NERFINISHED ⓘ |
| relatedTo |
RFC 882
NERFINISHED
ⓘ
RFC 883 NERFINISHED ⓘ |
| RFCNumber | 920 ⓘ |
| specifies |
administrative requirements for domain registration
ⓘ
criteria for establishing new top-level domains ⓘ naming conventions for domains ⓘ technical requirements for domain registration ⓘ |
| standardizes | domain registration procedures for the early Internet ⓘ |
| status | Historic ⓘ |
| title | Domain Requirements ⓘ |
| updates | early DNS domain registration procedures ⓘ |
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.
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.
Subject: RFC 920 Description of subject: RFC 920 is an early Internet standards document that defines the procedures and requirements for registering and managing top-level domains in the Domain Name System (DNS).
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.