RFC 3851
E740114
RFC 3851 is the original specification for S/MIME Version 3.1, defining how to provide cryptographic security services for MIME data such as email.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3851 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8513082 — 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 3851 Context triple: [RFC 8551, obsoletes, RFC 3851]
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
-
E.
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.
- 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 3851 Target entity description: RFC 3851 is the original specification for S/MIME Version 3.1, defining how to provide cryptographic security services for MIME data such as email.
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
-
E.
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.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments
ⓘ
technical standard ⓘ |
| addresses |
interoperability of S/MIME implementations
ⓘ
security services for MIME ⓘ |
| appliesTo |
Internet email
ⓘ
MIME ⓘ
linked to:
Multipurpose Internet Mail Extensions
|
| area | Security ⓘ |
| basedOn | PKCS #7 ⓘ |
| category | Standards Track ⓘ |
| defines |
S/MIME capabilities attribute
ⓘ
linked to:
S/MIME
S/MIME certificate attributes ⓘ application/pkcs7-mime MIME type ⓘ application/pkcs7-signature MIME type ⓘ processing rules for encrypted messages ⓘ processing rules for signed messages ⓘ processing rules for signed-and-encrypted messages ⓘ requirements for certificate chains in S/MIME ⓘ requirements for message canonicalization in S/MIME ⓘ smime-type parameter ⓘ |
| definesVersionOf |
S/MIME Version 3.1
ⓘ
linked to:
S/MIME
|
| focusesOn | end-to-end security for email ⓘ |
| isObsoletedBy | RFC 5751 ⓘ |
| language | English ⓘ |
| obsoletedBy |
S/MIME Version 3.2 specification
ⓘ
linked to:
S/MIME
|
| obsoletes |
RFC 2311
ⓘ
RFC 2633 ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
S/MIME
ⓘ
email security ⓘ public key cryptography ⓘ |
| RFCNumber | 3851 ⓘ |
| securityServices |
authentication
ⓘ
confidentiality ⓘ data origin authentication ⓘ integrity ⓘ non-repudiation ⓘ |
| specifies |
S/MIME message format
ⓘ
linked to:
S/MIME
certificate handling for S/MIME ⓘ cryptographic security services for MIME ⓘ digital signature for MIME entities ⓘ encryption for MIME entities ⓘ |
| standardizes |
MIME content types for S/MIME
ⓘ
use of X.509 certificates in S/MIME ⓘ |
| status | Obsoleted ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
ⓘ
linked to:
S/MIME
|
| updates | RFC 1847 ⓘ |
| uses |
CMS (Cryptographic Message Syntax)
ⓘ
linked to:
PKCS #7
|
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 3851 Description of subject: RFC 3851 is the original specification for S/MIME Version 3.1, defining how to provide cryptographic security services for MIME data such as email.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.