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

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 25 December 2018 11:09 UTC

To: rdd@cert.org, kaduk@mit.edu, ekr@rtfm.com, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: takeshi_takahashi@nict.go.jp, mile@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20181225110922.2DF84B804DA@rfc-editor.org>
Date: Tue, 25 Dec 2018 03:09:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/Nw78vO77F5Mqdj597NUwemQ3N2Y>
Subject: [mile] [Technical Errata Reported] RFC7970 (5582)
Precedence: list

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:
http://www.rfc-editor.org/errata/eid5582

--------------------------------------
Type: Technical
Reported by: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>

Section: 8

Original Text
-------------
    <xs:simpleType name="contact-role-type">
      <xs:restriction base="xs:NMTOKEN">
        <xs:enumeration value="creator"/>
        <xs:enumeration value="reporter"/>
        <xs:enumeration value="admin"/>
        <xs:enumeration value="tech"/>
        <xs:enumeration value="provider"/>
        <xs:enumeration value="user"/>
        <xs:enumeration value="billing"/>
        <xs:enumeration value="legal"/>
        <xs:enumeration value="abuse"/>
        <xs:enumeration value="irt"/>
        <xs:enumeration value="cc"/>
        <xs:enumeration value="cc-irt"/>
        <xs:enumeration value="leo"/>
        <xs:enumeration value="vendor"/>
        <xs:enumeration value="vendor-services"/>

Corrected Text
--------------
    <xs:simpleType name="contact-role-type">
      <xs:restriction base="xs:NMTOKEN">
        <xs:enumeration value="creator"/>
        <xs:enumeration value="reporter"/>
        <xs:enumeration value="admin"/>
        <xs:enumeration value="tech"/>
        <xs:enumeration value="provider"/>
        <xs:enumeration value="user"/>
        <xs:enumeration value="billing"/>
        <xs:enumeration value="legal"/>
        <xs:enumeration value="abuse"/>
        <xs:enumeration value="irt"/>
        <xs:enumeration value="cc"/>
        <xs:enumeration value="cc-irt"/>
        <xs:enumeration value="leo"/>
        <xs:enumeration value="vendor"/>
        <xs:enumeration value="vendor-support"/>

Notes
-----
In section 3.9, the body text says that the role attribute can take the value "vendor-support," but the schema says that the role can take the value "vendor-services." This inconsistency needs to be solved.

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 (5582) RFC Errata System