Re: I-D Action: draft-ietf-xmpp-posh-01.txt
Matt Miller <[email protected]> Thu, 19 Jun 2014 21:50:25 -0600
| Newsgroups | gmane.ietf.xmpp |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 6/19/14, 9:40 PM, [email protected] wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the Extensible Messaging > and Presence Protocol Working Group of the IETF. > > Title : PKIX over Secure HTTP (POSH) Authors : > Matthew Miller Peter Saint-Andre Filename : > draft-ietf-xmpp-posh-01.txt Pages : 14 Date : > 2014-06-19 > > Abstract: Experience has shown that it is extremely difficult to > deploy proper PKIX certificates for TLS in multi-tenanted > environments, since certification authorities will not issue > certificates for hosted domains to hosting services, hosted domains > do not want hosting services to hold their private keys, and > hosting services wish to avoid liability for holding those keys. > As a result, domains hosted in multi-tenanted environments often > deploy non-HTTP applications such as email and instant messaging > 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 > obvious security implications. This document defines two methods > that make it easier to deploy certificates for proper server > identity checking in non-HTTP application protocols. The first > method enables the TLS client associated with a user agent or peer > application server to obtain the end-entity certificate of a hosted > domain over secure HTTP as an alternative to standard PKIX > techniques. The second method enables a hosted domain to securely > delegate a non-HTTP application to a hosting service using > redirects provided by HTTPS itself or by a pointer in a file served > over HTTPS at the hosted domain. While this approach was developed > for use in the Extensible Messaging and Presence Protocol (XMPP) as > a Domain Name Association prooftype, it can be applied to any > non-HTTP application protocol. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-xmpp-posh/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-xmpp-posh-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-posh-01 > > > Please note that it may take a couple of minutes from the time of > submission until the htmlized version and diff are available at > tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > This revision changes the "by value" document from JWK-set to the fingerprints expressed in a previous email. - -- - - m&m Matt Miller < [email protected] > Cisco Systems, Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTo6+BAAoJEDWi+S0W7cO1aY4H/1r68xg0dZe66Rs1CpkZzWZF OU+R9rwGJcJF7MzZiDeZVHXV/gP/3eBVeOIozstddQn6j1Re7YyOVULisq+vC6+z na8Gqa7W4LyqAE3ppp9rrzSGLNAZVKNIMUn7Wfhtl+ZwgPGWlFmCQsGaTijwjUln DBzur4rbDpRZNkoyBk9qOMQHhxaJfdgHKpz2vMNgKxILSVgTo9MuuvgSSAXGK9gO 2hwxsBs8dwFYUKvIWVyfIK1tQg9pNAWZFJ9E91Ra4yAMBR1+7L3dnx2cDVpxISWw +9QeTArWVLRPJpZ+Gk4JE8zdkWGYs5pwR/LT9g1fu+/nt+eGOzvkyf8jcaWWgR0= =FRbW -----END PGP SIGNATURE-----