PKIX over Secure HTTP (POSH)
RFC 7711
| Document | Type |
RFC - Proposed Standard
(November 2015; No errata)
Was draft-ietf-xmpp-posh (xmpp WG)
|
|
|---|---|---|---|
| Last updated | 2015-11-19 | ||
| Replaces | draft-miller-posh | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Dave Cridland | ||
| Shepherd write-up | Show (last changed 2015-06-01) | ||
| IESG | IESG state | RFC 7711 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Miller
Request for Comments: 7711 Cisco Systems, Inc.
Category: Standards Track P. Saint-Andre
ISSN: 2070-1721 &yet
November 2015
PKIX over Secure HTTP (POSH)
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7711.
Miller & Saint-Andre Standards Track [Page 1]
RFC 7711 POSH November 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Obtaining Verification Material .................................5
3.1. Source Domain Possesses PKIX Certificate Information .......6
3.2. Source Domain References PKIX Certificate ..................8
3.3. Performing Verification ....................................9
4. Secure Delegation ...............................................9
5. Order of Operations ............................................10
6. Caching Results ................................................11
7. Guidance for Server Operators ..................................12
8. Guidance for Protocol Authors ..................................12
9. IANA Considerations ............................................13
9.1. Well-Known URI ............................................13
9.2. POSH Service Names ........................................13
10. Security Considerations .......................................14
11. References ....................................................15
11.1. Normative References .....................................15
11.2. Informative References ...................................16
Acknowledgements ..................................................18
Authors' Addresses ................................................18
Miller & Saint-Andre Standards Track [Page 2]
RFC 7711 POSH November 2015
1. Introduction
We begin with a thought experiment.
Imagine that you work on the operations team of a hosting company
that provides instances of the hypothetical "Secure Protocol for
Internet Content Exchange" (SPICE) service for ten thousand different
customer organizations. Each customer wants their instance to be
identified by the customer's domain name (e.g., bar.example.com), not
the hosting company's domain name (e.g., hosting.example.net).
In order to properly secure each customer's SPICE instance via
Transport Layer Security (TLS) [RFC5246], you need to obtain and
deploy PKIX certificates [RFC5280] containing identifiers such as
Show full document text