Distributed Tracing Working Group - Activity in 2023

Past meetings

• 1 meeting.

  • 5 December 2023

    Distributed Tracing Working Group bi-weekly, 5 December 2023. Minutes.

GitHub

w3c/baggage

• 1 issue opened.

  • 20 December 2023

    Precent character in value must be precent-encoded w3c/baggage#124, by @pellared.

• 1 pull request opened.

  • 20 December 2023

    Percent character in value MUST be percent-encoded w3c/baggage#125, by @pellared.

• 1 pull request received 4 new comments.

  • Latest comment 21 December 2023

    Percent character in value MUST be percent-encoded w3c/baggage#125 (4 comments by @MrAlias, @pellared, @w3cbot)

w3c/trace-context

• 1 issue closed.

  • 14 December 2023

    Add more normative text for flags processing in traceresponse w3c/trace-context#540.

• 4 issues received 7 new comments.

  • Latest comment 6 December 2023

    Proposal: Allow common base64 encoding in tracestate values w3c/trace-context#551 (3 comments by @basti1302, @feldentm-SAP, @SergeyKanzhelev)

  • Latest comment 5 December 2023

    Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service w3c/trace-context#550 (2 comments by @basti1302, @SergeyKanzhelev)

  • 6 December 2023

    Should tracing headers be included in 304 Not Modified responses? w3c/trace-context#554 (1 comment by @basti1302)

  • 6 December 2023

    tracestate response header proposal w3c/trace-context#483 (1 comment by @SergeyKanzhelev)
• 1 pull request opened.

  • 12 December 2023

    explict rules for traceresponse/random-trace-id when continuing a trace w3c/trace-context#555, by @basti1302.

• 2 pull requests merged.

  • 14 December 2023

    explict rules for traceresponse/random-trace-id when continuing a trace w3c/trace-context#555.

  • 5 December 2023

    remove test output file from version control w3c/trace-context#553.

• 1 pull request closed.

  • 5 December 2023

    Update tracestate duplicate keys in test_data.json w3c/trace-context#547.

• 1 pull request received 5 new comments.

  • Latest comment 12 December 2023

    explict rules for traceresponse/random-trace-id when continuing a trace w3c/trace-context#555 (5 comments by @basti1302, @kalyanaj)

Past meetings

• 1 meeting.

  • 14 November 2023

    Distributed Tracing Working Group bi-weekly, 14 November 2023. Minutes.

Participants

• 1 participant joined.

  • 9 November 2023

    Yash Shah (Microsoft Corporation) joined.

GitHub

w3c/trace-context

• 3 issues opened.

  • 13 November 2023

    Should tracing headers be included in 304 Not Modified responses? w3c/trace-context#554, by @mitar.

  • 2 November 2023

    Proposal: Allow common base64 encoding in tracestate values w3c/trace-context#551, by @feldentm-SAP.

  • 1 November 2023

    Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service w3c/trace-context#550, by @bogdandrutu.

• 1 issue closed.

  • 14 November 2023

    Document handling of tracestate duplicate keys w3c/trace-context#548.

• 4 issues received 17 new comments.

  • Latest comment 24 November 2023

    Should tracing headers be included in 304 Not Modified responses? w3c/trace-context#554 (12 comments by @basti1302, @kalyanaj, @mitar, @yurishkuro)

  • Latest comment 2 November 2023

    Proposal: Allow common base64 encoding in tracestate values w3c/trace-context#551 (2 comments by @feldentm-SAP, @yurishkuro)

  • Latest comment 1 November 2023

    Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service w3c/trace-context#550 (2 comments by @bogdandrutu, @yurishkuro)

  • 6 November 2023

    Document handling of tracestate duplicate keys w3c/trace-context#548 (1 comment by @basti1302)
• 2 pull requests opened.

  • 6 November 2023

    remove test output file from version control w3c/trace-context#553, by @basti1302.

  • 6 November 2023

    make wording around duplicate tracestate headers more precise w3c/trace-context#552, by @basti1302.

