[mile] RFC 7970 on The Incident Object Description Exchange Format Version 2
rfc-editor@rfc-editor.org Wed, 30 November 2016 23:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A28C129BC6; Wed, 30 Nov 2016 15:51:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.098
X-Spam-Level:
X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 zwk0VOodKqmz; Wed, 30 Nov 2016 15:51:39 -0800 (PST)
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 2091212998B; Wed, 30 Nov 2016 15:51:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 146E7B806EF; Wed, 30 Nov 2016 15:51:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161130235139.146E7B806EF@rfc-editor.org>
Date: Wed, 30 Nov 2016 15:51:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/7seWoZoavzh_ddeAOut4cqHWWXU>
Cc: mile@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [mile] RFC 7970 on The Incident Object Description Exchange Format Version 2
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2016 23:51:41 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7970
Title: The Incident Object Description Exchange
Format Version 2
Author: R. Danyliw
Status: Standards Track
Stream: IETF
Date: November 2016
Mailbox: rdd@cert.org
Pages: 172
Characters: 331061
Obsoletes: RFC 5070, RFC 6685
I-D Tag: draft-ietf-mile-rfc5070-bis-26.txt
URL: https://www.rfc-editor.org/info/rfc7970
DOI: 10.17487/RFC7970
The Incident Object Description Exchange Format (IODEF) defines a
data representation for security incident reports and indicators
commonly exchanged by operational security teams for mitigation and
watch and warning. This document describes an updated information
model for the IODEF and provides an associated data model specified
with the XML schema. This new information and data model obsoletes
RFCs 5070 and 6685.
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