- Bc-gnso - lists.icann.org

FILED: BC comment on ICANN Code of Conduct on SOIs
by Steve DelBianco 02 Dec '24

02 Dec '24

Today the BC filed the attached comment on the ICANN Community Participant Code of Conduct on SOIs and General Ethics Policy. See it online here<https://www.icann.org/en/public-comment/proceeding/icann-community-particip…>. Thanks to Bartlett, Lawrence, Segunfunmi, and Arinola for drafting. -- Steve DelBianco Vice Chair for Policy Coordination +1.703.615.6206

1 0

FILED: BC comment on Initial Report on Transfer Policy Review
by Steve DelBianco 30 Sep '24

30 Sep '24

Today the BC filed the attached comment on the Initial Report on the Transfer Policy Review<https://www.icann.org/en/public-comment/proceeding/initial-report-on-the-tr…> Thanks to Zak and Arinola for representing the BC on this working group, and for others who helped Zak to draft this comment: Lawrence, Tess Diaz, Sven Echternach, and Rachel Shitanda.

1 0

ICANN Registration Data Request System (RDRS) report for Aug-2024
by Steve DelBianco 23 Sep '24

23 Sep '24

BC members – the August report for RDRS is posted here<https://www.icann.org/en/system/files/files/rdrs-usage-metrics-16sep24-en.p…>. Below is a key graph of disclosure requests, which Org is using to gauge demand from our community. Requests are trending down, as you can see. [cid:image001.png@01DB0DBF.1439AB80] -- Steve DelBianco President & CEO NetChoice<https://netchoice.org/> +1.703.615.6206

1 0

FILED: BC moment on ICANN Strategic Plan and Operating Plan Framework for FY26-30
by Steve DelBianco 17 Sep '24

17 Sep '24

Here<https://www.icann.org/en/public-comment/proceeding/draft-icann-strategic-pl…> and attached is the BC comment on the Draft ICANN Strategic Plan and Operating Plan Framework for FY26-30<https://www.icann.org/en/public-comment/proceeding/draft-icann-strategic-pl…> Thanks again to drafters Tim Smith, Segunfunmi Olajide, David Snead, and Jimson Olufuye

1 0

FILED: BC support for Fundamental Bylaws Amendments Related to Grant Program
by Steve DelBianco 15 Sep '24

15 Sep '24

As discussed during our last two BC meetings, the BC filed today in SUPPORT of ICANN Org’s Proposed Fundamental Bylaws Amendments Related to Grant Program<https://www.icann.org/en/public-comment/proceeding/proposed-fundamental-byl…> As described by ICANN Org: The updated proposal incorporates specific language into both the Reconsideration (Article 4, Section 4.2) and Independent Review Process (Article 4, Section 4.3) sections of the ICANN Bylaws, but does not otherwise add to or modify the Bylaws governing either Accountability Mechanism. The language added within each section sets out an exclusion that the relevant Accountability Mechanism shall not be used for claims or disputes “relating to decisions to approve or not approve an application to the ICANN Grant Program.” This Bylaws amendment is offered as a way to fully implement part of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP) Final Report, which recommended that ICANN’s Accountability Mechanisms should not be used to challenge decisions on grant applications. That recommendation, often referred to as “Recommendation 7,” can only be fully implemented if the Bylaws that define each Accountability Mechanism are amended. -- Steve DelBianco Vice chair for policy coordinaation ICANN Business Constituency

1 0

FILED: BC comment on Data Processing Specification
by Steve DelBianco 09 Sep '24

09 Sep '24

Today we filed the attached BC comment on the Data Processing Specification for ICANN-Accredited Registries and Registrars<https://www.icann.org/en/public-comment/proceeding/data-processing-specific…>. Thanks to Segunfunmi Olajide, Margie Milam, and Steve Crocker for working on the draft.

2 1

FILED: BC comment on Han script IDN TLDs
by Steve DelBianco 16 Aug '24

16 Aug '24