• 2 pull requests merged.

  • 14 November 2023

    make wording around duplicate tracestate headers more precise w3c/trace-context#552.

  • 14 November 2023

    Improve the markdown format w3c/trace-context#546.

• 2 pull requests received 2 new comments.

  • 14 November 2023

    Improve the markdown format w3c/trace-context#546 (1 comment by @w3cbot)

  • 6 November 2023

    Update tracestate duplicate keys in test_data.json w3c/trace-context#547 (1 comment by @basti1302)

Past meetings

• 1 meeting.

  • 24 October 2023

    Distributed Tracing Working Group bi-weekly, 24 October 2023. Minutes.

Participants

• 1 participant joined.

  • 23 October 2023

    Aleksandr Bzikadze (Rakuten Group, Inc.) joined.

• 1 organization joined.

  • 23 October 2023

    Rakuten Group, Inc. joined.

GitHub

w3c/trace-context

• 2 issues opened.

  • 20 October 2023

    Does this specification define a way to handle retries? w3c/trace-context#549, by @ben221199.

  • 16 October 2023

    Document handling of tracestate duplicate keys w3c/trace-context#548, by @pellared.

• 1 issue closed.

  • 24 October 2023

    Does this specification define a way to handle retries? w3c/trace-context#549.

• 2 issues received 9 new comments.

  • Latest comment 27 October 2023

    Document handling of tracestate duplicate keys w3c/trace-context#548 (5 comments by @basti1302, @kalyanaj, @pellared)

  • Latest comment 25 October 2023

    Does this specification define a way to handle retries? w3c/trace-context#549 (4 comments by @basti1302, @ben221199, @kalyanaj)
• 1 pull request opened.

  • 16 October 2023

    Update tracestate duplicate keys in test_data.json w3c/trace-context#547, by @pellared.

• 1 pull request received 4 new comments.

  • Latest comment 25 October 2023

    Update tracestate duplicate keys in test_data.json w3c/trace-context#547 (4 comments by @basti1302, @pellared, @w3cbot)

w3c/tracestate-ids-registry

• 1 pull request opened.

  • 4 October 2023

    Add sn vendor code for ServiceNow trace state w3c/tracestate-ids-registry#18, by @jmacd.

Past meetings

• 1 meeting.

  • 12 September 2023

    Distributed Tracing Working Group, 12 September 2023.

Participants

• 1 participant joined.

  • 8 September 2023

    Jon Bringhurst (Microsoft Corporation) joined.

GitHub

w3c/trace-context

• 1 pull request opened.

  • 30 September 2023

    Improve the markdown format w3c/trace-context#546, by @reyang.

TR publications

• 1 document published.

  • 10 August 2023

    Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage

Past meetings

• 2 meetings.

  • 29 August 2023

    Distributed Tracing Working Group, 29 August 2023.

  • 15 August 2023

    Distributed Tracing Working Group, 15 August 2023.

Participants

• 1 participant joined.

  • 12 August 2023

    Joel Copi (IBM Corporation) joined.

GitHub

w3c/trace-context

• 1 issue opened.

  • 29 August 2023

    Autopublishing level2/Level3 specs need to work with multiple markdown files w3c/trace-context#545, by @kalyanaj.

• 1 issue received 1 new comment.

  • 10 August 2023

    Random part of trace ID should be uniformly distributed w3c/trace-context#544 (1 comment by @dyladan)
• 1 pull request merged.

  • 10 August 2023

    update editors w3c/trace-context#543.

w3c/trace-context-protocols-registry

• 1 issue received 1 new comment.

  • 21 August 2023

    w3c/trace-context-protocols-registry#4 (1 comment by @flx5)

w3c/baggage

• 1 issue closed.

  • 10 August 2023

    Acknowledgements w3c/baggage#122.

• 1 pull request merged.

  • 10 August 2023

    chore: add acknowledgments w3c/baggage#123.

Participants

