October 2025 - NA-Discuss - lists.icann.org

Re: [Ext] Re: Follow-up on RSSAC Liaison Interest and Background Alignment (Context Included) ... Re: Request from NARALO Member Mohibul
by Mohibul Mahmud Oct. 27, 2025

Oct. 27, 2025

*Subject:* Seeking Your Opinion on RSSAC Liaison Proposal – Context and Next Steps Dear NARALO Colleagues, I’m including you in this discussion as I seek input from the group regarding the possibility of establishing a liaison role between *ALAC/At-Large* and the *Root Server System Advisory Committee (RSSAC)*. To provide better context for understanding this issue, I wanted to share some background information on where things currently stand. As some of you may know, I’ve been exploring the idea of a liaison role for quite some time, driven by the growing need to ensure *end-user representation* in discussions around *root server operations*. Root servers are a critical part of the Internet’s infrastructure, and recent incidents have underscored the importance of having a strong *end-user perspective* in the decision-making processes that affect the Internet’s accessibility and stability. Given that *RSSAC currently does not have formal liaisons* with ICANN structures like ALAC, I’m advocating for establishing this relationship to help bridge the gap between technical discussions and the needs of the broader user community. For moving forward, I’d love to hear your opinions on this idea. What are your thoughts on establishing this liaison role? Do you think it’s something that could benefit the community? Any suggestions for how we might approach this or next steps to take? Looking forward to your feedback! Best regards, Mohibul Mahmud RSSAC Caucus & NARALO Member On Mon, Oct 27, 2025 at 11:55 AM Mohibul Mahmud <mohibul.mahmud(a)gmail.com> wrote: > Subject: Follow-up on RSSAC Liaison Proposal > > Dear Greg, > > Thank you for your thoughtful response and the valuable recommendations. I > wanted to clarify a few points regarding my interest in establishing a > liaison role between ALAC/At-Large and RSSAC. > > As a current member of the RSSAC, my suggestion for a liaison relationship > is not driven by personal interest, but rather by a broader concern for the > end-user group. Root servers are a critical part of the Internet ecosystem, > and recent incidents have highlighted the need for greater awareness and > oversight from the end-user perspective. Ensuring that the activities of > the RSSAC align with the interests and benefits of the end-user group seems > more important than ever. > > The absence of a formal liaison does not diminish the importance of this > relationship. I believe that fostering closer collaboration between > ALAC/At-Large and RSSAC will ensure that the end-user community has an > informed voice in the decision-making process related to root server > operations, which directly impacts the accessibility, security, and > stability of the Internet. > > I understand that this idea is unconventional, but I strongly believe that > creating this liaison role could greatly benefit the broader community. > > Thank you once again for your insights, and I look forward to your > thoughts on this matter. > > Best regards, > Mohibul Mahmud > RSSAC Caucus & NARLO Member > > > > > On Mon, Oct 27, 2025 at 11:24 AM Greg Shatan [NARALO] < > gregshatanalac(a)gmail.com> wrote: > >> All, >> >> I have done some brief research. The RSSAC does not currently have >> liaisons to or from other ICANN structures other than SSAC. I have seen no >> record of past liaisons either on the RSSAC site. Current liaisons are to >> or from other technical bodies or root zone specific bodies. >> >> I don’t know if ALAC ever had a liaison relationship with RSSAC; I assume >> not, but always happy to learn something new. >> >> I recommend the following two steps: >> >> 1. Mohibul you should look into joining the RSSAC Caucus. As you >> probably know, this is an open organization for those with Root Zone >> expertise and interest. This will give you good experience and insight. >> >> 2. ALAC, the At-Large appointments committee and/or Staff could consider >> whether there is ALAC/At-Large interest in a liaison relationship; if so, >> the next step would be contacting the RSSAC Chair to see if there is any >> RSSAC interest in a liaison relationship. >> >> Since there is no such position at the moment, there is no process or >> timeline related to such a position. >> >> Best, >> >> Greg >> *____________________* >> *Greg Shatan* >> *Chair, NARALO* >> gregshatanalac(a)gmail.com >> >> >> On Mon, Oct 27, 2025 at 11:57 Mohibul Mahmud <mohibul.mahmud(a)gmail.com> >> wrote: >> >>> *Subject:* Following Up: Status on At-Large Liaison Interest to RSSAC >>> >>> Dear Heidi, >>> >>> I hope this email finds you well. >>> >>> I’m writing to follow up on my previous message from June 5th regarding >>> my expressed interest in the *At-Large liaison role to the Root Server >>> System Advisory Committee (RSSAC)*. >>> >>> Given the time that has passed, could you please provide a brief status >>> update on this matter? I am eager to understand the process timeline and >>> when we might expect the next steps or information regarding this potential >>> engagement. >>> >>> As always, please don't hesitate to let me know if there’s any further >>> information I can provide on my end to help move this forward. >>> >>> Thank you, and I look forward to hearing from you. >>> >>> Warm regards, >>> >>> Mohibul Mahmud >>> >>> >>> >>> >>> On Thu, Jun 5, 2025 at 1:30 PM Mohibul Mahmud <mohibul.mahmud(a)gmail.com> >>> wrote: >>> >>>> Dear Heidi, >>>> >>>> Thank you for the update—I appreciate your response. Please let me know >>>> if there’s anything I can provide in the meantime. >>>> Looking forward to hearing from you. >>>> >>>> Warm regards, >>>> Mohibul >>>> >>>> >>>> >>>> On Wed, Jun 4, 2025 at 6:57 PM Heidi Ullrich <Heidi.Ullrich(a)icann.org> >>>> wrote: >>>> >>>>> Hi Mohibul, >>>>> >>>>> Thank you for your interest in At-Large and RSSAC. Many apologies for >>>>> the delay in responding. >>>>> >>>>> We are looking into your request. I’ll be in touch shortly. >>>>> >>>>> Kind regards, >>>>> Heidi >>>>> >>>>> On Jun 4, 2025, at 9:39 PM, Mohibul Mahmud <mohibul.mahmud(a)gmail.com> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> Dear Heidi, >>>>> >>>>> >>>>> >>>>> I hope you are doing well. In case you missed my previous email. >>>>> >>>>> >>>>> >>>>> I wanted to kindly follow up on my previous emails regarding my >>>>> interest in aligning my background and experience with RSSAC’s work, >>>>> particularly in DNS operations, root server monitoring, and incident >>>>> response. I am also eager to further explore the possibility of >>>>> contributing through a liaison role from the At-Large community to RSSAC. >>>>> >>>>> >>>>> >>>>> As highlighted earlier, I bring over a decade of experience in DNS and >>>>> infrastructure operations, complemented by my current role as a Cloud >>>>> Engineer at Microsoft. My ICANN engagement through the ICANN82 >>>>> Fellowship, coupled with active participation in NARALO and public policy >>>>> outreach, has further fueled my commitment to contributing meaningfully to >>>>> ICANN’s technical advisory efforts. >>>>> >>>>> >>>>> >>>>> I would greatly appreciate your guidance on how we might move this >>>>> conversation forward and whether there are any additional steps I should >>>>> take to facilitate this process. Your insights would be immensely valuable >>>>> in shaping my potential contribution to RSSAC. >>>>> >>>>> >>>>> >>>>> In case you are unavailable,* I am also including ICANN At-Large >>>>> Staff (staff(a)atlarge.icann.org <staff(a)atlarge.icann.org>) to ensure the >>>>> continuity of this discussion.* >>>>> >>>>> >>>>> >>>>> Please let me know if there’s any further information I can provide. I >>>>> truly appreciate your time and support and look forward to hearing from you >>>>> soon. >>>>> >>>>> >>>>> >>>>> Warm regards, >>>>> >>>>> Mohibul >>>>> >>>>> >>>>> >>>>> CC: Jonathan Zuck, Greg Shatan, Glenn McKnight >>>>> >>>>> On Thu, May 29, 2025 at 8:18 AM Mohibul Mahmud < >>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>> >>>>>> Subject: Follow-Up on RSSAC Liaison Engagement Discussion >>>>>> >>>>>> >>>>>> >>>>>> Dear Heidi, >>>>>> >>>>>> >>>>>> >>>>>> I hope you are doing well. >>>>>> >>>>>> >>>>>> >>>>>> I wanted to kindly follow up on my previous emails regarding my >>>>>> interest in aligning my background and experience with RSSAC’s work, >>>>>> particularly in DNS operations, root server monitoring, and incident >>>>>> response. I am also eager to further explore the possibility of >>>>>> contributing through a liaison role from the At-Large community to RSSAC. >>>>>> >>>>>> >>>>>> >>>>>> As highlighted earlier, I bring over a decade of experience in DNS >>>>>> and infrastructure operations, complemented by my current role as a Cloud >>>>>> Engineer at Microsoft. My ICANN engagement through the ICANN82 Fellowship, >>>>>> coupled with active participation in NARALO and public policy outreach, has >>>>>> further fueled my commitment to contributing meaningfully to ICANN’s >>>>>> technical advisory efforts. >>>>>> >>>>>> >>>>>> >>>>>> I would greatly appreciate your guidance on how we might move this >>>>>> conversation forward and whether there are any additional steps I should >>>>>> take to facilitate this process. Your insights would be immensely valuable >>>>>> in shaping my potential contribution to RSSAC. >>>>>> >>>>>> >>>>>> >>>>>> In case you are unavailable,* I am also including ICANN At-Large >>>>>> Staff (staff(a)atlarge.icann.org <staff(a)atlarge.icann.org>) to ensure the >>>>>> continuity of this discussion.* >>>>>> >>>>>> >>>>>> >>>>>> Please let me know if there’s any further information I can provide. >>>>>> I truly appreciate your time and support and look forward to hearing from >>>>>> you soon. >>>>>> >>>>>> >>>>>> >>>>>> Warm regards, >>>>>> >>>>>> Mohibul >>>>>> >>>>>> >>>>>> >>>>>> CC: Jonathan Zuck, Greg Shatan, Glenn McKnight >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Tue, May 27, 2025 at 3:11 PM Mohibul Mahmud < >>>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>>> >>>>>>> Subject: Follow-Up on RSSAC liaison Engagement Discussion >>>>>>> >>>>>>> >>>>>>> >>>>>>> Dear Heidi, >>>>>>> >>>>>>> >>>>>>> >>>>>>> I hope you are doing well and had a pleasant Memorial Day weekend. >>>>>>> >>>>>>> >>>>>>> >>>>>>> I wanted to kindly follow up on my previous email regarding the >>>>>>> potential alignment of my background and experience with RSSAC’s work, >>>>>>> particularly in DNS operations, root server monitoring, and incident >>>>>>> response. I’m also eager to further explore the possibility of contributing >>>>>>> through a liaison role from the At-Large community to RSSAC. >>>>>>> >>>>>>> >>>>>>> >>>>>>> As shared in my earlier message, I bring over a decade of experience >>>>>>> in DNS and infrastructure operations, complemented by my current role as a >>>>>>> Cloud Engineer at Microsoft. My ICANN engagement through the ICANN82 >>>>>>> Fellowship, coupled with active participation in NARALO and public policy >>>>>>> outreach, has further fueled my commitment to contributing to ICANN’s >>>>>>> technical advisory efforts. >>>>>>> >>>>>>> >>>>>>> >>>>>>> I would greatly appreciate your guidance on how we might move this >>>>>>> conversation forward and whether there are additional steps I should take >>>>>>> to facilitate this process. Your insights would be immensely valuable in >>>>>>> shaping my potential contribution to RSSAC. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Please let me know if there’s any further information I can provide. >>>>>>> I truly appreciate your time and support and look forward to hearing from >>>>>>> you soon. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Warm regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Mohibul >>>>>>> >>>>>>> >>>>>>> CC: Jonathan Zuck, Greg Shatan, Glenn McKnight >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, May 23, 2025 at 5:06 PM Mohibul Mahmud < >>>>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> Just for reference. You could find my profile also on ICANN WiKi >>>>>>>> https://icannwiki.org/Mohibul_Mahmud [icannwiki.org] >>>>>>>> <https://urldefense.com/v3/__https://icannwiki.org/Mohibul_Mahmud__;!!PtGJab…> >>>>>>>> >>>>>>>> I wish you all a nice Weekend. >>>>>>>> >>>>>>>> Best >>>>>>>> Mohibul >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, May 23, 2025 at 1:54 PM Mohibul Mahmud < >>>>>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Dear Jonathan, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Happy Friday! I hope this message finds you well. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> I wanted to kindly follow up on my previous emails regarding my >>>>>>>>> interest in aligning my background with the work of the RSSAC, particularly >>>>>>>>> in DNS operations, root server monitoring, and incident response. I’m >>>>>>>>> especially interested in exploring the potential of contributing through a >>>>>>>>> liaison role from the At-Large community to RSSAC. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> For context—especially for those copied for visibility—I have over >>>>>>>>> a decade of experience in DNS and infrastructure operations, including >>>>>>>>> configuring and maintaining ccTLD root servers in Bangladesh and working as >>>>>>>>> a Network/DNS administrator in the ISP sector. In my current role as a >>>>>>>>> Cloud Engineer at Microsoft, I continue to work on monitoring, >>>>>>>>> observability, and threat mitigation. My ICANN engagement began with >>>>>>>>> ICANN82 as a Fellow, and since then I have actively participated in NARALO >>>>>>>>> discussions and public policy outreach, with a strong desire to contribute >>>>>>>>> to ICANN’s technical advisory efforts. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Given my background and Glenn’s encouragement, I am hoping to gain >>>>>>>>> your perspective on how the liaison role could be structured and how I >>>>>>>>> might best position myself to contribute meaningfully. I am also open to >>>>>>>>> any additional guidance or follow-ups that might be helpful to facilitate >>>>>>>>> the conversation. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thank you again for your time and consideration. I appreciate your >>>>>>>>> support and look forward to your response. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Warm regards, >>>>>>>>> >>>>>>>>> Mohibul >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, May 15, 2025 at 12:44 PM Mohibul Mahmud < >>>>>>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Dear Jonathan, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I hope you are doing well. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I wanted to kindly follow up on my previous email from May 14 >>>>>>>>>> regarding my interest in aligning my background and >>>>>>>>>> >>>>>>>>>> experience with RSSAC’s work, particularly in areas such as DNS >>>>>>>>>> operations, root server monitoring, and incident response. I also wanted to >>>>>>>>>> reiterate my keen interest in understanding how the liaison role from >>>>>>>>>> AT-Large to RSSAC could be structured and how I might effectively >>>>>>>>>> contribute in that capacity. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Your guidance and perspective on how I can best position myself >>>>>>>>>> for further engagement would be immensely valuable. Please let me know if >>>>>>>>>> there is any additional information I can provide to facilitate the >>>>>>>>>> discussion. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thank you once again for your continued support. I look forward >>>>>>>>>> to hearing from you. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Warm regards, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Mohibul >>>>>>>>>> >>>>>>>>>> ICANN 82 Fellow | Cloud Engineer at Microsoft >>>>>>>>>> >>>>>>>>>> On Wed, May 14, 2025 at 9:42 AM Mohibul Mahmud < >>>>>>>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Dear Jonathan, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I hope you’re doing well. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I wanted to kindly follow up on my previous email from May 12 >>>>>>>>>>> regarding the potential alignment of my background and experience with >>>>>>>>>>> RSSAC’s work, particularly in areas such as DNS operations, root server >>>>>>>>>>> monitoring, and incident response. Additionally, I would appreciate any >>>>>>>>>>> insights you might have on how a liaison role from AT-Large to RSSAC could >>>>>>>>>>> be structured and how I might effectively contribute in that capacity. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Your guidance on how to best position myself for further >>>>>>>>>>> engagement would be immensely valuable. Please let me know if there’s any >>>>>>>>>>> further information I can provide to facilitate the discussion. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thank you for your continued support, and I look forward to your >>>>>>>>>>> response. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Warm regards, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Mohibul >>>>>>>>>>> >>>>>>>>>>> ICANN 82 Fellow | Cloud Engineer at Microsoft >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, May 12, 2025 at 2:32 PM Mohibul Mahmud < >>>>>>>>>>> mohibul.mahmud(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Glenn and Jonathan, >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thank you, Glenn, for bringing this to Jonathan’s attention. I >>>>>>>>>>>> truly appreciate your continued support and guidance. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Jonathan, as Glenn mentioned, I am keen on exploring the >>>>>>>>>>>> possibility of aligning my background and experience with the work of >>>>>>>>>>>> RSSAC, especially in areas such as DNS operations, root server monitoring, >>>>>>>>>>>> and incident response. Additionally, I’d like to understand how a liaison >>>>>>>>>>>> role from AT-Large to RSSAC could be structured and how I might contribute >>>>>>>>>>>> effectively in that capacity. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Your insights on how I can best position myself for further >>>>>>>>>>>> engagement would be incredibly valuable. I’m eager to hear your perspective >>>>>>>>>>>> and recommendations. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thank you both for your continued support. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Warm regards, >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Mohibul >>>>>>>>>>>> >>>>>>>>>>>> ICANN 82 Fellow | Cloud Engineer at Microsoft >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, May 12, 2025 at 1:39 PM Glenn McKnight < >>>>>>>>>>>> mcknight.glenn(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Hi Jonathan >>>>>>>>>>>>> I reviewed the list of ALAC Liaisons for the rep for RSSAC >>>>>>>>>>>>> but it appears that it is not included in this page >>>>>>>>>>>>> https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708472/AL… >>>>>>>>>>>>> [icann-community.atlassian.net] >>>>>>>>>>>>> <https://urldefense.com/v3/__https://icann-community.atlassian.net/wiki/spac…> >>>>>>>>>>>>> >>>>>>>>>>>>> Mohbiul is interested in RSSAC and the possibility of being a >>>>>>>>>>>>> liaison from AT-Large >>>>>>>>>>>>> >>>>>>>>>>>>> Note from Mohibul >>>>>>>>>>>>> >>>>>>>>>>>>> *I was referred to you by Glenn McKnight, who mentioned that >>>>>>>>>>>>> you could provide valuable insights on the relationship between RALO and >>>>>>>>>>>>> RSSAC. As someone with extensive experience in Internet infrastructure, DNS >>>>>>>>>>>>> administration, and cybersecurity, I am eager to contribute meaningfully to >>>>>>>>>>>>> RSSAC and deepen my engagement with ICANN's technical advisory bodies.* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Throughout my career, I’ve had the opportunity to work >>>>>>>>>>>>> extensively with DNS systems, having completed my ccTLD name server >>>>>>>>>>>>> training with Bill Manning and actively participated in configuring and >>>>>>>>>>>>> maintaining root server instances in Bangladesh. My technical journey also >>>>>>>>>>>>> includes working as a Network and DNS administrator for over a decade in >>>>>>>>>>>>> the ISP sector and my current role as a Cloud Engineer at Microsoft, >>>>>>>>>>>>> focusing on monitoring, observability, and security practices.* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *I believe my background aligns well with RSSAC’s mission, >>>>>>>>>>>>> particularly in areas such as DNS operations, root server monitoring, and >>>>>>>>>>>>> incident response. Additionally, I am enthusiastic about contributing to >>>>>>>>>>>>> ongoing projects that address DNS abuse, resolver behavior, and threat >>>>>>>>>>>>> mitigation.* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Could you kindly share your perspective on how I could best >>>>>>>>>>>>> position myself for active participation in RSSAC? Any guidance on aligning >>>>>>>>>>>>> my technical background with the current focus areas or projects within >>>>>>>>>>>>> RSSAC would be incredibly helpful.* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Thank you very much for your time, and I look forward to the >>>>>>>>>>>>> possibility of connecting with you.* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Warm regards,* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Mohibul* >>>>>>>>>>>>> >>>>>>>>>>>>> ICANN 82 Fellow | Cloud Engineer at Microsoft >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Glenn McKnight, MA >>>>>>>>>>>>> Virtual School of Internet Governance >>>>>>>>>>>>> Chief Information Officer >>>>>>>>>>>>> www.virtualsig.org [virtualsig.org] >>>>>>>>>>>>> <https://urldefense.com/v3/__http://www.virtualsig.org__;!!PtGJab4!_JaYuEDx4…> >>>>>>>>>>>>> >>>>>>>>>>>>> *YOUR SOURCE FOR INTERNET GOVERNANCE EDUCATION * >>>>>>>>>>>>> *Mobile 437-237-4655* >>>>>>>>>>>>> >>>>>>>>>>>>>

2 2

Alfredo Calderón Honored with Dr. Tarek Kamel Award for Capacity Building
by Glenn McKnight Oct. 27, 2025

Oct. 27, 2025

Alfredo Calderón Honored with Dr. Tarek Kamel Award for Capacity Building 27 October 2025 ------------------------------ Today, the Internet Corporation for Assigned Names and Numbers (ICANN) Board announced that Alfredo Calderón is the recipient of the 2025 Dr. Tarek Kamel Award for Capacity Building. Tripti Sinha, ICANN Board Chair, announced the Board's selection during the welcome ceremony of ICANN84 Annual General Meeting in Dublin, Ireland. The ICANN Board recognizes Calderón's significant efforts in capacity building on a local, regional, and global scale. Particularly notable is Calderón's leadership in founding and running the North American School of Internet Governance (NASIG) and the Virtual School on Internet Governance, which earned the ICANN Board's deep appreciation. Calderón participated in the award ceremony and thanked the ICANN Board for its recognition. A video of the award ceremony will be published later. Alfredo Calderón is an instructional designer for online courses and consultant for implementing distance learning programs. He is also a chemist, with over 20 years of experience as an academic professor. Calderón has served as a Board member of the Internet Society Puerto Rico Chapter since 2014. As a co-founder of NASIG, Calderón serves as NASIG academic program director. He has been involved as an active member of various working groups and committees in the At-Large and broader ICANN community including the ICANN Fellowship Selection and Mentoring Committees and Nominating Committee. The Dr. Tarek Kamel Award for Capacity Building <https://www.icann.org/en/community/community-recognition-programs/dr-tarek-…> was established in honor of the late Dr. Tarek Kamel, an Internet pioneer known for his contributions to global Internet governance. The award recognizes members of the ICANN community who have made significant contributions to national, regional, or global capacity-development programs related to ICANN's mission. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a nonprofit public benefit corporation with a community of participants from all over the world. Glenn McKnight, MA Virtual School of Internet Governance Chief Information Officer www.virtualsig.org *YOUR SOURCE FOR INTERNET GOVERNANCE EDUCATION * *Mobile 437-237-4655*

9 8

Attention- CALL FOR PROPOSALS UA DAY 2026- Deadline 24 November
by Silvia Vivanco Oct. 27, 2025

Oct. 27, 2025

Dear NARALO members, ICANN and the community are organizing the fourth global Universal Acceptance (UA) Day between 25 March through 30 May 2026. Building on its partnership with ICANN to advance Internet inclusivity, multilingualism, and equitable access online, UNESCO is supporting this fourth annual series of events that focus on the adoption of Universal Acceptance (UA). The deadline to submit<https://www.icann.org/ua-day-call-for-proposals-2026-en> a proposal is 24 November 2025. More information at : https://www.icann.org/ua-day-call-for-proposals-2026-en A wiki page has been created to post your proposals: https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/549257269/A… Thank you very much! Silvia Silvia Vivanco Senior Manager, At-Large Regional Affairs Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_3739878956]

1 0

Announcement of ALAC Appointed-NextGen Mentor ICANN85-87
by Heidi Ullrich Oct. 24, 2025

Oct. 24, 2025

Dear All, On behalf of Jonathan Zuck, Chair of the ALAC, this is to announce that Alfredo Calderon has been selected to be the ALAC Appointed-NextGen Mentor between ICANN85-87. The selection process consisted of the members of the ALAC Appointee Selection Committee (AASC) reviewing and ranking 14 candidate Expression of Interest (EOI) documents for the position of NextGen Mentor. The AASC sent the name of their selected candidate to the ALAC on 16 October 2025. The ALAC held a Consensus call ending on Monday, 20 October 2025. Please note that until such time as an ALAC Appointee Metrics framework is adopted by the ALAC, the ALAC Appointed-NextGen Mentor will be requested by the ALAC Leadership to participate in selected ALAC/At-Large activities. He/She may also be requested to provide periodic reports on his/her mentorship work. Such reports may be verbal or in written form, and notice will be given to the ALAC Appointee on the timing of such reports. Congratulations to Alfredo. Many thanks to all the candidates that applied for the position of ALAC Appointed-NextGen Mentor. Kind regards, At-Large Staff At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/>

