RFC 6186: Use of SRV Records for Locating Email Submission/Access Services
In plain English — editorial summary, not part of the RFC
This specification describes how SRV records can be used to locate email services. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6186
- Published
- March 2011
- Authors
- C. Daboo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 7817Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related ProtocolsCurrent
March 2016
- RFC 3656The Mailbox Update (MUPDATE) Distributed Mailbox Database ProtocolUpdated
December 2003
- RFC 2595Using TLS with IMAP, POP3 and ACAPUpdated
June 1999
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 6154IMAP LIST Extension for Special-Use MailboxesCurrent
March 2011
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?