From 6d78636bbe5968028f5553b609f32c8ad4a633c5 Mon Sep 17 00:00:00 2001
From: Luca Barbato <lu_zero@gentoo.org>
Date: Thu, 2 Mar 2023 13:36:16 +0100
Subject: [PATCH] Clarify the default behaviour for async actions

See #369
---
 index.html | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index d34dabf..4efbaa1 100644
--- a/index.html
+++ b/index.html
@@ -1671,7 +1671,19 @@ <h6 id="async-action-response">Asynchronous Action Response</h6>
               "timeRequested": "2021-11-10T11:43:19.135Z"
             }
           </pre>
-        </section>
+          <div class="rfc2119-assertion" id="http-basic-profile-protocol-binding-invokeaction-22">
+          <p>
+            In resource constrained environments, if the buffer becomes full then a Web Thing SHOULD
+            remove the oldest Action result ActionStatus from its buffer to make room for a newer one.
+          </p>
+          </div>
+          <div class="rfc2119-assertion" id="http-basic-profile-protocol-binding-invokeaction-23">
+          <p>
+            A Web Thing MUST return a <code>503</code> error response if the invocation cannot be enqueued,
+            e.g. the internal pending queue is full.
+          </p>
+          </div>
+         </section>
 
         <section id="http-basic-profile-protocol-binding-queryaction">
           <h5><code>queryaction</code></h5>