[Id-event] [Technical Errata Reported] RFC8417 (7175)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 21 October 2022 01:23 UTC

To: phil.hunt@yahoo.com, mbj@microsoft.com, rfc8417@wdenniss.com, morteza.ansari@cisco.com, rdd@cert.org, paul.wouters@aiven.io, dick.hardt@gmail.com, yaronf.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nigel@somerfield.co.nz, id-event@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20221021012309.A73B516E4D1@rfcpa.amsl.com>
Date: Thu, 20 Oct 2022 18:23:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/Pqa1q_nhv2j_URjTcbh4IovwAPU>
Subject: [Id-event] [Technical Errata Reported] RFC8417 (7175)
Precedence: list

The following errata report has been submitted for RFC8417,
"Security Event Token (SET)".

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

--------------------------------------
Type: Technical
Reported by: Nigel Somerfield <nigel@somerfield.co.nz>

Section: 2.1.4

Original Text
-------------
{
    "iss": "https://idp.example.com/",
    "jti": "756E69717565206964656E746966696572",
    "iat": 1508184845,
    "aud": "636C69656E745F6964",
    "events": {
  "https://schemas.openid.net/secevent/risc/event-type/account-disabled"
          : {
        "subject": {
          "subject_type": "iss-sub",
          "iss": "https://idp.example.com/",
          "sub": "7375626A656374"
        },
        "reason": "hijacking"
      }
    }
  }

                       Figure 4: Example RISC Event

   Notice that parameters to the event are included in the event
   payload, in this case, the "reason" and "cause-time" values.  The
   subject of the event is identified using the "subject" payload value,
   which itself is a JSON object.

Corrected Text
--------------
{
    "iss": "https://idp.example.com/",
    "jti": "756E69717565206964656E746966696572",
    "iat": 1508184845,
    "aud": "636C69656E745F6964",
    "events": {
  "https://schemas.openid.net/secevent/risc/event-type/account-disabled"
          : {
        "subject": {
          "subject_type": "iss-sub",
          "iss": "https://idp.example.com/",
          "sub": "7375626A656374"
        },
        "reason": "hijacking"
      }
    }
  }

                       Figure 4: Example RISC Event

   Notice that parameters to the event are included in the event
   payload, in this case, the "reason" value.  The
   subject of the event is identified using the "subject" payload value,
   which itself is a JSON object.

Notes
-----
The included RISC event example JSON object does not contain a "cause-time" member, however this is referred to in the explanation following the example.  It would be valuable to either include the "cause-time" member, or to remove it from the explanation as per the above.

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. 

--------------------------------------
RFC8417 (draft-ietf-secevent-token-13)
--------------------------------------
Title               : Security Event Token (SET)
Publication Date    : July 2018
Author(s)           : P. Hunt, Ed., M. Jones, W. Denniss, M. Ansari
Category            : PROPOSED STANDARD
Source              : Security Events
Area                : Security
Stream              : IETF
Verifying Party     : IESG

[Id-event] [Technical Errata Reported] RFC8417 (7… RFC Errata System
Re: [Id-event] [Technical Errata Reported] RFC841… Yaron Sheffer
Re: [Id-event] [Technical Errata Reported] RFC841… Phil Hunt