From 1003e6e8ddc39ba10e27fc433c631fccd0266413 Mon Sep 17 00:00:00 2001 From: Yaron Sheffer Date: Tue, 15 Oct 2024 20:34:56 +0300 Subject: [PATCH] Update draft-ietf-wimse-s2s-protocol.md --- draft-ietf-wimse-s2s-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-wimse-s2s-protocol.md b/draft-ietf-wimse-s2s-protocol.md index c660603..96893fd 100644 --- a/draft-ietf-wimse-s2s-protocol.md +++ b/draft-ietf-wimse-s2s-protocol.md @@ -501,7 +501,7 @@ asynchronous communication scenarios, such as event-driven systems. - Message Signatures, on the other hand, benefit from an existing HTTP specific RFC with some established implementations. This existing groundwork means that this option could -be simpler to deploy, to the extent such implementations are available and easily integrated. +be simpler to deploy, to the extent such implementations are available and easily integrated. - Given that the WIT (Workload Identity Token) is a type of JWT, the DPoP-inspired approach that also uses JWT is less complex and technology-intensive than Message