- CCPDP4-CS-SG - lists.icann.org

Invitation - Global UA Day
by CEO NIXI March 25, 2023

March 25, 2023

Dear Sir/Madam, UASG (Universal Acceptance Steering Group) is created by ICANN in 2015 with the objective of promoting Universal Acceptance in Computing systems across the world. Till date, there is a budge among technical community, user community, Government and academia about the need of Universal Acceptance. However, Universal Acceptance ready systems are below 3% globally. Therefore, there is an urgent need for all of us to work together as a team, as a community to ensure that those who are left out from the Internet revolution should be brought within Internet fold to make use of a wonderful invention called “Internet”. We expect out of 2.7 billion left out citizens globally, at least 1.0 billion can be brought within Internet system using UA ready software and hardware. UASG has taken an initiative to make a big awareness programme of UA by celebrating Global UA Day on 28 th March which is led by India for 2023 and I am chairing the Implementation Committee for the same. Global objective of UASG which will not only result in adding more broadband users but also initiate several other positive outcomes like development of new softwares, upgradation of existing hardware and also creation of new jobs. It is also expected that global GDP may see a boost by adding more internet users in the system. I as Chair of UASG Comm. Working Group invite you to two days inaugural Global UA Day celebration at New Delhi. Details of programme with link to join are enclosed for your reference. With kind regards, Anil Kumar Jain CEO, NIXI Chair, UASG Communication Working Group Chair, Implementation Committee, Global UA Day celebration 2023 Chair, India Internet Governance Forum Vice Chair – IDN ccTLD W4 Liaison Officer between IDN ccTLDW4 & IDN gTLD EDP Member-IDN gTLD EPDP Member - IGLC [ https://rashtragaan.in/ ]

1 1

Second reading procedural approach delineation scope of comparison
by Bart Boswinkel Feb. 24, 2023

Feb. 24, 2023

Dear all, Please find included the latest version of the working document on Confusing similarity. Note for those who were not able to attend the last call of the sub-group, the proposed procedural approach and related suggestions were supported by all on the call. As discussed on the call this is second reading of the final open issues. You are kindly requested to review the following sections for second reading * Section 4.1.2.3 page 27 – 29 (marked yellow). * Section 4.1.2.3 B page 30- 32) * Section 4.1.2.4 (page 32). This was original included as section 5.5.2.1.4) but will now be required given the procedural manner to delineate the scope of comparison. * Section 5.3.1 page 38, now includes reference to expansion of similarity evaluation panel (as required under 4.1.2.4) * Section 5.5.2.1.3 page 41 Finally, second reading of the notes and observation on page 43 (addressing situation selected IDN ccTLD is confusingly similar , but delegatable variant is not) and page 44, situation delegatable variant is confusingly similar with previously already delegated IDNccTLD referring to the same territory. If any substantive issues, please reply to this email by Wednesday 1 March 2023 17.00 UTC. Editorial suggestions are of course always welcome and can be send to me privately or to the list. Next Steps”: after the sub-group supports the proposed changes in second reading it will be put before the full group for adoption. Kind regards, Bart

1 0

