RFC 6186: Use of SRV Records for Locating Email Submission/Access Services
0 sources
RFC 6186: Use of SRV Records for Locating Email Submission/Access Services
Summary
RFC 6186: Use of SRV Records for Locating Email Submission/Access Services is a Request for Comments[1].
Key Facts
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services authored Use of SRV Records for Locating Email Submission/Access Services — author (P50): Cyrus Daboo[2].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's instance of is recorded as Use of SRV Records for Locating Email Submission/Access Services — instance of (P31): Request for Comments[3].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's publisher is recorded as Use of SRV Records for Locating Email Submission/Access Services — publisher (P123): Internet Engineering Task Force[4].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's based on is recorded as Use of SRV Records for Locating Email Submission/Access Services — based on (P144): RFC 1939: Post Office Protocol - Version 3[5].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's based on is recorded as Use of SRV Records for Locating Email Submission/Access Services — based on (P144): RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1[6].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's DOI is recorded as 10.17487/RFC6186[7].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's language of work or name is recorded as Use of SRV Records for Locating Email Submission/Access Services — language of work or name (P407): English[8].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's publication date is recorded as +2011-03-01T00:00:00Z[9].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's RfC ID is recorded as 6186[10].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's work available at URL is recorded as https://tools.ietf.org/html/rfc6186[11].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6186.txt[12].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6186.txt[13].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6186.txt.pdf[14].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's number of pages is recorded as {'unit': '1', 'amount': '+9'}[15].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's title is recorded as Use of SRV Records for Locating Email Submission/Access Services[16].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's amended by is recorded as Use of SRV Records for Locating Email Submission/Access Services — amended by (P2567): RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access[17].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's amended by is recorded as Use of SRV Records for Locating Email Submission/Access Services — amended by (P2567): RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names[18].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 1939: Post Office Protocol - Version 3[19].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 2119: Key words for use in RFCs to Indicate Requirement Levels[20].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 2595: Using TLS with IMAP, POP3 and ACAP[21].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 2782: A DNS RR for specifying the location of services (DNS SRV)[22].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 3207: SMTP Service Extension for Secure SMTP over Transport Layer Security[23].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1[24].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 4409: Message Submission for Mail[25].
- RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's cites work is recorded as Use of SRV Records for Locating Email Submission/Access Services — cites work (P2860): RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2[26].
Body
Designation and Status
RFC 6186: Use of SRV Records for Locating Email Submission/Access Services's instance of is recorded as Use of SRV Records for Locating Email Submission/Access Services — instance of (P31): Request for Comments[3].