RFC 1847
E853541
RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1847 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10243965 — 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 1847 Context triple: [RFC 5751, obsoletes, RFC 1847]
-
A.
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.
-
B.
RFC 1870
RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
-
C.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
- 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 1847 Target entity description: RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
-
A.
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.
-
B.
RFC 1870
RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
-
C.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
MIME security specification ⓘ Request for Comments ⓘ |
| appliesTo |
Internet mail
NERFINISHED
ⓘ
MIME email ⓘ |
| area |
Applications
ⓘ
Security ⓘ |
| category | Standards Track ⓘ |
| context | Internet mail security ⓘ |
| defines |
general framework for security multiparts in MIME
ⓘ
multipart/encrypted ⓘ multipart/signed ⓘ |
| definesConcept |
encapsulation of digital signatures in MIME
ⓘ
encapsulation of encrypted data in MIME ⓘ security multiparts ⓘ |
| definesHeaderUsageFor | MIME security multiparts ⓘ |
| definesProcessingRulesFor |
multipart/encrypted
ⓘ
multipart/signed ⓘ |
| definesRelationshipWith | underlying cryptographic mechanisms ⓘ |
| documentType | technical specification ⓘ |
| focusesOn |
interoperability of secure email
ⓘ
message confidentiality ⓘ message integrity ⓘ |
| intendedAudience |
email system implementers
ⓘ
security protocol designers ⓘ |
| language | English ⓘ |
| laysGroundworkFor |
OpenPGP/MIME
NERFINISHED
ⓘ
S/MIME NERFINISHED ⓘ later secure messaging specifications ⓘ |
| objective |
enable multiple security mechanisms to be used with MIME
ⓘ
provide a general framework for security services in MIME ⓘ support signed and encrypted Internet mail ⓘ |
| partOf | RFC series NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| RFCNumber | 1847 ⓘ |
| separates | MIME security encapsulation from cryptographic algorithms ⓘ |
| standardizes |
use of multipart/encrypted for encryption
ⓘ
use of multipart/signed for digital signatures ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted NERFINISHED ⓘ |
| updatesSpecificationOf | MIME NERFINISHED ⓘ |
| uses | MIME multipart structure ⓘ |
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 1847 Description of subject: RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.