Follow-up comments for ARL PR 34537

[tleacmcsa]

These comments need resolution for 1.4:

kSubscribeEventRequest: why is this needed given subscribe privileges are the same as read? #34537 (comment)

Clarification on request type and how to identify action being performed. I believe it is addressed, but @bzbarsky-apple should verify. #34537 (comment)

Similar to above, I believe I have addressed this comment but would like @andy31415 to confirm. #34537 (comment)

[bzbarsky-apple]

The request type bits are not addressed at least in the following:

1. There is some sort of asymmetry between "event" and "attribute" in the RequestType values that does not actually exist: you can read attributes and events, and you can subscribe to attributes and events.
2. The meaning of "wildcard" entityId is not defined. There is nothing like that in the spec in terms of the ARL bits, and it's really not clear what it means for that field to be "wildcard".
3. There is no clear definition of what entityId means for different request types.

[tleacmcsa]

@tcarmelveilleux The first piece of this issue came from your comment. Are we good with where it landed now?

@bzbarsky-apple and @andy31415, this should line up with the spec work (https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/10211). Is it clear in the spec? The intent is to be able to support restrictions on events separately from attributes.

[bzbarsky-apple]

The spec bits I looked at this morning looked reasonable, yes.

[tcarmelveilleux]

This is resolved.