Re: [scim] IET 115 Call for agenda

[Phillip Hunt <[e-mail]>]

Unfortunately due to recent eye surgery, I have been unable to spend any major amount of editing time on the SCIM Events document due to severe light sensitivity that will require further surgical intervention. Because of this and some other conflicts, I have decided not to attend.

Update on the SCIM Events Draft:
For the next SCIM Events draft revision, my proposal is to:
* Add support for the SecEvent Sub-ID draft spec - draft-ietf-secevent-subject-identifiers-13 .  The goal here is to make SCIM Events compatible with existing OpenID Shared Signals Frameworks
* Add non-normative sections discussing how recovery works in practice and why receiver based recovery is important in multi-domain scenarios (this was a requirement by Google and Amazon participants during the development of security event streams specifications). 
* Add Security Considerations and Privacy Considerations Sections
* Add IANA registration for SCIM Events URIs, as well as to register SCIM id and externalid format per the subject identifiers draft.

History of SCIM and Security Events: 
The registration of SCIM Events definitions (the SCIM Events draft) is the last step in a plan that the SCIM Working Group began when RFC7643,7644 was published. It was the goal of the older SCIM WG *not* to create a new protocol when other WGs were about to design something 95% the same.  The group opted for a single interoperable approach among the larger family of identity protocols. You will notice that SCIM is present in SET(RFC8417). Notice that event formats in Security Event Tokens are similar to SCIM resources except for the missing Schemas attribute. SETs were literally made in the wider security events community to support SCIM.

Going forwards:
I remain concerned that the working group is considering adopting a method that was previously considered unworkable by the prior SCIM working group (and even that of the much older LDAPEXT group).

I hope the group can have a good discussion about the future and come to a consensus on a single approach.

Cheers,

Phil Hunt
@independentid
[e-mail]




> On Oct 25, 2022, at 9:25 AM, Nancy Cam-Winget (ncamwing) <ncamwing=[e-mail]> wrote:
> 
> Hello SCIMers,
>  
> We have a 2hr session scheduled for IETF 115:
>     Monday, 7 November 2022, Session II 1300-1500 (London time)
>     Room Name: Richmond 2 size: 80
>  
> If you want time on the agenda please send your request to [e-mail] <mailto:[e-mail]>
>  
> Thanks, Nancy
> _______________________________________________
> scim mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/scim <https://www.ietf.org/mailman/listinfo/scim>