• 4 participants joined.

  • 24 July 2023

    Armin Ruech (Dynatrace LLC) joined.

  • 24 July 2023

    Daniel Dyla (Dynatrace LLC) joined.

  • 24 July 2023

    Christoph Neumüller (Dynatrace LLC) joined.

  • 24 July 2023

    Alois Reitbauer (Dynatrace LLC) joined.

• 16 participants left.

  • 24 July 2023

    Birinder Singh Tiwana (Cisco) left.

  • 24 July 2023

    Roque Gagliano (Cisco) left.

  • 24 July 2023

    William Holroyd (Lenovo) left.

  • 24 July 2023

    David Caro (Wikimedia Foundation) left.

  • 24 July 2023

    Caio Gondim (The New York Times) left.

  • 24 July 2023

    Michael Lewis (LSEG) left.

  • 24 July 2023

    Chris Wensel (Salesforce) left.

  • 24 July 2023

    Dimitar Georgievski (Wiley) left.

  • 24 July 2023

    Anton Leskovets (Wiley) left.

  • 24 July 2023

    Armin Ruech (Dynatrace LLC) left.

  • 24 July 2023

    Michael Kopp (Dynatrace LLC) left.

  • 24 July 2023

    Daniel Dyla (Dynatrace LLC) left.

  • 24 July 2023

    Adrian Muraru (Adobe) left.

  • 24 July 2023

    Michael Kopp (Dynatrace LLC) left.

  • 24 July 2023

    Christoph Neumüller (Dynatrace LLC) left.

  • 24 July 2023

    Alois Reitbauer (Dynatrace LLC) left.

• 1 organization joined.

  • 24 July 2023

    Dynatrace LLC joined.

Lifecycle

• 1 charter started.

  • 8 June 2023

    Chartered until 31 May 2025. Participants had to rejoin under this charter.

    Call for Participation

Past meetings

• 2 meetings.

  • 20 June 2023

    Distributed Tracing Working Group, 20 June 2023.

  • 6 June 2023

    Distributed Tracing Working Group, 6 June 2023.

Participants

• 1 participant joined.

  • 1 June 2023

    Birinder Singh Tiwana (Cisco) joined.

• 4 organizations joined.

  • 28 June 2023

    Google LLC joined.

  • 28 June 2023

    IBM Corporation joined.

  • 20 June 2023

    Microsoft Corporation joined.

  • 16 June 2023

    Meta joined.

• 14 organizations left.

  • 8 June 2023

    Cisco left.

  • 8 June 2023

    Lenovo left.

  • 8 June 2023

    Wikimedia Foundation left.

  • 8 June 2023

    Meta left.

  • 8 June 2023

    The New York Times left.

  • 8 June 2023

    LSEG left.

  • 8 June 2023

    IBM Corporation left.

  • 8 June 2023

    Salesforce left.

  • 8 June 2023

    Wiley left.

  • 8 June 2023

    Adobe left.

  • 8 June 2023

    Google LLC left.

  • 8 June 2023

    Dynatrace LLC left.

  • 8 June 2023

    Microsoft Corporation left.

  • 2 June 2023

    Pearson plc left.

GitHub

w3c/trace-context

• 2 issues opened.

  • 30 June 2023

    Random part of trace ID should be uniformly distributed w3c/trace-context#544, by @oertl.

  • 6 June 2023

    Level 3 spec: Update privacy section to include information about traceresponse headers. w3c/trace-context#542, by @kalyanaj.

• 1 issue received 1 new comment.

  • 30 June 2023

    Random part of trace ID should be uniformly distributed w3c/trace-context#544 (1 comment by @yurishkuro)
• 1 pull request opened.

  • 20 June 2023

    update editors w3c/trace-context#543, by @basti1302.

• 5 pull requests merged.

  • 6 June 2023

    editorial: Level 2 cr snapshot w3c/trace-context#530.

  • 6 June 2023

    update editors w3c/trace-context#534.

  • 6 June 2023

    explicitly describe rules for randomness flag when continuing a trace w3c/trace-context#541.

  • 6 June 2023

    update list of implementations and add spec level w3c/trace-context#538.

  • 6 June 2023

    Always run tests (backport to level-2) w3c/trace-context#539.

