RFC 1869
E280627
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1869 canonical | 6 |
How this entity was disambiguated
This entity first appeared as the object of triple T1866840 — 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 1869 Context triple: [RFC 5321, obsoletes, RFC 1869]
-
A.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
B.
RFC 1909
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
-
C.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
D.
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.
-
E.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
- 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 1869 Target entity description: RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
-
A.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
B.
RFC 1909
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
-
C.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
D.
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.
-
E.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
- F. None of above. chosen
Statements (39)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
SMTP clients
ⓘ
SMTP servers ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
ESMTP framework
ⓘ
Extended Simple Mail Transfer Protocol ⓘ backward compatibility with SMTP ⓘ rules for SMTP clients using extensions ⓘ rules for SMTP servers advertising extensions ⓘ semantics for SMTP extension keywords ⓘ syntax for SMTP extension keywords ⓘ |
| ensuresCompatibilityWith | existing SMTP implementations ⓘ |
| focusesOn | mail transfer over TCP/IP ⓘ |
| goal |
to allow optional SMTP features without breaking existing systems
ⓘ
to provide a general mechanism for extending SMTP ⓘ |
| introduces |
EHLO command
ⓘ
SMTP extension negotiation mechanism ⓘ keyword-based SMTP extensions ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 2821
ⓘ
RFC 5321 ⓘ |
| protocol | SMTP ⓘ |
| protocolFamily | Internet mail ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedIn |
RFCs
ⓘ
surface form:
RFC series
|
| relatedTo |
RFC 1651
ⓘ
RFC 1652 ⓘ RFC 1870 ⓘ RFC 2554 ⓘ |
| specifies | framework for SMTP service extensions ⓘ |
| standardizes |
EHLO command semantics
ⓘ
mechanism for advertising SMTP extensions ⓘ |
| status | Obsoleted ⓘ |
| title |
SMTP Service Extension for 8bit-MIMEtransport
ⓘ
surface form:
SMTP Service Extensions
|
| updates |
RFC 821
ⓘ
SMTP ⓘ
surface form:
Simple Mail Transfer Protocol
|
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 1869 Description of subject: RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.