RFC 8314
E184119
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8314 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631478 — 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 8314 Context triple: [RFC 1939, obsoletedBy, RFC 8314]
-
A.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
B.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
C.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
D.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
-
E.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
- 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 8314 Target entity description: RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
-
A.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
B.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
C.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
D.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
-
E.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| addressesThreat |
eavesdropping on email traffic
ⓘ
man-in-the-middle attacks on email protocols ⓘ |
| aimsTo | improve security of email communications ⓘ |
| appliesTo |
email clients
ⓘ
email servers ⓘ mail service providers ⓘ |
| area | Applications and Real-Time ⓘ |
| BCPNumber | BCP 195 ⓘ |
| category | Best Current Practice ⓘ |
| definesRequirement |
mandatory encryption for email access
ⓘ
mandatory encryption for email submission ⓘ |
| discourages |
cleartext email access
ⓘ
cleartext email submission ⓘ |
| documentType | Standards-track RFC ⓘ |
| focusesOn | transport-layer security for email ⓘ |
| hasKeyword |
IMAP
ⓘ
POP3 ⓘ SMTP submission ⓘ TLS ⓘ email ⓘ security ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 2595
ⓘ
RFC 3207 ⓘ RFC 3501 ⓘ RFC 5068 ⓘ RFC 6186 ⓘ RFC 6409 ⓘ |
| primarySecurityMechanism |
TLS
ⓘ
TLS ⓘ
surface form:
Transport Layer Security
|
| protocolScope |
IMAP
ⓘ
Message Submission ⓘ POP3 ⓘ SMTP submission ⓘ |
| publicationDate | 2018-01 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| recommends |
deprecation of cleartext and opportunistic-only modes
ⓘ
use of TLS for email access ⓘ use of TLS for email submission ⓘ use of implicit TLS ports for email protocols ⓘ |
| RFCNumber | 8314 ⓘ |
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access ⓘ |
| updatesSecurityPracticesFor | email protocols ⓘ |
| workingGroup | UTA (Using TLS in Applications) ⓘ |
| year | 2018 ⓘ |
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 8314 Description of subject: RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.