• 2 pull requests received 2 new comments.

  • 20 June 2023

    update editors w3c/trace-context#543 (1 comment by @basti1302)

  • 6 June 2023

    update editors w3c/trace-context#534 (1 comment by @basti1302)

w3c/baggage

• 1 issue opened.

  • 6 June 2023

    Acknowledgements w3c/baggage#122, by @basti1302.

• 1 issue received 5 new comments.

  • Latest comment 8 June 2023

    Acknowledgements w3c/baggage#122 (5 comments by @basti1302, @JonathanMace, @kalyanaj, @reyang)
• 1 pull request opened.

  • 21 June 2023

    chore: add acknowledgments w3c/baggage#123, by @basti1302.

• 1 pull request merged.

  • 6 June 2023

    update editors w3c/baggage#118.

• 1 pull request closed.

  • 6 June 2023

    Initial unicode baggage keys w3c/baggage#117.

• 2 pull requests received 4 new comments.

  • Latest comment 6 June 2023

    update editors w3c/baggage#118 (3 comments by @basti1302)

  • 20 June 2023

    Allow unicode in baggage keys by referencing XML w3c/baggage#120 (1 comment by @kalyanaj)

TR publications

• 1 document published.

  • 23 May 2023

    Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage

Past meetings

• 2 meetings.

  • 23 May 2023

    Distributed Tracing Working Group, 23 May 2023.

  • 9 May 2023

    Distributed Tracing Working Group, 9 May 2023.

GitHub

w3c/baggage

• 3 pull requests opened.

  • 23 May 2023

    Don't merge w3c/baggage#121, by @plehegar.

  • 9 May 2023

    Allow unicode in baggage keys by referencing XML w3c/baggage#120, by @dyladan.

  • 9 May 2023

    Run tests on pull requests w3c/baggage#119, by @dyladan.

• 1 pull request merged.

  • 23 May 2023

    Run tests on pull requests w3c/baggage#119.

• 1 pull request closed.

  • 9 May 2023

    DO NOT MERGE w3c/baggage#116.

• 2 pull requests received 2 new comments.

  • 9 May 2023

    Allow unicode in baggage keys by referencing XML w3c/baggage#120 (1 comment by @dyladan)

  • 9 May 2023

    DO NOT MERGE w3c/baggage#116 (1 comment by @dyladan)

w3c/trace-context

• 1 issue opened.

  • 19 May 2023

    Add more normative text for flags processing in traceresponse w3c/trace-context#540, by @kalyanaj.

• 1 issue closed.

  • 19 May 2023

    Incorporate Level 2 changes (random trace id flag) into traceresponse header in Level 3 w3c/trace-context#532.

• 1 issue received 1 new comment.

  • 11 May 2023

    tracestate response header proposal w3c/trace-context#483 (1 comment by @dyladan)
• 5 pull requests opened.

  • 19 May 2023

    explicitly describe rules for randomness flag when continuing a trace w3c/trace-context#541, by @basti1302.

  • 16 May 2023

    Always run tests (backport to level-2) w3c/trace-context#539, by @basti1302.

  • 12 May 2023

    update list of implementations and add spec level w3c/trace-context#538, by @basti1302.

  • 9 May 2023

    Always run tests w3c/trace-context#537, by @dyladan.

  • 4 May 2023

    explicitly describe rules for randomness flag when continuing a trace w3c/trace-context#536, by @basti1302.

• 5 pull requests merged.

  • 19 May 2023

    Added random trace id flag to traceresponse header w3c/trace-context#533.

  • 15 May 2023

    Sync with level 2. Rev'up level 3 w3c/trace-context#531.

  • 15 May 2023

    explicitly describe rules for randomness flag when continuing a trace w3c/trace-context#536.

  • 9 May 2023

    Updated the flags description in version format w3c/trace-context#535.

  • 9 May 2023

    Always run tests w3c/trace-context#537.

