RFC 2049
E832818
RFC 2049 is an Internet standards document that defines the conformance, operational considerations, and security issues for the MIME (Multipurpose Internet Mail Extensions) specification used in Internet email.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2049 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9931674 — 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 2049 Context triple: [MIME, standardizedIn, RFC 2049]
-
A.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
D.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
-
E.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
- 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 2049 Target entity description: RFC 2049 is an Internet standards document that defines the conformance, operational considerations, and security issues for the MIME (Multipurpose Internet Mail Extensions) specification used in Internet email.
-
A.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
D.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
-
E.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
MIME specification document ⓘ Request for Comments ⓘ |
| acronym | RFC 2049 NERFINISHED ⓘ |
| addresses |
backward compatibility with non-MIME email systems
ⓘ
interoperability between MIME implementations ⓘ security risks of active content in email ⓘ security risks of executable attachments ⓘ |
| appliesTo |
Internet email
ⓘ
SMTP-based email systems ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
MIME conformance criteria
ⓘ
MIME examples ⓘ MIME operational considerations ⓘ MIME security considerations ⓘ requirements for MIME-capable mail transfer agents ⓘ requirements for MIME-capable mail user agents ⓘ |
| focusesOn |
conformance of MIME implementations
ⓘ
operational issues of MIME deployment ⓘ security issues related to MIME ⓘ |
| includes |
examples of MIME headers
ⓘ
examples of MIME message bodies ⓘ |
| language | English ⓘ |
| medium | text ⓘ |
| obsoletes |
RFC 1521
NERFINISHED
ⓘ
RFC 1522 NERFINISHED ⓘ |
| partOf |
MIME
NERFINISHED
ⓘ
MIME Version 1.0 NERFINISHED ⓘ MIME specification ⓘ |
| protocolFamily | Internet protocol suite NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2045
NERFINISHED
ⓘ
RFC 2046 NERFINISHED ⓘ RFC 2047 NERFINISHED ⓘ RFC 2822 NERFINISHED ⓘ RFC 822 NERFINISHED ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| standardFor | Multipurpose Internet Mail Extensions NERFINISHED ⓘ |
| standardizes | use of MIME in Internet email ⓘ |
| status | Proposed Standard ⓘ |
| title | Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples NERFINISHED ⓘ |
| updates |
RFC 1521
NERFINISHED
ⓘ
RFC 1522 ⓘ |
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 2049 Description of subject: RFC 2049 is an Internet standards document that defines the conformance, operational considerations, and security issues for the MIME (Multipurpose Internet Mail Extensions) specification used in Internet email.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.