RFC 882
E36655
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 882 canonical | 6 |
How this entity was disambiguated
This entity first appeared as the object of triple T270987 — 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 882 Context triple: [RFC 1035, obsoletes, RFC 882]
-
A.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
B.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
C.
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.
-
D.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
E.
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.
- 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 882 Target entity description: RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
A.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
B.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
C.
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.
-
D.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
E.
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.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
Internet hosts
ⓘ
Name servers ⓘ Resolvers ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| author | Paul Mockapetris ⓘ |
| category | Standards Track ⓘ |
| defines |
Basic DNS concepts
ⓘ
DNS query and response model ⓘ Domain name space ⓘ Resource records model ⓘ |
| definesProtocol |
Domain Name System
ⓘ
surface form:
DNS
Domain Name System ⓘ |
| documentType | Standards specification ⓘ |
| hasNumber | 882 ⓘ |
| historicStatus | Historic DNS specification ⓘ |
| intendedUse |
Domain Name System
ⓘ
surface form:
Specification of the Domain Name System
|
| language | English ⓘ |
| networkLayer | Application layer ⓘ |
| obsoletedBy |
RFC 1034
ⓘ
RFC 1035 ⓘ |
| partOf | DNS specification ⓘ |
| predecessorOf |
RFC 1034
ⓘ
RFC 1035 ⓘ |
| protocolFamily | TCP/IP ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 883
ⓘ
RFC 973 ⓘ |
| replaced | Host table-based name resolution ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| standardizes |
Concepts for domain names
ⓘ
Facilities for domain names ⓘ |
| status | Obsoleted ⓘ |
| subject |
Domain names
ⓘ
Internet architecture ⓘ Name service ⓘ |
| supersededBy |
RFC 1034
ⓘ
RFC 1035 ⓘ |
| title |
Domain Name System
ⓘ
surface form:
Domain Names - Concepts and Facilities
|
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 882 Description of subject: RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
Paul Mockapetris