• 3 pull requests received 9 new comments.

  • Latest comment 19 May 2023

    Added random trace id flag to traceresponse header w3c/trace-context#533 (5 comments by @basti1302, @kalyanaj)

  • Latest comment 4 May 2023

    explicitly describe rules for randomness flag when continuing a trace w3c/trace-context#536 (3 comments by @basti1302)

  • 4 May 2023

    Updated the flags description in version format w3c/trace-context#535 (1 comment by @basti1302)

w3c/tracestate-ids-registry

• 1 pull request opened.

  • 12 May 2023

    Updated registry.md to add vendor identifier for Microsoft w3c/tracestate-ids-registry#17, by @kalyanaj.

• 1 pull request merged.

  • 12 May 2023

    Updated registry.md to add vendor identifier for Microsoft w3c/tracestate-ids-registry#17.

Lifecycle

• 1 charter extension.

  • 6 April 2023

    Charter extended until 31 May 2023.

    Announcement

TR publications

• 2 documents published.

  • 18 April 2023

    Trace Context Level 2 published as a Candidate Recommendation Snapshot. History of Trace Context Level 2

  • 6 April 2023

    Trace Context Level 2 published as a Working Draft. History of Trace Context Level 2

Past meetings

• 2 meetings.

  • 25 April 2023

    Distributed Tracing Working Group, 25 April 2023.

  • 11 April 2023

    Distributed Tracing Working Group, 11 April 2023.

GitHub

w3c/baggage

• 1 issue received 1 new comment.

  • 12 April 2023

    Keys don't permit non-ASCII? w3c/baggage#99 (1 comment by @dyladan)
• 2 pull requests opened.

  • 26 April 2023

    update editors w3c/baggage#118, by @basti1302.

  • 11 April 2023

    Initial unicode baggage keys w3c/baggage#117, by @dyladan.

• 2 pull requests received 11 new comments.

  • Latest comment 27 April 2023

    update editors w3c/baggage#118 (9 comments by @basti1302, @kalyanaj, @SergeyKanzhelev)

  • Latest comment 12 April 2023

    Initial unicode baggage keys w3c/baggage#117 (2 comments by @dyladan, @yurishkuro)

w3c/trace-context

• 2 issues opened.

  • 11 April 2023

    Incorporate Level 2 changes (random trace id flag) into traceresponse header in Level 3 w3c/trace-context#532, by @kalyanaj.

  • 11 April 2023

    Update tests to test Trace Context level 2 by default w3c/trace-context#529, by @kalyanaj.

• 5 pull requests opened.

  • 26 April 2023

    Updated the flags description in version format w3c/trace-context#535, by @basti1302.

  • 26 April 2023

    update editors w3c/trace-context#534, by @basti1302.

  • 12 April 2023

    Added random trace id flag to traceresponse header w3c/trace-context#533, by @kalyanaj.

  • 11 April 2023

    Sync with level 2. Rev'up level 3 w3c/trace-context#531, by @plehegar.

  • 11 April 2023

    editorial: Level 2 cr snapshot w3c/trace-context#530, by @plehegar.

• 1 pull request closed.

  • 11 April 2023

    DO NOT MERGE w3c/trace-context#528.

• 5 pull requests received 11 new comments.

  • Latest comment 26 April 2023

    update editors w3c/trace-context#534 (4 comments by @basti1302, @yurishkuro)

  • Latest comment 26 April 2023

    Added random trace id flag to traceresponse header w3c/trace-context#533 (4 comments by @basti1302, @kalyanaj, @yurishkuro)

  • 26 April 2023

    Updated the flags description in version format w3c/trace-context#535 (1 comment by @basti1302)

  • 17 April 2023

    editorial: Level 2 cr snapshot w3c/trace-context#530 (1 comment by @basti1302)

  • 11 April 2023

    DO NOT MERGE w3c/trace-context#528 (1 comment by @kalyanaj)

w3c/trace-context-protocols-registry

