diff --git a/FAPI_2_0_Implementation_Advice.md b/FAPI_2_0_Implementation_Advice.md
index a042313..ae22de4 100644
--- a/FAPI_2_0_Implementation_Advice.md
+++ b/FAPI_2_0_Implementation_Advice.md
@@ -197,6 +197,10 @@ Some ecosystems issue certificates to organizations rather than to individual cl
NOTE: One way to distinguish a client from the organization that operates it is for each client to register the certificates and keys it uses: the subject distinguished name of its TLS client certificate using the `tls_client_auth_subject_dn` client metadata parameter [@RFC8705], and its signing keys at a `jwks_uri` [@RFC7591].
+## JARM Downgrade
+
+A client should reject the response if it requests a JARM [@JARM] response from an authorization server that advertises JARM support in its `response_modes_supported` metadata but receives the authorization response parameters, such as `code` and `state`, directly instead of in a `response` JWT.
+
## Access Token Size Considerations
As key size grows and more elements are added to access tokens, it's possible for the HTTP Authorization header containing the access token plus other headers to cumulatively be larger than the allowed buffer size for HTTP requests in many web infrastructure components. It is important to watch this closely via logging and alerting to ensure that production traffic is not adversely affected and that adjustments to the allowed buffer size can be made in a timely manner.
@@ -323,6 +327,19 @@ This document was developed by the OpenID FAPI Working Group.
+
+
+ JWT Secured Authorization Response Mode for OAuth 2.0 (JARM)
+
+ Yes
+
+
+ Ping
+
+
+
+
+
Recommendation for Key Management: Part 1 – General