[w3ctag/design-reviews] Distributed Tracing WG: Baggage specification TAG review (#650)

Ya ya yawm TAG!

I'm requesting a TAG review of Baggage specification

Baggage is a header format and behavior specification that enables scenarios of opaque values propagation along the distributed trace. Distributed Trace can spawn across multiple components and types of servers: browsers, proxies and
load balancers, server applications, and SaaS services. Baggage from incoming request is propagated to all related outgoing calls. This enables many inter-operability scenarios for end users when monitoring and troubleshooting highly distributed applications. There is a lot of prior art in a form of vendor-specific headers, this specification solves the interoperability issue when many app components may not be controlled by the end user.

  - Explainer (minimally containing user needs and example code): https://github.com/w3c/distributed-tracing-wg/blob/main/EXPLAINER.md

  - Specification URL: https://w3c.github.io/baggage/

  - Tests: WIP
  - Security and Privacy self-review²: WIP
  - GitHub repo (if you prefer feedback filed there): https://github.com/w3c/baggage/

  - Primary contacts (and their relationship to the specification):
      - [Sergey Kanzhelev](https://github.com/SergeyKanzhelev), [Google], editor
      - [Daniel Khan](https://github.com/danielkhan), [Dynatrace], editor 
  - Organization(s)/project(s) driving the specification: 
  - Key pieces of existing multi-stakeholder review or discussion of this specification:
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://github.com/w3c/baggage/issues


Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: we want to get to CR this calendar year
  - The group where the work on this specification is currently being done: [Distributed Tracing Working Group](https://www.w3.org/groups/wg/distributed-tracing)
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): [Distributed Tracing Working Group](https://www.w3.org/groups/wg/distributed-tracing)
  - Major unresolved issues with or opposition to this specification: none
  - This work is being funded by: multiple companies

You should also know that...

Previous form of this specification is built-in into [ASP.NET framework](https://devblogs.microsoft.com/aspnet/improvements-in-net-core-3-0-for-troubleshooting-and-monitoring-distributed-apps/#passing-additional-context), current version of specification is implemented by many [OpenTelemetry](https://opentelemetry.io/) SDKs.

We found that it is great to have predictability in which field is being automatically propagated as it increases transparency for end-user, as oppose to numerous vendor-specific headers.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  🐛 open issues in our GitHub repo for **each point of feedback**


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/650