[mile] [Technical Errata Reported] RFC7970 (6168)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 11 May 2020 13:24 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 605B33A0AC8 for <mile@ietfa.amsl.com>; Mon, 11 May 2020 06:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Hx7Fxzxma4Sd for <mile@ietfa.amsl.com>; Mon, 11 May 2020 06:24:06 -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 704E43A0AC5 for <mile@ietf.org>; Mon, 11 May 2020 06:24:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1B9CEF4071E; Mon, 11 May 2020 06:23:53 -0700 (PDT)
To: rdd@cert.org, rdd@cert.org, kaduk@mit.edu, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: fpoirotte@gmail.com, mile@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200511132353.1B9CEF4071E@rfc-editor.org>
Date: Mon, 11 May 2020 06:23:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/uGDx0--Afd6warv9GRkQbTaPzCY>
Subject: [mile] [Technical Errata Reported] RFC7970 (6168)
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: Mon, 11 May 2020 13:24:09 -0000
The following errata report has been submitted for RFC7970, "The Incident Object Description Exchange Format Version 2". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6168 -------------------------------------- Type: Technical Reported by: François Poirotte <fpoirotte@gmail.com> Section: 2.17 Original Text ------------- There is no original text (new section) Corrected Text -------------- 2.17. Boolean A boolean is represented in the information model by the BOOLEAN data type. The BOOLEAN data type is implemented in the data model as an "xs:boolean" type per Section 3.2.2 of [W3C.SCHEMA.DTYPES]. Notes ----- Section 2.16 defines "boolean" as a valid value for the "dtype" attribute, stating that "The element content is of type BOOLEAN.". This is reinforced by the definition of "dtype-type" inside the XML schema in section 8 where "boolean" is indeed listed as a valid value. However, the BOOLEAN type is never actually defined in the RFC. This change adds a new section (tentatively named 2.17) under section 2 which defines the BOOLEAN type based on the definition of other types used by the RFC. It might be preferable to put the new section near the beginning of section 2 with other primitive datatypes like INTEGER and REAL. Please note that this change also impacts the table of contents. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7970 (draft-ietf-mile-rfc5070-bis-26) -------------------------------------- Title : The Incident Object Description Exchange Format Version 2 Publication Date : November 2016 Author(s) : R. Danyliw Category : PROPOSED STANDARD Source : Managed Incident Lightweight Exchange Area : Security Stream : IETF Verifying Party : IESG
- [mile] [Technical Errata Reported] RFC7970 (6168) RFC Errata System