Fwd: Advice to the Board?
Dear At-Large Community If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings. The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN. During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model". I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "* I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board. *Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.* Maureen ---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org> Dear ALAC members It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond. Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic. If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least. I look forward to a yay or nay from members about sending this as advice. Regards Maureen Marita Moll via At-Large 2:32 AM (20 hours ago) to At With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community: 10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture 9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings 8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together 7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing. 6. No one is taking ownership of this waiver. The Board position on it is unclear 5. There has been no general explanation to the community or any attempt seek buy-in for this waiver 4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation 3. The waiver infringes on individual rights 2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization *Top reason why this waiver is a really bad idea:* *1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.* Marita (now signing off on this topic -- thanks for bearing with me)
Dear colleagues: I support the advice that We the At-Large community and myself as a volunteer must submit to the ICANN Board. As a Mentor to the Fellowship Program I wonder how the ICANN Org and Board would address Fellows that with sacrifice and undet unintentional circumstances suffer any issues and are left on their own as the waiver implies. It comes to my mind, has ICANN encounter any legal situations prior to the COVID-19 that has made them asume this position? Please add me as a supporter of the Advice. Alfredo Calderon Email: calderon.alfredo@gmail.com Twitter: acalderon52 LinkedIn: pr.linkedin.com/in/acalderon52 Skype: alfredo_1212 Business Card: http://myonepage.com/acalderon Blog: https://aprendizajedistancia.blogspot.com VSIG: Virtual School on Internet Governance - https://virtualsig.org
On Apr 29, 2022, at 7:29 PM, Maureen Hilyard via At-Large <at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, as the basis of our Advice to the Board that the waiver be withdrawn. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago)
to At With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture 9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings 8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together 7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing. 6. No one is taking ownership of this waiver. The Board position on it is unclear 5. There has been no general explanation to the community or any attempt seek buy-in for this waiver 4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation 3. The waiver infringes on individual rights 2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization Top reason why this waiver is a really bad idea: 1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community. Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Please add me as a support. The work done by the community is certainly what we all have stood for. I agree with the point of the statement that in safeguarding ICANN itself, it shouldn't make the volunteer feel different. Regards Shreedeep On Sat, 30 Apr 2022, 5:14 am Maureen Hilyard via At-Large, < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Hello As Euralo Chair I supporte this statement and would like that my name (and responsibility) be added. Thanks Marita, Maureen and all. Sébastien Bachollet Envoyé de mon iPhone
Le 30 avr. 2022 à 01:29, Maureen Hilyard via At-Large <at-large@atlarge-lists.icann.org> a écrit :
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, as the basis of our Advice to the Board that the waiver be withdrawn. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago)
to At With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture 9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings 8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together 7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing. 6. No one is taking ownership of this waiver. The Board position on it is unclear 5. There has been no general explanation to the community or any attempt seek buy-in for this waiver 4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation 3. The waiver infringes on individual rights 2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization Top reason why this waiver is a really bad idea: 1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community. Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
I have already commented on the matter, and I would like to formally support Marita’s points. I would also like to add that, while the formal justification by ICANN for the waiver is the COVID situation, the waiver itself covers areas that have nothing to do with the pandemic. Particularly puzzling for me is the following sentence: I agree to indemnify and hold ICANN and its affiliate harmless from and against any claims, suits, causes of action, loss, liability, damage or costs, including court cost and attorneys’ fees, and fees to enforce this Agreement, that ICANN may incur arising from my involvement in the Event. IANAL, but my understanding is that I should indemnify ICANN for any legal action, even if brought forward by third parties, if there is any relation to my “involvement” in the event (and may I stress “involvement”, not “participation” or “attendance”). And that can be related to anything, even injuries caused by the fall of a loosely fixed object. My question is how could I continue trusting ICANN when ICANN shows this distrust in my participation as volunteer? Regardless the final result of the matter, something has definitively been broken. And I fully agree with Alfredo Calderón, how can we explain this to the newcomers? I have myself a responsibility towards newcomers, as NextGen Mentor, and could not refuse to sign the waiver because this would have meant deprive my mentees from a personal presence and support in Den Haag - but I am furious about this situation. Cheers, Roberto
On 30.04.2022, at 01:29, Maureen Hilyard via At-Large <at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, as the basis of our Advice to the Board that the waiver be withdrawn. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com <mailto:maureen.hilyard@gmail.com>> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org <mailto:ALAC-members@icann.org>>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago)
to At With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture 9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings 8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together 7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing. 6. No one is taking ownership of this waiver. The Board position on it is unclear 5. There has been no general explanation to the community or any attempt seek buy-in for this waiver 4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation 3. The waiver infringes on individual rights 2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization Top reason why this waiver is a really bad idea: 1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community. Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Dear All, To be clear, removal of the indemnity will just mean more virtual meetings and less physical meetings which saves money for ICANN and is a win win for everyone. No organisation in their right mind will want to be liable for claims against it especially when hosting events. This would also mean the end of At Large in an indirect way as volunteers prefer volunteering for the sheer love of the opportunity to meet and discuss their work issues. Sometimes, we have to pick which battles are worth fighting for. Sala On Sat, 30 Apr 2022 at 11:00, Roberto Gaetano via At-Large < at-large@atlarge-lists.icann.org> wrote:
I have already commented on the matter, and I would like to formally support Marita’s points.
I would also like to add that, while the formal justification by ICANN for the waiver is the COVID situation, the waiver itself covers areas that have nothing to do with the pandemic. Particularly puzzling for me is the following sentence:
*I agree to indemnify and hold ICANN and its affiliate harmless from and against **any claims, suits, causes of action, loss, liability, damage or costs, including court **cost and attorneys’ fees, and fees to enforce this Agreement, that ICANN may **incur arising from my involvement in the Event.*
IANAL, but my understanding is that I should indemnify ICANN for any legal action, even if brought forward by third parties, if there is any relation to my “involvement” in the event (and may I stress “involvement”, not “participation” or “attendance”). And that can be related to anything, even injuries caused by the fall of a loosely fixed object.
My question is how could I continue trusting ICANN when ICANN shows this distrust in my participation as volunteer? Regardless the final result of the matter, something has definitively been broken. And I fully agree with Alfredo Calderón, how can we explain this to the newcomers? I have myself a responsibility towards newcomers, as NextGen Mentor, and could not refuse to sign the waiver because this would have meant deprive my mentees from a personal presence and support in Den Haag - but I am furious about this situation.
Cheers, Roberto
On 30.04.2022, at 01:29, Maureen Hilyard via At-Large < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
-- "The entrance of Your words gives light; It gives understanding to the simple". Psalms 119:130
Sorry. Such waivers were not required in the past and tons of organizations have meetings that do not require such waivers of liability. John More
On Apr 30, 2022, at 9:13 AM, Salanieta T. Tamanikaiwaimaro via At-Large <at-large@atlarge-lists.icann.org> wrote:
Dear All,
To be clear, removal of the indemnity will just mean more virtual meetings and less physical meetings which saves money for ICANN and is a win win for everyone.
No organisation in their right mind will want to be liable for claims against it especially when hosting events.
This would also mean the end of At Large in an indirect way as volunteers prefer volunteering for the sheer love of the opportunity to meet and discuss their work issues.
Sometimes, we have to pick which battles are worth fighting for.
Sala
On Sat, 30 Apr 2022 at 11:00, Roberto Gaetano via At-Large <at-large@atlarge-lists.icann.org <mailto:at-large@atlarge-lists.icann.org>> wrote: I have already commented on the matter, and I would like to formally support Marita’s points.
I would also like to add that, while the formal justification by ICANN for the waiver is the COVID situation, the waiver itself covers areas that have nothing to do with the pandemic. Particularly puzzling for me is the following sentence:
I agree to indemnify and hold ICANN and its affiliate harmless from and against any claims, suits, causes of action, loss, liability, damage or costs, including court cost and attorneys’ fees, and fees to enforce this Agreement, that ICANN may incur arising from my involvement in the Event.
IANAL, but my understanding is that I should indemnify ICANN for any legal action, even if brought forward by third parties, if there is any relation to my “involvement” in the event (and may I stress “involvement”, not “participation” or “attendance”). And that can be related to anything, even injuries caused by the fall of a loosely fixed object.
My question is how could I continue trusting ICANN when ICANN shows this distrust in my participation as volunteer? Regardless the final result of the matter, something has definitively been broken. And I fully agree with Alfredo Calderón, how can we explain this to the newcomers? I have myself a responsibility towards newcomers, as NextGen Mentor, and could not refuse to sign the waiver because this would have meant deprive my mentees from a personal presence and support in Den Haag - but I am furious about this situation.
Cheers, Roberto
On 30.04.2022, at 01:29, Maureen Hilyard via At-Large <at-large@atlarge-lists.icann.org <mailto:at-large@atlarge-lists.icann.org>> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, as the basis of our Advice to the Board that the waiver be withdrawn. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com <mailto:maureen.hilyard@gmail.com>> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org <mailto:ALAC-members@icann.org>>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago)
to At With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture 9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings 8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together 7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing. 6. No one is taking ownership of this waiver. The Board position on it is unclear 5. There has been no general explanation to the community or any attempt seek buy-in for this waiver 4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation 3. The waiver infringes on individual rights 2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization Top reason why this waiver is a really bad idea: 1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community. Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org <mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large <https://atlarge-lists.icann.org/mailman/listinfo/at-large>
At-Large Official Site: http://atlarge.icann.org <http://atlarge.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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org <mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large <https://atlarge-lists.icann.org/mailman/listinfo/at-large>
At-Large Official Site: http://atlarge.icann.org <http://atlarge.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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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. -- "The entrance of Your words gives light; It gives understanding to the simple". Psalms 119:130 _______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Hello Maureen, all After checking with the AFRALO leadership, I'd like to note the support of the leadership for the statement. Regards Chair AFRALO Sent from my mobile Kindly excuse brevity and typos Every word has consequences. Every silence does too! On Sat, 30 Apr 2022, 00:29 Maureen Hilyard via At-Large, < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Dear all On behalf of APRALO, I support the statement. With kind regards satish On Sat, Apr 30, 2022 at 7:39 PM Seun Ojedeji via At-Large < at-large@atlarge-lists.icann.org> wrote:
Hello Maureen, all
After checking with the AFRALO leadership, I'd like to note the support of the leadership for the statement.
Regards Chair AFRALO Sent from my mobile Kindly excuse brevity and typos Every word has consequences. Every silence does too!
On Sat, 30 Apr 2022, 00:29 Maureen Hilyard via At-Large, < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Maureen: I did an impromptus canvas in the NARALO region, and four members supported this. Due to the short time to the deadline set by you, I, as NARALO Chair, cannot categorically indicate that NARALO, the region, can or cannot support the sending of this advice based on these numbers. However, as a member of the At-Large and an active and engaged volunteer in ICANN’s work, I support sending the statement from ALAC to the Board. So please count me as one of the signatories. I would also like to add that I have signed up to participate in ICANN74 on my profound interest in interacting f2f with most of you. This *“we do not care about you*” waiver will hinder our outreach and engagement efforts going forward. -ed On Fri, Apr 29, 2022 at 7:29 PM Maureen Hilyard via At-Large < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
-- *Notice*: This email may contain confidential information, is 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.
If ever you need further proof of how the ICANN enterprise values volunteers, here it is. The suggestion is unconscionable, broadly uncaring and totally dismissive of volunteer contributions. This blatant attempt to hand volunteers a dagger for their own heart could be indicative of a long game just booted. Maybe the enterprise has come to decide it no longer needs the fig leaf that is largely the role of us volunteers so it's winding down time. ICANN 4.0. Let the record show I find this example of an indulgence corrosively insulting. Add my name to the list of those opposed. Carlton Samuels ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* ============================= On Fri, 29 Apr 2022 at 18:29, Maureen Hilyard via At-Large < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Friends, Carlton has taken the words out of my mouth, I fully agree with what he says. Please also add my name to the list of those who oppose. Kind regards *Sergio Salinas Porto**Presidente Internauta Argentina - LACRALO/ICANN <https://atlarge.icann.org/ralos/lacralo>**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>**FUILAC- Federación de Usuarios de Internet de LAC <https://fuilac.org>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra * * conciencia o violan nuestro sentido común" Eduardo Galeano* El lun, 2 may 2022 a las 14:06, Carlton Samuels via At-Large (< at-large@atlarge-lists.icann.org>) escribió:
If ever you need further proof of how the ICANN enterprise values volunteers, here it is. The suggestion is unconscionable, broadly uncaring and totally dismissive of volunteer contributions.
This blatant attempt to hand volunteers a dagger for their own heart could be indicative of a long game just booted. Maybe the enterprise has come to decide it no longer needs the fig leaf that is largely the role of us volunteers so it's winding down time. ICANN 4.0.
Let the record show I find this example of an indulgence corrosively insulting. Add my name to the list of those opposed.
Carlton Samuels
============================== *Carlton A Samuels*
*Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================
On Fri, 29 Apr 2022 at 18:29, Maureen Hilyard via At-Large < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Done. Thank you Sergio On Tue, May 3, 2022 at 11:32 AM Sergio Salinas Porto < presidencia@internauta.org.ar> wrote:
Friends, Carlton has taken the words out of my mouth, I fully agree with what he says. Please also add my name to the list of those who oppose. Kind regards
*Sergio Salinas Porto**Presidente Internauta Argentina - LACRALO/ICANN <https://atlarge.icann.org/ralos/lacralo>**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>**FUILAC- Federación de Usuarios de Internet de LAC <https://fuilac.org>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra *
* conciencia o violan nuestro sentido común" Eduardo Galeano*
El lun, 2 may 2022 a las 14:06, Carlton Samuels via At-Large (< at-large@atlarge-lists.icann.org>) escribió:
If ever you need further proof of how the ICANN enterprise values volunteers, here it is. The suggestion is unconscionable, broadly uncaring and totally dismissive of volunteer contributions.
This blatant attempt to hand volunteers a dagger for their own heart could be indicative of a long game just booted. Maybe the enterprise has come to decide it no longer needs the fig leaf that is largely the role of us volunteers so it's winding down time. ICANN 4.0.
Let the record show I find this example of an indulgence corrosively insulting. Add my name to the list of those opposed.
Carlton Samuels
============================== *Carlton A Samuels*
*Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================
On Fri, 29 Apr 2022 at 18:29, Maureen Hilyard via At-Large < at-large@atlarge-lists.icann.org> wrote:
Dear At-Large Community
If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings.
The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN.
During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model".
I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "*the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn*" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "*I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN "*
I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, *as the basis of our Advice to the Board that the waiver be withdrawn*. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board.
*Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board.*
Maureen
---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org>
Dear ALAC members
It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond.
Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic.
If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least.
I look forward to a yay or nay from members about sending this as advice. Regards Maureen
Marita Moll via At-Large 2:32 AM (20 hours ago) to At
With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community:
10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture
9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings
8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together
7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing.
6. No one is taking ownership of this waiver. The Board position on it is unclear
5. There has been no general explanation to the community or any attempt seek buy-in for this waiver
4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation
3. The waiver infringes on individual rights
2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization
*Top reason why this waiver is a really bad idea:*
*1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community.*
Marita (now signing off on this topic -- thanks for bearing with me)
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
_______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.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.
Please add my name, too. It is a well-known challenge in all democratic procedures - associations, co-operatives, democracies etc. How to avoid moving from a participative democracy to an elective democracy? In the case of ICANN, sufficient encouragement and support of the people is decisive. Taking care and helping people for participating is a very important part of it. Erich SCHWEIGHOFER Erich ao. Univ.-Prof. (UniWien, Rechtsinformatik, Europarecht, Internationales Multistakeholderrecht) Mag. rer.soc.oec. Dr. iur. Dr. rer.soc.oec. Lg.IntStud (freigestellt für die Europäische Kommission, Rue de la Loi 130, 1040 Brussel BE, erich.schweighofer@ec.europa.eu, Tel. +32 2 29 52283) Rechtsinformatik an der Uni-Wien Sprecher des Vorstands der ARI Arbeitsgruppe Rechtsinformatik, Juridicum, Universität Wien Vorsitz: iris-conferences.eu Präsident: WZRI LII-Austria CEILI RI@ ADRI Institut für Europarecht, Internationales Recht und Rechtsvergleichung (auch Abteilung für Völkerrecht), Schottenbastei 10-16/2/5, Zi. 546, 1010 Wien AT, Tel. +43 1 4277 35305 (Anrufbeantworter) https://rechtsinformatik.univie.ac.at, https://rechtsinformatik.ACADEMY, https://iris-conferences.eu, https://wzri.eu office@rechtsinformatik.ACADEMY; office@iris-conferences.eu; rechtsinformatik@univie.ac.at; Erich.Schweighofer@univie.ac.at Bitte um Teilnahme und Beiträge: IRI§22 https://iris-conferences.eu, Frühlingssemester: Event Rechtslogik in der Praxis Do 31.03.22, 16-19 Uhr (gemeinsam mit ReMeP) Jusletter IT http://jusletter-it.eu Schriftenreihe Arbeitsgruppe Rechtsinformatik, rechtsinformatik.ACADEMY & IRIS-Journal: https://irisj.eu PHAIDRA ________________________________________ Von: At-Large [at-large-bounces@atlarge-lists.icann.org] im Auftrag von Maureen Hilyard via At-Large [at-large@atlarge-lists.icann.org] Gesendet: Dienstag, 3. Mai 2022 01:48 An: Sergio Salinas Porto Cc: At-Large Worldwide Betreff: Re: [At-Large] Fwd: Advice to the Board? Done. Thank you Sergio On Tue, May 3, 2022 at 11:32 AM Sergio Salinas Porto <presidencia@internauta.org.ar<mailto:presidencia@internauta.org.ar>> wrote: Friends, Carlton has taken the words out of my mouth, I fully agree with what he says. Please also add my name to the list of those who oppose. Kind regards Sergio Salinas Porto Presidente Internauta Argentina - LACRALO/ICANN<https://atlarge.icann.org/ralos/lacralo> Asociación Argentina de Usuarios de Internet<http://www.internauta.org.ar/>/FeTIA<http://www.fetia.org.ar/> FUILAC- Federación de Usuarios de Internet de LAC<https://fuilac.org> facebook: salinasporto<http://www.facebook.com/salinasporto> twitter: sergiosalinas<http://twitter.com/sergiosalinas> Mobi:+54 9 223 5 215819 "Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra conciencia o violan nuestro sentido común" Eduardo Galeano El lun, 2 may 2022 a las 14:06, Carlton Samuels via At-Large (<at-large@atlarge-lists.icann.org<mailto:at-large@atlarge-lists.icann.org>>) escribió: If ever you need further proof of how the ICANN enterprise values volunteers, here it is. The suggestion is unconscionable, broadly uncaring and totally dismissive of volunteer contributions. This blatant attempt to hand volunteers a dagger for their own heart could be indicative of a long game just booted. Maybe the enterprise has come to decide it no longer needs the fig leaf that is largely the role of us volunteers so it's winding down time. ICANN 4.0. Let the record show I find this example of an indulgence corrosively insulting. Add my name to the list of those opposed. Carlton Samuels ============================== Carlton A Samuels Mobile: 876-818-1799 Strategy, Process, Governance, Assessment & Turnaround ============================= On Fri, 29 Apr 2022 at 18:29, Maureen Hilyard via At-Large <at-large@atlarge-lists.icann.org<mailto:at-large@atlarge-lists.icann.org>> wrote: Dear At-Large Community If you have been following the At-Large community discussion list, you will have noted the concern that has been raised about a waiver that ICANN is imposing on the volunteer community to provide their signature to the document, as a prerequisite to being granted travel sponsorship to attend F2F ICANN Meetings. The waiver absolves ICANN of any responsibility for an ICANN participant'sgetting ill or is harmed in any way, even if it is ICANN's fault. This is the core concern for us as volunteers. It is seen as an unreasonable ask of volunteers who have always known that they have to take responsibility for themselves not only when attending ICANN meetings, but also when they participate in other F2F meetings and working group activities that occur in between ICANN meetings. We can appreciate that ICANN needs to protect itself, but while doing so they should not abdicate their duty of care to all those members of the ICANN community who have dedicated many years to providing personal inputs into ICANN's important work - to produce policy that will help to protect the DNS. It is taken for granted that "years" is the normal measurement in time which is required to produce formal outputs from ICANN. During the At-Large community discussions, a raft of reasons developed which related to how this waiver that has been imposed as a pre-requisite to any travel support, impacts volunteer communities throughout ICANN. These reasons were noted and transformed into a list of 10 reasons why the waiver is not one of the best decisions that has come out of ICANN - more especially because it did not adhere to one of its core principles "the bottom-up, multistakeholder model". I have called the ALAC members together to make a decision about the waiver (the invitations for them to do so is below) to seek their support for "the waiver and the expectation that it is signed before any travel sponsorship is provided, to be withdrawn" Although we have to consider that this course of action may not be actionable before ICANN74, we would ultimately like to return to what was the practice of the past when the community was trusted. We have always known that we were attending ICANN meetings at our own risk and would not have earlier contemplated taking action against ICANN for any illness or harm that might befall us if it was the fault of the individual during an ICANN meeting. There was also some need to address the section that had been identified as a key sticking point "I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN " I already have a majority of the ALAC members who have immediately added their support to my request to submit Marita's 10 reasons why the waivers should be removed, as the basis of our Advice to the Board that the waiver be withdrawn. In case they are otherwise engaged, other ALAC members still have a bit of time to respond (by Sunday 1 May 23.59utc) before the request is formally submitted as ALAC advice to the Board. Although many of our community already participated earlier, I would hope that others in our At-Large community will also support this request. Please let me know if you would like to add your name to our letter of Advice to the Board. Maureen ---------- Forwarded message --------- From: Maureen Hilyard <maureen.hilyard@gmail.com<mailto:maureen.hilyard@gmail.com>> Date: Fri, Apr 29, 2022 at 11:14 PM Subject: Advice to the Board? To: ALAC Members <ALAC-members@icann.org<mailto:ALAC-members@icann.org>> Dear ALAC members It has been suggested that we propose Marita's email to the community as ADVICE to the Board of the community's feelings about the waiver, so that the Board has to officially respond. Earlier messages of concern about other issues about volunteer support have only been noted because they were not formal advice, even though they reflected many discussions by the At-Large community, particularly during the pandemic. If you have any concerns about this summary list, please let me know before Sunday 23.59UTC. I think it is an important issue and that we need to make sure that it is given the consideration that it deserves. I realise that any change may not happen for ICANN74 but if can address these issues for future meetings we will have achieved something at least. I look forward to a yay or nay from members about sending this as advice. Regards Maureen Marita Moll via At-Large 2:32 AM (20 hours ago) [https://mail.google.com/mail/u/0/images/cleardot.gif] [https://mail.google.com/mail/u/0/images/cleardot.gif] to At [https://mail.google.com/mail/u/0/images/cleardot.gif] With apologies to former late show host David Letterman and thanks to all those who provided input, here are my top 10 reasons why this waiver is a bad idea for ICANN and for the community: 10. It is insensitive to the global community as it can be interpreted as an exportation of U.S.-based litigious culture 9. It disregards the fact that participants at ICANN meetings have always willingly and knowingly accepted personal responsibility for health issues that arise during meetings 8. It is a disincentive to attending ICANN meetings in person, thereby damaging the ability of the community to work together 7. Concerns which have arisen throughout the community about the broad scope of the waiver are not being addressed – including legal opinions warning potential participants against signing. 6. No one is taking ownership of this waiver. The Board position on it is unclear 5. There has been no general explanation to the community or any attempt seek buy-in for this waiver 4. This kind of blanket waiver could be unenforceable and in that case, serves only as intimidation 3. The waiver infringes on individual rights 2. ICANN appears to be abandoning its duty of care to the participating community who are voluntarily contributing their time and energy to fulfilling ICANN's mandate to operate as a bottom-up multistakeholder organization Top reason why this waiver is a really bad idea: 1. It leaves a lasting unpleasant taste in the mouths of participants contributing to ICANN's multistakeholder model -- which is presented as a source of pride and accomplishment to the internet governance community. Marita (now signing off on this topic -- thanks for bearing with me) _______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org<mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.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. _______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org<mailto:At-Large@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.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.
participants (13)
-
Alfredo Calderon -
Carlton Samuels -
Eduardo Diaz -
John More -
Maureen Hilyard -
Roberto Gaetano -
Salanieta T. Tamanikaiwaimaro -
Satish Babu -
SCHWEIGHOFER Erich Prof. Dr. Dr.. -
Sebastien Bachollet -
Sergio Salinas Porto -
Seun Ojedeji -
Shreedeep Rayamajhi