RFC 3655
E709134
RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T8009162 — 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.
Target entity: RFC 3655 Context triple: [RFC 4033, obsoletes, RFC 3655]
-
A.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
B.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
C.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
D.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 3655 Target entity description: RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
-
A.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
B.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
C.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
D.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- F. None of above. chosen
Statements (29)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| area | Internet Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| context | Internet standards ⓘ |
| defines | redefinition of the DNS AD (Authenticated Data) bit semantics ⓘ |
| documentType | Standards-track RFC ⓘ |
| focusesOn |
DNS resolver behavior
ⓘ
DNS security ⓘ |
| format | Text ⓘ |
| hasNumber | 3655 ⓘ |
| hasSuccessor | RFC 4033 NERFINISHED ⓘ |
| hasTitle | Redefinition of DNS Authenticated Data (AD) bit NERFINISHED ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4033 NERFINISHED ⓘ |
| partOfSeries | RFC series NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relatedTo |
DNSSEC protocol design
ⓘ
DNSSEC validation semantics ⓘ |
| relatedToProtocol |
DNS
NERFINISHED
ⓘ
Domain Name System NERFINISHED ⓘ |
| relatedToStandard |
DNS Security Extensions
NERFINISHED
ⓘ
DNSSEC NERFINISHED ⓘ |
| standardizationBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Obsoleted ⓘ |
| stream | IETF Stream NERFINISHED ⓘ |
| updatesSpecificationOf | DNS header AD (Authenticated Data) bit ⓘ |
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.
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.
Subject: RFC 3655 Description of subject: RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.