RFC 2048
E831060
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2048 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T9931673 — 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 2048 Context triple: [MIME, standardizedIn, RFC 2048]
-
A.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
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 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- 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 2048 Target entity description: RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
A.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
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 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| author |
Keith Moore
ⓘ
Ned Freed ⓘ |
| BCPNumber | BCP 13 ⓘ |
| category | Best Current Practice ⓘ |
| defines |
procedures for registering MIME application subtypes
ⓘ
procedures for registering MIME audio subtypes ⓘ procedures for registering MIME character sets ⓘ procedures for registering MIME content-encoding values ⓘ procedures for registering MIME content-transfer-encodings ⓘ procedures for registering MIME external-body access types ⓘ procedures for registering MIME header fields ⓘ procedures for registering MIME image subtypes ⓘ procedures for registering MIME media types ⓘ procedures for registering MIME message subtypes ⓘ procedures for registering MIME model subtypes ⓘ procedures for registering MIME multipart subtypes ⓘ procedures for registering MIME text subtypes ⓘ procedures for registering MIME video subtypes ⓘ |
| hasRFCNumber | 2048 ⓘ |
| isReplacedBy |
RFC 4288
ⓘ
RFC 4289 ⓘ
linked to:
RFC 4288
|
| language | English ⓘ |
| obsoletes | RFC 1590 ⓘ |
| partNumber | Part Four ⓘ |
| partOf | MIME specification series ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedIn | November 1996 ⓘ |
| relatedTo |
MIME
ⓘ
Multipurpose Internet Mail Extensions ⓘ |
| specifies |
IANA registration procedures for MIME access types
ⓘ
IANA registration procedures for MIME parameters ⓘ IANA registration procedures for content-disposition values ⓘ IANA registration procedures for message header fields ⓘ expert review for certain MIME registrations ⓘ requirements for MIME type registration templates ⓘ review process for MIME registrations ⓘ |
| status | Best Current Practice ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
ⓘ
linked to:
MIME
|
| updates |
RFC 1521
ⓘ
RFC 1522 ⓘ |
| year | 1996 ⓘ |
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 2048 Description of subject: RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.