March 2020 - Bc-gnso - lists.icann.org

Draft Proposal for NextGen@ICANN Program Improvements
by Steve DelBianco 31 Mar '20

31 Mar '20

Attached is the comment of ICANN’s Business Constituency (BC) regarding the Draft Proposal for NextGen@ICANN Program Improvements. This comment was drafted by Mark Datysgeld. It was approved in accord with our Charter. -- Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency (BC)

1 0

Business Constituency (BC) comment on Name Collision Analysis Project (NCAP) Study 1
by Steve DelBianco 31 Mar '20

31 Mar '20

Below (and attached) is the comment of ICANN’s Business Constituency (BC), regarding the Name Collision Analysis Project (NCAP) Study 1. (https://www.icann.org/public-comments/ncap-study-1-2020-02-13-en ) The BC appreciates the work of SSAC and of the Study authors, and offers brief comments on just two sections of the Study: Section 4. Evidence of harm from prior experience. The Study explains there is only scant data in evidence of collisions. The BC is concerned that an apparent lack of evidence might lead SSAC and ICANN to become casual or complacent about collision risks in the next round of gTLD expansion. The Study explains the difficulty of getting reliable evidence, so continued mitigation seems prudent. That would be especially true for .home, .corp, and .mail. Section 5. the purpose and scope of upcoming study 2 and Study 3. The author of this Study seems to suggest that data sets and further data studies may not be warranted: “It is not obvious that additional datasets would be needed for Studies 2 and 3. Information on previous and recent leakage of corp, home, and mail should already be captured in the DITL and ORDINAL datasets. A current dataset for corp.com could be valuable for comparing current leakage of the corp domain to 2014-era leakage. Similar datasets for the home and mail counterparts to corp.com (e.g., home.com and mail.com) might also be valuable, although much of the same information might be available through the DITL and ORDINAL datasets. As for identifying causes of name collisions, they have already been established in some cases, usually by individuals researching a particular leaked TLD to find its origin. There is unlikely to be any dataset that would contain root causes; identifying root causes is generally going to require research on a case-by-case basis. Based on previous research and studies, such as [76], it seems quite likely that there is not a single root cause for most name collisions, but rather several types of root causes.” (page 39 of the Study) The BC is also not convinced that we need additional data sets and studies, and defers to SSAC to make that determination. But the BC does support further research on case-by-case basis when collision potential or problem is reported. -- This comment was drafted by Mark Svancarek and Steve DelBianco and was approved in accord with our charter. -- Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency (BC)

1 0

Re: [bc-gnso] [Ext] Business Constituency (BC) response to EPDP Phase 2 Initial Report
by Caitlin Tubergen 23 Mar '20

23 Mar '20

Hi Steve, I confirm that your public comment submission has been officially received, and I have entered the remaining BC comments into the Google Form Spreadsheet. Thank you. Best regards, Caitlin From: Steve DelBianco <sdelbianco(a)netchoice.org> Date: Monday, March 23, 2020 at 10:34 AM To: Caitlin Tubergen <caitlin.tubergen(a)icann.org>, Policy Staff <policy-staff(a)icann.org> Cc: "Bennett, Andrew" <Andrew.Bennett(a)disney.com>, Mason Cole <MCole(a)perkinscoie.com>, BC List <bc-gnso(a)icann.org> Subject: [Ext] Business Constituency (BC) response to EPDP Phase 2 Initial Report Caitlin, Attached is the response of the ICANN Business Constituency (BC), in both Word and PDF formats. These comments were drafted by Mason Cole and Andrew Bennett. They were approved in accord with the BC Charter. Please just confirm that this email is sufficient as our official submission. Thanks, Steve On 3/23/20, 12:56 PM, "Caitlin Tubergen" <caitlin.tubergen(a)icann.org> wrote: Hi Steve, Thank you for reaching out. If you or one of your colleagues can please submit your entire response in Word format, we can manually input the comments for you. Thank you. Best regards, Caitlin From: Steve DelBianco <sdelbianco(a)netchoice.org> Date: Monday, March 23, 2020 at 9:55 AM To: Policy Staff <policy-staff(a)icann.org>, Caitlin Tubergen <caitlin.tubergen(a)icann.org> Cc: "Bennett, Andrew" <Andrew.Bennett(a)disney.com>, Mason Cole <MCole(a)perkinscoie.com> Subject: [Ext] EPDP phase 2 draft Caitlin – While submitting our EPDP phase 2 response, we get the error message “Your response is too large. Try shortening some answers.” And we’re only halfway thru our responses at this point! Can you help with that? Or should we just submit all of our responses in a single document? --Steve

1 0

Business Constituency (BC) response to EPDP Phase 2 Initial Report
by Steve DelBianco 23 Mar '20

23 Mar '20

Caitlin, Attached is the response of the ICANN Business Constituency (BC), in both Word and PDF formats. These comments were drafted by Mason Cole and Andrew Bennett. They were approved in accord with the BC Charter. Please just confirm that this email is sufficient as our official submission. Thanks, Steve On 3/23/20, 12:56 PM, "Caitlin Tubergen" <caitlin.tubergen(a)icann.org<mailto:caitlin.tubergen@icann.org>> wrote: Hi Steve, Thank you for reaching out. If you or one of your colleagues can please submit your entire response in Word format, we can manually input the comments for you. Thank you. Best regards, Caitlin From: Steve DelBianco <sdelbianco(a)netchoice.org> Date: Monday, March 23, 2020 at 9:55 AM To: Policy Staff <policy-staff(a)icann.org>, Caitlin Tubergen <caitlin.tubergen(a)icann.org> Cc: "Bennett, Andrew" <Andrew.Bennett(a)disney.com>, Mason Cole <MCole(a)perkinscoie.com> Subject: [Ext] EPDP phase 2 draft Caitlin – While submitting our EPDP phase 2 response, we get the error message “Your response is too large. Try shortening some answers.” And we’re only halfway thru our responses at this point! Can you help with that? Or should we just submit all of our responses in a single document? --Steve

1 0

Business Constituency (BC) comment on 2nd Security, Stability, and Resiliency (SSR2) Review Draft Report
by Steve DelBianco 10 Mar '20

10 Mar '20

Attached is the comment of ICANN’s Business Constituency (BC) regarding the 2nd Security, Stability, and Resiliency (SSR2) Review Team Draft Report. This comment was drafted by Mason Cole, Susan Kawaguchi, Ben Wallis, Roger Baah, and Yusuph Kileo. It was approved in accord with our Charter. -- Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency (BC)

1 0