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

 
Document Type Active Internet-Draft (xmpp WG)
Last updated 2015-06-24 (latest revision 2015-03-24)
Replaces draft-saintandre-xmpp-dna
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Dave Cridland
Shepherd write-up Show (last changed 2015-06-01)
IESG IESG state In Last Call (ends 2015-07-08)
Telechat date
Responsible AD Ben Campbell
Send notices to draft-ietf-xmpp-dna.ad@ietf.org, draft-ietf-xmpp-dna@ietf.org, xmpp-chairs@ietf.org, dave@cridland.net, draft-ietf-xmpp-dna.shepherd@ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
Network Working Group                                     P. Saint-Andre
Internet-Draft                                                      &yet
Intended status: Standards Track                               M. Miller
Expires: September 25, 2015                          Cisco Systems, Inc.
                                                               P. Hancke
                                                                    &yet
                                                          March 24, 2015

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

Abstract

   This document improves the security of the Extensible Messaging and
   Presence Protocol (XMPP) in two ways.  First, it specifies how to
   establish a strong association between a domain name and an XML
   stream, using the concept of "prooftypes".  Second, it describes how
   to securely delegate a service domain name (e.g., example.com) to a
   target server host name (e.g., hosting.example.net), which is
   especially important in multi-tenanted environments where the same
   target server hosts a large number of domains.

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 September 25, 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

Saint-Andre, et al.    Expires September 25, 2015               [Page 1]
Internet-Draft                  XMPP DNA                      March 2015

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

1.  Introduction

   In systems that use the Extensible Messaging and Presence Protocol
Show full document text