RFC 2197
E774044
RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2197 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8852466 — 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 2197 Context triple: [RFC 2821, obsoletes, RFC 2197]
-
A.
RFC 2195
RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
-
B.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
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 2197 Target entity description: RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
-
A.
RFC 2195
RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
-
B.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
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 (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Email ⓘ |
| category | Standards Track ⓘ |
| defines |
ONDEMAND SMTP extension keyword
ⓘ
SMTP ONDEMAND extension ⓘ
linked to:
SMTP
|
| definesExtensionFor |
ESMTP
ⓘ
linked to:
Extended Simple Mail Transfer Protocol
|
| documentType | Standards Track RFC ⓘ |
| format | Text ⓘ |
| intendedUse | On-demand mail relay ⓘ |
| keyword |
ESMTP
ⓘ
linked to:
Extended Simple Mail Transfer Protocol
ONDEMAND ⓘ SMTP ⓘ mail relay ⓘ |
| language | English ⓘ |
| networkLayer | Application layer ⓘ |
| obsoletedBy |
RFC 2821
ⓘ
Simple Mail Transfer Protocol (SMTP) specification in RFC 2821 ⓘ
linked to:
RFC 2821
|
| protocol |
Simple Mail Transfer Protocol
ⓘ
linked to:
SMTP
|
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
Extended SMTP
ⓘ
RFC 2821 ⓘ RFC 821 ⓘ |
| RFCNumber | 2197 ⓘ |
| standardizes | ONDEMAND ESMTP service extension ⓘ |
| status | Obsolete ⓘ |
| statusInRFCIndex | Obsoleted RFC ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | SMTP Service Extension for Command Pipelining and On-Demand Mail Relay ⓘ |
| updatesProtocol | SMTP ⓘ |
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 2197 Description of subject: RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.