Please make sure that all Subteam Status is up to date
I ask that the Rapporteur for each subteam to update the status in the google spreadsheed before the call on Wednesday. https://docs.google.com/spreadsheets/d/1cOZ1lPXqHfuZNt68zvB5xRB63eBoL3gonDbh... The information in this spreadsheet will drive the discussion on Wednesday. Thanks, Russ - - - - - - - - Subteam No. / Rapporteur 1 Russ 2 Boban 3 Kerry-Ann 4 Noorul 5 Laurin 6 Norm 7 Boban 8 Boban 9 Boban 10 Denise 11 Denise 12 Denise 13 Denise 14 Denise 15 Laurin 16 Laurin 17 Laurin 18 Laurin 19 kc 20 Eric 21 Eric 22 kc 23 Zarko 24 kc 25 kc 26 Zarko 27 Alain 28 Naveed 29 Kerry-Ann 30 Eric 31 Zarko
On Mon, Jun 29, 2020 at 02:10:11PM -0400, Russ Housley wrote: I ask that the Rapporteur for each subteam to update the status in the google spreadsheed before the call on Wednesday. https://docs.google.com/spreadsheets/d/1cOZ1lPXqHfuZNt68zvB5xRB63eBoL3gonDbh... The information in this spreadsheet will drive the discussion on Wednesday. Thanks, Russ for mine: 19: folded into the other abuse-related recommendations (10-16) 20-21: Phase 3 Eric drafting text, said he'd have for call tomorrow 22: emailed Ram, no answer. made comments in spreadsheet that include recommendation to remove 22.3 and 22.4 as not measurable or related to well articulated problem/need, but keeps rest in tact as public comments support it. probably need another subteam formed or just send to main list. 24: Phase 4, Eric and I filled in spreadsheet and new text on document Heather sent him. She will have URL I trust. Ready for Full RT review. 25: CZDS: I'm afraid we need an update from ICANN Org on status of all recommendations in SAC097, to start. Measurable outcomes we could put CZDS rec: - There is no requirement for registries to ever respond to requests - Suggestion: have requests auto approve after an amount of time if the registry does not respond to requests. - Registries sometimes deny requests for invalid reasons - Suggestion: educate registries on what is and is not a valid reason for denial - No way to renew access before existing access expires - Suggestion: have zone file access auto renew unless the requestor or registry opts-out of auto-renewal. - Allow requests for zone files access/renewals be submitted before existing access expires - - Downloads are sometimes broken, incomplete, or empty - Suggestion: provide a hash/md5 of the files as part of the API could fix this - Additionally, enforce a standard format for the returned zone files, ex: ASCII files with punycode encoded domains, all lowercase, sorted, etc... - Downloads are not always updated - Suggestion: update zone files daily at a minimum - Also, add an API feature to see the last-modified time to know when the zone file is from - No automated way to send ICANN complaints - Suggestion: make this part of CZDS and provide API access - ICANN sometimes takes months to respond to complaints - Suggestion: Post stats of latency of complain resolutions k
participants (2)
-
k claffy -
Russ Housley