RFC 4288
E856203
RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4288 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10329102 — 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 4288 Context triple: [IANA media type registry, documentedIn, RFC 4288]
-
A.
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.
-
B.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
C.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
-
D.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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 4288 Target entity description: RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
-
A.
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.
-
B.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
C.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
-
D.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| appliesTo |
modification of existing MIME media type registrations
ⓘ
registration of media type suffixes ⓘ registration of new MIME media types ⓘ |
| area | Applications Area NERFINISHED ⓘ |
| BCPNumber | 13 ⓘ |
| category | Best Current Practice ⓘ |
| concerns |
Internet media types
ⓘ
MIME media types ⓘ |
| defines |
IANA considerations for media type registrations
ⓘ
guidelines for media type specifications ⓘ procedures for media type tree registration ⓘ procedures for registering media types with IANA ⓘ procedures for updating existing media type registrations ⓘ requirements for interoperability considerations in media type registrations ⓘ requirements for media type registration templates ⓘ requirements for publication of media type specifications ⓘ requirements for security considerations in media type registrations ⓘ requirements for standards-tree media types ⓘ requirements for vendor and personal media type trees ⓘ review and approval process for media type registrations ⓘ |
| format | Text ⓘ |
| governs |
registration of personal or vanity media types
ⓘ
registration of vendor-specific media types ⓘ structure of media type names ⓘ use of media type trees ⓘ |
| intendedAudience |
IANA media type reviewers
NERFINISHED
ⓘ
media type authors ⓘ protocol designers ⓘ |
| language | English ⓘ |
| managedBy |
IANA
NERFINISHED
ⓘ
Internet Assigned Numbers Authority NERFINISHED ⓘ |
| obsoletedBy | RFC 6838 NERFINISHED ⓘ |
| obsoletes |
RFC 1590
NERFINISHED
ⓘ
RFC 2048 NERFINISHED ⓘ |
| partOf | MIME standards family NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2045
NERFINISHED
ⓘ
RFC 2046 NERFINISHED ⓘ RFC 6838 NERFINISHED ⓘ |
| RFCNumber | 4288 ⓘ |
| status | Obsoleted ⓘ |
| stream | IETF Stream NERFINISHED ⓘ |
| title | Media Type Specifications and Registration Procedures NERFINISHED ⓘ |
| updates | MIME registration procedures ⓘ |
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 4288 Description of subject: RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.