November 2022 - Gnso-epdp-idn-team

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 01 December 2022 at 13:30 UTC
by Devan Reed Nov. 30, 2022

Nov. 30, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 01 December 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/N4YFDQ * Check your time zone: https://tinyurl.com/2r8cs89c [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2r8cs89c__;!!PtGJab4!5Cm11f2…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

Post Call | Joint: IDNs EPDP Team with ccPDP4 | Tuesday, 29 November 2022
by Devan Reed Nov. 30, 2022

Nov. 30, 2022

Dear all, All recordings for the Joint: IDNs EPDP Team with ccPDP4 held on Tuesday, 29 November 2022 can be found on the agenda wiki page <https://community.icann.org/x/cYoFDQ> (attendance included) and the GNSO Master Calendar. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-idn-team/> and the main wiki page<https://community.icann.org/x/uAPpCQ>. Thank you! Kind Regards, Devan

3 2

Proposed Agenda - IDN EPDP Meeting #60 - Thursday 1 December 2022 at 13:30 UTC
by Emily Barabas Nov. 30, 2022

Nov. 30, 2022

Dear all, Please find below the proposed agenda for our meeting on Thursday 1 December 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #60 Proposed Agenda 1. Roll Call and SOI Updates (2 mins) 2. Welcome and Chair Updates (5 min) 3. Recap of Charter Question B4<https://docs.google.com/document/d/1LlorzuwJlZ1jUZTw9Frwy-wJkTdQ559p0R2ogGR…> - Delegation of variants gTLDs vis a vis primary string (5 mins) 4. Continued Discussion of Charter Question E2<https://docs.google.com/document/d/1glGuJwSoYlYFvdRWtDWf9UvrLKk2hq7kW-osHJe…> (75 mins) * Potential Outcomes for Legal Rights and Community Objections * Exceptions Process 1. AOB (3 mins)

1 0

Notes and action items - Joint Meeting: ccPDP4 IDN and GNSO IDN EPDP - 29 November 2022
by Emily Barabas Nov. 29, 2022

Nov. 29, 2022

Dear all, Please find below the notes and action items from today’s meeting on 29 November 2022 at 14:00 UTC. Kind regards, Ariel, Steve, and Emily Joint Meeting: ccPDP4 IDN and GNSO IDN EPDP 29 November at 14:00 UTC High-Level Notes and Action Items Welcome to joint meeting * Agenda review Why joint session? * Slide 3: Board asked ccNSO and GNSO to coordinate their policy development efforts with respect to variant management. The respective working groups are making progress on work related to variant management for the confusing similarity validation process (ccPDP4 term) and string similarity review (GNSO EPDP term). ccNSO Perspective on Confusing Similarity and Variants * Slide 5: Scope of ccPDP4 is review, overhaul and completion of 2013 recommendations on the selection of IDN ccTLD strings. * Slide 6: Overhaul 2013 recommendations is needed to align with curent procedures under the Fast Track process (which is on-going). * Slide 7: Overhaul Confusing Similarity Validation: Goal and Criteria * Slide 8: Overhaul Confusing Similarity Validation: Base of Comparison * Slide 9: Overhaul Confusing Similarity Validation: Base of Comparison Rationale * Question: On the GNSO side, applications for IDNs will be part of the new gTLD application process. These applications will come in as part of standard rounds that also include ASCII applications. There may be up to 2000 or more applications in a round. The recommendations seek to provide guidance on processes that will handle such circumstances. How and when will applications be submitted on the cc side? * Response: Once the ccPDP4 completes its work and policy is confirmed, the application process will be kicked off. The timeframe will likely be different from the GNSO timeframe. GNSO Perspective * Slide 11-12: Background -- EPDP Team focused its discussion on variants’ role in the String Similarity Review. It considered three possible levels of comparison, and then put forward a preliminary recommendation on a “hybrid model.” * Slide 13: Three Levels of Comparison * Slide 14-15: Recommendation: Hybrid Model – note that this recommendation has not yet been finalized pending analysis of input from ICANN org on the operational implications of the recommended approach. * Slide 16: How Does the Hybrid Model Work: Arabic TLDs Example – this example includes applied-for primary strings, allocatable variants and blocked variants. * Slide 17: How Does the Hybrid Model Work: Arabic TLDs Example – each number represents a comparison that will take place. * Slide 18: Summary: Arabic TLDs Example – demonstrates the potential outcomes of such a set of comparisons. * Slide 19: Rationale for the Hybrid Model – seeks to strike the balance of reducing the total number of comparisons while mitigating the risk of failure modes. * Slide 20: Relevant Background for Consideration of Hybrid Model -- RFC 5891, RFC 6912, SAC 089, Staff Paper. * Slide 23: Misconnection: Potential Consequences – Misconnection may be more problematic than denial of service and cause more harm to the user beyond confusion and frustration, including becoming a vector for DNS abuse. · Question: ccPDP4 focused on misconnection as the primary problem that needs to be addressed from a security and stability perspective. They also looked the “no connection” (denial of service) issue. The ccPDP4 decided that it was not necessary to focus on this, given that it is not necessary to build a process around a potential mistyped or misremembered string. To what extent did the IDN EPDP decided to include this as a point of focus? · Response: IDN EPDP also considered the misconnection risk as more prominent and requiring mitigation compared to denial of service. This seems consistent with the ccPDP4’s conclusion. · Slide 26: Ongoing Deliberations on the Hybrid Model – general support from the EPDP team for the hybrid model, but some reservations have been expressed. EPDP Team requested input from ICANN org on the operational implications of this model to help the EPDP Team to understand impact of recommendations. · Question: What is the ccPDP’s policy recommendation language likely to look like? It may be acceptable for the policy recommendations to be different given that they address two different processes. · Response: The ccPDP4 has shared a document containing core recommendations on confusing similarity. One of the major differences between the two processes is that the ccPDP4 recommendations will feed into a process that is ongoing (as opposed to in rounds). A second major difference is that the cc process is more focused/limited, as summarized on slide 8. The focus is on the selected string, and its requested, delegatable variants. Delegatable Variant = Allocatable Variant that is meaningful representation of name of territory in designated language and script in which designated language is expressed. The pool of potential applicants is known and limited in the cc process. On the GNSO side, it is unknown how many applications will be received and for labels in which scripts. · The fundamental approaches seem to be the same: use of the same definitions, focusing on the potential risk of misconnection, etc. Because of differences in the processes, the specific recommendations may be different, but these differences appear to be appropriate. · As long as the recommendations are not inconsistent, there should not be any issues. If there do turn out to be inconsistencies, these will need to be explained to the Board. · Current timeline for ccPDP4 is to produce its Initial Report prior to ICANN76. · GNSO members are interested in the upcoming ccPDP4 stress test exercise, which will tentatively take place in mid-January. This will include developing scenarios and checking to see how the recommendations play out under these scenarios. The ccPDP4 will determine whether any adjustments are needed to the recommendations. Action Item: ccPDP4 to provide details of stress test sessions to IDN EPDP to allow IDN EPDP Team members to attend. Wrap-up: further coordination needed? * It was agreed that it may be helpful to meet again after the ccPDP4 has completed the stress test and before the two groups submit their respective Initial Reports (ccPDP4 tentatively to deliver Initial Report prior to ICANN76, IDN EPDP tentatively to deliver Initial Report in April 2023).

