Using Extensible Messaging and Presence Protocol (XMPP) for Security Information Exchange
RFC 8600

Document Type RFC - Proposed Standard (June 2019; No errata)
Last updated 2019-06-21
Replaces draft-appala-mile-xmpp-grid
Stream IETF
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Takeshi Takahashi
Shepherd write-up Show (last changed 2018-11-04)
IESG IESG state RFC 8600 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to mile-chairs@ietf.org, mile@ietf.org, Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
Internet Engineering Task Force (IETF)                N. Cam-Winget, Ed.
Request for Comments: 8600                                     S. Appala
Category: Standards Track                                        S. Pope
ISSN: 2070-1721                                            Cisco Systems
                                                          P. Saint-Andre
                                                                 Mozilla
                                                               June 2019

        Using Extensible Messaging and Presence Protocol (XMPP)
                   for Security Information Exchange

Abstract

   This document describes how to use the Extensible Messaging and
   Presence Protocol (XMPP) to collect and distribute security incident
   reports and other security-relevant information between network-
   connected devices, primarily for the purpose of communication among
   Computer Security Incident Response Teams and associated entities.
   To illustrate the principles involved, this document describes such a
   usage for the Incident Object Description Exchange Format (IODEF).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8600.

Cam-Winget, et al.           Standards Track                    [Page 1]
RFC 8600                        XMPP Grid                      June 2019

Copyright Notice

   Copyright (c) 2019 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Workflow  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Service Discovery . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Publish-Subscribe . . . . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     8.1.  Trust Model . . . . . . . . . . . . . . . . . . . . . . .  14
     8.2.  Threat Model  . . . . . . . . . . . . . . . . . . . . . .  16
     8.3.  Countermeasures . . . . . . . . . . . . . . . . . . . . .  20
     8.4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  23
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  24
   10. Operations and Management Considerations  . . . . . . . . . .  25
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  25
     11.2.  Informative References . . . . . . . . . . . . . . . . .  27
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  27
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  28

Cam-Winget, et al.           Standards Track                    [Page 2]
RFC 8600                        XMPP Grid                      June 2019

1.  Introduction

   This document defines an architecture, i.e., "XMPP-Grid", as a method
   for using the Extensible Messaging and Presence Protocol (XMPP)
   [RFC6120] to collect and distribute security incident reports and
   other security-relevant information among network platforms,
   endpoints, and any other network-connected device, primarily for the
   purpose of communication among Computer Security Incident Response
   Teams and associated entities.  In effect, this document specifies an
   Applicability Statement ([RFC2026], Section 3.2) that defines how to
   use XMPP for the exchange of security notifications on a controlled-
   access network among authorized entities.

   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
Show full document text