Atul Tulshibagwale comments

Results 58 comments of


                                            Atul Tulshibagwale

Sign access decision?

We can add a note in the draft "Security Considerations" section that reliable mechanisms must be used to ensure PDP - PEP communication integrity, privacy and authenticity (e.g. MTLS)

Rework the "examples" sections

@timcappalli please provide an update as it looks like you had an action item related to this.

Search API Use Cases

The `id` field in the asset is optional. Does this suffice for your use case? See related discussion #24

Markdown source cleanup

Is this issue resolved? @timcappalli

Stream creation lanaguage imply that transmiter must suport the poll delivery method if delivery method is not specified

This is a backward-incompatible change, so we should not include this in v3.

Supply 'aud' in the stream creation POST request

I don't know if we can work on this now that ID-2 has shipped. I'd like to know everyone's thoughts here.

Explicit event retention policy in event stream metadata

Does the new language in section 7.1.2 address this issue?

Explicit event retention policy in event stream metadata

Ok. I see the problem. The status values are repeated in 7.1.2.1, whereas they were cleaned up in 7.1.2. I will remove the ambiguity and problematice language from 7.1.2.1, since...

Explicit event retention policy in event stream metadata

@ysarig1 is this issue closed in the latest spec? If so, could you please close this? Thanks

[CAEP] device management change is not captured in the existing events

I agree that option 3 is a good one, although I'd like to call the event "device management status" (IMO we should stop using "change" in event names, because all...