RFC 2535
E707271
RFC 2535 is an earlier DNS Security Extensions (DNSSEC) specification that was later superseded by updated standards such as RFC 4033.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2535 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T8009158 — 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 2535 Context triple: [RFC 4033, obsoletes, RFC 2535]
-
A.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
B.
RFC 4515
RFC 4515 is an Internet standard that specifies the string representation of LDAP search filters used in directory service queries.
-
C.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
D.
RFC 1055
RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
-
E.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
- 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 2535 Target entity description: RFC 2535 is an earlier DNS Security Extensions (DNSSEC) specification that was later superseded by updated standards such as RFC 4033.
-
A.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
B.
RFC 4515
RFC 4515 is an Internet standard that specifies the string representation of LDAP search filters used in directory service queries.
-
C.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
D.
RFC 1055
RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
-
E.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard specification
ⓘ
Request for Comments ⓘ |
| area | Internet Area ⓘ |
| category | Standards Track ⓘ |
| defines |
DNS KEY resource record
ⓘ
DNS NXT resource record ⓘ DNS SIG resource record ⓘ DNS security policy framework ⓘ DNS zone signing procedures ⓘ DNSSEC authentication model ⓘ |
| definesProtocol |
DNS Security Extensions
ⓘ
linked to:
DNSSEC
|
| doesNotProvide | confidentiality ⓘ |
| focusesOn |
digital signatures for DNS resource records
ⓘ
public key cryptography for DNS ⓘ |
| format | text ⓘ |
| intendedTo |
protect DNS against cache poisoning
ⓘ
protect DNS against spoofing ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 2536
ⓘ
RFC 2537 ⓘ RFC 2538 ⓘ RFC 3007 ⓘ RFC 3090 ⓘ RFC 3445 ⓘ RFC 3655 ⓘ RFC 3658 ⓘ RFC 3755 ⓘ RFC 3757 ⓘ RFC 4033 ⓘ RFC 4034 ⓘ RFC 4035 ⓘ |
| partOf | DNSSEC specification family ⓘ |
| protocolDomain |
DNS
ⓘ
linked to:
Domain Name System
Domain Name System ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relation | earlier DNSSEC specification ⓘ |
| RFCNumber | 2535 ⓘ |
| securityProperty |
data integrity for DNS responses
ⓘ
data origin authentication for DNS ⓘ |
| shortName | DNSSEC ⓘ |
| standardizes | mechanisms for securing DNS information ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| supersededBy | updated DNSSEC standards such as RFC 4033 ⓘ |
| title | Domain Name System Security Extensions ⓘ |
| updates |
RFC 1034
ⓘ
RFC 1035 ⓘ |
| workingGroup |
DNSIND
ⓘ
Domain Name System Working Group ⓘ
linked to:
IETF DNSOP
|
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 2535 Description of subject: RFC 2535 is an earlier DNS Security Extensions (DNSSEC) specification that was later superseded by updated standards such as RFC 4033.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.