- From: J. Kalyana Sundaram via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jun 2022 15:47:03 +0000
- To: public-web-security@w3.org
kalyanaj has just labeled an issue for https://github.com/w3c/security-request as "REVIEW REQUESTED": == Baggage 2022-06-08 == - name of spec to be reviewed: W3C Baggage - URL of spec: https://www.w3.org/TR/baggage/ - Does your document have an in-line Security Considerations section, ideally one separate from the Privacy 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: https://github.com/w3c/baggage/issues/95 - Where and how to file issues arising? https://github.com/w3c/baggage/issues - Pointer to any explainer for the spec? https://github.com/w3c/baggage/blob/main/baggage/README.md provides an overview and the use cases. See https://github.com/w3c/security-request/issues/34 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 June 2022 15:47:04 UTC