RFC 7674
E837882
RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7674 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9932170 — 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 7674 Context triple: [DANE, definedIn, RFC 7674]
-
A.
RFC 7344
RFC 7344 is an Internet Engineering Task Force (IETF) standard that specifies automated mechanisms for maintaining DNSSEC delegation trust using CDS and related records.
-
B.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
C.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
D.
RFC 7671
RFC 7671 is an Internet Engineering Task Force (IETF) standard that specifies operational and security guidelines for using DNS-Based Authentication of Named Entities (DANE) with TLS.
-
E.
RFC 7484
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
- 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 7674 Target entity description: RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
-
A.
RFC 7344
RFC 7344 is an Internet Engineering Task Force (IETF) standard that specifies automated mechanisms for maintaining DNSSEC delegation trust using CDS and related records.
-
B.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
C.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
D.
RFC 7671
RFC 7671 is an Internet Engineering Task Force (IETF) standard that specifies operational and security guidelines for using DNS-Based Authentication of Named Entities (DANE) with TLS.
-
E.
RFC 7484
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf |
Internet Standards Document
ⓘ
Request for Comments ⓘ |
| appliesTo |
SMTP clients
ⓘ
SMTP servers ⓘ email service providers ⓘ |
| area |
Applications
ⓘ
Security ⓘ |
| category | Standards Track ⓘ |
| defines |
operational and deployment considerations for DANE with SMTP
ⓘ
security considerations for DANE-protected SMTP ⓘ use of DANE TLSA records with SMTP ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn |
opportunistic TLS for SMTP
ⓘ
securing email transport with TLS ⓘ server authentication using DNSSEC-validated TLSA records ⓘ |
| goal |
enable secure email transport without traditional PKI
ⓘ
improve authenticity of SMTP servers ⓘ prevent SMTP TLS downgrade attacks ⓘ |
| language | English ⓘ |
| obsoletes | none ⓘ |
| protocol |
SMTP
ⓘ
TLS ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
DANE
ⓘ
RFC 6698 ⓘ SMTP security ⓘ email transport security ⓘ |
| requires | DNSSEC validation of TLSA records ⓘ |
| specifies |
how SMTP clients use DANE to authenticate SMTP servers
ⓘ
use of TLSA records in DNS for SMTP over TLS ⓘ |
| standardizes |
client behavior when TLSA records are present
ⓘ
handling of certificate usage values in TLSA records for SMTP ⓘ interaction between SMTP STARTTLS and DANE ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Using DNS-Based Authentication of Named Entities (DANE) TLSA Records with SMTP ⓘ |
| updates | RFC 6698 ⓘ |
| usesTechnology |
DANE
ⓘ
DNS-Based Authentication of Named Entities ⓘ
linked to:
DNS-based Authentication of Named Entities
DNSSEC ⓘ TLS ⓘ |
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 7674 Description of subject: RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.