From 2d610154e116e9d9aceb08319401bea3661740b7 Mon Sep 17 00:00:00 2001
From: Arndt Schwenkschuster <17650715+arndt-s@users.noreply.github.com>
Date: Wed, 13 Nov 2024 14:25:34 +0000
Subject: [PATCH] add document history

---
 draft-ietf-wimse-workload-identity-bcp.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/draft-ietf-wimse-workload-identity-bcp.md b/draft-ietf-wimse-workload-identity-bcp.md
index a524ac1..0003711 100644
--- a/draft-ietf-wimse-workload-identity-bcp.md
+++ b/draft-ietf-wimse-workload-identity-bcp.md
@@ -544,3 +544,26 @@ In this case, technically, the protected resource and workload are part of the s
 ## Custom assertion flows
 
 While {{RFC7521}} and {{RFC7523}} are the proposed standards for this pattern, some authorization servers use {{RFC8693}} or a custom API for the issuance of an access token based on an existing platform identity credentials. These pattern are not recommended and prevent interoperability.
+
+# Document History
+
+   [[ To be removed from the final specification ]]
+
+   -02
+
+   * Move scope from Kubernetes to generic workload identity platform
+   * Add various patterns to appendix
+      * Kubernetes
+      * Cloud providers
+      * SPIFFE
+      * CI/CD
+   * Add some security considerations
+   * Update title
+
+   -01
+
+   * Editorial updates
+
+   -00
+
+   * Adopted by the WIMSE WG