Add change notification expectations to Security Considerations.

[msporny]

This PR is an attempt to address issue #909 by adding add change notification service expectations to the Security Considerations section.

---

Preview | Diff

[TallTed]

A few small changes suggested. Approved either way.

[TallTed]

Suggested change

	and be a core part of change notification service specifications.
	and be a core part of the specifications of change notification services.

[msporny]

The group discussed this on 2026-01-15 and decided that we should remove the section because we haven't done an analysis on change notification sections and don't have much implementation experience and it is confusing/concerning people that are reading the section.

The PR should be modified to remove the section.

[w3cbot]

This was discussed during the #did meeting on 15 January 2026.

View the transcript

w3c/did#916

ottomorac: Manu can you give us a summary

manu: This one is a request from PING to detail considerations for change notification text

manu: this is about VDRs, with a DID in it, how do you let people know about that

manu: PING thinks this matters. Talk about what you need to do to harden that surface

<Zakim> JoeAndrieu, you wanted to ask why we have change notification

JoeAndrieu: I think we should get this section out of the spec...

<swcurran> +1 to Joe

JoeAndrieu: I think we should not be speaking to this in spec

manu: I'm fine with doing that as well. This text came from the early days.
… This talked as if this is a regular thing, but it isn't really.
… It confused the reviewers. Since we haven't done the analysis, we should probably stay quiet

---

[mccown]

Approve updates.

[msporny]

… It confused the reviewers. Since we haven't done the analysis, we should probably stay quiet

I have removed the section, per the discussion in the DID WG.

[msporny]

Editorial, multiple reviews, changes requested and made, no objections, merging.