RFC 8551
E201504
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8551 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1711926 — 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 8551 Context triple: [S/MIME, definedIn, RFC 8551]
-
A.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
-
B.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- 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 8551 Target entity description: RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
A.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
-
B.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
Internet email
ⓘ
MIME entities ⓘ |
| area | security ⓘ |
| basedOn |
CMS (Cryptographic Message Syntax)
ⓘ
linked to:
PKCS #7
|
| category | Standards Track ⓘ |
| concerns |
end-to-end email security
ⓘ
message authentication ⓘ message confidentiality ⓘ message integrity ⓘ non-repudiation of origin ⓘ |
| defines |
S/MIME capabilities
ⓘ
S/MIME certificate handling rules ⓘ S/MIME content types ⓘ S/MIME header fields ⓘ S/MIME key management requirements ⓘ S/MIME media types ⓘ
linked to:
S/MIME
S/MIME message format ⓘ
linked to:
S/MIME
S/MIME security services ⓘ
linked to:
S/MIME
processing rules for S/MIME messages ⓘ requirements for S/MIME-compliant implementations ⓘ security considerations for S/MIME ⓘ use of CMS for S/MIME ⓘ |
| field |
computer security
ⓘ
email security ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 3851
ⓘ
RFC 5751 ⓘ |
| organization | Internet Engineering Task Force ⓘ |
| protocolSpecified | S/MIME ⓘ |
| relatedTo |
RFC 8550
ⓘ
RFC 8552 ⓘ RFC 8553 ⓘ RFC 8554 ⓘ S/MIME Version 3.2 ⓘ
linked to:
S/MIME
|
| specifiesVersion |
S/MIME Version 4.0
ⓘ
linked to:
S/MIME
|
| standardizes |
digitally signed email
ⓘ
encrypted email ⓘ secure email ⓘ |
| status | Internet Standard ⓘ |
| title |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification
ⓘ
linked to:
S/MIME
|
| updatesSpecificationOf | MIME ⓘ |
| useCase |
authenticating email senders
ⓘ
protecting email contents ⓘ |
| uses |
Cryptographic Message Syntax
ⓘ
linked to:
PKCS #7
X.509 public key certificates ⓘ |
| workingGroup | Lamps Working Group ⓘ |
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 8551 Description of subject: RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.