Today the BC filed<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…> its comment on Han Script Single Character IDN Generic Top-Level Domains. Thanks again to Ching Ciao and Asteway Negash for drafting. Here is the summary paragraph I posted, drawing from the comment: In our Mar-2024 comment on this topic, the BC said that "cross-community consultation should help evaluate whether the current objection process is sufficient." We still believe ICANN Org should seek community consultation on this issue. At the very least, ICANN Org should arrange for the CJK GPs to sit together and develop a prohibitive list and/or reach consensus regarding strings that may be confused with geographic names. At this point, we ask ICANN Org why it seeks further community comment, since Org now says that “no further analysis is required”. The BC does not believe the string similarity review or the community objection process are sufficient in confusions related to geographic names. The BC also believes that SSAC’s SAC052 advisory from 2012 might be overcome by events, and SSAC should be asked for updated advice regarding single-character IDNs. On 8/14/24, 9:05 AM, "Steve DelBianco" <sdelbianco(a)netchoice.org> wrote: This is LAST CALL for review of our draft Draft is here<on%20Han%20Script%20Single%20Character%20IDN%20Generic%20Top-Level%20Domains> and attached. Please reply with any questions or edits before 16-Aug. Thanks again to Ching Ciao and Asteway Negash for drafting. --Steve On 8/5/24, 6:48 PM, "Steve DelBianco" <sdelbianco(a)netchoice.org> wrote: BC members: Just want to give members lots of time to review for our draft comment on Han Script Single Character IDN Generic Top-Level Domains (link<https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-scr…>). Comments close 16-Aug. We can discuss on our 8-Aug BC call as well. Thanks to Ching Chiao and Astaway Negash for drafting the BC comment (here<https://docs.google.com/document/d/1-EZHamXQFoOZYer7_VjSzstbhgvY-6AcKueGLSI…> and attached) The GNSO Final Report on the new gTLD Subsequent Procedures Policy Development Process<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…>, Rec 25.4 stated that single character gTLDs may be allowed for a character in ideograph (or ideogram) script. The GNSO’s Phase 1 Final Report on the Internationalized Domain Names Expedited Policy Development Process<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/epdp-…> (IDN EPDP Phase 1) further stated: “...the only script that meets the criteria is the Han script, which is used in the Chinese, Japanese, and Korean languages. Nevertheless, applications for single-character gTLDs that are ideographs must not be accepted until relevant guidelines from the Chinese, Japanese, and Korean Generation Panels are developed, finalized after Public Comment, and implemented in the New gTLD Program. In the event that the Generation Panels determine such additional guidelines beyond the analysis already provided in the RZ-LGR unnecessary, applications for single-character gTLDs in the Han script shall be accepted.” Thanks again to Ching and Asteway from drafting

1 0

Business Constituency (BC) response on Applicant Support Program Use of Auction Proceeds
by Steve DelBianco 12 Aug '24

12 Aug '24

Dear Tripti and members of the ICANN Board, Please see attached PDF for the ICANN Business Constituency (BC) response to your request for input on Applicant Support Program Use of Auction Proceeds<https://www.icann.org/en/blogs/details/icann-board-seeks-input-on-applicant…> Sincerely, Mason Chair ICANN Business Constituency (BC) Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency (BC)

1 0

RDRS Updates This Week
by Steve DelBianco 09 Aug '24

09 Aug '24

FYI, regarding the Registration Data Request Service (RDRS) ICANN Staff released a couple of updates to RDRS this week: (1) The ICANN Lookup Tool results page (https://lookup.icann.org<https://lookup.icann.org/>) was updated to add additional text and a link to the RDRS login page in all available languages (Arabic, Simplified Chinese, English, French, Russian, Spanish). The new text and link instruct users who don't find the registration data they seek to log in to RDRS and submit a request if they have a legitimate interest in accessing nonpublic registrations data. (2) We also released an updated "registrar concluded the review" email notification that highlights getting RDRS user feedback. Both the subject line and email body have new language that should help to increase the number of survey responses we get for RDRS.

1 0

ICANN Webinar: Registration Data Request Service (RDRS) | 8 August 2024
by Steve DelBianco 30 Jul '24

30 Jul '24

FYI on an ICANN webinar on the RDRS, Thursday, 8 August 2024, at 16:00 UTC Register here<https://icann.zoom.us/webinar/register/WN_W0Z-c55dTDm-3fDRRpdNEw#/registrat…> [https://nj88a9rab.cc.rs6.net/on.jsp?ca=c7f35d5b-dc12-4246-b891-5e62d8fa098d…] [https://files.constantcontact.com/d2ded047401/08df3b1f-27bc-477b-8c08-68928…] [https://files.constantcontact.com/d2ded047401/2a19dd51-70c1-4f34-914d-ada03…]<https://nj88a9rab.cc.rs6.net/tn.jsp?f=001fx0tgj9GACNV1zzu7z1I4_AGzM5u9GEL6g…> Don't miss the upcoming ICANN webinar on RDRS Enhancements and Insights! ICANN is pleased to announce an upcoming virtual event on the Registration Data Request Service (RDRS), scheduled for Thursday, 8 August 2024, at 16:00 UTC (9:00 a.m. PST; 12:00 p.m. EDT). The RDRS provides a more consistent and standardized format for handling requests to access nonpublic registration data related to generic top-level domains (gTLDs). We invite all stakeholders to register for this informative session, which will educate potential requesters with an aim of increasing overall participation. This webinar will explain the purpose and benefits of RDRS to registrants and those with a need to access non-public gTLD registration data. In addition to providing an overview and sharing resources, the webinar will provide an overview of the service and more. The webinar will be followed by a Q&A session, allowing prospective and current users to engage directly with the speakers. Join us on Thursday, 8 August 2024, at 16:00 UTC! WEBINAR REGISTRATION<https://nj88a9rab.cc.rs6.net/tn.jsp?f=001fx0tgj9GACNV1zzu7z1I4_AGzM5u9GEL6g…> [LinkedIn]<https://nj88a9rab.cc.rs6.net/tn.jsp?f=001fx0tgj9GACNV1zzu7z1I4_AGzM5u9GEL6g…> [X] <https://nj88a9rab.cc.rs6.net/tn.jsp?f=001fx0tgj9GACNV1zzu7z1I4_AGzM5u9GEL6g…> [Instagram] <https://nj88a9rab.cc.rs6.net/tn.jsp?f=001fx0tgj9GACNV1zzu7z1I4_AGzM5u9GEL6g…> [Facebook] <https://nj88a9rab.cc.rs6.net/tn.jsp?f=001fx0tgj9GACNV1zzu7z1I4_AGzM5u9GEL6g…> Follow ICANN on Social Media ICANN | 12025 Waterfront Dr. Suite 300 | Los Angeles, CA 90094 US Unsubscribe<https://visitor.constantcontact.com/do?p=un&m=001fV5zcrmnzCVnMiD3Cw8NvQ%3D&…> | Update Profile<https://visitor.constantcontact.com/do?p=oo&m=001fV5zcrmnzCVnMiD3Cw8NvQ%3D&…> | Our Privacy Policy<https://www.icann.org/privacy/policy> | Constant Contact Data Notice<http://www.constantcontact.com/legal/about-constant-contact>

1 0