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

rfc-editor@rfc-editor.org Fri, 21 June 2019 16:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90423120463; Fri, 21 Jun 2019 09:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aS0V5ygd-SzM; Fri, 21 Jun 2019 09:38:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D06F012045B; Fri, 21 Jun 2019 09:38:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 71E03B81EC0; Fri, 21 Jun 2019 09:38:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2MDAgb24gVXNpbmcgRXh0ZW5zaWJsZSBNZXNzYWdpbmcgYW5kIFByZXNlbmNlIFByb3RvY29sIChYTVBQKSBmb3IgU2VjdXJpdHkgSW5mb3JtYXRpb24gRXhjaGFuZ2U=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mile@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190621163836.71E03B81EC0@rfc-editor.org>
Date: Fri, 21 Jun 2019 09:38:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/suJMmeMhuAOmGn_PJYgX5Vm8lNA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2019 16:39:02 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8600

        Title:      Using Extensible Messaging and Presence 
                    Protocol (XMPP) for Security Information Exchange 
        Author:     N. Cam-Winget, Ed.,
                    S. Appala,
                    S. Pope,
                    P. Saint-Andre
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2019
        Mailbox:    ncamwing@cisco.com, 
                    syam1@cisco.com, 
                    scottp@cisco.com,
                    stpeter@mozilla.com
        Pages:      28
        Characters: 61866
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mile-xmpp-grid-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8600

        DOI:        10.17487/RFC8600

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).

This document is a product of the Managed Incident Lightweight Exchange Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC