RFC 3090
E712946
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3090 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8113422 — 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 3090 Context triple: [RFC 4035, obsoletes, RFC 3090]
-
A.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
B.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
RFC 3008
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
-
E.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
- 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 3090 Target entity description: RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
A.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
B.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
C.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
D.
RFC 3008
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
-
E.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
- F. None of above. chosen
Statements (24)
| Predicate | Object |
|---|---|
| instanceOf |
DNS-related specification
ⓘ
RFC ⓘ |
| appliesTo |
DNS authoritative servers
ⓘ
DNS resolvers ⓘ |
| area | Internet NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines | clarifications for DNSSEC zone status ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn | zone status in DNSSEC ⓘ |
| hasSuccessor | RFC 4035 NERFINISHED ⓘ |
| isPartOf | DNSSEC standards ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4035 NERFINISHED ⓘ |
| partOfSeries | Request for Comments NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
DNS Security Extensions
NERFINISHED
ⓘ
Domain Name System NERFINISHED ⓘ |
| standardizes | behavior for DNSSEC-aware name servers ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | DNS Security Extension Clarification on Zone Status NERFINISHED ⓘ |
| updates | DNSSEC specifications ⓘ |
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 3090 Description of subject: RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.