[mile] [Technical Errata Reported] RFC7970 (6177)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 17 May 2020 10:54 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 A9A253A0FE4 for <mile@ietfa.amsl.com>; Sun, 17 May 2020 03:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.839
X-Spam-Level:
X-Spam-Status: No, score=0.839 tagged_above=-999 required=5 tests=[CTE_8BIT_MISMATCH=0.839, 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 Di8ahA9lMEGT for <mile@ietfa.amsl.com>; Sun, 17 May 2020 03:54:46 -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 64C203A0FE2 for <mile@ietf.org>; Sun, 17 May 2020 03:54:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 93CBCF406D8; Sun, 17 May 2020 03:54:44 -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: <20200517105444.93CBCF406D8@rfc-editor.org>
Date: Sun, 17 May 2020 03:54:44 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/CSY74qqg9zZKAGkY5phc_0ebI-E>
Subject: [mile] [Technical Errata Reported] RFC7970 (6177)
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: Sun, 17 May 2020 10:54:49 -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/eid6177

--------------------------------------
Type: Technical
Reported by: Fran├žois Poirotte <fpoirotte@gmail.com>

Section: 3.26

Original Text
-------------
3.26.  HashData Class

   The HashData class describes different types of hashes on a given
   object (e.g., file, part of a file, email).

   +--------------------------+
   | HashData                 |
   +--------------------------+
   | ENUM scope               |<>--{0..1}--[ HashTargetID ]
   |                          |<>--{0..*}--[ Hash         ]
   |                          |<>--{0..*}--[ FuzzyHash    ]
   +--------------------------+

                       Figure 54: The HashData Class

Corrected Text
--------------
3.26.  HashData Class

   The HashData class describes different types of hashes on a given
   object (e.g., file, part of a file, email).

   +--------------------------+
   | HashData                 |
   +--------------------------+
   | ENUM scope               |<>--{0..1}--[ HashTargetID ]
   | STRING ext-scope         |<>--{0..*}--[ Hash         ]
   |                          |<>--{0..*}--[ FuzzyHash    ]
   +--------------------------+

                       Figure 54: The HashData Class

Notes
-----
Both the main body inside section 3.26 & the XML schema in section 8 mention "ext-scope" as a valid attribute of the HashData class, but the attribute was missing from the UML diagram in section 3.26.

(The attribute is necessary so that the "scope" attribute of HashData can be extended using the principles edicted in section 5.1.1)

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