Home › Entities › request_for_comments › RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access

RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access

request for comments publication
Place request_for_comments Q48078442
Press Enter · cited answer in seconds

RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access

Summary

RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access is a Request for Comments[1].

Key Facts

  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access authored Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — author (P50): Chris Newman[2].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's instance of is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — instance of (P31): Request for Comments[3].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's publisher is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — publisher (P123): Internet Engineering Task Force[4].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's based on is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — based on (P144): RFC 1939: Post Office Protocol - Version 3[5].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's based on is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — based on (P144): RFC 2595: Using TLS with IMAP, POP3 and ACAP[6].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's based on is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — based on (P144): RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1[7].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's based on is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — based on (P144): RFC 5068: Email Submission Operations: Access and Accountability Requirements[8].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's based on is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — based on (P144): RFC 6186: Use of SRV Records for Locating Email Submission/Access Services[9].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's based on is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — based on (P144): RFC 6409: Message Submission for Mail[10].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's DOI is recorded as 10.17487/RFC8314[11].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's language of work or name is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — language of work or name (P407): English[12].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's publication date is recorded as +2018-01-01T00:00:00Z[13].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's RfC ID is recorded as 8314[14].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's work available at URL is recorded as https://tools.ietf.org/html/rfc8314[15].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's work available at URL is recorded as https://tools.ietf.org/rfc/rfc8314.txt[16].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc8314.txt[17].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc8314.txt.pdf[18].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's number of pages is recorded as {'unit': '1', 'amount': '+26'}[19].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's title is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access[20].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's author name string is recorded as K. Moore[21].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's amended by is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — amended by (P2567): RFC 8997: Deprecation of TLS 1.1 for Email Submission and Access[22].
  • RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's DBLP publication ID is recorded as journals/rfc/rfc8314[23].

Body

Designation and Status

RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access's instance of is recorded as Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — instance of (P31): Request for Comments[3].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . RFC Index. Retrieved . wikidata.org.
  19. [20] ↑ . RFC Index. Retrieved . wikidata.org.
  20. [21] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . RFC Index. Retrieved . wikidata.org.
  22. [23] ↑ . DBLP Dataset 2021-01-02. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-8314-cleartext-considered-obsolete-use-of-transport-layer-security-tls-for-email-submission-and-access
MLA “RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-8314-cleartext-considered-obsolete-use-of-transport-layer-security-tls-for-email-submission-and-access.
BibTeX @misc{4ortxyz_rfc-8314-cleartext-considered-obsolete-use-of-transport-layer-security-tls-for-email-submission-and-access_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-8314-cleartext-considered-obsolete-use-of-transport-layer-security-tls-for-email-submission-and-access}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access — https://4ort.xyz/entity/rfc-8314-cleartext-considered-obsolete-use-of-transport-layer-security-tls-for-email-submission-and-access (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-8314-cleartext-considered-obsolete-use-of-transport-layer-security-tls-for-email-submission-and-access · Last refreshed: