Closed Bug 1439123 Opened 2 years ago Closed 2 years ago

GoDaddy: Failure to respond to January 2018 survey

Categories

(NSS :: CA Certificate Compliance, task)

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wayne, Assigned: dreynolds)

Details

(Whiteboard: [ca-compliance])

The deadline for response to the January 2018 CA Communication survey was February 9. GoDaddy has not responded as of February 16.

Please respond to this incident with the following information:
1. Why was no response received from your organization?
2. Confirm that the CA email alias in CCADB is correct for your organization.
3. Explain why your monitoring of the mozilla.dev.security.policy list (a requirement of Mozilla policy section 2.1), did not result in your organization responding to this survey.
3. Explain what changes will be made to ensure that future actions requested of your organization by Mozilla occur promptly and no later than any communicated deadline.
Assignee: wthayer → dreynolds
Whiteboard: [ca-compliance]
Wayne,  I have tried multiple times to login and submit this report.  Each time I am unable to edit this. Is my account properly setup?  Here are the instructions I have followed:

To submit your response, you must login to the CCADB, click on the 'CA Communications (Page)' tab, and select the 'January 2018 CA Communication' survey. Make sure you click on the 'Submit' button at the bottom of the survey, and make sure you get a good 
'survey submitted' response -- there are required fields.

This leads me to a read only page where I am unable to submit.

Daymion
(In reply to Daymion Reynolds from comment #1)
> 
> This leads me to a read only page where I am unable to submit.


That is because the survey due-date was Feb 9, so the survey Expiration Date had been extended to Feb 17. But clearly, this is past that date...

Wayne will have to re-extend the survey Expiration Date, so you will be able to submit your response.
1. Why was no response received from your organization? - This is on me, as I checked the link twice and thought it was still in read only mode. I was using the wrong link.  I am now familiar with the cadence of Mozilla requests and this should no longer be an issue going forward. 
2. Confirm that the CA email alias in CCADB is correct for your organization. - My contact information looks correct. Will seek out of there is a way to add a distribution group to this contact list. 
3. Explain why your monitoring of the mozilla.dev.security.policy list (a requirement of Mozilla policy section 2.1), did not result in your organization responding to this survey. - This is not expected to happen again, as there was unfamiliarity with the timelines and requests being made.  This is now well understood.
3. Explain what changes will be made to ensure that future actions requested of your organization by Mozilla occur promptly and no later than any communicated deadline. The notifications mozilla.dev.security.policy are better understood with some additional background.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
I'm going to re-open this as it's not up to the CA to decide when compliance bugs get closed.

I wouldn't be surprised if there are additional questions based on the response.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Seeing no further questions, I'm resolving this.
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.