1 0

ON NOW REMINDER | Meeting Invitation | Joint Meeting: IDNs EPDP Team with ccPDP4 | Tuesday, 29 November 2022 at 14:00 UTC
by Devan Reed Nov. 29, 2022

Nov. 29, 2022

Dear all, The Joint Meeting: IDNs EPDP Team with ccPDP4 is scheduled on Tuesday, 29 November 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/99842046105?pwd=ZkRHVk9UMlZOSlpHUGtVOXFsYSs2UT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/99842046105?pwd=ZkRHVk9U…> Passcode: PDP4-Nov29 If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/ZIoFDQ * Check your time zone: https://tinyurl.com/5n6nhc24<https://urldefense.com/v3/__https:/tinyurl.com/5n6nhc24__;!!PtGJab4!6j1Sa1h…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

1 0

Joint ccPDP4 IDN and EPDP-IDNs Agenda
by Steve Chan Nov. 28, 2022

Nov. 28, 2022

Dear EPDP Team Members, Below, please find the agenda for the joint ccPDP4 IDN and IDNs EPDP meeting, scheduled for Tuesday, 29 November at 14:00 UTC. Best, Steve From: ccPDP4-IDNWG <ccpdp4-idnwg-bounces(a)icann.org> on behalf of Kimberly Carlson via ccPDP4-IDNWG <ccpdp4-idnwg(a)icann.org> Reply-To: Kimberly Carlson <kimberly.carlson(a)icann.org> Date: Monday, November 28, 2022 at 7:14 AM To: "ccpdp4-idnwg(a)icann.org" <ccpdp4-idnwg(a)icann.org> Subject: [ccPDP4-IDNWG] REMINDER: JOINT ccPDP4 IDN and GNSO EPDP teleconference | 29 Nov at 14:00 UTC Dear all, As a reminder, the JOINT: ccPDP4 IDN and GNSO EPDP teleconference, is scheduled for 29 November at 14:00 UTC. Agenda: 1. Welcome to joint meeting 2. Why a joint session? 3. ccNSO perspective on Confusing Similarity and Variants 4. GNSO perspective 5. Wrap-up: further coordination needed? Please click the link below to join the webinar: https://icann.zoom.us/j/99842046105?pwd=ZkRHVk9UMlZOSlpHUGtVOXFsYSs2UT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/99842046105?pwd=ZkRHVk9U…> Passcode: PDP4-Nov29 Wiki: https://community.icann.org/x/ZIoFDQ

