Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+3/-1/💬7)
  3 issues created:
  - Trace Context Level 2: Self-review for accessibility (by kalyanaj)
    https://github.com/w3c/trace-context/issues/499 
  - Trace Context Level 2: Self review for i18n (by kalyanaj)
    https://github.com/w3c/trace-context/issues/498 
  - Self-Review Questionnaire for Trace Context Level 2: Security and Privacy (by kalyanaj)
    https://github.com/w3c/trace-context/issues/496 

  2 issues received 7 new comments:
  - #493 Need to publish latest draft of trace-context-2 (3 by kalyanaj, plehegar)
    https://github.com/w3c/trace-context/issues/493 
  - #492 Start Wide Review for Trace Context Level 2 Spec (4 by kalyanaj)
    https://github.com/w3c/trace-context/issues/492 

  1 issues closed:
  - Need to publish latest draft of trace-context-2 https://github.com/w3c/trace-context/issues/493 

* w3c/correlation-context (+0/-3/💬8)
  6 issues received 8 new comments:
  - #112 Need to update the limits section in rationale to be in sync with the new lower limits (1 by kalyanaj)
    https://github.com/w3c/baggage/issues/112 
  - #106 Relationship to other HTTP Header encoding proposals (3 by kalyanaj, pes10k)
    https://github.com/w3c/baggage/issues/106 [privacy-tracker] 
  - #99 Keys don't permit non-ASCII? (1 by basti1302)
    https://github.com/w3c/baggage/issues/99 [i18n-needs-resolution] 
  - #55 Clarify whether length is in bytes or characters (1 by kalyanaj)
    https://github.com/w3c/baggage/issues/55 
  - #53 Remove optional whitespace (1 by dyladan)
    https://github.com/w3c/baggage/issues/53 
  - #30 limitations do not appear to have standard implementation for enforcement (1 by dyladan)
    https://github.com/w3c/baggage/issues/30 [workshop-fall-2020] 

  3 issues closed:
  - Relationship to other HTTP Header encoding proposals https://github.com/w3c/baggage/issues/106 [privacy-tracker] 
  - Clarify in text the relationship to Trace Context https://github.com/w3c/baggage/issues/105 [privacy-needs-resolution] 
  - Remove optional whitespace https://github.com/w3c/baggage/issues/53 



Pull requests
-------------
* w3c/trace-context (+3/-0/💬0)
  3 pull requests submitted:
  - Level 2 tweaks (by plehegar)
    https://github.com/w3c/trace-context/pull/497 
  - Remove incorrect randomness claim from privacy considerations (by dyladan)
    https://github.com/w3c/trace-context/pull/495 
  - Remove contradiction in TraceState mutations #428 (by dyladan)
    https://github.com/w3c/trace-context/pull/494 

* w3c/correlation-context (+1/-2/💬2)
  1 pull requests submitted:
  - Clarify what happens when limits are violated (by dyladan)
    https://github.com/w3c/baggage/pull/113 

  1 pull requests received 2 new comments:
  - #111 Add note that applications using baggage must be aware that data can be propagated to other systems (2 by dyladan, kalyanaj)
    https://github.com/w3c/baggage/pull/111 

  2 pull requests merged:
  - Specify Relationship to other HTTP Header encoding proposals.
    https://github.com/w3c/baggage/pull/110 
  - Provide clarification for how this specification is different from TraceContext.
    https://github.com/w3c/baggage/pull/109 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config