-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PING Horizontal Review #291
Comments
@jonathan-consensysHealth volunteered to fill out the questionairre |
Will forward to my friend and colleague @jonathan-consensysHealth. Would someone please forward me the submission from the VC working group. Also, I'll need help with the threat model section. |
@agropper and myself have volunteered to help draft the responses |
… On Tue, Jul 14, 2020 at 11:44 AM wyc ***@***.***> wrote:
@agropper <https://github.com/agropper> and myself have volunteered to
help draft the responses
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABB4YKOZ7EIKMTEQ4JO6ITR3R4NVANCNFSM4NHZSC3Q>
.
|
@agropper @jonnycrunch due to the time passed, would you like to reconvene later this week or early next week in an open-to-did-wg/public meeting and prepare a working item for comments? hopefully there has been some progress on the service endpoint discussions |
yep, how is Monday again? I'll send an invite. |
+1, probably a good idea to inform the public did wg list after we figure out where/when. We can use the CCG Jitsi instance here: https://meet.w3c-ccg.org/DIDSecurityPrivacyReview |
+1 for 2PM EST?
…On Wed, Aug 12, 2020 at 3:27 PM wyc ***@***.***> wrote:
+1, probably a good idea to inform the public did wg list after we figure
out where/when.
We can use the CCG Jitsi instance here:
https://meet.w3c-ccg.org/DIDSecurityPrivacyReview
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABB4YKFEEKWCFUNLHVM3PTSALUJHANCNFSM4NHZSC3Q>
.
|
@agropper @wyc @jonathan-consensysHealth what is the status of the security and privacy questionnaire? |
@brentzundel and those following, the latest response is here: My apologies, I think I was supposed to write an update to the list and forgot. We are preparing to begin work on sections 3 and 4, but we there were 2 major concerns around scope that would impact the models in those sections significantly:
|
We need to have the Security Questionnaire done for this issue to be closed. We cannot close this issue until PING does a review on the specification. |
I am adding myself to track contributing to the questionnaire. |
I added a few changes. Reviewed until 2.16. |
We're getting closer on the security questionaire with sections covering all of the security parts (section 3 - might need additional points added as well but solid set in there already), but it appears that section 4 needs to be added still. Also, who is currently handling editorship of this document so that we can get the comments merged/resolved? If no one has time to do this I'm happy to step in and carry this to the end, but I'll need editor rights to the document. |
@kdenhartog I added some details, but IMO this needs an editorial merging session, and then we should focus on the weakest parts. |
I think the first checkbox is done now? |
PING has been contacted for review. |
PING response of "no blocking issues": https://lists.w3.org/Archives/Public/public-privacy/2021JanMar/0021.html |
I'm reminded of the compiler message: "None of the errors detected."
Adrian
…On Wed, Feb 24, 2021 at 5:56 PM Daniel Burnett ***@***.***> wrote:
PING response of "no blocking issues":
https://lists.w3.org/Archives/Public/public-privacy/2021JanMar/0021.html
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABB4YP3HJQX7YOZMQCQ3K3TAV7YLANCNFSM4NHZSC3Q>
.
|
Link to invitation for Security review of Decentralized Identifier Specification v1.0: https://lists.w3.org/Archives/Public/public-web-security/2020Dec/0003.html No response was received and no issues were raised. |
Horizontal review is complete, closing |
The text was updated successfully, but these errors were encountered: