[TSG-Access-RD] F2F notes and homework assignment

Eleeza Agopian eleeza.agopian at icann.org
Wed Jan 16 19:12:03 UTC 2019


Dear all,

Thanks again for two productive days of work this week. I have added some more details to the shared Google notes document<https://docs.google.com/document/d/1Bpt9-wpT7y6TVJ6GWP6YTN3tp97jG9m64OuNq5rgVi4/edit>, which can be found here and attached. Included toward the end of the notes is the list of action items. Also, please note action item 8, which is the homework assignment the group discussed yesterday. Here are the action items:


  1.  Add to charter assumptions: Data holders assume that ICANN will ensure validity of credentials. (DONE)
  2.  Enumerate list of errors that can happen in data collection (registrants and registrars). The outcomes of what should be done with these errors should be referred to policy decision makers
  3.  Recommend that ICANN have a web portal to report on collection errors. In the RDAP process, provide a response with a link to the process
  4.  Group should consider what attributes (claims) to associate/encode in tokens? Who/why/what (data fields)/by when?
  5.  Who has access to logs and who maintains logs. Answer: If there’s a central model, then it could be done on a requestor-by-requestor basis. Counter productive in a decentralized model. (See Data Transport/Storage Question 2)
  6.  Whether access is centralized or not; in order to provide authorized parties with access to logs, having ICANN be the party that aggregates logs and provides access is the only feasible model. Would require CPs to submit their log data to ICANN on some schedule and in a standardized format. How third parties can access that data is an implementation choice for ICANN. (See Data Transport/Storage Question 3)
  7.  Benedict/John/Tomofumi to send language on current security/resiliency standards, referencing e.g. ISO standards, etc. (Received language from Benedict that’s added in the notes.)
  8.  All to email list with features they believe are required for the system. To be discussed on 22 Jan. 2019 TSG call.

Attached a pic from our team dinner. Scott, we’ll be sure to photoshop you in. 😊

Thanks again,
Eleeza

Eleeza Agopian
Strategic Planning & Initiatives Senior Manager
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA  90094
+1 310 418 8985 mobile
eleeza.agopian at icann.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tsg-access-rd/attachments/20190116/c03e975c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMG_2177.jpg
Type: image/jpeg
Size: 2001497 bytes
Desc: IMG_2177.jpg
URL: <http://mm.icann.org/pipermail/tsg-access-rd/attachments/20190116/c03e975c/IMG_2177-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TSG Jan. 2019 F2F notes.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 15705 bytes
Desc: TSG Jan. 2019 F2F notes.docx
URL: <http://mm.icann.org/pipermail/tsg-access-rd/attachments/20190116/c03e975c/TSGJan.2019F2Fnotes-0001.docx>


More information about the TSG-Access-RD mailing list