datatracker.ietf.org
Sign in
Version 5.6.3, 2014-09-19
Report a bug

Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)
draft-ietf-xmpp-dna-06

Document type: Active Internet-Draft (xmpp WG)
Document stream: IETF
Last updated: 2014-06-21
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                     P. Saint-Andre
Internet-Draft                                                      &yet
Intended status: Standards Track                               M. Miller
Expires: December 23, 2014                           Cisco Systems, Inc.
                                                           June 21, 2014

Domain Name Associations (DNA) in the Extensible Messaging and Presence
                            Protocol (XMPP)
                         draft-ietf-xmpp-dna-06

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
   multi-tenanted 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 December 23, 2014.

Copyright Notice

   Copyright (c) 2014 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

Saint-Andre & Miller    Expires December 23, 2014               [Page 1]
Internet-Draft                  XMPP DNA                       June 2014

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Client-to-Server (C2S) DNA  . . . . . . . . . . . . . . . . .   3
     3.1.  C2S Flow  . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  C2S Description . . . . . . . . . . . . . . . . . . . . .   4
   4.  Server-to-Server (S2S) DNA  . . . . . . . . . . . . . . . . .   5
     4.1.  S2S Flow Chart  . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  A Simple S2S Scenario . . . . . . . . . . . . . . . . . .   7
     4.3.  One-Way Authentication  . . . . . . . . . . . . . . . . .   8
     4.4.  Piggybacking  . . . . . . . . . . . . . . . . . . . . . .   9
       4.4.1.  Assertion . . . . . . . . . . . . . . . . . . . . . .   9
       4.4.2.  Supposition . . . . . . . . . . . . . . . . . . . . .  10
   5.  Alternative Prooftypes  . . . . . . . . . . . . . . . . . . .  12
     5.1.  DANE  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  POSH  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Secure Delegation and Multi-Tenancy . . . . . . . . . . . . .  13
   7.  Prooftype Model . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Well-Known URI for xmpp-client Service  . . . . . . . . .  14
     8.2.  Well-Known URI for xmpp-server Service  . . . . . . . . .  14
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

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) [RFC6120].  Because XMPP servers are typically identified by
   DNS domain names, a client or peer server needs to verify the
   identity of a server to which it connects.

[include full document text]