Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+0/-1/💬2)
  2 issues received 2 new comments:
  - #469 Release trace context level-1 (1 by plehegar)
    https://github.com/w3c/trace-context/issues/469 
  - #392 Define the intended implementer (1 by kalyanaj)
    https://github.com/w3c/trace-context/issues/392 [privacy-needs-resolution] [workshop-fall-2020] 

  1 issues closed:
  - Release trace context level-1 https://github.com/w3c/trace-context/issues/469 

* w3c/correlation-context (+4/-0/💬1)
  4 issues created:
  - Different behaviour in private browsing/incognito mode? (by hadleybeeman)
    https://github.com/w3c/baggage/issues/84 
  - Name 'baggage' is a metaphor and could be hard for non-native English speakers (by hadleybeeman)
    https://github.com/w3c/baggage/issues/83 
  - Reference the relevant RFC for URL encoding baggage values (by kalyanaj)
    https://github.com/w3c/baggage/issues/81 
  - Update baggage specification to clarify expectation when length is exceeded or when invalid entry is found (by kalyanaj)
    https://github.com/w3c/baggage/issues/80 

  1 issues received 1 new comments:
  - #83 Name 'baggage' is a metaphor and could be hard for non-native English speakers (1 by kalyanaj)
    https://github.com/w3c/baggage/issues/83 



Pull requests
-------------
* w3c/trace-context (+0/-1/💬5)
  3 pull requests received 5 new comments:
  - #479 must->should for keys mutation fix up (1 by plehegar)
    https://github.com/w3c/trace-context/pull/479 [trace-context-1] 
  - #477 Specify uniqueness of tracestate keys as the sender's responsibility (2 by basti1302)
    https://github.com/w3c/trace-context/pull/477 
  - #475 Specify expected behaviour when no traceparent is received (2 by basti1302)
    https://github.com/w3c/trace-context/pull/475 

  1 pull requests merged:
  - add required "on" trigger to Github action "self-test"
    https://github.com/w3c/trace-context/pull/478 

* w3c/correlation-context (+2/-2/💬3)
  2 pull requests submitted:
  - Clarify what implementations should do when baggage length is exceeded or when invalid entry is found (by kalyanaj)
    https://github.com/w3c/baggage/pull/82 
  - Use RFC 7230 for token definition (by dyladan)
    https://github.com/w3c/baggage/pull/79 

  2 pull requests received 3 new comments:
  - #79 Use RFC 7230 for token definition (1 by dyladan)
    https://github.com/w3c/baggage/pull/79 
  - #78 Apply url encoding to single header example, matching multiple (2 by plehegar, w3cbot)
    https://github.com/w3c/baggage/pull/78 

  2 pull requests merged:
  - Apply url encoding to single header example, matching multiple
    https://github.com/w3c/baggage/pull/78 
  - Use RFC 7230 for token definition
    https://github.com/w3c/baggage/pull/79 


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