July 2019 - CPWG - lists.icann.org

Re: [CPWG] [registration-issues-wg] NARALO Insight: DNS Over HTTPS
by Eduardo Diaz Sept. 24, 2019

Sept. 24, 2019

My recommendation to the CPWG is to take this and create an advice to the Board by presenting our opinions about this technology, indicate how the end-user is affected, possible way of implementing this technology from the ICANN perspective and point out posible ICANN policies or ICANN structural changes needed to cope with its implementation. The topic is very hot and we should take the opportunity to steer this discussion within ICANN since for I have seen it can split the DNS system in many ways and capture the end-user at the application level . -ed On Wed, Jun 19, 2019 at 4:18 AM Hadia Abdelsalam Mokhtar EL miniawi < Hadia(a)tra.gov.eg> wrote: > Hi All, > > > > Going through the paper published by CENTR, depending on the means of > implementation of DoH it could directly affect end users by limiting > consumers choice and competition. Currently the users, if they wish could > change the resolvers they are using. Again depending on the means of > implementation, the browser companies, which are mainly 2-4 companies could > have control over the traffic of the users and choose which resolvers they > use. The paper raises many different questions and issues, like the > possible impact on the multistakeholder model. In my opinion it is worth > reading. > > > > Kind regards > > Hadia > > > > *From:* CPWG [mailto:cpwg-bounces@icann.org] *On Behalf Of *Hadia El > Miniawi via CPWG > *Sent:* Tuesday, June 18, 2019 2:59 PM > *To:* Eduardo Diaz; Humberto Carrasco > *Cc:* CPWG > *Subject:* Re: [CPWG] [registration-issues-wg] NARALO Insight: DNS Over > HTTPS > > > > Thank you Eduardo and Glenn. > > > > CENTR published yesterday a paper on DoH, the link is herewith > > > > CENTR Issue Paper on DNS over HTTPs > <https://centr.org/library/library/policy-document/centr-issue-paper-on-dns-…> > > > > > CENTR Issue Paper on DNS over HTTPs > > CENTR is the association of European coutry code top-level domain name > registries. CENTR’s main purpose is to pr... > > > > > > Kind regards > > Hadia > > > > On Monday, June 17, 2019, 3:37:05 PM GMT+2, Humberto Carrasco < > hcarrascob(a)gmail.com> wrote: > > > > > > Thanks a lot Eduardo!!! > > Enviado desde mi iPhone > > > El 14-06-2019, a la(s) 13:25, Eduardo Diaz <eduardodiazrivera(a)gmail.com> > escribió: > > All: > > > > Our region believes that this will become a hot topic within ICANN in the > near future. > > > > We invited Dan York from ISOC to explain this technology in layman's terms > and to answer the following questions: [1] Will this affect the end-user? > [2] Will this impact ICANN's remit?. Link to the video: > https://youtu.be/c5CXaphNxU0 (Note: there is an approximate 1 minute gap > around 9 minutes into the video. The rest of the video is OK after that). > > > > NARALO Insights are a dedicated video series on Internet Governance > concerns with a special onus on relevant and topical discussion at ICANN. > Our goal is to have community experts exchange ideas and regional > perspectives on current hot topics to augment policy discussions within > ALAC. > > > > -ed > > > > > > -- > > *NOTICE:* This email may contain information which is confidential and/or > subject to legal privilege, and is intended for the use of the named > addressee only. If you are not the intended recipient, you must not use, > disclose or copy any part of this email. If you have received this email by > mistake, please notify the sender and delete this message immediately. > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > 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. > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > 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. > > _______________________________________________ > registration-issues-wg mailing list > registration-issues-wg(a)atlarge-lists.icann.org > https://mm.icann.org/mailman/listinfo/registration-issues-wg > > _______________________________________________ > 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. > -- *NOTICE:* This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately.

18 44

Subsequent Procedures Update: Applicant Support Program, snapshot as at 26 Jul 2019
by Justine Chew Aug. 5, 2019

Aug. 5, 2019

