Baggage 2022-06-08

[kalyanaj]

• name of spec to be reviewed: W3C Baggage
• URL of spec: https://www.w3.org/TR/baggage/
• Does your document have an in-line Privacy Considerations section, ideally one separate from the Security Considerations? Yes
• Do you need a reply by a particular date? Yes, we are looking to move this spec to the CR stage in the next few months, so a reply by end of June will be helpful to be able to react to any issues filed.
• Please point to the results of your own self-review: Self-Review Questionnaire: Security and Privacy w3c/baggage#95
• Where and how to file issues arising? https:/w3c/baggage/issues
• Pointer to any explainer for the spec? https:/w3c/baggage/blob/main/baggage/README.md provides an overview and the use cases.

[pes10k]

I've completed this review, and filed these three issues as a result:

• Clarify in text the relationship to Trace Context w3c/baggage#105
• Relationship to other HTTP Header encoding proposals w3c/baggage#106
• Make trust/privacy boundary explicit (at least in browsers) w3c/baggage#107