• 1 pull request merged.

  • 25 April 2023

    Updated registry.md to fix link to CloudEvents extension w3c/trace-context-protocols-registry#13.

Past meetings

• 2 meetings.

  • 28 March 2023

    Distributed Tracing Working Group, 28 March 2023.

  • 14 March 2023

    Distributed Tracing Working Group, 14 March 2023.

Participants

• 1 participant joined.

  • 13 March 2023

    Roque Gagliano (Cisco) joined.

• 1 organization joined.

  • 13 March 2023

    Cisco joined.

GitHub

w3c/trace-context

• 2 issues closed.

  • 28 March 2023

    Start Wide Review for Trace Context Level 2 Spec w3c/trace-context#492.

  • 28 March 2023

    Trace Context Level 2: Self review for i18n w3c/trace-context#498.

• 3 issues received 6 new comments.

  • Latest comment 30 March 2023

    Trace Context: Apache Kafka protocol specification w3c/trace-context#504 (3 comments by @kalyanaj, @ppatierno)

  • Latest comment 31 March 2023

    Start Wide Review for Trace Context Level 2 Spec w3c/trace-context#492 (2 comments by @kalyanaj, @plehegar)

  • 28 March 2023

    Trace Context Level 2: Self review for i18n w3c/trace-context#498 (1 comment by @kalyanaj)
• 4 pull requests opened.

  • 15 March 2023

    DO NOT MERGE w3c/trace-context#528, by @plehegar.

  • 14 March 2023

    [Do NOT merge] Update client.py w3c/trace-context#527, by @SergeyKanzhelev.

  • 14 March 2023

    [Do NOT merge] Update README.md w3c/trace-context#526, by @SergeyKanzhelev.

  • 14 March 2023

    [Do NOT MERGE] Update README.md w3c/trace-context#525, by @SergeyKanzhelev.

• 2 pull requests merged.

  • 14 March 2023

    update references to RFC7230 to RFC9110 (backport to level 2) w3c/trace-context#523.

  • 14 March 2023

    updates the versions used in the Github action to run the tests w3c/trace-context#524.

• 3 pull requests closed.

  • 14 March 2023

    [Do NOT merge] Update client.py w3c/trace-context#527.

  • 14 March 2023

    [Do NOT merge] Update README.md w3c/trace-context#526.

  • 14 March 2023

    [Do NOT MERGE] Update README.md w3c/trace-context#525.

w3c/trace-context-protocols-registry

• 1 pull request opened.

  • 30 March 2023

    Updated registry.md to fix link to CloudEvents extension w3c/trace-context-protocols-registry#13, by @kalyanaj.

w3c/distributed-tracing-wg

• 1 pull request merged.

  • 28 March 2023

    Clarify that browsers are not the target implementation for the W3C TraceContext specification w3c/distributed-tracing-wg#50.

• 1 pull request received 1 new comment.

  • 3 March 2023

    Clarify that browsers are not the target implementation for the W3C TraceContext specification w3c/distributed-tracing-wg#50 (1 comment by @kalyanaj)

w3c/baggage

• 1 issue received 1 new comment.

  • 28 March 2023

    Keys don't permit non-ASCII? w3c/baggage#99 (1 comment by @dyladan)
• 1 pull request opened.

  • 15 March 2023

    DO NOT MERGE w3c/baggage#116, by @plehegar.

• 1 pull request received 1 new comment.

  • 15 March 2023

    DO NOT MERGE w3c/baggage#116 (1 comment by @plehegar)

Past meetings

• 2 meetings.

  • 28 February 2023

    Distributed Tracing Working Group, 28 February 2023.

  • 14 February 2023

    Distributed Tracing Working Group, 14 February 2023.

GitHub

w3c/trace-context

• 1 issue opened.

  • 14 February 2023

    Change the defining document for HTTP from RFC7230 to RFC9110 w3c/trace-context#519, by @kalyanaj.

