Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+2/-4/💬1)
  2 issues created:
  - Use of W3C Trace-Context with multiple agents in a single process, inject issue (by pavolloffay)
    https://github.com/w3c/trace-context/issues/451 
  - Define entry/value length/size consistently (by dyladan)
    https://github.com/w3c/trace-context/issues/449 

  1 issues received 1 new comments:
  - #447 Consider renaming parent-id / child-id to span-id (1 by mwear)
    https://github.com/w3c/trace-context/issues/447 

  4 issues closed:
  - How should tracestate list members be truncated when they exceed 32? https://github.com/w3c/trace-context/issues/440 
  - Encourage traceresponse to be provided even when traceparent is used https://github.com/w3c/trace-context/issues/437 
  - Remove proposed-parent-id from response header https://github.com/w3c/trace-context/issues/406 [workshop-fall-2020] 
  - Consider renaming parent-id / child-id to span-id https://github.com/w3c/trace-context/issues/447 



Pull requests
-------------
* w3c/trace-context (+1/-2/💬2)
  1 pull requests submitted:
  - Move traceresponse processing to processing model (by dyladan)
    https://github.com/w3c/trace-context/pull/450 

  1 pull requests received 2 new comments:
  - #448 When the 32-entry limit is met, the right-most entry is removed (2 by SergeyKanzhelev, dyladan)
    https://github.com/w3c/trace-context/pull/448 

  2 pull requests merged:
  - When the 32-entry limit is met, the right-most entry is removed
    https://github.com/w3c/trace-context/pull/448 
  - Replace proposed-parent-id with child-id. All fields required.
    https://github.com/w3c/trace-context/pull/443 


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