IETF RFC 7711
[ACTIVE]
PKIX over Secure HTTP (POSH)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 18
- Abstract
- Experience has shown that it is difficult to deploy proper PKIX certificates for Transport Layer Security (TLS) in multi-tenanted environments. As a result, domains hosted in such environments often deploy applications using certificates that identify the hosting service, not the hosted domain. Such deployments force end users and peer services to accept a certificate with an improper identifier, resulting in degraded security. This document defines methods that make it easier to deploy certificates for proper server identity checking in non-HTTP application protocols. Although these methods were developed for use in the Extensible Messaging and Presence Protocol (XMPP) as a Domain Name Association (DNA) prooftype, they might also be usable in other non-HTTP application protocols.
- Publication Date
- 2015-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7711- Link
- https://doi.org/10.17487/RFC7711
- Author(s)
- Matthew A. MillerPeter Saint-Andre
- Keyword(s)
- XMPP, Jabber
Latest version of IETF RFC 7711
Document Versions — IETF RFC 7711
-
▶ IETF RFC 7711 (2015-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 4648 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5785 [Superseded*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 7159 [Superseded*]
- IETF RFC 7230 [Superseded*]
- IETF RFC 7231 [Superseded*]
- IETF RFC 7525 [Superseded*]
Bibliographic Reference(s)
- "Hash Function Textual Names", < http://www.iana.org/assignments/ hash-function-text-names >. EXTERNAL
- IETF RFC 2782 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 4270 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 6120 [Active*]
- IETF RFC 6335 [Active*]
- IETF RFC 6555 [Superseded*]
- IETF RFC 6698 [Active*]
- IETF RFC 6797 [Active*]
- IETF RFC 7030 [Active*]
- IETF RFC 7469 [Active*]
- IETF RFC 7538 [Superseded*]
- IETF RFC 7673 [Active*]
- RFC7712 — RFC7712 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7711.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7711, PKIX over Secure HTTP (POSH). Available at https://doi.org/10.17487/RFC7711
Snippet:
IETF RFC 7711, PKIX over Secure HTTP (POSH). Available at https://doi.org/10.17487/RFC7711
HTML (ISO 690 compliant)
Preview:
IETF RFC 7711, PKIX over Secure HTTP (POSH). Available at https://doi.org/10.17487/RFC7711
Snippet:
<span class="citation"><cite>IETF RFC 7711</cite>, PKIX over Secure HTTP (POSH). Available at <a href="https://doi.org/10.17487/RFC7711" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7711</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7711, PKIX over Secure HTTP (POSH)
doi: 10.17487/RFC7711
url: https://doi.org/10.17487/RFC7711
doi: 10.17487/RFC7711
url: https://doi.org/10.17487/RFC7711
Snippet:
<li> <cite id="bib-rfc7711">IETF RFC 7711</cite>, PKIX over Secure HTTP (POSH) <span class="doi">10.17487/RFC7711</span> </li>
Referenced By
- IETF RFC 7817 [Active*]