RFC 7203 on An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity Information
rfc-editor@rfc-editor.org Mon, 21 April 2014 22:28 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29C2D1A02E6; Mon, 21 Apr 2014 15:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.474
X-Spam-Level:
X-Spam-Status: No, score=-99.474 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 irhsFTQDoAdA; Mon, 21 Apr 2014 15:28:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 61C0E1A0067; Mon, 21 Apr 2014 15:28:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4ED4718000C; Mon, 21 Apr 2014 15:27:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7203 on An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity Information
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140421222729.4ED4718000C@rfc-editor.org>
Date: Mon, 21 Apr 2014 15:27:29 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/SBjQejVou2tOnFOJGG-j48YgSKE
Cc: mile@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 Apr 2014 22:28:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7203
Title: An Incident Object Description Exchange
Format (IODEF) Extension for Structured
Cybersecurity Information
Author: T. Takahashi, K. Landfield, Y. Kadobayashi
Status: Standards Track
Stream: IETF
Date: April 2014
Mailbox: takeshi_takahashi@nict.go.jp,
kent_landfield@mcafee.com,
youki-k@is.aist-nara.ac.jp
Pages: 28
Characters: 57694
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mile-sci-13.txt
URL: http://www.rfc-editor.org/rfc/rfc7203.txt
This document extends the Incident Object Description Exchange Format
(IODEF) defined in RFC 5070 to exchange enriched cybersecurity
information among security experts at organizations and facilitate
their operations. It provides a well-defined pattern to consistently
embed structured information, such as identifier- and XML-based
information.
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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
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