Dear all, Reference is made to an earlier email with subject "Draft Issues List for Subsequent Procedures". I have attempted to generate a *snapshot of where the Subsequent Procedures PDP WG is at in its deliberations on the Applicant Support Program as at 26 Jul 2019 <https://community.icann.org/download/attachments/111390697/01.%20SubPro%20A…>*, post its last WG call on 25 Jul 15:00 UTC. Please note that that this snapshot is not intended to reflect a complete picture as deliberations on the same topic will continue on the next SubPro PDP WG Call of 29 Jul 20:00 UTC. At-Large members on the SubPro PDP WG are encouraged to attend the SubPro PDP WG call of 29 Jul 20:00 UTC, to help support the ALAC/At-Large inputs on the Applicant Support Program and/or help flesh out more concrete recommendations for the Program, seeing that this is one of the topics for which At-Large has helped to drive in respect of the new gTLD application round of 2012 and has continued to provide substantial input. After the said SubPro PDP WG call, I will attempt to present an updated snapshot at the next CPWG call. Thank you, Justine Chew ----- ---------- Forwarded message --------- From: Jeff Neuman <jeff.neuman(a)comlaude.com> Date: Thu, 25 Jul 2019 at 05:10 Subject: [Gnso-newgtld-wg] Reminder: Applicant Support discussion on July 25th WG Call To: Julie Hedlund <julie.hedlund(a)icann.org>, gnso-newgtld-wg(a)icann.org < gnso-newgtld-wg(a)icann.org> All, I just wanted to draw everyone’s attention to the fact that we will likely be starting our next discussion on Applicant Support on the July 25th Working Group call at 15:00 UTC. The reason we are specifically calling this out is because this has been one of the topics that has generated the most amount of interest from the community and the most amount of dissatisfaction from the community on how it was handled in the 2012 round. Although we have a few recommendations from the initial report and some back up for those, we really want to encourage discussion on developing more specific recommendations. Yes, we all know that there is wide dissatisfaction on the way it was handled before, but without concrete recommendations from the community, we will not be able to do better this next time around. Thanks! Reminder: Materials for tomorrow’s call can be found at: https://docs.google.com/document/d/11mtncTwPLPx6vpbunACToRZy1vWyls-MxVAb3wq…. Applicant Support starts at page 17. *Jeffrey J. Neuman* Senior Vice President *Com Laude | Valideus *1751 Pinnacle Drive , Suite 600 Mclean , VA 22102 UNITED STATES T: +1.703.635.7514 M: +1.202.549.5079 CONFIRMATION OF ORDERS: Please note that we always confirm receipt of orders. To assist us in identifying orders, please use the word ORDER in the subject line of your email. If you have sent us an order and have not received confirmation on the same working day (PST) it is possible that your order has not been received or has been trapped by our spam filter. In this case, please contact your client manager or admin(a)comlaude.com for confirmation that the order has been received and is being processed. Thank you. *From:* Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org> *On Behalf Of *Julie Hedlund *Sent:* Tuesday, July 23, 2019 2:13 PM *To:* gnso-newgtld-wg(a)icann.org *Subject:* [Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Thursday, 25 July 2019 at 15:00 UTC Dear WG members, Please find below the proposed agenda for the upcoming call on *Thursday, 25 July 2019 at 15:00 UTC for 90 minutes:* Draft Agenda: 1. Welcome and Updates to Statements of Interest 2. Review of summary document: (continued) – See: https://docs.google.com/document/d/11mtncTwPLPx6vpbunACToRZy1vWyls-MxVAb3wq… 1. Application Submission Period, page 14 2. Applicant Support, page 17 3. Terms and Conditions, page 24 (time permitting) 3. AOB Note, in relation to agenda item 2, WG leadership and staff have tried to prepare summary documents for each topic that seeks to help you review some of the background material, consider a high-level summary of what we believe the WG is seeking to accomplish for the topic, a high-level summary of public comment received, and finally, a catch all at the end of each section (e.g., follow-up, parking lot, next steps). A PDF snapshot also is attached for reference. If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org. Best, Julie Julie Hedlund, Policy Director ------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see www.comlaude.com <https://comlaude.com> _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg _______________________________________________ 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.

5 11

Call for Comments: Evolving ICANN’s Multistakeholder Model
by ICANN At-Large Staff Aug. 4, 2019

Aug. 4, 2019

