trace-context
trace-context copied to clipboard
w3c
Trace Context
`Privacy of traceparent field` section incorrectly states that `trace-id` is randomly generated. Section should be modified such that PII in trace ids is discouraged or forbidden, and randomness suggested as...
The [Limits Section](https://w3c.github.io/baggage/#limits) in the Baggage Propagation document specifies the following: > 1. A platform MUST propagate all list-members up to at least 64 list-members including any list-members added by...
…1 spec I wanted to draft this to propose it as an alternative to the https://github.com/w3c/trace-context/pull/474. As discussed before, spec already had all suggestions to generate randomness and keep it...
Update wording on "response headers" in privacy section to disambiguate from traceresponse headers.
Should we remove this from the Level 1 spec? Section 6.3 in https://www.w3.org/TR/trace-context/?msclkid=8fb94facc59711eca3572297845ae7e1#other-risks "When vendors include traceparent and tracestate headers in responses, these values may inadvertently be passed to cross-origin...
While making changes on both this repo and on baggage, I noticed that our text style is quite inconsistent. I would like to try to make some decisions on our...
One issue that is frequently raised with response headers is the absence of a mechanism similar to tracestate which can be used to return tracing-system-specific information to the caller. As...
The term "call" is used in several places, but its meaning might be a little hard to understand (e.g. in [the security section](https://github.com/w3c/trace-context/blob/master/spec/51-security.md)).
As discussed in https://docs.google.com/document/d/1Gr9QD6kt3_DcxRJSFpuoqWWMAJMRqCGd1kPcroNUyh8/edit?pli=1#heading=h.q99n7jrc8dcc, we want to add general text protocols to the spec. FYI @plehegar @mtwo @SergeyKanzhelev
I admit I wrote the initial example which was about multiple fictitious vendors rojo and congo, proxies for cloud vendors in the room at one point, nothing more. It probably...
See https://lists.w3.org/Archives/Public/public-trace-context/2020Feb/0004.html This spec is intended for vendors who operate distributed tracing systems (or operate distributed systems and want to use or connect to distributed tracing systems) and this protocol...