[rfc-dist] RFC 7203 on An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity Information

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Apr 21 15:27:29 PDT 2014

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 at nict.go.jp, 
                    kent_landfield at mcafee.com, 
                    youki-k at 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

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

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 at 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

More information about the rfc-dist mailing list