1 0

REMINDER | Meeting Invitation | Joint Meeting: IDNs EPDP Team with ccPDP4 | Tuesday, 29 November 2022 at 14:00 UTC
by Devan Reed Nov. 28, 2022

Nov. 28, 2022

Dear all, The Joint Meeting: IDNs EPDP Team with ccPDP4 is scheduled on Tuesday, 29 November 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/99842046105?pwd=ZkRHVk9UMlZOSlpHUGtVOXFsYSs2UT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/99842046105?pwd=ZkRHVk9U…> Passcode: PDP4-Nov29 If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/ZIoFDQ * Check your time zone: https://tinyurl.com/5n6nhc24<https://urldefense.com/v3/__https:/tinyurl.com/5n6nhc24__;!!PtGJab4!6j1Sa1h…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

2 2

Notes and action items - IDNs EPDP Meeting #58 - 17 November 2022
by Emily Barabas Nov. 28, 2022

Nov. 28, 2022

Dear all, Please find below the notes and action items from today’s meeting on Thursday, 17 November 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily Notes and Action Items - IDNs EPDP Call – 17 November 2022 Action Items Action Item 1: EPDP Team members to review input from ICANN org and send any clarification questions to the mailing list. Action Item 2: Leadership Team to draft text in response to Charter Question B4 based on today’s discussion. Notes Welcome and Chair Updates * The GNSO Council approved the EPDP’s Project Change Request during the November Council meeting. There was some discussion on this list about the timeline, to which the leadership team provided a reply. As a reminder, the EPDP Team seeks to complete the Phase 1 Initial Report by April 2023. Donna may request to make calls two hours in length to continue making progress towards this goal. * ICANN Org has provided early input on the EPDP’s stable recommendations. The substance of this input will be covered on calls once everyone has had a chance to review. * Multiple org SMEs provided input on operational impacts of the recommendations. The org document includes three types of input: substantive, non-substantive, and assumptions (org’s interpretations of the text to be confirmed by the EPDP). There are also some general comments at the top of the document that apply to multiple sections of the text. There is an impact analysis of the String Similarity hybrid model at the end of the document. The org team did not explicitly look at other models but could do so upon request of the EPDP Team. * This may be something the EPDP Team requests in the future if it can’t find a path forward. Action Item 1: EPDP Team members to review input from ICANN org and send any clarification questions to the mailing list. Continued Discussion of Charter Question B4 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1LlorzuwJlZ1j…> - Delegation of variants gTLDs vis a vis primary string * Introduction: The EPDP Team previously discussed the possibility of delegating the variant string ahead of the primary string. From a technical perspective, it is possible to delegate the variant ahead of the primary string. But is it what we want to do from a policy perspective? Should strings in a set be delegated within the same set timeframe or should this be flexible? * Slide 4 – B4 Additional Discussion Topic * B4: What should an application process look like in terms of timing and sequence for an existing and future Registry Operator with respect to applying or activating their allocatable variant TLD labels? * Discussion Questions: 1. Should a variant gTLD be allowed for delegation prior to delegation of the primary string? 2. Should the primary string and allocatable variant labels that pass evaluation be delegated within the timeframe as affirmed by SubPro recommendations? 3. Should the variant string and the primary be delegated at the same time? * Slide 5 – Question 1 Example and Factors for Consideration * What are the assumptions of the group about whether the intent is that all of the TLDs in a set need to be delegated in close timing to one another or whether it can be done over a period of time? As a reminder, the group previously discussed that whichever string is delegated first must be delegated within a 12 months. * Comment: There are four steps 1. Application for a variant set 2. Evaluation process 3. Execution of the RA with expectation of delegation 4. Sunrise. The question of whether the primary needs to be delegated first is not trivial. The 12 month timeframe for delegation results in all of the contractual obligations kicking in. If there were different options for the timing of strings in a set, someone would have to manage that. There is no requirement for sunrise and the timing is up to the RO. In that way, they can manage the sequencing while complying with the obligations for those variant sets. The concern is the burden of managing the variants in the set. Is that something for ICANN org to manage or for the RO to manage? * Clarification: Sunrise is the process of starting to offer registrations in the TLD. This is done by the RO based on certain requirements, but the RO picks the date to sunrise. * Comment: Support for the idea that if an applicant applies for several variant labels that they all need to be activated at once or in a small window of time. The RO could decide to wait on a sunrise for certain strings based on business choices. But what would this mean for fees that the RO pays? The RO may not want to pay fees for a string it is not ready to sunrise. Additional point: If we say that the main string always needs to exist along with the variant, would you be able to delete/remove/sunset the main label and keep that variant? * Comment: On the one hand, it might benefit end users to have all of the TLDs in a set available at once. On the other hand, the RO may end up paying more fees for strings they are not yet ready to use. If there is one contract for a variant set, they should all be launched within 12 months. * Comment: It seems more complex to have serial launch of TLDs in a set and then manage that coordination/harmonization by retrofitting. It seems hard to imagine a use case where you would want that complexity rather than launching at the same time and doing coordination/harmonization of the set at once. * Response: This is something that we will have to deal with anyway, because every TLD operator will be able to apply for variant TLDs in later rounds, and the complexity associated with this later activation will need to be managed. * Question: It was noted that for Chinese TLDs from the first round, the ROs were disadvantaged because they couldn’t get their variants. When they are able to get their variants, how will this be managed? * Response: Currently without the IDN variant TLD, there are users who are not able to access certain domains as expected. This will be resolved once variants are available. It is up to the registries to deal appropriately with the addition of variants. Their plan to do so will be evaluated as part of the application process. * Comment: What does appropriate mean respect to the operation of variants? * Response: There is no guarantee of a consistent user experience. The policy is intended to enable the possibility of a consistent user experience. But it is up to the registry, registrar, and registrant to make that happen in practice. * Comment: We should not talk about guaranteeing the experience of the end user in the context of this work. There are too many steps between this work and the final experience of the end user. We can seek to make a better experience, but we can’t make guarantees. * Comment: There is a different between delegation and use. Delegation means introduction to the root. Once the applicant gets the TLD and the variants, we could have a baseline position that those strings get delegated into the root. They would be subject to the associated fees. We should not go into questions related to sunrise. This is up to the RO to manage. If an RO wants to delay delegation of the set or part of the set, they should apply to ICANN for an extension. Why are we looking beyond delegation in this discussion? * Response: Agree that our discussion should focus on delegation. But reviewing the details of sunrise helped the group understand what happens after delegation. * Suggestion: The policy doesn’t mandate the order in which the strings are delegated. There is an expectation that the primary and the variants will be delegated within a set period of time. * Slide 6 – Question 2 – Factors for Consideration * Question 2: Should the primary string and allocatable variant labels that pass evaluation be delegated within the timeframe as affirmed by SubPro recommendations? * Clarification regarding SubPro recommendation: based on the rationale, the term “use” draws on the existing definition – delegation into the root and meeting of the associated contractual commitments. * Staff note: The question with respect to applicant intent on slide 6 may need to be revisited and restructured for clarity. * Comment: We intend to be consistent with the SubPro recommendations regarding required timeframes for entering into an RA and for delegation. If multiple strings are under the same RA, it makes sense that they all follow the same timeframe requirements. To do otherwise would create excessive complexity. * Summary: There seems to be support for the idea that the sequence for delegation should not be mandated in policy, but the set should be delegated within the same timeframe. The question of how annual fees will be incurred is still outstanding and will be discussed in the future. Action Item 2: Leadership Team to draft text in response to Charter Question B4 based on today’s discussion. * Additional potential question for future consideration: Should an applicant be able to apply for a variant and not the primary label of a set. Continued Discussion of Charter Question E2 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1glGuJwSoYlYF…>- Options for Legal Rights and Community Objections * Deferred to a future call. AOB * No call next week. * Joint Meeting between IDNs EPDP Team and ccPDP4 is on Tuesday 29 November 2022 at 14:00 UTC for 90 minutes. * Next regular EPDP call is on Thursday 1 December at 13:30 UTC.

3 3

ccPDP4 Draft Document: Proposed Process and Method for Confusing Similarity Evaluation
by Ariel Liang Nov. 23, 2022

Nov. 23, 2022

Dear All, In preparation for the joint meeting with ccPDP4 on Tuesday, 29 November at 14:00-15:30 UTC, please find attached the ccPDP4’ draft document on the proposed process and method for confusing similarity evaluation. Based on staff’s understanding, the scope of discussion of string similarity in ccPDP4 seems to be much broader than IDN EPDP Team, as the EPDP Team focused on variants’ role in the review and the proposed hybrid model. It is expected that the EPDP Team will explain the mechanism and rationale of the hybrid model with ccPDP4 during the joint meeting. Please feel free to preview ccPDP4’s document in advance of the call. Thank you, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 17 November 2022 at 13:30 UTC
by Devan Reed Nov. 17, 2022

Nov. 17, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 17 November 2022 at 13:30 UTC for 90 minutes. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/NYYFDQ * Check your time zone: https://tinyurl.com/5n7jf7ca <https://urldefense.com/v3/__https:/tinyurl.com/5n7jf7ca__;!!PtGJab4!_G1vGrn…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan

2 1