Distributed Tracing Working Group - Activity in 2022
No matches.
Past meetings
GitHub
w3c/baggage
-
1 issue received 1 new comment.
-
1 pull request received 2 new comments.
-
Add note that applications using baggage must be aware that data can be propagated to other systems w3c/baggage#111 (2 comments by @kalyanaj, @pes10k)
-
w3c/distributed-tracing-wg
-
1 pull request opened.
-
Clarify that browsers are not the target implementation for the W3C TraceContext specification w3c/distributed-tracing-wg#50, by @kalyanaj.
-
-
1 pull request received 2 new comments.
-
Clarify that browsers are not the target implementation for the W3C TraceContext specification w3c/distributed-tracing-wg#50 (2 comments by @kalyanaj, @yurishkuro)
-
w3c/trace-context
-
3 issues closed.
-
Version number relationship to ASCII and UTF-8 w3c/trace-context#507.
-
specification of lowercase is incomplete w3c/trace-context#506.
-
Why should keys be restricted to lowercase ASCII? w3c/trace-context#508.
-
-
4 issues received 9 new comments.
-
Why should keys be restricted to lowercase ASCII? w3c/trace-context#508 (5 comments by @aphillips, @basti1302)
-
Trace Context: Apache Kafka protocol specification w3c/trace-context#504 (2 comments by @kalyanaj, @ppatierno)
-
-
8 pull requests opened.
-
improve wording for casing of request header names w3c/trace-context#518, by @basti1302.
-
improve description of version field in traceparent request header w3c/trace-context#517, by @basti1302.
-
Incorporate feedback from privacy review. Resolves #510. w3c/trace-context#516, by @kalyanaj.
-
add reasoning for the restriction of tracestate keys w3c/trace-context#515, by @basti1302.
-
improve wording for casing of response header name w3c/trace-context#514, by @basti1302.
-
improve wording for casing of request header names w3c/trace-context#513, by @basti1302.
-
improve description of version field in traceresponse header w3c/trace-context#512, by @basti1302.
-
improve description of version field in traceparent request header w3c/trace-context#511, by @basti1302.
-
-
4 pull requests merged.
-
improve description of version field in traceparent request header w3c/trace-context#511.
-
improve wording for casing of request header names w3c/trace-context#513.
-
improve description of version field in traceresponse header w3c/trace-context#512.
-
improve wording for casing of response header name w3c/trace-context#514.
-
-
1 pull request closed.
-
add reasoning for the restriction of tracestate keys w3c/trace-context#515.
-
-
5 pull requests received 23 new comments.
-
add reasoning for the restriction of tracestate keys w3c/trace-context#515 (8 comments by @aphillips, @basti1302)
-
improve description of version field in traceparent request header w3c/trace-context#511 (6 comments by @basti1302, @dyladan, @kalyanaj)
-
improve description of version field in traceresponse header w3c/trace-context#512 (5 comments by @basti1302, @dyladan)
-
improve wording for casing of response header name w3c/trace-context#514 (2 comments by @basti1302, @dyladan)
-
improve wording for casing of request header names w3c/trace-context#513 (2 comments by @basti1302, @dyladan)
-
Past meetings
GitHub
w3c/trace-context
-
2 issues opened.
-
When headers should be propagated in browsers should be made more clear w3c/trace-context#510, by @pes10k.
-
Adopt either span-id or parent-id for section headings w3c/trace-context#509, by @pes10k.
-
-
3 issues closed.
-
Adopt either span-id or parent-id for section headings w3c/trace-context#509.
-
Trace Context Level 2: Self-review for accessibility w3c/trace-context#499.
-
-
5 issues received 11 new comments.
-
Adopt either span-id or parent-id for section headings w3c/trace-context#509 (4 comments by @kalyanaj, @pes10k, @yurishkuro)
-
specification of lowercase is incomplete w3c/trace-context#506 (2 comments by @aphillips, @kalyanaj)
-
Why should keys be restricted to lowercase ASCII? w3c/trace-context#508 (2 comments by @aphillips, @kalyanaj)
-
When headers should be propagated in browsers should be made more clear w3c/trace-context#510 (2 comments by @kalyanaj, @pes10k)
-
-
3 pull requests merged.
-
Add test case for random flag propagation w3c/trace-context#500.
-
Updated the flags description in version format w3c/trace-context#505.
-
1 pull request closed.
-
An alternative proposal on implementing randomness by updating level … w3c/trace-context#480.
-
-
2 pull requests received 4 new comments.
-
Add test case for random flag propagation w3c/trace-context#500 (3 comments by @reyang, @TimothyMothra)
-
An alternative proposal on implementing randomness by updating level … w3c/trace-context#480 (1 comment by @kalyanaj)
-
w3c/baggage
-
1 issue closed.
-
1 pull request merged.
-
Update rationale with text that applies to lower limits w3c/baggage#114.
-
-
1 pull request received 4 new comments.
-
Add note that applications using baggage must be aware that data can be propagated to other systems w3c/baggage#111 (4 comments by @kalyanaj, @pes10k)
-
Past meetings
Participants
-
1 participant left.
-
Aaron Young (IBM Corporation) left.
-
GitHub
w3c/baggage
-
1 issue opened.
-
Clarification on how baggage should be propagated when using websockets w3c/baggage#115, by @mediocregopher.
-
-
3 issues closed.
-
Clarify Baggage Propagation Limits w3c/baggage#108.
-
2 issues received 3 new comments.
-
Clarification on how baggage should be propagated when using websockets w3c/baggage#115 (2 comments by @basti1302, @mediocregopher)
-
-
1 pull request opened.
-
Update rationale with text that applies to lower limits w3c/baggage#114, by @dyladan.
-
-
1 pull request merged.
-
Clarify what happens when limits are violated w3c/baggage#113.
-
-
2 pull requests received 4 new comments.
-
Add note that applications using baggage must be aware that data can be propagated to other systems w3c/baggage#111 (3 comments by @kalyanaj, @pes10k)
-
w3c/trace-context
-
6 issues opened.
-
Why should keys be restricted to lowercase ASCII? w3c/trace-context#508, by @aphillips.
-
Version number relationship to ASCII and UTF-8 w3c/trace-context#507, by @aphillips.
-
specification of lowercase is incomplete w3c/trace-context#506, by @aphillips.
-
Trace Context: Apache Kafka protocol specification w3c/trace-context#504, by @ppatierno.
-
Request to republish level-1 spec (to publish a recent editorial change) w3c/trace-context#503, by @kalyanaj.
-
Enable automatic publishing for Level 2 branch w3c/trace-context#502, by @kalyanaj.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Updated the flags description in version format w3c/trace-context#505, by @kalyanaj.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#501, by @dyladan.
-
Add test case for random flag propagation w3c/trace-context#500, by @dyladan.
-
-
2 pull requests merged.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#495.
-
Level 2 tweaks w3c/trace-context#497.
-
-
1 pull request closed.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#501.
-
-
3 pull requests received 13 new comments.
-
Add test case for random flag propagation w3c/trace-context#500 (10 comments by @basti1302, @dyladan, @kalyanaj)
-
Updated the flags description in version format w3c/trace-context#505 (2 comments by @basti1302, @yurishkuro)
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#501 (1 comment by @kalyanaj)
-
w3c/distributed-tracing-wg
-
1 pull request opened.
-
Add a markdown style guide w3c/distributed-tracing-wg#49, by @dyladan.
-
-
1 pull request received 7 new comments.
TR publications
-
3 documents published.
-
Propagation format for distributed context: Baggage published twice as a Working Draft. History of Propagation format for distributed context: Baggage
-
Trace Context Level 2 published as a First Public Working Draft. History of Trace Context Level 2
-
Past meetings
GitHub
w3c/baggage
-
1 issue opened.
-
4 issues closed.
-
Relationship to other HTTP Header encoding proposals w3c/baggage#106.
-
Clarify in text the relationship to Trace Context w3c/baggage#105.
-
Remove optional whitespace w3c/baggage#53.
-
i18n review checklist for baggage w3c/baggage#93.
-
-
8 issues received 12 new comments.
-
Relationship to other HTTP Header encoding proposals w3c/baggage#106 (4 comments by @basti1302, @kalyanaj, @pes10k)
-
Need to update the limits section in rationale to be in sync with the new lower limits w3c/baggage#112 (1 comment by @kalyanaj)
-
limitations do not appear to have standard implementation for enforcement w3c/baggage#30 (1 comment by @dyladan)
-
-
4 pull requests opened.
-
Clarify what happens when limits are violated w3c/baggage#113, by @dyladan.
-
Specify Relationship to other HTTP Header encoding proposals. w3c/baggage#110, by @kalyanaj.
-
-
2 pull requests merged.
-
Specify Relationship to other HTTP Header encoding proposals. w3c/baggage#110.
-
-
4 pull requests received 14 new comments.
-
Clarify what happens when limits are violated w3c/baggage#113 (7 comments by @kalyanaj, @yurishkuro)
-
Add note that applications using baggage must be aware that data can be propagated to other systems w3c/baggage#111 (3 comments by @dyladan, @yurishkuro)
-
Specify Relationship to other HTTP Header encoding proposals. w3c/baggage#110 (2 comments by @basti1302, @kalyanaj)
-
Provide clarification for how this specification is different from TraceContext. w3c/baggage#109 (2 comments by @yurishkuro)
-
w3c/trace-context
-
5 issues opened.
-
Trace Context Level 2: Self-review for accessibility w3c/trace-context#499, by @kalyanaj.
-
Trace Context Level 2: Self review for i18n w3c/trace-context#498, by @kalyanaj.
-
Self-Review Questionnaire for Trace Context Level 2: Security and Privacy w3c/trace-context#496, by @kalyanaj.
-
Need to publish latest draft of trace-context-2 w3c/trace-context#493, by @kalyanaj.
-
Start Wide Review for Trace Context Level 2 Spec w3c/trace-context#492, by @kalyanaj.
-
-
1 issue closed.
-
Need to publish latest draft of trace-context-2 w3c/trace-context#493.
-
-
3 issues received 8 new comments.
-
Need to publish latest draft of trace-context-2 w3c/trace-context#493 (3 comments by @kalyanaj, @plehegar)
-
Update wording on "response headers" in privacy section to disambiguate from traceresponse headers. w3c/trace-context#487 (1 comment by @kalyanaj)
-
4 pull requests opened.
-
Level 2 tweaks w3c/trace-context#497, by @plehegar.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#495, by @dyladan.
-
Remove contradiction in TraceState mutations #428 w3c/trace-context#494, by @dyladan.
-
-
1 pull request closed.
-
Remove contradiction in TraceState mutations #428 w3c/trace-context#494.
-
-
2 pull requests received 5 new comments.
-
Resolves #487: Update wording on "response headers" in privacy section to disambiguate from traceresponse headers. w3c/trace-context#491 (4 comments by @basti1302, @kalyanaj)
-
Past meetings
GitHub
w3c/baggage
-
2 issues closed.
-
RFC 8941 w3c/baggage#104.
-
Spec title should not mention "tracing" w3c/baggage#96.
-
-
2 issues received 2 new comments.
Past meetings
GitHub
w3c/baggage
-
4 issues opened.
-
Make trust/privacy boundary explicit (at least in browsers) w3c/baggage#107, by @pes10k.
-
Relationship to other HTTP Header encoding proposals w3c/baggage#106, by @pes10k.
-
Clarify in text the relationship to Trace Context w3c/baggage#105, by @pes10k.
-
RFC 8941 w3c/baggage#104, by @martinthomson.
-
-
2 issues received 5 new comments.
-
Relationship to other HTTP Header encoding proposals w3c/baggage#106 (4 comments by @martinthomson, @pes10k, @yurishkuro)
-
TR publications
-
2 documents published.
-
Propagation format for distributed context: Baggage published twice as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
-
1 meeting.
Participants
-
1 organization left.
-
ZIIOT left.
-
GitHub
w3c/trace-context
-
2 pull requests opened.
-
Fix typo in "however" w3c/trace-context#490, by @mwalser.
-
Update implementations.md with Kamon.io w3c/trace-context#489, by @lzhuor.
-
-
3 pull requests merged.
-
Fix typo in "however" w3c/trace-context#490.
-
Update implementations.md with Kamon.io w3c/trace-context#489.
-
Remove response headers for level-2 w3c/trace-context#484.
-
-
1 pull request reopened.
-
Update implementations.md with Kamon.io w3c/trace-context#489, by @lzhuor.
-
-
2 pull requests received 3 new comments.
w3c/baggage
-
2 issues closed.
-
no non-ASCII examples w3c/baggage#98.
-
UTF-8 encoding of value should be more clearly defined w3c/baggage#100.
-
-
4 issues received 7 new comments.
-
3 pull requests opened.
-
ReSpec fix w3c/baggage#103, by @xfq.
-
Resolves #100 (UTF-8 encoding of value should be more clearly defined). w3c/baggage#101, by @kalyanaj.
-
-
3 pull requests merged.
-
ReSpec fix w3c/baggage#103.
-
-
1 pull request received 1 new comment.
-
Resolves #100 (UTF-8 encoding of value should be more clearly defined). w3c/baggage#101 (1 comment by @aphillips)
-
TR publications
-
1 document published.
-
Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
Participants
-
1 Team contact appointed.
-
Philippe Le Hegaret became a Team contact.
-
-
1 Team contact stepped down.
-
Philippe Le Hegaret stepped down as a Team contact.
-
-
1 participant joined.
-
Philippe Le Hegaret (W3C) joined.
-
-
1 participant left.
-
Philippe Le Hegaret (W3C) left.
-
GitHub
w3c/baggage
-
3 issues opened.
-
UTF-8 encoding of value should be more clearly defined w3c/baggage#100, by @aphillips.
-
Keys don't permit non-ASCII? w3c/baggage#99, by @aphillips.
-
no non-ASCII examples w3c/baggage#98, by @aphillips.
-
-
1 issue closed.
-
Self-review for accessibility w3c/baggage#94.
-
-
3 issues received 4 new comments.
-
1 pull request opened.
-
Updated title to reflect that this specification is for distributed context w3c/baggage#97, by @kalyanaj.
-
-
1 pull request merged.
-
1 pull request received 3 new comments.
-
Updated title to reflect that this specification is for distributed context w3c/baggage#97 (3 comments by @kalyanaj, @yurishkuro)
-
w3c/trace-interchange-format
-
1 pull request merged.
-
chore: use groups shortnames, and other refresh w3c/trace-interchange-format#1.
-
w3c/trace-context
-
1 pull request received 1 new comment.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#482 (1 comment by @plehegar)
-
TR publications
-
3 documents published.
-
Propagation format for distributed trace context: Baggage published 3 times as a Working Draft. History of Propagation format for distributed trace context: Baggage
-
Past meetings
GitHub
w3c/baggage
-
5 issues opened.
-
Spec title should not mention "tracing" w3c/baggage#96, by @yurishkuro.
-
Self-Review Questionnaire: Security and Privacy w3c/baggage#95, by @kalyanaj.
-
Self-review for accessibility w3c/baggage#94, by @kalyanaj.
-
Clarify Baggage Propagation Limits w3c/baggage#108, by @dpauls.
-
i18n review checklist for baggage w3c/baggage#93, by @kalyanaj.
-
-
6 issues closed.
-
Create a test as a reference implementation w3c/baggage#74.
-
Requirement to strip OWS out of scope w3c/baggage#58.
-
Reference the relevant RFC for URL encoding baggage values w3c/baggage#81.
-
Different behaviour in private browsing/incognito mode? w3c/baggage#84.
-
Consider lowering baggage limits w3c/baggage#65.
-
-
6 issues received 6 new comments.
-
limitations do not appear to have standard implementation for enforcement w3c/baggage#30 (1 comment by @kalyanaj)
-
Name 'baggage' is a metaphor and could be hard for non-native English speakers w3c/baggage#83 (1 comment by @kalyanaj)
-
-
1 pull request opened.
-
Define RFC for percent-encoding w3c/baggage#92, by @dyladan.
-
-
5 pull requests merged.
-
Create a baggage reference implementation w3c/baggage#86.
-
Define RFC for percent-encoding w3c/baggage#92.
-
Use a more descriptive sentence instead of "opaque" w3c/baggage#88.
-
Define lower bounds for header limits w3c/baggage#89.
-
Remove unenforceable requirement to strip whitespace w3c/baggage#87.
-
-
4 pull requests received 10 new comments.
-
Use a more descriptive sentence instead of "opaque" w3c/baggage#88 (2 comments by @dyladan, @SergeyKanzhelev)
w3c/trace-context
-
2 issues opened.
-
Update wording on "response headers" in privacy section to disambiguate from traceresponse headers. w3c/trace-context#487, by @kalyanaj.
-
Inconsistent text style w3c/trace-context#485, by @dyladan.
-
-
1 issue closed.
-
Randomness flag bit w3c/trace-context#467.
-
-
2 issues received 3 new comments.
-
2 pull requests opened.
-
cherry-pick: Add the random trace id flag (#474) w3c/trace-context#486, by @dyladan.
-
Remove response headers for level-2 w3c/trace-context#484, by @dyladan.
-
-
2 pull requests merged.
-
cherry-pick: Add the random trace id flag (#474) w3c/trace-context#486.
-
Add the random trace id flag w3c/trace-context#474.
-
-
4 pull requests received 24 new comments.
-
Add the random trace id flag w3c/trace-context#474 (14 comments by @dyladan, @kalyanaj, @SergeyKanzhelev, @yurishkuro)
-
An alternative proposal on implementing randomness by updating level … w3c/trace-context#480 (1 comment by @bogdandrutu)
-
TR publications
-
1 document published.
Past meetings
GitHub
w3c/trace-context
-
1 issue opened.
-
tracestate response header proposal w3c/trace-context#483, by @dyladan.
-
-
2 issues closed.
-
IETF/IANA registration of header fields w3c/trace-context#120.
-
ABNF improvement w3c/trace-context#364.
-
-
2 issues received 7 new comments.
w3c/baggage
-
1 issue opened.
-
Wide review w3c/baggage#91, by @plehegar.
-
-
2 issues received 3 new comments.
-
5 pull requests opened.
-
chore: use group shortnames w3c/baggage#90, by @plehegar.
-
Define lower bounds for header limits w3c/baggage#89, by @dyladan.
-
Use a more descriptive sentence instead of "opaque" w3c/baggage#88, by @dyladan.
-
Remove unenforceable requirement to strip whitespace w3c/baggage#87, by @dyladan.
-
Create a baggage reference implementation w3c/baggage#86, by @dyladan.
-
-
1 pull request merged.
-
chore: use group shortnames w3c/baggage#90.
-
-
4 pull requests received 11 new comments.
-
Define lower bounds for header limits w3c/baggage#89 (5 comments by @dyladan, @kalyanaj, @SergeyKanzhelev)
-
w3c/trace-interchange-format
-
1 pull request opened.
-
chore: use groups shortnames, and other refresh w3c/trace-interchange-format#1, by @plehegar.
-
Past meetings
GitHub
w3c/baggage
-
1 issue received 1 new comment.
-
Reference the relevant RFC for URL encoding baggage values w3c/baggage#81 (1 comment by @SergeyKanzhelev)
-
TR publications
-
1 document published.
Past meetings
GitHub
w3c/baggage
-
1 issue closed.
-
3 issues received 4 new comments.
-
Different behaviour in private browsing/incognito mode? w3c/baggage#84 (1 comment by @SergeyKanzhelev)
-
Name 'baggage' is a metaphor and could be hard for non-native English speakers w3c/baggage#83 (1 comment by @kalyanaj)
-
1 pull request merged.
w3c/trace-context
-
1 issue opened.
-
Incorrect randomness claim in 50-privacy.md w3c/trace-context#481, by @dyladan.
-
-
3 issues closed.
-
Clarify handling of duplicate keys in tracestate w3c/trace-context#369.
-
Clarify tracestate keys MUST be unique w3c/trace-context#446.
-
Expected behavior with regard to starting a trace should be spelled out explicitly w3c/trace-context#442.
-
-
2 issues received 2 new comments.
-
w3c/trace-context#120 (1 comment by @kalyanaj)
-
-
1 pull request opened.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#482, by @dyladan.
-
-
3 pull requests merged.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#482.
-
Specify uniqueness of tracestate keys as the sender's responsibility w3c/trace-context#477.
-
Specify expected behaviour when no traceparent is received w3c/trace-context#475.
-
-
1 pull request received 3 new comments.
-
Remove incorrect randomness claim from privacy considerations w3c/trace-context#482 (3 comments by @dyladan, @kalyanaj)
-