RFC 6838
E856202
RFC 6838 is an IETF standard that defines the structure, registration procedures, and management rules for media (MIME) type specifications on the internet.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6838 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T10329100 — 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 6838 Context triple: [IANA media type registry, documentedIn, RFC 6838]
-
A.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
-
B.
RFC 7858
RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
-
C.
RFC 7868
RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
-
D.
RFC 7218
RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
-
E.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
- 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 6838 Target entity description: RFC 6838 is an IETF standard that defines the structure, registration procedures, and management rules for media (MIME) type specifications on the internet.
-
A.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
-
B.
RFC 7858
RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
-
C.
RFC 7868
RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
-
D.
RFC 7218
RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
-
E.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard ⓘ MIME specification ⓘ |
| area | Applications ⓘ |
| category | Best Current Practice ⓘ |
| concerns |
Internet media types
ⓘ
linked to:
IANA media type registry
MIME media types ⓘ
linked to:
IANA media type registry
content-type header field values ⓘ |
| defines |
media type management rules
ⓘ
media type registration procedures ⓘ media type structure ⓘ procedures for media type trees ⓘ procedures for personal or vanity media types ⓘ procedures for registering media types ⓘ procedures for retiring media type registrations ⓘ procedures for unregistered media types ⓘ procedures for updating media type registrations ⓘ procedures for vendor media types ⓘ requirements for media type specifications ⓘ |
| definesTerm |
media type tree
ⓘ
personal tree ⓘ standards tree ⓘ structured syntax suffix ⓘ vendor tree ⓘ |
| governs |
deprecation of media type registrations
ⓘ
modification of existing media type registrations ⓘ registration of media type parameters ⓘ registration of new top-level media type trees ⓘ registration of subtypes under existing media type trees ⓘ |
| obsoletes |
RFC 4288
ⓘ
RFC 4289 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| registry | IANA media type registry ⓘ |
| specifies |
IANA media type registry procedures
ⓘ
change control for media type registrations ⓘ naming conventions for media types ⓘ procedures for structured syntax suffixes ⓘ requirements for IANA registration templates ⓘ review processes for media type registrations ⓘ security considerations for media type registrations ⓘ use of media type suffixes ⓘ |
| status | Best Current Practice ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Media Type Specifications and Registration Procedures
ⓘ
linked to:
IANA media type registry
|
| updates |
RFC 2045
ⓘ
RFC 2046 ⓘ RFC 4288 ⓘ RFC 4289 ⓘ |
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 6838 Description of subject: RFC 6838 is an IETF standard that defines the structure, registration procedures, and management rules for media (MIME) type specifications on the internet.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.