Network Working Group P. Saint-Andre
Internet-Draft M. Miller
Intended status: Standards Track Cisco Systems, Inc.
Expires: October 17, 2013 April 15, 2013
Domain Name Associations (DNA) in the Extensible Messaging and Presence
Protocol (XMPP)
draft-saintandre-xmpp-dna-02
Abstract
This document improves the security of the Extensible Messaging and
Presence Protocol (XMPP) in two ways. First, it specifies how
"prooftypes" can establish a strong association between a domain name
and an XML stream. Second, it describes how to securely delegate a
source domain to a derived domain, which is especially important in
virtual hosting environments.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 17, 2013.
Copyright Notice
Copyright (c) 2013 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
Saint-Andre & Miller Expires October 17, 2013 [Page 1]
Internet-Draft XMPP DNA April 2013
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Flow Chart . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. A Simple Scenario . . . . . . . . . . . . . . . . . . . . . . 5
5. One-Way Authentication . . . . . . . . . . . . . . . . . . . 6
6. Piggybacking . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Assertion . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Supposition . . . . . . . . . . . . . . . . . . . . . . . 9
7. Alternative Prooftypes . . . . . . . . . . . . . . . . . . . 10
7.1. DANE . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.2. POSH . . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Secure Delegation and Multi-Tenancy . . . . . . . . . . . . . 11
9. Prooftype Model . . . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
12.1. Normative References . . . . . . . . . . . . . . . . . . 12
12.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
The need to establish a strong association between a domain name and
an XML stream arises in both client-to-server and server-to-server
communication using the Extensible Messaging and Presence Protocol
(XMPP), because XMPP servers are typically identified by DNS domain
names. However, a client or peer server needs to verify the identity
of a server to which it connects. To date, such verification has
been established based on information obtained from the Domain Name
System (DNS), the Public Key Infrastructure (PKI), or similar
sources. This document (1) generalizes the model currently in use so
that additional prooftypes can be defined, (2) provides a basis for
modernizing some prooftypes to reflect progress in underlying
technologies such as DNS Security [RFC4033], and (3) describes the
flow of operations for establishing a domain name association.
Furthermore, the process for resolving the domain name of an XMPP
datatracker.ietf.org