Using XMPP for Security Information Exchange
draft-ietf-mile-xmpp-grid-08

Document Type Active Internet-Draft (mile WG)
Last updated 2018-11-04
Replaces draft-appala-mile-xmpp-grid
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2018 - Submit a draft on XM... )
Document shepherd Takeshi Takahashi
Shepherd write-up Show (last changed 2018-11-04)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to mile-chairs@tools.ietf.org, mile@ietf.org, Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
MILE                                                  N. Cam-Winget, Ed.
Internet-Draft                                                 S. Appala
Intended status: Standards Track                                 S. Pope
Expires: May 8, 2019                                       Cisco Systems
                                                          P. Saint-Andre
                                                                 Mozilla
                                                        November 4, 2018

              Using XMPP for Security Information Exchange
                      draft-ietf-mile-xmpp-grid-08

Abstract

   This document describes how to use the Extensible Messaging and
   Presence Protocol (XMPP) to collect and distribute security-relevant
   information between network-connected devices.  To illustrate the
   principles involved, this document describes such a usage for the
   Incident Object Description Exchange Format (IODEF).

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 https://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 May 8, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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

Cam-Winget, et al.         Expires May 8, 2019                  [Page 1]
Internet-Draft                  XMPP Grid                  November 2018

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Workflow  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Service Discovery . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Publish-Subscribe . . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
     8.1.  Trust Model . . . . . . . . . . . . . . . . . . . . . . .  12
     8.2.  Threat Model  . . . . . . . . . . . . . . . . . . . . . .  13
     8.3.  Countermeasures . . . . . . . . . . . . . . . . . . . . .  17
     8.4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  20
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  21
   10. Operations and Management Considerations  . . . . . . . . . .  21
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  22
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  22
     12.2.  Informative References . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

   This document describes "XMPP-Grid": a method for using the
   Extensible Messaging and Presence Protocol (XMPP) [RFC6120] to
   collect and distribute security-relevant information among network
   platforms, endpoints, and any other network-connected device.  Among
   other things, XMPP provides a publish-subscribe service [XEP-0060]
   that acts as a broker, enabling control-plane functions by which
   entities can discover available information to be published or
   consumed.  Although such information can take the form of any
   structured data (XML, JSON, etc.), this document illustrates the
   principles of XMPP-Grid with examples that use the Incident Object
   Description Exchange Format (IODEF) [RFC7970].  That is, while other
   security information formats can be shared using XMPP, this document
   uses IODEF as one such example format that can be published and
   consumed using XMPP.

2.  Terminology

   This document uses XMPP terminology defined in [RFC6120] and
   [XEP-0060].  Because the intended audience for this document is those
Show full document text