[xmpp] RFC 7711 on PKIX over Secure HTTP (POSH)
rfc-editor@rfc-editor.org Thu, 19 November 2015 23:55 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0701B37D5; Thu, 19 Nov 2015 15:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level:
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVL2t56BfE28; Thu, 19 Nov 2015 15:55:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id EA0581B37A2; Thu, 19 Nov 2015 15:55:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 79E32180014; Thu, 19 Nov 2015 15:53:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151119235353.79E32180014@rfc-editor.org>
Date: Thu, 19 Nov 2015 15:53:53 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/_0RDZDA9sJaL-wuCVAB9C4GCWdM>
Cc: drafts-update-ref@iana.org, xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] RFC 7711 on PKIX over Secure HTTP (POSH)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 23:55:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7711
Title: PKIX over Secure HTTP (POSH)
Author: M. Miller,
P. Saint-Andre
Status: Standards Track
Stream: IETF
Date: November 2015
Mailbox: mamille2@cisco.com,
peter@andyet.com
Pages: 18
Characters: 41302
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-xmpp-posh-06.txt
URL: https://www.rfc-editor.org/info/rfc7711
DOI: http://dx.doi.org/10.17487/RFC7711
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.
This document is a product of the Extensible Messaging and Presence Protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC