- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 18 Jan 2022 17:00:58 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1n9rqs-00068o-RH@uranus.w3.org>
Issues
------
* w3c/trace-context (+0/-0/💬2)
  2 issues received 2 new comments:
  - #364 ABNF improvement (1 by kalyanaj)
    https://github.com/w3c/trace-context/issues/364 [Editorial] [enhancement] [todo] 
  - #120 IETF/IANA registration of header fields (1 by kalyanaj)
    https://github.com/w3c/trace-context/issues/120 [w3c] [discuss-next-meeting] [todo] [workshop-fall-2020] 
* w3c/correlation-context (+0/-1/💬3)
  2 issues received 3 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 
  - #74 Create a test as a reference implementation (2 by dyladan, kalyanaj)
    https://github.com/w3c/baggage/issues/74 
  1 issues closed:
  - Update baggage specification to clarify expectation when length is exceeded or when invalid entry is found https://github.com/w3c/baggage/issues/80 
Pull requests
-------------
* w3c/trace-context (+0/-1/💬0)
  1 pull requests merged:
  - Remove incorrect randomness claim from privacy considerations
    https://github.com/w3c/trace-context/pull/482 
* w3c/correlation-context (+0/-1/💬0)
  1 pull requests merged:
  - Clarify what implementations should do when baggage length is exceeded or when invalid entry is found
    https://github.com/w3c/baggage/pull/82 
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
Received on Tuesday, 18 January 2022 17:01:00 UTC