draft 06, incorporated pr see https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header-06#appendix-A

Author: sdatapix

draft-ietf-httpapi-idempotency-key-header.md

@@ -45,7 +45,7 @@ In mathematics and computer science, an idempotent operation is one that can be
 
 Idempotency is important in building fault-tolerant HTTP APIs. An HTTP request method is considered `idempotent` if the intended effect on the server of multiple identical requests with that method is the same as the effect for a single such request. Per {{!RFC9110}}, the methods `OPTIONS`, `HEAD`, `GET`, `PUT` and `DELETE` are idempotent while methods `POST` and `PATCH` are not.
 
-Let's say a client of an HTTP API wants to create (or update) a resource using a `POST` method. Repeating the request multiple times can result in duplication or incorrect updates. Consider a scenario where the client sent a `POST` request to the server, but the request timed out. The client is left uncertain about the status of the resource. It doesn't know if the resource was created or updated, or if the server even completed processing the request. Furthermore, the client does not know if it can safely retry the request. 
+Let's say a client of an HTTP API wants to create (or update) a resource using a `POST` method. Repeating the request multiple times can result in duplication or incorrect updates. Consider a scenario where the client sent a `POST` request to the server, but the request timed out. The client is left uncertain about the status of the resource. It doesn't know if the resource was created or updated, or if the server even completed processing the request. Furthermore, the client does not know if it can safely retry the request.
 
 
 ##  Notational Conventions
@@ -54,15 +54,15 @@ Let's say a client of an HTTP API wants to create (or update) a resource using a
 
 This specification uses the Augmented Backus-Naur Form (ABNF) notation of {{!RFC5234}} and includes, by reference, the IMF-fixdate rule as defined in Section 7.1.1.1 of {{!RFC7231}}.
 
-The term "resource" is to be interpreted as defined in Section 2 of {{!RFC7231}}, that is identified by an URI. 
+The term "resource" is to be interpreted as defined in Section 2 of {{!RFC7231}}, that is identified by an URI.
 
 # The Idempotency-Key HTTP Request Header Field
 
 An idempotency key is a unique value generated by the client which the resource uses to recognize subsequent retries of the same request. The `Idempotency-Key` HTTP request header field carries this value.
 
 ## Syntax
 
-`Idempotency-Key` is an Item Structured Header {{!RFC8941}}. Its value MUST be a String (Section 3.3.3 of {{!RFC8941}}). 
+`Idempotency-Key` is an Item Structured Header {{!RFC8941}}. Its value MUST be a String (Section 3.3.3 of {{!RFC8941}}).
 
 
 ## Uniqueness of Idempotency Key
@@ -359,9 +359,14 @@ Second example shows an idempotency-key header field with key value using a rand
 
     Idempotency-Key: "clkyoesmbgybucifusbbtdsbohtyuuwz"
 
-
 --- back
 
+# Changes from Draft-05 {#changes}
+
+This revision has made the following changes:
+  * Added change log starting from previous draft
+  * Correction in introduction
+  * Added an implementer
 
 # Acknowledgments
 {:numbered="false"}