Dear All, Please note the first draft ALAC statement on Evolving ICANN’s Multistakeholder Model<https://community.icann.org/x/NIWGBg> is ready for your review. Please take a moment to review this draft and if you have input, please submit it in the comment-only Google Doc<https://docs.google.com/document/d/13nLdYeIB2wbTERgBdiE55z0RnM69F-nSXbrF4Rw…> or wiki workspace<https://community.icann.org/x/NIWGBg> using the comment function by Wednesday, 29 May 2019 at 23:59 UTC. Pertinent resources that provide background to this statement, can be found in its wiki workspace here: https://community.icann.org/x/NIWGBg. You will need to log in to the wiki to use the comment function. If you don’t have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 4

REMINDER / First ZOOM meeting with RTT / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 31 July 2019 at 21:00 UTC
by ICANN At-Large Staff July 31, 2019

July 31, 2019

Real Time Transcribing (RTT) will be provided on this call in ENGLISH. If you do not have the bandwidth to join the call, the live transcribing streaming is available via this link: https://www.streamtext.net/player?event=ICANN [streamtext.net]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 31 July 2019 at 21:00 UTC for 90 mins. For other times: https://tinyurl.com/y3usxsfh The agenda and call details can be found at: https://community.icann.org/x/a7KjBg Zoom Room: https://icann.zoom.us/j/531558192 /<https://icann.zoom.us/j/531558192%20/> Meeting ID: 531-558-192 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

First ZOOM meeting with RTT / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 31 July 2019 at 21:00 UTC
by ICANN At-Large Staff July 31, 2019

July 31, 2019

Real Time Transcribing (RTT) will be provided on this call in ENGLISH. If you do not have the bandwidth to join the call, the live transcribing streaming is available via this link: https://www.streamtext.net/player?event=ICANN [streamtext.net]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 31 July 2019 at 21:00 UTC for 90 mins. For other times: https://tinyurl.com/y3usxsfh The agenda and call details can be found at: https://community.icann.org/x/a7KjBg Zoom Room: https://icann.zoom.us/j/531558192 /<https://icann.zoom.us/j/531558192%20/> Meeting ID: 531-558-192 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

REMINDER / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 31 July 2019 at 21:00 UTC
by ICANN At-Large Staff July 31, 2019

July 31, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 31 July 2019 at 21:00 UTC for 90 mins. For other times: https://tinyurl.com/y3usxsfh The agenda and call details can be found at: https://community.icann.org/x/a7KjBg Zoom Room: https://icann.zoom.us/j/531558192 /<https://icann.zoom.us/j/531558192%20/> Meeting ID: 531-558-192 ADIGO Conference Bridge: EN: 1638 ES: 1738 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Draft Issues List for Subsequent Procedures
by Justine Chew July 29, 2019

July 29, 2019

Dear all, I was assigned an action item at the last CPWG Call of 24 Jul 2019 along the lines of *"**ID of issues - "What subsequent procedures and where else do we go? Who is audience?"*" *Context* - Those of you who follow the proceedings of the GNSO Subsequent Procedures PDP WG ("SubPro WG") will know that the SubPro WG have in Apr 2019 commenced deliberations on the public comments received in response to the call for public comments to its Initial Report of Jul 2018. And the said deliberations, the SubPro WG welcomes input (especially from SubPro WG members) whether it be through its calls or mailing list - The ALAC has over a long period of time (dating back to 2008) provided inputs or advice on various issues relating to Subsequent Procedures - At this point, there may not be a further need for intervention within the SubPro WG by At-Large/ALAC provided it can be established that our inputs or advice have been satisfactorily taken into account by the SubPro WG. This is aside from continuing efforts by several active At-Large members in the SubPro WG in helping ensure that the ALAC inputs aren't inadvertently omitted, overlooked or misinterpreted in the context of the deliberations (especially when an input relates to more than one issue within the SubPro WG's agenda). - In some cases, the ALAC's inputs in the form of statements submitted through the public comments process are shared by other constituencies; which leads to a finding of "high level agreement" thus enabling the SubPro WG to at least develop a recommendation for the same. - *It is the ALAC inputs which are not shared by other constituencies or which do not receive sufficient support that we are concerned with now. And what we have to now consider is whether we believe such inputs are crucial enough for At-Large to keep pressing for and if yes, how. * *Action Taken* - Holly Raiche and I have prepared a list of Issues within Subsequent Procedures for which we think At-Large/ALAC have provided substantial input, as a starting reference point -- *please go to the relevant At-Large Workspace: https://community.icann.org/x/6a_jBg <https://community.icann.org/x/6a_jBg> to view or to comment on this said list.* - The idea we and Jonathan Zuck have is to try and highlight, over a series of CPWG calls, where the SubPro WG is at in terms of its deliberations, on a topic by topic basis, covering only those topics which relate to issues within subsequent procedures for which the ALAC has provided inputs (or advice). Since the SubPro WG is currently deliberating the topic of Applicant Support (during its calls of 24 Jul and upcoming of 29 Jul 20:00 UTC), we thought we might *try* to properly start our exercise with this topic. I will be sending a separate email on Applicant Support shortly. Kind regards, Justine Chew -----

