Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+3/-2/💬7)
  3 issues created:
  - Clarify tracestate keys MUST be unique (by adriancole)
    https://github.com/w3c/trace-context/issues/446 
  - may be this paragraph would work better in request processing section which is non-formative. It sounds like an example rather than a spec. Maybe spec may only say that sampling bit returned in response header may not match the flag that was sent in the request and processing will give this example with the event that happens during the processing in the processing section. (by dyladan)
    https://github.com/w3c/trace-context/issues/445 
  - term `negative sampling decision` may not be very clear to a reader (by dyladan)
    https://github.com/w3c/trace-context/issues/444 

  4 issues received 7 new comments:
  - #446 Clarify tracestate keys MUST be unique (2 by adriancole)
    https://github.com/w3c/trace-context/issues/446 
  - #437 Encourage traceresponse to be provided even when traceparent is used (2 by briancr-ms, dyladan)
    https://github.com/w3c/trace-context/issues/437 
  - #398 Should response header fields be optional? (1 by dyladan)
    https://github.com/w3c/trace-context/issues/398 [workshop-fall-2020] 
  - #364 ABNF improvement (2 by danielkhan, plehegar)
    https://github.com/w3c/trace-context/issues/364 [editorial] [enhancement] [todo] 

  2 issues closed:
  - ABNF improvement https://github.com/w3c/trace-context/issues/364 [editorial] [enhancement] [todo] 
  - Bogus trace and parent IDs when not sampling   https://github.com/w3c/trace-context/issues/390 [workshop-fall-2020] 



Pull requests
-------------
* w3c/trace-context (+1/-1/💬2)
  1 pull requests submitted:
  - Replace proposed-parent-id with child-id. All fields required. (by dyladan)
    https://github.com/w3c/trace-context/pull/443 

  2 pull requests received 2 new comments:
  - #443 Replace proposed-parent-id with child-id. All fields required. (1 by danielkhan)
    https://github.com/w3c/trace-context/pull/443 
  - #411 Clarify description of tracestate value (1 by adriancole)
    https://github.com/w3c/trace-context/pull/411 [editorial] 

  1 pull requests merged:
  - Clarify behaviour when starting a trace and not recording
    https://github.com/w3c/trace-context/pull/433 


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