Attempt to define a valid event (#1045)

* Attempt to define a valid event Resolves #1044. Well, maybe. * Changelog * link to /rooms, thanks Travis Co-authored-by: Travis Ralston <travpc@gmail.com> Co-authored-by: Travis Ralston <travpc@gmail.com>
matrix-org · May 10, 2022 · 9ede29a · 9ede29a
1 parent 61e7a73
commit 9ede29a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/changelogs/server_server/newsfragments/1045.clarification b/changelogs/server_server/newsfragments/1045.clarification
@@ -0,0 +1 @@
+Expand a little on what it means for a PDU to be valid when discussing checks on PDUs.
diff --git a/content/server-server-api.md b/content/server-server-api.md
@@ -356,7 +356,9 @@ specification](/rooms).
 Whenever a server receives an event from a remote server, the receiving
 server must ensure that the event:
 
-1.  Is a valid event, otherwise it is dropped.
+1.  Is a valid event, otherwise it is dropped. For an event to be valid, it
+    must contain a `room_id`, and it must comply with the event format of
+    that [room version](/rooms).
 2.  Passes signature checks, otherwise it is dropped.
 3.  Passes hash checks, otherwise it is redacted before being processed
     further.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		Expand a little on what it means for a PDU to be valid when discussing checks on PDUs.