• 3 issues closed.

  • 28 February 2023

    Change the defining document for HTTP from RFC7230 to RFC9110 w3c/trace-context#519.

  • 14 February 2023

    Incorrect randomness claim in 50-privacy.md w3c/trace-context#481.

  • 14 February 2023

    Self-Review Questionnaire for Trace Context Level 2: Security and Privacy w3c/trace-context#496.

• 4 issues received 5 new comments.

  • Latest comment 14 February 2023

    Change the defining document for HTTP from RFC7230 to RFC9110 w3c/trace-context#519 (2 comments by @basti1302, @kalyanaj)

  • 23 February 2023

    specification of lowercase is incomplete w3c/trace-context#506 (1 comment by @aphillips)

  • 14 February 2023

    Incorrect randomness claim in 50-privacy.md w3c/trace-context#481 (1 comment by @kalyanaj)

  • 14 February 2023

    Self-Review Questionnaire for Trace Context Level 2: Security and Privacy w3c/trace-context#496 (1 comment by @kalyanaj)
• 5 pull requests opened.

  • 28 February 2023

    updates the versions used in the Github action to run the tests w3c/trace-context#524, by @basti1302.

  • 28 February 2023

    update references to RFC7230 to RFC9110 (backport to level 2) w3c/trace-context#523, by @basti1302.

  • 27 February 2023

    updates the versions used in the Github action to run the tests w3c/trace-context#522, by @basti1302.

  • 27 February 2023

    update references to RFC7230 to RFC9110 w3c/trace-context#521, by @basti1302.

  • 14 February 2023

    Incorporate feedback from privacy review. Resolves #510 w3c/trace-context#520, by @kalyanaj.

• 3 pull requests merged.

  • 28 February 2023

    updates the versions used in the Github action to run the tests w3c/trace-context#522.

  • 28 February 2023

    update references to RFC7230 to RFC9110 w3c/trace-context#521.

  • 14 February 2023

    Incorporate feedback from privacy review. Resolves #510 w3c/trace-context#520.

• 1 pull request received 4 new comments.

  • Latest comment 27 February 2023

    update references to RFC7230 to RFC9110 w3c/trace-context#521 (4 comments by @basti1302)

w3c/baggage

• 1 issue closed.

  • 14 February 2023

    Self-Review Questionnaire: Security and Privacy w3c/baggage#95.

• 1 issue received 1 new comment.

  • 14 February 2023

    Self-Review Questionnaire: Security and Privacy w3c/baggage#95 (1 comment by @kalyanaj)

w3c/distributed-tracing-wg

• 1 pull request merged.

  • 14 February 2023

    Add a markdown style guide w3c/distributed-tracing-wg#49.

• 2 pull requests received 12 new comments.

  • Latest comment 8 February 2023

    Clarify that browsers are not the target implementation for the W3C TraceContext specification w3c/distributed-tracing-wg#50 (11 comments by @basti1302)

  • 9 February 2023

    Add a markdown style guide w3c/distributed-tracing-wg#49 (1 comment by @basti1302)

Past meetings

• 1 meeting.

  • 31 January 2023

    Distributed Tracing Working Group, 31 January 2023.

GitHub

w3c/baggage

• 1 issue closed.

  • 3 January 2023

    Make trust/privacy boundary explicit (at least in browsers) w3c/baggage#107.

• 1 issue received 2 new comments.

  • Latest comment 31 January 2023

    Keys don't permit non-ASCII? w3c/baggage#99 (2 comments by @aphillips, @dyladan)
• 1 pull request merged.

  • 3 January 2023

    Add note that applications using baggage must be aware that data can be propagated to other systems w3c/baggage#111.

w3c/trace-context

• 1 issue closed.

  • 31 January 2023

    When headers should be propagated in browsers should be made more clear w3c/trace-context#510.

• 3 pull requests merged.

  • 31 January 2023

    improve description of version field in traceparent request header w3c/trace-context#517.

  • 31 January 2023

    improve wording for casing of request header names w3c/trace-context#518.

  • 31 January 2023

    Incorporate feedback from privacy review. Resolves #510. w3c/trace-context#516.