From e63d6c353c54bcb03be31c8501ebb7ecd83ac125 Mon Sep 17 00:00:00 2001 From: Yaron Sheffer Date: Tue, 15 Oct 2024 20:32:18 +0300 Subject: [PATCH] Update draft-ietf-wimse-s2s-protocol.md Co-authored-by: Brian Campbell <71398439+bc-pi@users.noreply.github.com> --- draft-ietf-wimse-s2s-protocol.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-wimse-s2s-protocol.md b/draft-ietf-wimse-s2s-protocol.md index 892142e..0f6c793 100644 --- a/draft-ietf-wimse-s2s-protocol.md +++ b/draft-ietf-wimse-s2s-protocol.md @@ -499,9 +499,9 @@ complexity, extensibility and security. Here is a summary of the main difference other protocols beyond HTTP. This flexibility is particularly valuable for asynchronous communication scenarios, such as event-driven systems. -- Message Signatures, on the other hand, benefit from an existing RFC with -established implementations. This existing groundwork means that this option could -be simpler to deploy. +- 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. - Given that the WIT (Workload Identity Token) is a type of JWT, the DPoP-inspired approach is less complex and technology-intensive than Message