[mile] [Editorial Errata Reported] RFC6545 (5614)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 28 January 2019 00:20 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 C82EB130EE7 for <mile@ietfa.amsl.com>; Sun, 27 Jan 2019 16:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 sAt0hichxxu3 for <mile@ietfa.amsl.com>; Sun, 27 Jan 2019 16:20:40 -0800 (PST)
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 4EFCC130DF1 for <mile@ietf.org>; Sun, 27 Jan 2019 16:20:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E616BB82553; Sun, 27 Jan 2019 16:20:32 -0800 (PST)
To: Kathleen.Moriarty@emc.com, kaduk@mit.edu, ekr@rtfm.com, 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: logan.widick@gmail.com, mile@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20190128002032.E616BB82553@rfc-editor.org>
Date: Sun, 27 Jan 2019 16:20:32 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/ExKeCYkEYqaNMLbO2AyUsr_LK8I>
Subject: [mile] [Editorial Errata Reported] RFC6545 (5614)
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, 28 Jan 2019 00:20:42 -0000

The following errata report has been submitted for RFC6545,
"Real-time Inter-network Defense (RID)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5614

--------------------------------------
Type: Editorial
Reported by: Logan Widick <logan.widick@gmail.com>;

Section: 5.1

Original Text
-------------
TrafficType

      One or many.  REQUIRED.  The values for the attribute "type" are
      meant to assist in determining if a trace is appropriate for the
      SP receiving the request to continue the trace.  Multiple values
      may be selected for this element; however, where possible, it
      should be restricted to one value that most accurately describes
      the traffic type.

   type

      One or many.  REQUIRED.  ENUM.  The attribute type is used to
      identify the type of information included in the RID message or
      the type of incident.




Corrected Text
--------------
TrafficType

      One or many.  REQUIRED.  The values for the attribute "type" are
      meant to assist in determining if a trace is appropriate for the
      SP receiving the request to continue the trace.  Multiple values
      may be selected for this element; however, where possible, it
      should be restricted to one value that most accurately describes
      the traffic type.

   type

      One.  REQUIRED.  ENUM.  The attribute type is used to
      identify the type of information included in the RID message or
      the type of incident.




Notes
-----
This is the "similar
issue [that] is also present with the way that the TrafficType is defined
on pages 19-20" that was mentioned in the original submission for errata id 5588. 

The text as written (with "One or many" instances of the "type" attribute) suggests that 
<TrafficType type="Attack" type="Network"/> 
would be legal.

However, the schema (Section 8) and the fact that a single XML tag can't contain more than one instance of a given attribute (see https://www.w3.org/TR/xml/#uniqattspec, "An attribute name MUST NOT appear more than once in the same start-tag or empty-element tag") indicate that the above example of a TrafficType is not legal, and would need to be replaced with:
<TrafficType type="Attack"/>
<TrafficType type="Network"/>

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. 

--------------------------------------
RFC6545 (draft-ietf-mile-rfc6045-bis-11)
--------------------------------------
Title               : Real-time Inter-network Defense (RID)
Publication Date    : April 2012
Author(s)           : K. Moriarty
Category            : PROPOSED STANDARD
Source              : Managed Incident Lightweight Exchange
Area                : Security
Stream              : IETF
Verifying Party     : IESG