RFC 1
E211681
RFC 1 is the first Request for Comments document, published in 1969, which laid the groundwork for the development of the ARPANET and the modern Internet protocol standards process.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1896901 — 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 1 Context triple: [Steve Crocker, wrote, RFC 1]
-
A.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
B.
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.
-
C.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
D.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
E.
RFC 1591
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).
- 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 1 Target entity description: RFC 1 is the first Request for Comments document, published in 1969, which laid the groundwork for the development of the ARPANET and the modern Internet protocol standards process.
-
A.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
B.
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.
-
C.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
D.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
E.
RFC 1591
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).
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments document
ⓘ
technical memorandum ⓘ |
| author | Steve Crocker ⓘ |
| authorAffiliation | University of California, Los Angeles ⓘ |
| category |
Internet history
ⓘ
computer networking documentation ⓘ |
| citedAs | Crocker, S., RFC 1, Host Software, April 1969 ⓘ |
| citedBy | numerous later RFCs ⓘ |
| context | early packet-switched networking research ⓘ |
| createdInContextOf |
ARPANET project
ⓘ
linked to:
ARPANET
|
| describes |
early ARPANET host software concepts
ⓘ
initial ideas for host-to-host protocols ⓘ |
| documentType | informational ⓘ |
| hasAbbreviation | RFC 1 ⓘ |
| hasPageCount | 4 ⓘ |
| hasSeriesAbbreviation |
RFC
ⓘ
linked to:
RFCs
|
| hasURL | https://www.rfc-editor.org/rfc/rfc1 ⓘ |
| historicSignificance |
first document in the RFC series
ⓘ
origin of the RFC publication model ⓘ |
| identifier | RFC0001 ⓘ |
| influenced |
Internet standards development
ⓘ
subsequent RFC documents ⓘ |
| isPartOf | ARPANET documentation ⓘ |
| language | English ⓘ |
| laysGroundworkFor |
ARPANET development
ⓘ
Internet protocol standards process ⓘ |
| maintainedBy | RFC Editor ⓘ |
| mentionsOrganization |
Network Information Center
ⓘ
Stanford Research Institute ⓘ |
| partOfSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| publicationDate | 1969-04-07 ⓘ |
| publicationYear | 1969 ⓘ |
| publishedBy | Network Working Group ⓘ |
| region |
United States
ⓘ
linked to:
United States of America
|
| RFCNumber | 1 ⓘ |
| seriesPublisher |
Defense Advanced Research Projects Agency
ⓘ
United States Department of Defense ⓘ
linked to:
Department of Defense
|
| status | Historic ⓘ |
| subject |
ARPANET
ⓘ
Internet standards process ⓘ host software ⓘ network protocols ⓘ |
| title | Host Software ⓘ |
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 1 Description of subject: RFC 1 is the first Request for Comments document, published in 1969, which laid the groundwork for the development of the ARPANET and the modern Internet protocol standards process.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.