From 7946bf26d149e19e2ea4fb476765d98ce1bf85e8 Mon Sep 17 00:00:00 2001 From: Bastian Krol Date: Mon, 6 Nov 2023 09:14:49 +0100 Subject: [PATCH] make wording around duplicate tracestate headers more precise Participants must not add duplicated tracestate keys, but they are not responsible for cleaning up duplicated tracestate keys that another updstream participant has added. fixes #548 --- spec/20-http_request_header_format.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/20-http_request_header_format.md b/spec/20-http_request_header_format.md index fe3c2b9..64e5f21 100644 --- a/spec/20-http_request_header_format.md +++ b/spec/20-http_request_header_format.md @@ -318,7 +318,7 @@ The `tracestate` value is the concatenation of trace graph key/value pairs. Example: `vendorname1=opaqueValue1,vendorname2=opaqueValue2` -Only one entry per key is allowed. For example, if a vendor name is Congo and a trace started in their system and then went through a system named Rojo and later returned to Congo, the `tracestate` value would not be: +Tracing tools are not supposed to add the same header multiple times. For example, if a vendor name is Congo and a trace started in their system and then went through a system named Rojo and later returned to Congo, the `tracestate` value would not be: `congo=congosFirstPosition,rojo=rojosFirstPosition,congo=congosSecondPosition`