RFC 2311
E853540
RFC 2311 is an early Internet standard that originally defined S/MIME (Secure/Multipurpose Internet Mail Extensions) for providing cryptographic security services for electronic messaging.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2311 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10243964 — 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 2311 Context triple: [RFC 5751, obsoletes, RFC 2311]
-
A.
RFC 2911
RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
-
B.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
C.
RFC 1031
RFC 1031 is an early Internet standards document that specified guidelines for the implementation and operation of certain TCP/IP networking protocols before being superseded by later updates.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
- 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 2311 Target entity description: RFC 2311 is an early Internet standard that originally defined S/MIME (Secure/Multipurpose Internet Mail Extensions) for providing cryptographic security services for electronic messaging.
-
A.
RFC 2911
RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
-
B.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
C.
RFC 1031
RFC 1031 is an early Internet standards document that specified guidelines for the implementation and operation of certain TCP/IP networking protocols before being superseded by later updates.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
Internet email
ⓘ
MIME-compliant messaging systems ⓘ |
| area |
email security
ⓘ
public key cryptography ⓘ |
| category | Standards Track ⓘ |
| defines |
S/MIME
NERFINISHED
ⓘ
S/MIME Version 2 NERFINISHED ⓘ Secure/Multipurpose Internet Mail Extensions NERFINISHED ⓘ |
| obsoletedBy | RFC 2633 NERFINISHED ⓘ |
| organizationInvolved |
IETF S/MIME Working Group
NERFINISHED
ⓘ
Internet Engineering Task Force NERFINISHED ⓘ |
| provides | cryptographic security services for electronic messaging ⓘ |
| purpose | to define a standard for secure electronic mail using S/MIME ⓘ |
| relatedTo |
MIME
NERFINISHED
ⓘ
RFC 2312 NERFINISHED ⓘ S/MIME Version 3 NERFINISHED ⓘ |
| specifies |
digital signatures for email
ⓘ
key management for S/MIME ⓘ message encryption for email ⓘ message integrity for email ⓘ non-repudiation mechanisms for email ⓘ |
| standardizes |
format of S/MIME messages
ⓘ
use of certificates in S/MIME ⓘ use of cryptographic algorithms in S/MIME ⓘ |
| title | S/MIME Version 2 Message Specification NERFINISHED ⓘ |
| uses |
MIME
NERFINISHED
ⓘ
Public Key Cryptography Standards NERFINISHED ⓘ X.509 certificates NERFINISHED ⓘ |
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 2311 Description of subject: RFC 2311 is an early Internet standard that originally defined S/MIME (Secure/Multipurpose Internet Mail Extensions) for providing cryptographic security services for electronic messaging.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.