2 1

EDPB Annual Report 2018
by Carlton Samuels July 25, 2019

July 25, 2019

.... everything you need to know about how they see GDPR looking back...and forward.... https://edpb.europa.eu/our-work-tools/our-documents/publication-type/annual… -Carlton -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

1 0

Re: [CPWG] [GTLD-WG] Draft comment on the Fundamental Bylaw change.
by Alan Greenberg July 25, 2019

July 25, 2019

Evan, inclusion of the non-ccNSO ccTLDs was an integral (and by some deemed critical) part of the IANA Stewardship transition process, and since IANA serves non-ccNSO ccTLDs, it was felt important that they too can participate in any review. I do not believe that it is within our (ICANN's) mandate to re-litigate this and change the overall intent. Or at least, that is my understanding. For the record, currently 17 2ccTLDs out of 249 defined ccTLD are members and the list has been growing at about 5 per year over the last 5 years. Alan At 25/07/2019 01:35 AM, Evan Leibovitch wrote: I understand the problem to be solved but don't like the wording of the replacement. Why should non-ccNSO-member ccTLD managers even be eligible? There is precious little incentive for ccTLD registries to have anything to do with ICANN. Eligibility for selection here ought to be part of such incentive. They should just change "Two" to "Three" in 18.7(a) and drop 18.7(b) entirely. No other rewording is needed. - Evan On Wed, 24 Jul 2019 at 18:18, Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca> > wrote: I was asked to draft the comment for the ALAC's response to the Public Comment on the Fundamental Bylaw Change ( https://community.icann.org/pages/viewpage.action?pageId=111384218 ). The Public Comment closes this Friday at 23:59 UTC. (about 50 hours from now) =================================== The ALAC supported the current version of the ICANN Bylaws Section 18.7(a) and 18.7(b), but understands that it has now proven to be difficult to implement. The ALAC agrees that the proposed change preserves the intent of the original Fundamental Bylaw and supports the change. Subject to any new information being brought to the ALAC's attention, the current intention is that the ALAC will support this Fundamental Bylaw change when it is present to the Empowered Community. _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ 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. _______________________________________________ GTLD-WG mailing list GTLD-WG(a)atlarge-lists.icann.org<mailto:GTLD-WG@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg Working Group direct URL: https://community.icann.org/display/atlarge/New+GTLDs _______________________________________________ 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. -- Evan Leibovitch, Toronto Canada @evanleibovitch or @el56

2 1

Draft comment on the Fundamental Bylaw change.
by Alan Greenberg July 25, 2019

July 25, 2019

I was asked to draft the comment for the ALAC's response to the Public Comment on the Fundamental Bylaw Change (https://community.icann.org/pages/viewpage.action?pageId=111384218) The Public Comment closes this Friday at 23:59 UTC. (about 50 hours from now) =================================== The ALAC supported the current version of the ICANN Bylaws Section 18.7(a) and 18.7(b), but understands that it has now proven to be difficult to implement. The ALAC agrees that the proposed change preserves the intent of the original Fundamental Bylaw and supports the change. Subject to any new information being brought to the ALAC's attention, the current intention is that the ALAC will support this Fundamental Bylaw change when it is present to the Empowered Community.

4 4