1 0

Call for Expressions of Interest – ICANN Board Seat 15 (2025–2026 Cycle)
by Heidi Ullrich Oct. 17, 2025

Oct. 17, 2025

** La version francaise est en dessous de la version anglaise. ** ** La versión en español está debajo de la versión en francés.** ** Dear At-Large Community Members, On behalf of the Board Candidate Evaluation Committee (BCEC), we invite Expressions of Interest (EOI) from individuals who would like to serve as the ICANN Board Director nominated by the At-Large Community (Seat 15). The successful candidate will begin a three-year term at the close of ICANN87 (2026 Annual General Meeting). Why does this matter? Seat 15 is the only ICANN Board seat chosen directly by the At-Large Community. It has been held since ICANN60 (2017 AGM) by León Sánchez, whose third and final term ends at ICANN87. This is a rare opportunity for an At-Large leader to bring their knowledge and experience to ICANN’s highest level of governance. About the selection process: The BCEC defines candidate requirements, issues the call for applications, and evaluates submissions. The Board Member Selection Process Committee (BMSPC) oversees the timeline and election. Both groups have regionally balanced membership and operate under a strict code of conduct and confidentiality. Regional At-Large Organizations (RALOs) may petition to add candidates to the slate. Unsuccessful applicants may have opted for their candidacy to be considered by the RALOs after the BCEC slate is published. The full process is expected to conclude no later than 22 April 2026, when the selected candidate to be nominated as an ICANN Board Member will be announced. For full information, visit the At-Large Board Member Selection Home – 2025-2026<https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/394657793>. How to apply: 1. Review the requirements – At-Large Board Member Candidate Requirements 2025-2026<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/483065909> – Candidate Reference Links & Resources<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/517800468> Please pay special attention to the “Additional Bylaws Qualifications” section to confirm your eligibility. 2. Email the BCEC Staff – Send a brief note indicating your interest to bcec-staff(a)icann.org<mailto:bcec-staff@icann.org>. – Staff will provide you access to the online EoI Form. 3. Complete the EOI Form – Submit by 23:59 UTC on Friday, 21 November 2025. – List three to four referees who are willing to provide a written reference at short notice. Questions? Please email bcec-staff(a)icann.org<mailto:bcec-staff@icann.org> for clarification. This is your opportunity to contribute your experience, vision, and commitment at ICANN’s highest level of decision-making. We encourage all qualified individuals to step forward. ICANN Policy Staff supporting the At-Large Community ** Sujet : Appel à manifestations d’intérêt pour le siège 15 du Conseil d’administration de l’ICANN (cycle 2025-2026) Chers membres de la communauté At-Large, Au nom du Comité d’évaluation des candidats au Conseil d’administration (BCEC), nous avons le plaisir de lancer un appel à manifestation d’intérêt pour le poste d’administrateur nominé par la communauté At-Large au Conseil d’administration de l’ICANN (siège 15). La personne retenue entamera un mandat de trois ans à l’issue de l’ICANN87 (Réunion générale annuelle de 2026). Pourquoi cela est-il important ? Le siège 15 est le seul siège du Conseil d’administration de l’ICANN qui soit directement pourvu par la communauté At-Large. Occupé depuis l’ICANN60 (Réunion générale annuelle 2017) par León Sánchez, dont le troisième et dernier mandat s’achèvera à l’ICANN87, ce poste représente une occasion unique pour un leader de la communauté At-Large d’apporter ses connaissances et son expérience au plus haut niveau de la gouvernance de l’ICANN. Le processus de sélection : Le BCEC est chargé de définir les critères de candidature, de publier l’appel à candidatures et d’évaluer les dossiers. De son côté, le Comité chargé du processus de sélection d’un membre du Conseil d’administration (BMSPC) supervise le calendrier et le déroulement de l’élection. Les deux groupes, équilibrés sur le plan régional au niveau de leur composition, s’acquittent de leurs tâches suivant un code de conduite et des règles de confidentialité des plus stricts. Les organisations régionales At-Large (RALO) peuvent proposer l’ajout de noms à la liste des candidats. Les candidats non retenus peuvent avoir choisi que leur candidature soit examinée par les RALO après la publication de la liste du BCEC. L’ensemble du processus devrait s’achever au plus tard le 22 avril 2026, date à laquelle sera annoncé le nom du nouvel administrateur. Pour en savoir plus, rendez-vous sur l’espace dédié à la sélection d’un membre du Conseil d’administration en représentation d’At-Large – 2025-2026<https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/394657793>. Comment déposer sa candidature ? 1. Vérifier les critères — Exigences pour les candidats au poste de membre du Conseil d’administration en représentation d’At-Large 2025-2026<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/483065909>. — Liens et ressources de référence à l’usage du candidat<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/517800468> (à actualiser) Veuillez porter une attention particulière à la section « Compétences supplémentaires au titre des statuts constitutif ». Elle vous aidera à confirmer votre éligibilité. 1. Échanger avec le BCEC par courrier électronique — Envoyez une courte note à bcec-staff(a)icann.org<mailto:bcec-staff@icann.org> pour faire part de votre intérêt. — L’équipe vous donnera alors accès au formulaire de manifestation d’intérêt (EoI). 1. Soumettre le formulaire EoI — Veuillez remplir le formulaire et le soumettre avant le vendredi 21 novembre 2025 à 23 h 59 UTC. — Indiquez-y trois à quatre personnes de référence qui seraient disposées à fournir une lettre de recommandation dans de brefs délais. Des questions ? N’hésitez pas à écrire à bcec-staff(a)icann.org. C’est pour vous l’occasion de contribuer, par votre expérience, votre vision et votre engagement, à la plus haute instance décisionnelle de l’ICANN. Toutes les personnes qualifiées sont vivement encouragées à se porter candidates. Cordialement, L’équipe de l’ICANN chargée du soutien aux politiques pour la communauté At-Large ** Asunto: Convocatoria a presentar manifestaciones de interés – Puesto 15 de la Junta Directiva de la ICANN (ciclo 2025–2026) Estimado miembro de la comunidad At-Large, En nombre del Comité para la Evaluación de Candidatos a la Junta Directiva (BCEC), invitamos a presentar manifestaciones de interés (EoI) a las personas que deseen desempeñar las funciones de Miembro de la Junta Directiva de la ICANN seleccionado por la comunidad At-Large (Puesto 15). El candidato nominado comenzará un mandato de tres años al finalizar la reunión ICANN87 (Reunión General Anual 2026). ¿Por qué es importante? El puesto 15 es el único de la Junta Directiva de la ICANN elegido directamente por la comunidad At-Large. Lo ocupa desde la reunión ICANN60 (AGM de 2017) León Sánchez, cuyo tercer y último mandato finaliza en ICANN87. Se trata de una oportunidad excepcional para que un líder de At-Large aporte sus conocimientos y experiencia al más alto nivel de gobernanza de la ICANN. Acerca del proceso de selección: El BCEC define los requisitos de los candidatos, publica la convocatoria a presentar solicitudes y evalúa las presentaciones. El Comité para el Proceso de Selección de Miembros de la Junta Directiva (BMSPC) supervisa el calendario y la elección. Ambos grupos tienen una composición regional equilibrada y funcionan conforme a un estricto código de conducta y confidencialidad. Las Organizaciones Regionales At-Large (RALO) pueden solicitar que se agreguen candidatos a la lista. Los candidatos no seleccionados pueden haber optado por que su candidatura sea considerada por los RALO después de que se publique la lista del BCEC. Se prevé que el proceso completo concluya a más tardar el 22 de abril de 2026, fecha en la que se anunciará el Miembro de la Junta Directiva nominado. Para obtener toda la información, los invitamos a consultar el espacio de trabajo para la selección del miembro de la Junta Directiva por parte de la comunidad At-Large (2025-2026)<https://icann-community.atlassian.net/wiki/spaces/ABMS/pages/394657793>. Cómo presentar una solicitud: 1. Consulte los requisitos – Requisitos para Postulantes al Puesto de la Junta Directiva en Representación de At-Large 2025-2026<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/483065909> – Enlaces y recursos de referencia para postulantes<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/517800468> (a actualizar) Preste especial atención a la sección "Cualificaciones Adicionales conforme a los Estatutos" para confirmar su elegibilidad. 1. Envíe un correo electrónico al personal del BCEC – Envíe una breve nota manifestando su interés a bcec-staff(a)icann.org<mailto:bcec-staff@icann.org>. – El personal le proporcionará acceso al formulario de EoI en línea. 1. Complete el formulario de EoI – Preséntelo antes de las 23:59 UTC del viernes 21 de noviembre de 2025. – Indique tres o cuatro personas de referencia que estén dispuestas a facilitar una referencia por escrito en un plazo breve. ¿Preguntas? Envíe un correo electrónico a bcec-staff(a)icann.org<mailto:bcec-staff@icann.org> si tiene alguna duda o consulta. Esta es su oportunidad de aportar su experiencia, visión y compromiso al más alto nivel de toma de decisiones de la ICANN. Alentamos a todas las personas cualificadas a que den un paso al frente. Saludos cordiales, Personal de políticas de la ICANN en apoyo de la comunidad At-Large At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/>

