[mile] RFC 8727 on JSON Binding of the Incident Object Description Exchange Format
rfc-editor@rfc-editor.org Wed, 05 August 2020 23:47 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 676513A09AF; Wed, 5 Aug 2020 16:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3nKEHIUzSKIu; Wed, 5 Aug 2020 16:47:37 -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 41F863A09A6; Wed, 5 Aug 2020 16:47:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7F050F4074B; Wed, 5 Aug 2020 16:47:30 -0700 (PDT)
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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mile@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200805234730.7F050F4074B@rfc-editor.org>
Date: Wed, 05 Aug 2020 16:47:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/E3rZByJ0cPJQ6PtV-dyq-aWUb1o>
Subject: [mile] RFC 8727 on JSON Binding of the Incident Object Description Exchange Format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Aug 2020 23:47:40 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8727
Title: JSON Binding of the Incident
Object Description Exchange Format
Author: T. Takahashi,
R. Danyliw,
M. Suzuki
Status: Standards Track
Stream: IETF
Date: August 2020
Mailbox: takeshi_takahashi@nict.go.jp,
rdd@cert.org,
mio@nict.go.jp
Pages: 88
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mile-jsoniodef-14.txt
URL: https://www.rfc-editor.org/info/rfc8727
DOI: 10.17487/RFC8727
The Incident Object Description Exchange Format (IODEF) defined in
RFC 7970 provides an information model and a corresponding XML data
model for exchanging incident and indicator information. This
document gives implementers and operators an alternative format to
exchange the same information by defining an alternative data model
implementation in JSON and its encoding in Concise Binary Object
Representation (CBOR).
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