RFC 3445
E707273
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3445 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T8009161 — 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 3445 Context triple: [RFC 4033, obsoletes, RFC 3445]
-
A.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 4555
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
D.
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.
-
E.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
- 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 3445 Target entity description: RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
A.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 4555
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
D.
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.
-
E.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
- F. None of above. chosen
Statements (24)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
DNS resource records
ⓘ
Domain Name System ⓘ |
| area |
DNS security
ⓘ
Domain Name System ⓘ |
| category | Standards Track ⓘ |
| defines | limitations on the use of the DNS KEY resource record ⓘ |
| documentType | Technical specification ⓘ |
| focusesOn | security considerations for the DNS KEY resource record ⓘ |
| governingBody | Internet Engineering Task Force ⓘ |
| hasNumber | 3445 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4033 ⓘ |
| protocolFamily |
Internet Protocol Suite
ⓘ
linked to:
TCP/IP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
DNS Security Extensions
ⓘ
linked to:
Domain Name System Security Extensions
DNSSEC ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Obsoleted ⓘ |
| title | Limiting the Scope of the KEY Resource Record (RR) ⓘ |
| updates | DNS security specifications prior to RFC 4033 ⓘ |
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 3445 Description of subject: RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.