From 3b072c35278d38626c039941e066fb92c9a2b524 Mon Sep 17 00:00:00 2001 From: Dave Tonge Date: Wed, 28 Oct 2026 14:18:26 +0100 Subject: [PATCH 1/2] Cite RFC 9562 for UUID values RFC 9562 obsoletes RFC 4122. The second clause also used a plain [RFC4122] label that did not render as a reference. Refs #487 --- FAPI_2_0_Implementation_Advice.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/FAPI_2_0_Implementation_Advice.md b/FAPI_2_0_Implementation_Advice.md index e1432aa..ac345f8 100644 --- a/FAPI_2_0_Implementation_Advice.md +++ b/FAPI_2_0_Implementation_Advice.md @@ -87,8 +87,8 @@ the following clauses apply: 1. clients shall send the `x-fapi-interaction-id` request header, the value shall be a -RFC4122 UUID, e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; -1. the AS or RS shall set the response header `x-fapi-interaction-id` to the value received from the corresponding FAPI client request header or to a [RFC4122] UUID value if the request header was not provided to track the interaction, e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; +UUID [@RFC9562], e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; +1. the AS or RS shall set the response header `x-fapi-interaction-id` to the value received from the corresponding FAPI client request header or to a UUID [@RFC9562] value if the request header was not provided to track the interaction, e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; 1. participants (whether Client, AS or RS) shall log the value of `x-fapi-interaction-id` in the log entry. NOTE: Clients may reuse the same `x-fapi-interaction-id` value across related requests within From 3b09a039deb85b955f57c4b3c7dfef4eeb7a6a18 Mon Sep 17 00:00:00 2001 From: Dave Tonge Date: Wed, 28 Oct 2026 14:18:38 +0100 Subject: [PATCH 2/2] Only echo interaction ids that are UUIDs Only copy the client's value into the response header when it is a UUID, otherwise use a new UUID as for a missing header. The FAPI 1.0 errata is not covered. Refs #487 --- FAPI_2_0_Implementation_Advice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAPI_2_0_Implementation_Advice.md b/FAPI_2_0_Implementation_Advice.md index ac345f8..474ced6 100644 --- a/FAPI_2_0_Implementation_Advice.md +++ b/FAPI_2_0_Implementation_Advice.md @@ -88,7 +88,7 @@ the following clauses apply: 1. clients shall send the `x-fapi-interaction-id` request header, the value shall be a UUID [@RFC9562], e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; -1. the AS or RS shall set the response header `x-fapi-interaction-id` to the value received from the corresponding FAPI client request header or to a UUID [@RFC9562] value if the request header was not provided to track the interaction, e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; +1. the AS or RS shall set the response header `x-fapi-interaction-id` to the value received from the corresponding FAPI client request header if that value is a UUID [@RFC9562], or otherwise to a new UUID [@RFC9562] value to track the interaction, e.g., `x-fapi-interaction-id: c770aef3-6784-41f7-8e0e-ff5f97bddb3a`; 1. participants (whether Client, AS or RS) shall log the value of `x-fapi-interaction-id` in the log entry. NOTE: Clients may reuse the same `x-fapi-interaction-id` value across related requests within