From 94040521a0dd17450e8482fc9012656049ec39ca Mon Sep 17 00:00:00 2001
From: Kegan Dougal <7190048+kegsay@users.noreply.github.com>
Date: Fri, 7 Jun 2024 12:13:08 +0100
Subject: [PATCH] Give examples of "unreachable" servers

---
 proposals/4081-claim-fallback-keys-on-network-failure.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/proposals/4081-claim-fallback-keys-on-network-failure.md b/proposals/4081-claim-fallback-keys-on-network-failure.md
index 694b0da5..80a5be86 100644
--- a/proposals/4081-claim-fallback-keys-on-network-failure.md
+++ b/proposals/4081-claim-fallback-keys-on-network-failure.md
@@ -115,7 +115,10 @@ An example of an EDU with the new property:
 ### Changed semantics for `/keys/claim`
 
 [`POST /_matrix/client/v3/keys/claim`](https://spec.matrix.org/v1.9/client-server-api/#post_matrixclientv3keysclaim) can
-now respond with a cached fallback key if the remote server is unreachable.
+now respond with a cached fallback key if the remote server is unreachable. "Unreachable" includes:
+ - unable to connect to the server
+ - the sending server is backing off the remote server
+ - the remote server responded with an error code such as 429 Too Many Requests.
 
 ### Changed semantics for rotating fallback keys