Rename the header to Baggage

[SergeyKanzhelev]

this is an alternative proposal to #13. During the workshop today there was a proposal to rename header to the Baggage. Creating issue to discuss this proposal

[dyladan]

I would definitely prefer this to correlationcontext. If we're going to change the name, then there is no reason to keep the long two-word format.

[mtwo]

I am indifferent towards the name that we choose

[SergeyKanzhelev]

Please see this document for more context: https://docs.google.com/document/d/1Crnp9XguH3BY5b1hcAV2QNiHZV0SKyIuC3moZgdpgiE/edit#

[shakuzen]

What about baggage? It would avoid issues with protocols that do not support case sensitivity - same reasoning as traceparent and tracestate.

[codefromthecrypt]

We should get buy in from @JonathanMace and/or @rfonseca as I believe the term Baggage was coined at Brown University with a different meaning albeit propagation related. This is less about this header being used for something lightly inspired by Baggage, rather any unlikely IP concerns that might exist

https://groups.google.com/forum/#!msg/distributed-tracing/m2ztbNAPsjY/4-mQkrfvBwAJ

[codefromthecrypt]

There's some baggage around the term baggage, but it has some weight to it.

I know the tracing inner circle is familiar with the name baggage, as it was suggested to b3 some time back openzipkin/b3-propagation#22

Some end users may also be familiar with this as spring-cloud-sleuth uses a similar terminology from the early days of OpenTracing. https://cloud.spring.io/spring-cloud-sleuth/reference/html/#propagating-span-context

[JonathanMace]

There's some baggage around the term baggage, but it has some weight to it.

🤦‍♂

Baggage is an appropriate alternative name for correlation context, and it would be consistent with the way that other distributed tracing tools (Jaeger, OpenTracing) use the term (since they also use it to refer to K-V pairs).

Originally we picked the name baggage to refer to "arbitrary stuff" that you propagate with a request because we liked the metaphor. In this case the metaphor is the same, so I don't see why not to call it baggage.

For some background on baggage:

1. We first introduced it in Pivot Tracing as maps, sets and tuples.
2. We then spun baggage out as a standalone component that we called BaggageContext and considered some of the nuances of making it general purpose.

It's true that the implementations we proposed in these papers are different to the K-V pair implementation proposed here, but conceptually the goal is the same.

[dyladan]

Personally, I would suggest baggage (all lowercase) as it is consistent with the naming/casing of the other specs this WG is working on, it is short, and it conveys the meaning in a clear and obvious way.

[yurishkuro]

+1 for baggage

[discostu105]

+1 for baggage as well

[rfonseca]

Hi all, I second what Jonathan said above. The only other thing I want to add is that there is absolutely no IP issue, the term and use was introduced in published work, with no encumbrances or claims of intellectual property. Eventually, when use cases arise when baggage from different paths have to end up merging, the BaggageContex paper describes ways of implementing this allowing for different ways to merge (set union, max, min, last, etc), in a generic way. Glad to see this moving forward! Best, Rodrigo

…

On Fri, Mar 27, 2020 at 9:50 AM Christoph Neumüller < ***@***.***> wrote: +1 for baggage as well — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABHZR5OYW25GLAW2OJNCFTRJTKMBANCNFSM4LUBF7BQ> .

[mwear]

+1 to baggage as well. A single word header avoids the pitfalls of a longer concatenated header, or one with a -.

[codefromthecrypt]

I thumbs upped the original suggestion to use baggage, but doing more explicitly here +1

Thanks @JonathanMace and @rfonseca for clearing the name! I recall the SPDY days which turned into http/2 over name related stuff. nice to be able to avoid that.

[codefromthecrypt]

FYI: In Zipkin Brave we'll rename our stuff around baggage naming, since it is general purpose now. will slide into concepts here nicely.