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

[Phil Hunt <[e-mail]>]

Agreed “Verified”

Phil Hunt
[e-mail]



> On Nov 12, 2022, at 11:09 AM, Yaron Sheffer <[e-mail]> wrote:
> 
> IMO this errata should be verified (=accepted). Indeed "cause-time" does not exist in the example, which is copied verbatim from the referenced OpenID document.
> 
> Having said that, I would classify the errata as Editorial rather than Technical, because it refers to a non-normative example (see top of Sec. 2.1, "This section illustrates several possible uses of SETs through non-normative examples") and is a simple typo.
> 
> Thanks,
> 	Yaron
> 
> On 21/10/2022, 4:23, "Id-event on behalf of RFC Errata System" <[e-mail] on behalf of [e-mail]> wrote:
> 
>    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 <[e-mail]>
> 
>    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 mailing list
>    [e-mail]
>    https://www.ietf.org/mailman/listinfo/id-event
> 
> 
> _______________________________________________
> Id-event mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/id-event