RFC 918 (POP1)
E900225
RFC 918 (POP1) is an early Internet standards document that specifies the original Post Office Protocol (POP) for retrieving email from a remote server.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Post Office Protocol | 1 |
| RFC 918 (POP1) canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T11016667 — 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 918 (POP1) Context triple: [POP, definedIn, RFC 918 (POP1)]
-
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 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
C.
RFC 943
RFC 943 is an Internet standards document that superseded RFC 870 by providing updated specifications for early TCP/IP networking protocols.
-
D.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
-
E.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
- 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 918 (POP1) Target entity description: RFC 918 (POP1) is an early Internet standards document that specifies the original Post Office Protocol (POP) for retrieving email from a remote server.
-
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 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
C.
RFC 943
RFC 943 is an Internet standards document that superseded RFC 870 by providing updated specifications for early TCP/IP networking protocols.
-
D.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
-
E.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ email protocol specification ⓘ |
| abbreviation | POP NERFINISHED ⓘ |
| accessMethod | text file available via RFC repositories ⓘ |
| area | Application layer ⓘ |
| category | experimental protocol ⓘ |
| defines | original Post Office Protocol ⓘ |
| definesOperation |
deleting messages from the server
ⓘ
listing messages in a mailbox ⓘ retrieving messages ⓘ user authentication to maildrop ⓘ |
| definesRole |
POP client
ⓘ
POP server ⓘ |
| focusesOn | offline mail reading model ⓘ |
| influenced |
design of POP3
ⓘ
later POP versions ⓘ |
| intendedEnvironment | early Internet email systems ⓘ |
| language | English ⓘ |
| layer | Application layer of the Internet protocol suite ⓘ |
| organization | Internet Engineering Task Force NERFINISHED ⓘ |
| predecessorOf |
RFC 1081
NERFINISHED
ⓘ
RFC 1225 NERFINISHED ⓘ RFC 1460 NERFINISHED ⓘ RFC 1725 NERFINISHED ⓘ RFC 1939 NERFINISHED ⓘ RFC 937 NERFINISHED ⓘ |
| protocolName | Post Office Protocol NERFINISHED ⓘ |
| protocolType | mail retrieval protocol ⓘ |
| purpose | to allow a workstation or personal computer to retrieve mail from a remote server ⓘ |
| relatedProtocol |
IMAP
NERFINISHED
ⓘ
POP2 NERFINISHED ⓘ POP3 NERFINISHED ⓘ SMTP NERFINISHED ⓘ |
| RFCNumber | 918 ⓘ |
| series | RFC series NERFINISHED ⓘ |
| shortTitle | POP1 ⓘ |
| specifies |
client-server protocol for mail retrieval
ⓘ
mechanism for retrieving email from a remote server ⓘ |
| standardizes | POP1 NERFINISHED ⓘ |
| status | obsolete ⓘ |
| title | Post Office Protocol NERFINISHED ⓘ |
| topic |
application protocols
ⓘ
electronic mail ⓘ |
| transportProtocol | TCP NERFINISHED ⓘ |
| useCase | retrieving messages from a maildrop on a remote host ⓘ |
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 918 (POP1) Description of subject: RFC 918 (POP1) is an early Internet standards document that specifies the original Post Office Protocol (POP) for retrieving email from a remote server.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.