NOTES | ccPDP4 IDN Confusing Similarities SG teleconference (#17) | 21 February at 14:00 UTC
by Joke Braeken Feb. 21, 2023

Feb. 21, 2023

DOCUMENT TYPE NOTES SESSION ccPDP4 IDN Confusing Similarities SG teleconference (#17) DATE 21 February 2023 TIME 14:00 UTC 1. Welcome Welcome by Anil 2. Admin matters Bart: very low participation today. Do you wish to continue? Anil: yes. Others might join later 2 action items: * Katrina and Patricio appointed as board liaisons. They both joined today’s meeting. * Following discussions 4 weeks ago, the base for comparison had to be adjusted, to be used for CS review. 1 major item still to discuss: the base for comparison. Other items have been agreed upon. The section on CS will be included in the base doc, for discussion and adoption by the full group. If the CS subgroup finalises its work on 7 March, the full group will meet every week, to have the initial report ready for public comment by end April. Update EPDP effort: No fresh update from Anil. deferred to next week, when the full group meets. Ariel: In general the EPDP Team is wrapping up its phase 1 deliberation, still aiming to publish Initial Report in April 2023 Anil: will the meeting on 7 March happen? Close to ICANN76 Bart: let’s discuss at the end of the meeting today 3. Update base document 1. Review section 4.1.2 (3) Page 28 Does the procedural approach address your concerns? Mirjana: it does Jaap: yes, good to see Mirjana is happy. Bart: noted the typos and formatting. Do you agree with including the likelihood of misconnection? No red marks Mirjana: what is “likelihood”? Bart: probable, but not possible. Expending similarity evaluation panel Do you agree? No red marks 2. Review deleting section 5.5.2.1.4 (now included in 4.1.2 (3) Page 41. Similarity evaluation Group agrees to include section in yello 3. What if section (2) added notes and observations (page 43) Page 43. Question by Sarmad. What would happen if a selected IDN ccTLD string is considered not valid, but a delegatable string would be valid, and the applicant needs to apply again. Restart process is an administrative burden. Delegatable variant will become the preferred string. Notes & observations: not part of the policy itself. Help with the interpretation. Do you agree? No red marks Bart: second reading online only 4. Next meeting 1. 28 February – Full Group 2. 7 March – CS subgroup TBD Not needed, 2nd reading online 5. Closure Thank you all. Bye Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> = = = ICANN76 LINKS TO BOOKMARK NOW • ccNSO Schedule https://community.icann.org/x/8IMFDQ • ccNSO Session Highlights https://community.icann.org/x/kYYFDQ • Tech Day https://community.icann.org/x/WIQ-DQ From: CCPDP4-CS-SG <ccpdp4-cs-sg-bounces(a)icann.org> on behalf of Kimberly Carlson <kimberly.carlson(a)icann.org> Date: Friday, 17 February 2023 at 18:10 To: "ccpdp4-cs-sg(a)icann.org" <ccpdp4-cs-sg(a)icann.org> Subject: [CCPDP4-CS-SG] REMINDER: ccPDP4 IDN Confusing Similarities SG teleconference (#17) | 21 February at 14:00 UTC Dear all, As a reminder, the next ccPDP4 IDN Confusing Similarities SG teleconference (#17) is scheduled for 21 February at 14:00 UTC. Agenda: 1. Welcome 2. Admin matters 3. Update base document 1. Review section 4.1.2 (3) 2. Review deleting section 5.5.2.1.4 (now included in 4.1.2 (3) 3. What if section (2) added notes and observations (page 43) 1. Next meeting 1. 27 February – Full Group 2. 7 March – CS subgroup TBD 1. Closure Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=ZmRTRGhLSWsxVldNa0NQZHdldTNsZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/91528741726?pwd=ZmRTRGhL…> Meeting ID: 915 2874 1726 Passcode: PDP4-CS#17 Wiki: https://community.icann.org/x/aIDKDQ

1 0

REMINDER: ccPDP4 IDN Confusing Similarities SG teleconference (#17) | 21 February at 14:00 UTC
by Kimberly Carlson Feb. 21, 2023

Feb. 21, 2023

Dear all, As a reminder, the next ccPDP4 IDN Confusing Similarities SG teleconference (#17) is scheduled for 21 February at 14:00 UTC. Agenda: 1. Welcome 2. Admin matters 3. Update base document 1. Review section 4.1.2 (3) 2. Review deleting section 5.5.2.1.4 (now included in 4.1.2 (3) 3. What if section (2) added notes and observations (page 43) 1. Next meeting 1. 27 February – Full Group 2. 7 March – CS subgroup TBD 1. Closure Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=ZmRTRGhLSWsxVldNa0NQZHdldTNsZz09 Meeting ID: 915 2874 1726 Passcode: PDP4-CS#17 Wiki: https://community.icann.org/x/aIDKDQ

2 1

ccPDP4 IDN Confusing Similarities SG teleconference (#17) | 21 February at 14:00 UTC
by Kimberly Carlson Feb. 21, 2023

Feb. 21, 2023

**STARTING IN ONE HOUR*** Dear all, The next ccPDP4 IDN Confusing Similarities SG teleconference (#17) is scheduled for 21 February at 14:00 UTC. An agenda will be circulated prior to the call Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=ZmRTRGhLSWsxVldNa0NQZHdldTNsZz09 Meeting ID: 915 2874 1726 Passcode: PDP4-CS#17 Wiki: https://community.icann.org/x/aIDKDQ

1 0

ccPDP4 IDN Confusing Similarities SG teleconference (#17) | 21 February at 14:00 UTC
by Kimberly Carlson Feb. 7, 2023

Feb. 7, 2023

Dear all, The next ccPDP4 IDN Confusing Similarities SG teleconference (#17) is scheduled for 21 February at 14:00 UTC. An agenda will be circulated prior to the call Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=ZmRTRGhLSWsxVldNa0NQZHdldTNsZz09 Meeting ID: 915 2874 1726 Passcode: PDP4-CS#17 Wiki: https://community.icann.org/x/aIDKDQ

1 0

Canceled: ccPDP4 Confusing Similarities SG teleconference (16) | 7 February at 14:00 UTC
by Kimberly Carlson Feb. 6, 2023

Feb. 6, 2023

Dear all, The ccPDP4 Confusing Similarities SG teleconference (16) is scheduled for 7 February at 14:00 UTC. An agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=eVFybTZsRVZaQUJsc3ZRY1JRaUNmdz09 Meeting ID: 915 2874 1726 Passcode: PDP4-CS#16 Wiki: https://community.icann.org/x/YgWjDQ

1 0

CANCELED: ccDPP4 Confusing Similarities teleconference |(16) | 7 February
by Kimberly Carlson Feb. 6, 2023

Feb. 6, 2023

Dear all, Apologies for the late notice. The ccPDP4 Confusing Similarities SG teleconference scheduled for 7 February has been canceled. The full group will meet next Tuesday, 14 February at 14:00 UTC and CS Subgroup on 21 February at 14:00 UTC. Call invitations will be sent shortly. Best, Kim

1 0

ccPDP4 Confusing Similarities SG teleconference (16) | 7 February at 14:00 UTC
by Kimberly Carlson Jan. 25, 2023

Jan. 25, 2023

Dear all, The ccPDP4 Confusing Similarities SG teleconference (16) is scheduled for 7 February at 14:00 UTC. An agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/91528741726?pwd=eVFybTZsRVZaQUJsc3ZRY1JRaUNmdz09 Meeting ID: 915 2874 1726 Passcode: PDP4-CS#16 Wiki: https://community.icann.org/x/YgWjDQ

1 0

NOTES | ccPDP4 Confusing Similarities SG #15 | Tuesday, 24 January 2023 (14:00 UTC)
by Joke Braeken Jan. 25, 2023

Jan. 25, 2023

NOTES | ccPDP4 Confusing Similarities SG #15 | Tuesday, 24 January 2023 (14:00 UTC) 1. Welcome Welcome by Kenny and Anil 2. Admin items, if any a. Action Items none b. Meeting GNSO EPDP Anil: have we invited the EPDP WG? Bart: ICANN staff and Dennis confirmed they would invite the other group Kim: I forwarded the invite to Ariel Anil: i will also mention it during the upcoming EPDP session on Thursday c. Progress Full group (Review Mechanisms is completed) The full group completed its work on the review mechanism a week ago. Next work item: stress testing by the full group. They will continue until completed. Idea is to invite the EPDP group to the next full group meeting, next Tuesday. They will participate in the stress testing. The full wG will focus on stress testing, in parallel with the CS-subgroup. Highlights: * The RM as proposed by ccPDP3-RM will apply to decisions regarding the de-selection of IDN ccTLDs. * The group also completed its discussion whether or not the validation checks by icann org should be subject to the RM. They agreed that none of the validations should be subject to review. They are very factual, the impact is low, and there is an opportunity to discuss. * The 2nd panel (risk mitigation CS) is subject to (notes missing) * General statement: the icann independent review process and reconsideration process are not applicable. The selection procedure for this policy is excluded from the IRP and reconsideration. 3. Review of CS Document a. Updates of doc after 20 December meeting 1. Section 4.1 page 26-32 Now includes Description of base of comparison now includes the text from the originally agreed working document from August 2022, to provide more context to the choices made at the time. 2 risk categories: * No connection * Misconnection Bart: Do you agree that we go back to the text, agreed upon in August last year? Anil: What do members think? Open the floor to all Bart: what was discussed with Mirjana needs to be separated out. We will revisit that Bart: see docs on wiki. If you agree to go back to August, please use green zoom marks No red, some green. Bart: Any concerns regarding this text? Just to make sure the subgroup supports the approach Sarmad: This is slightly different from the solution by the GNSO. That is ok, but needs to be pointed out. In the request from the board there was a request for consistency. The WG may want to explain, or discuss with GNSO. Bart: this was raised during the last joint meeting as well. It was clear that with respect to this part of the CS, there are some differences. Alo in terms of process and procedures. Type of process, scope of policy, specifics from around IDN ccTLD strings. Need to be delegatable etc. to be included, once the doc will be published. This was an issue. Agreed to explain, along the lines just sketched. Remains to be seen whether this is sufficient to the Board. Jiankang: can Sarmad give a summary of the main differences between ccNSO and GNSO policy recommendations? Sarmad: scope of comparison for gTLDs is the string and its allocatable variants. That is a slightly larger set than the delegatable variants. When it is compared, the comparison is with string and allocatable variants on the one hand, and on the other hand the string, allocatable variants and the blocked ones. L2 on one side, level 3 on the other side. 2. Discussion impact of confusing similarity Requested variant Case B and C (page 43- 44) In green: what was discussed on 6 December meeting Agreement by group Yellow sections Do you agree? Few green marks, no red Sarmad: suppose there is an application. All meaningful labels. One is found CS. whole set then gets rejected. Re-application with the same set. Primary is changed to one of the delegatable variants. Only one is rejected (originally the primary) and the others get passed. 2 different outcomes, with the same set of strings. Bart: appreciate the point. But it is what it is. Applicant could foresee this upfront. Mirjana: when we applied for our IDN, we were not sure whether it was going to be accepted. Icann staff advised us to ask for 2 strings. Bart: is it is a concern whether it is string A or B? End-result is a delegatable variant Suggests to include Sarmad’s observation, alerting to the example Mirjana raised. Anil: agree Bart: selected string has passed. The primary core string is considered invalid? Then there is the opportunity for review, since it is the selected string. Should a review be allowed in case a delegatable variant is considered to be invalid, by the first panel Sarmad: primary string and delegatable string could be similar to each other, but not to other strings Bart: thar is dealt with. Variants always need to be delegated to the same entity If it is delegatable or confusingly similar to another TLD operated by the same entity (ascii and IDN), it should pass. To be noted. Sarmad: to be mentioned explicitly. Bart: agrees. Refer to the specific section in the similarity review process. 3. For 2nd reading: Inclusion of expansion of the SEP, page 40 See comment by Jiankang Expert with familiarity of the script Anil: should we call it ESEP? Sarmad: clarifications from process point of view. To be done before the evaluation? Bart: should be done before the evaluation. Before the final evaluation result is done. c. Discussion scope base for comparison Mirjana’s note (page 28-32) Mirjana: see note Bart: concerns regarding misconnection? Mirjana: indeed. No connection is no harm Bart: how does the misconnection work? The blocked variant cannot be included in the DNS Mirjana: correct. Bart: assumption the misconnection will only happen if the string is included in the DNS. there might be confusion, but more along the lines of typos. Sarmad: in the case of Mirjana, A1 may not be visually similar, but same for other reasons. Looking at Mirjana’s example, the 2 strings are variants potentially of eachother, but the 3rd one is not. If someone applies for the 2nd string on the screen, and someone else applies for the 3rd string, the panel might consider them similar. If someone applies for string 1 and someone else for string 3, they are not considered similar. Both can get delegated and added to the root zone. If someone is just looking at string 3, they may think it is something like string 2, and therefor think it is the same as string 1. Jaap: not up to the rule makers. If there is a blocked variant, they look the same in this case. Bart: procedural approach, allow the panel to come up with a rationale Jaap: that would work Mirjana: still do not see how the panelists would handle this They must have a script specialist. Sarmad: IDN pdpd group is coming to a similar conclusion. Panel to see in which blocked cases become relevant Bart: we come from different directions. Interesting. 4. First reading consolidated document 5. Next meetings o Full Group | 31 January 2023 @ 14.00 UTC o CS Subgroup | 07 February 2023 @ 14.00 UTC Anil and Bart thank all for the lively discussion. Bye all. Joke Braeken joke.braeken(a)icann.org From: CCPDP4-CS-SG <ccpdp4-cs-sg-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 24 January 2023 at 15:13 To: Kimberly Carlson <kimberly.carlson(a)icann.org>, "ccpdp4-cs-sg(a)icann.org" <ccpdp4-cs-sg(a)icann.org> Subject: Re: [CCPDP4-CS-SG] ccPDP4 Confusing Similarities SG teleconference (15) | 23 January at 14:00 UTC Hello All. To follow the live notes during today’s ccPDP4-CS subgroup meeting, go to https://docs.google.com/document/d/1Ct_ev0vMijD_qEqGZEKXYP5TAuBtjZGwVGJut02… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Ct_ev0vMijD_…> Best regards, Joke Braeken joke.braeken(a)icann.org From: CCPDP4-CS-SG <ccpdp4-cs-sg-bounces(a)icann.org> on behalf of Kimberly Carlson <kimberly.carlson(a)icann.org> Date: Monday, 23 January 2023 at 12:55 To: "ccpdp4-cs-sg(a)icann.org" <ccpdp4-cs-sg(a)icann.org> Subject: [CCPDP4-CS-SG] ccPDP4 Confusing Similarities SG teleconference (15) | 23 January at 14:00 UTC Dear all, As a reminder, the ccPDP4 Confusing Similarities SG teleconference (15) will be 23 January at 14:00 UTC. Agenda: 1. Welcome 2. Admin items, if any a. Action Items b. Meeting GNSO EPDP c. Progress Full group (Review Mechanisms is completed) 1. Review of CS Document a. Updates of doc after 20 December meeting * Section 4,1 page 26-32 Now includes Description of base of comparison now includes the text from the originally agreed working document from August 2022, to provide more context to the choices made at the time. * Discussion impact of confusing similarity Requested variant Case B and C (page 43- 44) * For 2nd reading: Inclusion of expansion of the SEP, page 40 * Discussion scope base for comparison Mirjana’s note (page 28-32) 1. First reading consolidated document 2. Next meetings * Full Group | 31 January 2023 @ 14.00 UTC * CS Subgroup | 07 February 2023 @ 14.00 UTC Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/97250338439?pwd=OW1qbVhEaUFYeHAzcVZrcExYVDdHQT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/97250338439?pwd=OW1qbVhE…> Meeting ID: 972 5033 8439 Passcode: PDP4CS-124 Wiki: https://community.icann.org/x/wgGBDQ

2 1