1 0

Fwd: [ICANN Community Leaders] DNS Abuse ICANN84 Session
by Greg Shatan [NARALO] Oct. 17, 2025

Oct. 17, 2025

All, I am looking for expressions of interest for a seat at the "U-Table" for this meeting at ICANN84. Anyone can attend the session, but each group (including NARALO) has been asked to designate two people to sit at the table and be prepared to actively participate. Please respond to this email if you are interested. Thanks! Greg ---------- Forwarded message --------- From: Devan Reed via SO-AC-SG-CLeaders <so-ac-sg-cleaders(a)icann.org> Date: Tue, Oct 14, 2025 at 11:20 AM Subject: [ICANN Community Leaders] DNS Abuse ICANN84 Session To: so-ac-sg-cleaders(a)icann.org <so-ac-sg-cleaders(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Dear SO/AC/SG/C Chairs, We look forward to your participation in the upcoming ICANN84 session on DNS Abuse taking place on *26 October at 10:30 IST <https://icann84.sched.com/event/29QJN/gnso-dns-abuse-work-session>.* Please find the agenda attached. The discussion will focus on the PDP structure and the two priority issues identified in the Preliminary Issue Report: (1) Unrestricted API access for high-volume registrations and (2) Associated-Domain Checks. The guidance questions in the agenda are drawn from the current draft charter attached to the Preliminary Issue Report. While the session is open to all attendees, in order to better ensure an effective exchange, we kindly invite each group to identify two designated participants to sit at the U-table and actively contribute to the discussion. Having at least two representatives per group at the table will help us work through the topics efficiently and ensure that all perspectives are heard. However, as the session is open to all attendees, we welcome and encourage broad community engagement. In preparation for the session, we encourage U-table participants in particular to: - Review the Preliminary Issue Report and - Review the attached agenda and the questions derived from the draft charter. For planning purposes, we would very much appreciate you sending the names of your two U-table participants at your earliest convenience. We look forward to a productive session. Kind regards, *Feodora Hamza* Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) * Mobile:* +32 496 30 24 15 *Email:* feodora.hamza(a)icann.org *Website:* www.icann.org _______________________________________________ SO-AC-SG-CLeaders mailing list -- so-ac-sg-cleaders(a)icann.org To unsubscribe send an email to so-ac-sg-cleaders-leave(a)icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- *____________________* *Greg Shatan* *Chair, NARALO* gregshatanalac(a)gmail.com

1 0

FOR COMMENT: Third draft ALAC Appointee Metrics document
by Heidi Ullrich Oct. 16, 2025

Oct. 16, 2025

Dear All, On behalf of the ALAC Leadership Team, please find for your input the third draft ALAC Appointee Metrics document (see:https://docs.google.com/document/d/1tL0yOViFberRJLmoFzsiq8VqUkk8x5oQdgp…) which was reported on during the ALAC Monthly Call of September 2025. Having previously received comments from a select group of current and immediate past ALAC Appointees, followed by a round of rationalization by ALAC members, comments are now invited from the At-Large Community members. Please add your input by way of the comment function, by 15 November 2025 at 23:59 UTC. This draft should be considered part of a larger continuous improvement effort for the ALAC, consistent with the ALAC Continuous Improvement Program (CIP) initiative. It seeks to establish both an ALAC Appointee's and the At-Large Community's understanding of the roles and responsibilities of each ALAC Appointee (which includes the ALAC Liaisons and Representatives) and the standards expected of them. In the same manner, it is also meant to serve as guidance for any At-Large Community member who wishes to be considered for any of the roles included in the document, as and when a vacancy is to be filled by the ALAC. A final version of this document is anticipated to be proposed to the ALAC, after community comments, revision (if necessary) and settlement, for adoption as an adjunct document to the ALAC Rules of Procedures (i.e., ALAC Rules of Procedure Adjunct Document – Metrics and Remedial Actions for Appointees). Kind regards, Heidi Heidi Ullrich, PhD VP, Policy Development & At-Large Relations Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 437 3956 Fax: +1 310 823 8649 Website: atlarge.icann.org<https://atlarge.icann.org/>

1 0

Final treatment
by Glenn McKnight Oct. 8, 2025

Oct. 8, 2025

Hi folks I had my last treatment today. It's been two years of immunotherapy. Thanks to all for the support G Glenn McKnight, MA Virtual School of Internet Governance Chief Information Officer www.virtualsig.org *YOUR SOURCE FOR INTERNET GOVERNANCE EDUCATION * *Mobile 437-237-4655*

9 8

CALL FOR EOIs - ALAC Selection of 2026 NextGen Mentor for ICANN85-87
by Heidi Ullrich Oct. 6, 2025

Oct. 6, 2025

Dear All, On behalf of Jonathan Zuck, ALAC Chair, this is a call for Expressions of Interest (EOIs) for persons to apply for the position of NextGen Mentor. The NextGen@ICANN Program seeks nominations to fill three (3) slots for the 2026 Mentor Program. These appointments will serve for the ICANN85-87 meetings. Please note that the ALAC will be able to fill one slot. . NextGen@ICANN Program Mentoring The NextGen@ICANN Program Mentoring process helps participants to prepare for the NextGen@ICANN experience and strengthens the relationship between NextGen and the ICANN community. ICANN provides travel funding (including hotel accommodation and a stipend) for up to three SO/AC-appointed mentors to attend an ICANN Public Meeting<https://meetings.icann.org/en/> as a NextGen@ICANN Program mentor. Mentors support up to four NextGen@ICANN participants per meeting. Mentors will assist newcomers to become actively involved in the ICANN community and its policy development processes, working groups, and regional work. Mentors are expected to devote considerable time to pre-meeting preparation with their mentees, to offer advice and networking support and regular check-ins on-site, and to complete evaluations following the meeting. Based on previous estimates, mentors spend about 40 hours during the six-week period in advance of the meeting and about 10 hours on-site at the ICANN meeting. For more information about the role of a mentor, see ICANN NextGen Program Mentoring Guidelines<https://www.icann.org/en/system/files/files/nextgen-mentoring-guidelines-13…>. Interested At-Large Members are requested to send their Expression of Interest (EOI) to At-Large Staff no later than Tuesday, 7 October 2025 by 23:59 UTC. The ALAC Appointee Selection Subcommittee (AASC) will review the EOIs and notify the ALAC of their selections. ALAC Nominations must be submitted to the NextGen Support Staff no later than Thursday, 7 November 2025. Kind regards, At-Large staff Heidi Ullrich, PhD VP, Policy Development & At-Large Relations Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 437 3956 Fax: +1 310 823 8649 Website: atlarge.icann.org<https://atlarge.icann.org/>

5 5

Re: NA-Discuss Digest, Vol 228, Issue 4
by Denise de alcantara-hochbaum Oct. 4, 2025

Oct. 4, 2025

Hello Joly and ICANN Staff and Leaders, First of all, I want to congratulate Joly for this excellent edition produced from the NEXTGEN material recorded at ICANN83 in Seattle. This work showcases clear audio, captions, slides, and speaker videos — a truly comprehensive and professional package. I recognize that this material was created through Joly’s personal effort and initiative, and it stands as a strong example of what can become a continued practice for all upcoming NEXTGEN presentations. I would therefore suggest that ICANN consider adopting this model going forward, so the community can benefit from high-quality access to presentations. This would also create valuable opportunities for engagement, including connecting with students who may become future partners. Many thanks again to Joly for your dedication and initiative! *Denise Avivit de Alcantara Hochbaum*, PhD, AIA International Member *Mobile: +1 (917) 757-2513 * *910 M Street NW Apt 501 Washington DC* *Design Factor Solutions, President* On Fri, Oct 3, 2025 at 8:00 PM <na-discuss-request(a)icann.org> wrote: > Send NA-Discuss mailing list submissions to > na-discuss(a)icann.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > na-discuss-request(a)icann.org > > You can reach the person managing the list at > na-discuss-owner(a)icann.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NA-Discuss digest..."Today's Topics: > > 1. Re: CALL FOR EOIs - ALAC Selection of 2026 NextGen Mentor for > ICANN85-87 > (Joly MacFie) > > > > ---------- Forwarded message ---------- > From: Joly MacFie <joly(a)punkcast.com> > To: Evan Leibovitch <evanleibovitch(a)gmail.com> > Cc: Heidi Ullrich <Heidi.Ullrich(a)icann.org>, ICANN At-Large Staff via > NA-Discuss <na-discuss(a)icann.org>, Jonathan Zuck < > JZuck(a)innovatorsnetwork.org> > Bcc: > Date: Fri, 3 Oct 2025 16:35:21 -0400 > Subject: [NA-Discuss] Re: CALL FOR EOIs - ALAC Selection of 2026 NextGen > Mentor for ICANN85-87 > > I took some effort to archive the the ICANN82 NextGen presentations, which > were of a high quality > https://isoc.live/19018/ > > I recorded the ICANN83 session, but never got around to processing. I have > put it back on the pile! > > -- > -------------------------------------- > Joly MacFie +12185659365 > -------------------------------------- > - > _______________________________________________ > NA-Discuss mailing list -- na-discuss(a)icann.org > To unsubscribe send an email to na-discuss-leave(a)icann.org > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

2 1