RFC 1652
E230348
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1652 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777482 — 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 1652 Context triple: [RFC 1901, obsoletes, RFC 1652]
-
A.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
B.
RFC 1592
RFC 1592 is an early Internet standards document that specified procedures and mechanisms related to network management and operations before being superseded by later RFCs.
-
C.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
-
D.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- 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 1652 Target entity description: RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
A.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
B.
RFC 1592
RFC 1592 is an early Internet standards document that specified procedures and mechanisms related to network management and operations before being superseded by later RFCs.
-
C.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
-
D.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| abbreviation |
SMTP Service Extension for 8bit-MIMEtransport
ⓘ
surface form:
8BITMIME
|
| addressesProblem | limitations of 7-bit SMTP for international character sets ⓘ |
| appliesTo |
Internet email
ⓘ
SMTP message transport ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| constrains | use of 8BITMIME to message body only ⓘ |
| defines |
MIME
ⓘ
surface form:
8BITMIME
SMTP Service Extension for 8bit-MIMEtransport ⓘ
surface form:
SMTP Service Extension for 8-bit MIME transport
backward compatibility rules with 7-bit SMTP ⓘ error handling when 8BITMIME is not supported by the server ⓘ use of 8-bit data only when both client and server advertise 8BITMIME ⓘ |
| enables |
transfer of 8-bit MIME data via SMTP
ⓘ
use of 8-bit character sets in email bodies ⓘ |
| hasKeyword |
8BITMIME
ⓘ
MIME ⓘ SMTP ⓘ email ⓘ internationalization ⓘ |
| intendedFor |
SMTP client developers
ⓘ
SMTP server developers ⓘ email system implementers ⓘ |
| language | English ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| partOf |
IETF Internet standards process
ⓘ
surface form:
Internet Standards Process
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| relatedTo |
SMTP
ⓘ
surface form:
Extended SMTP
MIME ⓘ RFC 1521 ⓘ RFC 1522 ⓘ |
| relatesToProtocol |
SMTP
ⓘ
surface form:
Simple Mail Transfer Protocol
|
| specifies |
8BITMIME SMTP service extension keyword
ⓘ
EHLO advertisement of 8BITMIME capability ⓘ requirements for SMTP clients using 8BITMIME ⓘ requirements for SMTP servers supporting 8BITMIME ⓘ semantics of MAIL FROM and RCPT TO with 8BITMIME ⓘ |
| standardizes | 8-bit character data transfer in SMTP ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | SMTP Service Extension for 8bit-MIMEtransport ⓘ |
| updates | RFC 821 ⓘ |
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 1652 Description of subject: RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.