You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other comments: What: The main difference from Trace Context Level 1 (which is already in recommendation status) is the ability to express whether at least a part of the traceID has been randomly (or pseudo-randomly) generated. Why: This enables downstream systems to use the trace ID for sampling purposes or for sharding purposes. How: This is achieved by the introduction of a new flag called "Random Trace ID flag". If the newly introduced random-trace-id flag is set, at least the right-most 7 bytes of the trace-id MUST be randomly (or pseudo-randomly) generated.
The text was updated successfully, but these errors were encountered:
The Privacy IG prefers groups to complete a self-review around the time of FPWD. See https://w3ctag.github.io/security-questionnaire/.
If you still want us to review your spec, please provide the information below.
In the issue title above add the document name followed by the date of this request.
Explainer: https://github.com/w3c/distributed-tracing-wg/blob/main/EXPLAINER.md.
Other comments:
What: The main difference from Trace Context Level 1 (which is already in recommendation status) is the ability to express whether at least a part of the traceID has been randomly (or pseudo-randomly) generated.
Why: This enables downstream systems to use the trace ID for sampling purposes or for sharding purposes.
How: This is achieved by the introduction of a new flag called "Random Trace ID flag". If the newly introduced random-trace-id flag is set, at least the right-most 7 bytes of the trace-id MUST be randomly (or pseudo-randomly) generated.
The text was updated successfully, but these errors were encountered: