RFC 2595: Using TLS with IMAP, POP3 and ACAP

Recognizing that such sites will desire simple password authentication in combination with TLS encryption, this specification defines the PLAIN SASL mechanism…

Read RFC 2595 on the RFC Editor

Outgoing relationships (12 related RFCs)

Informative reference — RFC 2246: The TLS Protocol Version 1.0
Informative reference — RFC 2234: Augmented BNF for Syntax Specifications: ABNF
Informative reference — RFC 2279: UTF-8, a transformation format of ISO 10646
Informative reference — RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
Informative reference — RFC 2244: ACAP -- Application Configuration Access Protocol
Informative reference — RFC 2222: Simple Authentication and Security Layer (SASL)
Informative reference — RFC 1704: On Internet Authentication
Informative reference — RFC 2060: Internet Message Access Protocol - Version 4rev1
Informative reference — RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response
Informative reference — RFC 1734: POP3 AUTHentication command
Informative reference — RFC 2449: POP3 Extension Mechanism
Informative reference — RFC 2487: SMTP Service Extension for Secure SMTP over TLS

Incoming relationships (22 related RFCs)

Updated by, Informatively referenced by — RFC 4616: The PLAIN Simple Authentication and Security Layer (SASL) Mechanism
Updated by, Informatively referenced by — RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
Updated by, Informatively referenced by — RFC 7817: Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
Normatively referenced by — RFC 6186: Use of SRV Records for Locating Email Submission/Access Services
Normatively referenced by — RFC 4744: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
Normatively referenced by — RFC 5034: The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism
Informatively referenced by — RFC 6125: Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
Informatively referenced by — RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core
Informatively referenced by — RFC 5730: Extensible Provisioning Protocol (EPP)
Informatively referenced by — RFC 3730: Extensible Provisioning Protocol (EPP)
Informatively referenced by — RFC 4930: Extensible Provisioning Protocol (EPP)
Informatively referenced by — RFC 5054: Using the Secure Remote Password (SRP) Protocol for TLS Authentication
Informatively referenced by — RFC 4642: Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)
Informatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Informatively referenced by — RFC 9174: Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4
Informatively referenced by — RFC 5721: POP3 Support for UTF-8
Informatively referenced by — RFC 6856: Post Office Protocol Version 3 (POP3) Support for UTF-8
Informatively referenced by — RFC 4261: Common Open Policy Service (COPS) Over Transport Layer Security (TLS)
Informatively referenced by — RFC 6394: Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)
Informatively referenced by — RFC 3117: On the Design of Application Protocols
Informatively referenced by — RFC 5538: The 'news' and 'nntp' URI Schemes
Informatively referenced by — RFC 7508: Securing Header Fields with S/MIME