RFC 2633
E853539
RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2633 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10243963 — 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 2633 Context triple: [RFC 5751, obsoletes, RFC 2633]
-
A.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
-
E.
RFC 2433
RFC 2433 is an older Internet Engineering Task Force (IETF) specification that was later superseded by RFC 4250 as part of updates to SSH-related protocol definitions.
- 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 2633 Target entity description: RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
-
A.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
-
E.
RFC 2433
RFC 2433 is an older Internet Engineering Task Force (IETF) specification that was later superseded by RFC 4250 as part of updates to SSH-related protocol definitions.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| appliesTo |
Internet email
ⓘ
MIME entities ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| concerns |
message authentication
ⓘ
message confidentiality ⓘ message integrity ⓘ non-repudiation of origin ⓘ secure electronic mail ⓘ |
| defines |
S/MIME certificate handling
ⓘ
S/MIME content types ⓘ S/MIME key management requirements ⓘ S/MIME message encapsulation ⓘ S/MIME security services NERFINISHED ⓘ application/pkcs7-mime media type ⓘ application/pkcs7-signature media type ⓘ format for secure MIME messages ⓘ message/sipfrag S/MIME usage ⓘ use of CMS for S/MIME ⓘ |
| documentType | Standards-track RFC ⓘ |
| focusesOn | end-to-end email security ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 5751 NERFINISHED ⓘ |
| obsoletes | RFC 2311 NERFINISHED ⓘ |
| protocol | S/MIME NERFINISHED ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2311
NERFINISHED
ⓘ
RFC 2632 NERFINISHED ⓘ RFC 2634 NERFINISHED ⓘ |
| securityMechanism |
certificate-based authentication
ⓘ
digital signatures ⓘ encryption ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| specifies |
S/MIME Version 3
NERFINISHED
ⓘ
secure MIME message specification ⓘ |
| standardizes | use of public key cryptography in MIME ⓘ |
| status | Obsoleted ⓘ |
| stdStatus | Proposed Standard ⓘ |
| supersededBy | S/MIME Version 3.1 NERFINISHED ⓘ |
| title | S/MIME Version 3 Message Specification NERFINISHED ⓘ |
| updates | MIME security mechanisms ⓘ |
| uses |
Cryptographic Message Syntax
NERFINISHED
ⓘ
X.509 public key 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 2633 Description of subject: RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.