RFC 3501
E39860
RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
All labels observed (6)
| Label | Occurrences |
|---|---|
| RFC 3501 canonical | 7 |
| IMAP4rev1 | 3 |
| Internet Message Access Protocol version 4rev1 | 2 |
| IMAP4 | 1 |
| INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 | 1 |
| Internet Message Access Protocol - Version 4rev1 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T306622 — 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 3501 Context triple: [IMAP, definedIn, RFC 3501]
-
A.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
B.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
C.
IMAP
IMAP (Internet Message Access Protocol) is a standard email protocol that allows clients to access and manage messages stored on a mail server while keeping them synchronized across multiple devices.
-
D.
POP3
POP3 (Post Office Protocol version 3) is a standard email protocol used by clients to retrieve messages from a remote mail server over a TCP/IP network, typically downloading them for local storage.
-
E.
SMTP
SMTP (Simple Mail Transfer Protocol) is a standard communication protocol used for sending and routing email messages across 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 3501 Target entity description: RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
-
A.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
B.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
C.
IMAP
IMAP (Internet Message Access Protocol) is a standard email protocol that allows clients to access and manage messages stored on a mail server while keeping them synchronized across multiple devices.
-
D.
POP3
POP3 (Post Office Protocol version 3) is a standard email protocol used by clients to retrieve messages from a remote mail server over a TCP/IP network, typically downloading them for local storage.
-
E.
SMTP
SMTP (Simple Mail Transfer Protocol) is a standard communication protocol used for sending and routing email messages across IP networks.
- F. None of above. chosen
Statements (70)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| abbreviation |
IMAP4rev1
ⓘ
linked to:
IMAP
|
| area |
Internet
ⓘ
linked to:
the internet
|
| category | Standards Track ⓘ |
| definesAuthenticationModel | username and password ⓘ |
| definesCommand |
APPEND
ⓘ
AUTHENTICATE ⓘ COPY ⓘ CREATE ⓘ DELETE ⓘ EXAMINE ⓘ FETCH ⓘ LOGIN ⓘ LOGOUT ⓘ NOOP ⓘ RENAME ⓘ SEARCH ⓘ SELECT ⓘ STORE ⓘ SUBSCRIBE ⓘ UID ⓘ UNSUBSCRIBE ⓘ |
| definesDataModel | mailboxes containing messages ⓘ |
| definesMailboxNameSyntax | hierarchical mailbox names ⓘ |
| definesMessageAttribute |
body structure
ⓘ
envelope ⓘ flags ⓘ |
| definesOperation |
concurrent access to mailboxes
ⓘ
email message management ⓘ email message retrieval ⓘ mailbox management ⓘ message fetching by parts ⓘ message flag manipulation ⓘ server-side search ⓘ |
| definesPort |
143
ⓘ
993 ⓘ |
| definesProtocol |
Internet Message Access Protocol version 4rev1
ⓘ
linked to:
IMAP
|
| definesResponse |
BAD
ⓘ
BYE ⓘ NO ⓘ OK ⓘ PREAUTH ⓘ |
| documentFormat | text ⓘ |
| intendedUse | email access on a mail server ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 1730
ⓘ
RFC 2060 ⓘ |
| port143Usage | IMAP over TCP ⓘ |
| port993Usage | IMAP over TLS/SSL ⓘ |
| protocolFamily | IMAP ⓘ |
| protocolType | application-layer protocol ⓘ |
| publicationMonth | March ⓘ |
| publicationYear | 2003 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| relatedProtocol |
POP3
ⓘ
SMTP ⓘ |
| rfcNumber | 3501 ⓘ |
| securityConsiderationsSection | yes ⓘ |
| shortTitle |
IMAP4rev1
ⓘ
linked to:
IMAP
|
| standardsStatus | Internet Standard ⓘ |
| statusAtPublication | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| supportsExtensionMechanism | IMAP capability mechanism ⓘ |
| title |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
ⓘ
linked to:
RFC 3501
|
| transportProtocol |
TCP
ⓘ
linked to:
Transmission Control Protocol
|
| usesCharacterSet | US-ASCII ⓘ |
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 3501 Description of subject: RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
Referenced by (15)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 3501
linked to: RFC 3501
linked to: RFC 3501
linked to: RFC 3501
linked to: RFC 3501