Joshua MacDonald

As an example of what this is hoping to clarify, see https://github.com/open-telemetry/opentelemetry-go/issues/5030

@kalyanaj I've updated this PR to reflect the reality of the W3C trace context specification regarding unknown flags. The PR itself is much less important, as a result, but still...

I may not re-open this; it serves very little purpose in its current form. It shows we need work on #1929.

@kentquirk @oertl @PeterF778 @kalyanaj Please take a look. I believe a bit more prototyping will be required, so I leave this open as a draft PR. I am looking to...

@kentquirk @oertl @PeterF778 @kalyanaj TL;DR I found about half of the text in the old, experimental specification to be overkill and removed a lot of it. If you see something...

I have a couple of concern about the absence of an explicit statement about `tracestate`, which is usually mentioned in the list of W3C trace context fields. In this case,...

Related: https://github.com/open-telemetry/opentelemetry-specification/pull/3924

@carlos I thought we should merge #3923 before merging this one. #3924 is related but not a prereq

@carlosalberto please see https://github.com/open-telemetry/opentelemetry-specification/pull/3923#discussion_r1538294693, thanks!

I support the statement by @reyang -- we should ensure the default behavior with cumulative aggregation matches Prometheus. I agree with @MrAlias that the "unfairness" is intentional, that the specified...