- From: <sysbot+notifier@w3.org>
- Date: Tue, 28 Mar 2023 19:23:17 +0000
- To: public-transition-announce@w3.org
This is a transition request for a Candidate Recommendation CR Request for W3C TraceContext Level 2 Specification from https://github.com/w3c/transitions/issues/495 # Document title, URLs, estimated publication date Title: Trace Context Level 2 URL: https://w3c.github.io/trace-context/ (latest editors' draft) Estimated publication date: After approval (no other strong deadline). # Abstract This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios. The specification standardizes how context information is sent and modified between services. Context information uniquely identifies individual requests in a distributed system and also defines a means to add and propagate provider-specific context information. # Status Level 1 of this specification is already in Recommendation status since 2019. This is a minor incremental update to it called Trace Context Level 2: https://w3c.github.io/trace-context/ (latest editor's draft) https://www.w3.org/TR/trace-context-2/ (FPWD) # Link to group's decision to request transition We discussed this in the Distributed Tracing WG meeting on 03/28/2023. The group unanimously decided to request this transition. Meeting notes are at: https://docs.google.com/document/d/1EaY1zhmlOut4qZzpFue4vLc96_GrRWMtmzXYLfd1Ehc/edit#. # Changes The main changes are: - It introduces a new "flag" in the traceparent header called the random-trace-id flag. This is to indicate if the trace-id was generated randomly (or pseudo-randomly). - If the random-trace-id flag is set, at least the right-most 7 bytes of the trace-id MUST be randomly (or pseudo-randomly) generated. # Requirements satisfied No specific requirements document was created. # Dependencies met (or not) Please see next section. # Wide Review Yes the wide review was done (https://github.com/w3c/trace-context/issues/492) and issues have been addressed. # Issues addressed - Change the defining document for HTTP from RFC7230 to RFC9110 (https://github.com/w3c/trace-context/issues/519) - When headers should be propagated in browsers should be made more clear (https://github.com/w3c/trace-context/issues/510) - Adopt either span-id or parent-id for section headings (https://github.com/w3c/trace-context/issues/509) - Why should keys be restricted to lowercase ASCII? (https://github.com/w3c/trace-context/issues/508) - Version number relationship to ASCII and UTF-8 (https://github.com/w3c/trace-context/issues/507) - Specification of lowercase is incomplete (https://github.com/w3c/trace-context/issues/506) # Formal Objections None so far # Implementation https://github.com/open-telemetry/oteps/pull/226/ is an OpenTelemetry sampler specification enhancement proposal that references the above specification. Minimum CR duration: 3 months Exit criteria: At least 2 implementations adopting this specification and making use of it. The test suite will be updated as well. # Patent disclosures None -- This email was generated automatically using https://github.com/w3c/transition-issues-bot
Received on Tuesday, 28 March 2023 19:23:23 UTC