[Ssr2-review] Please make sure that all Subteam Status is up to date

k claffy kc at caida.org
Wed Jul 1 04:23:02 UTC 2020


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/1cOZ1lPXqHfuZNt68zvB5xRB63eBoL3gonDbhDuHEx7k/edit#gid=0
  
  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


More information about the Ssr2-review mailing list