January 2020 - ALAC - lists.icann.org

Re: [ALAC] [ALAC-Members] [CPWG] [ALT-Plus] PIR and Dot Org
by carlosraul＠gutierrez.se Jan. 8, 2020

Jan. 8, 2020

5 5

Re: [ALAC] [CPWG] [ALT-Plus] PIR and Dot Org
by Holly Raiche Jan. 7, 2020

Jan. 7, 2020

Well said Holly > On Jan 7, 2020, at 12:13 PM, Greg Shatan <greg(a)isoc-ny.org> wrote: > > Maureen and all, > > I agree with Roberto, and would perhaps go even further. The best solution would be to have a voting seat on the PIR board, rather than a non-voting liaison. I'm not sure which Roberto was suggesting. To my mind, true "representation" comes with a vote.. > > I also agree with everything Jonathan Zuck said -- about the mission, about Malthouse, about that "editorial." Nasty stuff. An appropriate response needs to be considered, but I'm not sure what that might be. It might be a message from someone else in At Large, pointing out that in a bottom-up organization, it's not the Chair's job to go flying into battle on their own impetus. Or maybe it can come from a bunch of somebodies.... > > However, I'm concerned that if ALAC and At-large do not speak for themselves, the "record" is going to be the garbage that is being thrown at us. > > There are more important things than a pissing match in the toilet of public opinion. > > We have ALAC's "superpower" -- the mandate to provide formal advice to the Board. (Not quite as "super" as GAC advice, but it's what we've got, and if it is exercised properly, it will grow in strength, like a muscle.) > > Then we can go into toilets with Jacob and Nat.... > > Greg > > > > > Greg Shatan > greg(a)isoc-ny.org <mailto:greg@isoc-ny.org> > President, ISOC-NY > "The Internet is for everyone" > > > On Mon, Jan 6, 2020 at 2:10 PM Olivier MJ Crépin-Leblond <ocl(a)gih.com <mailto:ocl@gih.com>> wrote: > Dear all, > > indeed - the DotMobi Liaison was on the DotMobi Policy Advisory Board. But IMHO Roberto's suggestion for a Liaison to the PIR Board sounds good. > For those interested, DotMobi Liaison Reports can be found on: https://community.icann.org/display/atlarge/dotMOBI+Liaison+Reports <https://community.icann.org/display/atlarge/dotMOBI+Liaison+Reports> > > Kindest regards, > > Olivier > > > On 06/01/2020 11:24, Maureen Hilyard wrote: >> Excellent points Roberto. >> Your experience on the PIR Board is invaluable in this regard. and your recommendations noted. >> >> Maureen >> >> On Mon, Jan 6, 2020 at 12:02 AM Roberto Gaetano <mail.roberto.gaetano(a)gmail.com <mailto:mail.roberto.gaetano@gmail.com>> wrote: >> Hi Maureen. >> I have been thinking further about this, and came to the conclusion that our proposal would be not to have a representative on the Stewardship Council but on the PIR Board. >> Here is the rationale for that. >> The Stewardship Council will play the role that was previously of the Advisory Council. Its purpose was to get multiple voices from different part of the user community, and in particular the NGOs, ensuring diversity of opinions. This body was advisory to a Board that had already built-in the fundamental non-profit, user-community DNA, because it was selected by ISOC. >> With the changed situation, we can safely assume that the new PIR Board will be selected by Ethos to take care of the interests of the investors, and there is no guarantee that the public interest is being taken care of. >> This will be a good option for Ethos as well, because it would show in a concrete way the commitment to the public interest beyond mere verbal expression of intents. On the other hand, Ethos and the investors would keep a solid majority that will ensure that their interests are protected. >> We should remember that while the Advisory Council was surely empowered to provide advice, and was surely listened to, a Director would have access to more information and definitively better opportunities to discuss different ideas and approaches with his/her fellow Directors, therefore presenting the point of view of the public interest more effectively. >> In short, this person wold play a role that is similar to the one that León plays in ICANN: committed to the fiduciary responsibility to the corporation but able to be a strong voice to the discussion. >> I think that we should not be shy, all in remaining reasonable with our proposals. I believe that this one is a win-win, bringing the voice of the user community in PIR and being a good opportunity for Ethos to show a commitment while still remaining in control of PIR. >> Cheers, >> Roberto >> >> PS: As I am not subscribed to the different mailing lists, please forward this if you see fit >> >> >>> On 06.01.2020, at 01:40, Maureen Hilyard <maureen.hilyard(a)gmail.com <mailto:maureen.hilyard@gmail.com>> wrote: >>> >>> http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… <http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act…> >>> >>> Well that is certainly forcing our hand to take some action. But with arrows flying in all sorts of directions it has been difficult to know which one to follow, and I note there has been a break in the conversations on this topic. >>> >>> Interesting and very timely that Roberto raised the .org issue again in an earlier email today. I started a response until JZ reminded us that the thread was about .com >>> >>> I agree with Roberto's approach - that we should focus on our role as the voice of At-Large end-users and offer some creative advice on how we might influence the behaviour of PIR and any future decisions they make that will impact on .org end-users. PIR/Ethos already presented a webinar and said all the right things.. but how can we be assured that they will stick to what they said that they would do in the future? Who will monitor this on behalf of ordinary end-users? Who will be represented on the Stewardship Council? >>> >>> At the same time we may also need to advise the ICANN Board about how they might deal with the ICANN-PIR/Ethos contract - especially Roberto's recommendation of some commitment from ICANN that ethical behaviour towards .org end-users will be built into it. >>> >>> We are aware that the Board is looking into every legal issue relating to how they can deal with matters that are being raised by letters that are flowing their way. We don't need to add more of the same. >>> >>> While i think it might be seen to be a simplistic approach, I believe that we should stick to what our job is and focus on advice to the Board and to PIR- but lets try to be creative about how we advise them, looking at the impacts on end-users from all perspectives. >>> >>> My 2c >>> M >>> >>> >>> _______________________________________________ >>> CPWG mailing list >>> CPWG(a)icann.org <mailto:CPWG@icann.org> >>> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg> >>> >>> _______________________________________________ >>> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy <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. >> >> >> >> _______________________________________________ >> ALT-Plus mailing list >> ALT-Plus(a)icann.org <mailto:ALT-Plus@icann.org> >> https://mm.icann.org/mailman/listinfo/alt-plus <https://mm.icann.org/mailman/listinfo/alt-plus> >> >> _______________________________________________ >> 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. > > -- > Olivier MJ Crépin-Leblond, PhD > http://www.gih.com/ocl.html <http://www.gih.com/ocl.html>_______________________________________________ > CPWG mailing list > CPWG(a)icann.org <mailto:CPWG@icann.org> > https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg> > > _______________________________________________ > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy <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. > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

2 1

Re: [ALAC] [CPWG] [ALT-Plus] PIR and Dot Org
by Maureen Hilyard Jan. 7, 2020

Jan. 7, 2020

Totally agree. It's a team effort. Power to the people!! M On Mon, 6 Jan 2020, 3:13 PM Greg Shatan, <greg(a)isoc-ny.org> wrote: > Maureen and all, > > I agree with Roberto, and would perhaps go even further. The best > solution would be to have a voting seat on the PIR board, rather than a > non-voting liaison. I'm not sure which Roberto was suggesting. To my mind, > true "representation" comes with a vote.. > > I also agree with everything Jonathan Zuck said -- about the mission, > about Malthouse, about that "editorial." Nasty stuff. An appropriate > response needs to be considered, but I'm not sure what that might be. It > might be a message from someone else in At Large, pointing out that in a > bottom-up organization, it's not the Chair's job to go flying into battle > on their own impetus. Or maybe it can come from a bunch of somebodies.... > > However, I'm concerned that if ALAC and At-large do not speak for > themselves, the "record" is going to be the garbage that is being thrown at > us. > > There are more important things than a pissing match in the toilet of > public opinion. > > We have ALAC's "superpower" -- the mandate to provide formal advice to the > Board. (Not quite as "super" as GAC advice, but it's what we've got, and > if it is exercised properly, it will grow in strength, like a muscle.) > > Then we can go into toilets with Jacob and Nat.... > > Greg > > > > > Greg Shatan > greg(a)isoc-ny.org > President, ISOC-NY > *"The Internet is for everyone"* > > > On Mon, Jan 6, 2020 at 2:10 PM Olivier MJ Crépin-Leblond <ocl(a)gih.com> > wrote: > >> Dear all, >> >> indeed - the DotMobi Liaison was on the DotMobi Policy Advisory Board. >> But IMHO Roberto's suggestion for a Liaison to the PIR Board sounds good. >> For those interested, DotMobi Liaison Reports can be found on: >> https://community.icann.org/display/atlarge/dotMOBI+Liaison+Reports >> >> Kindest regards, >> >> Olivier >> >> >> On 06/01/2020 11:24, Maureen Hilyard wrote: >> >> Excellent points Roberto. >> Your experience on the PIR Board is invaluable in this regard. and your >> recommendations noted. >> >> Maureen >> >> On Mon, Jan 6, 2020 at 12:02 AM Roberto Gaetano < >> mail.roberto.gaetano(a)gmail.com> wrote: >> >>> Hi Maureen. >>> I have been thinking further about this, and came to the conclusion that >>> our proposal would be not to have a representative on the Stewardship >>> Council but on the PIR Board. >>> Here is the rationale for that. >>> The Stewardship Council will play the role that was previously of the >>> Advisory Council. Its purpose was to get multiple voices from different >>> part of the user community, and in particular the NGOs, ensuring diversity >>> of opinions. This body was advisory to a Board that had already built-in >>> the fundamental non-profit, user-community DNA, because it was selected by >>> ISOC. >>> With the changed situation, we can safely assume that the new PIR Board >>> will be selected by Ethos to take care of the interests of the investors, >>> and there is no guarantee that the public interest is being taken care of. >>> This will be a good option for Ethos as well, because it would show in a >>> concrete way the commitment to the public interest beyond mere verbal >>> expression of intents. On the other hand, Ethos and the investors would >>> keep a solid majority that will ensure that their interests are protected. >>> We should remember that while the Advisory Council was surely empowered >>> to provide advice, and was surely listened to, a Director would have access >>> to more information and definitively better opportunities to discuss >>> different ideas and approaches with his/her fellow Directors, therefore >>> presenting the point of view of the public interest more effectively. >>> In short, this person wold play a role that is similar to the one that >>> León plays in ICANN: committed to the fiduciary responsibility to the >>> corporation but able to be a strong voice to the discussion. >>> I think that we should not be shy, all in remaining reasonable with our >>> proposals. I believe that this one is a win-win, bringing the voice of the >>> user community in PIR and being a good opportunity for Ethos to show a >>> commitment while still remaining in control of PIR. >>> Cheers, >>> Roberto >>> >>> PS: As I am not subscribed to the different mailing lists, please >>> forward this if you see fit >>> >>> >>> On 06.01.2020, at 01:40, Maureen Hilyard <maureen.hilyard(a)gmail.com> >>> wrote: >>> >>> >>> http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… >>> >>> Well that is certainly forcing our hand to take some action. But with >>> arrows flying in all sorts of directions it has been difficult to know >>> which one to follow, and I note there has been a break in the conversations >>> on this topic. >>> >>> Interesting and very timely that Roberto raised the .org issue again in >>> an earlier email today. I started a response until JZ reminded us that the >>> thread was about .com >>> >>> I agree with Roberto's approach - that we should focus on our role as >>> the voice of At-Large end-users and offer some creative advice on how we >>> might influence the behaviour of PIR and any future decisions they make >>> that will impact on .org end-users. PIR/Ethos already presented a webinar >>> and said all the right things.. but how can we be assured that they will >>> stick to what they said that they would do in the future? Who will monitor >>> this on behalf of ordinary end-users? Who will be represented on the >>> Stewardship Council? >>> >>> At the same time we may also need to advise the ICANN Board about how >>> they might deal with the ICANN-PIR/Ethos contract - especially Roberto's >>> recommendation of some commitment from ICANN that ethical behaviour >>> towards .org end-users will be built into it. >>> >>> We are aware that the Board is looking into every legal issue relating >>> to how they can deal with matters that are being raised by letters that are >>> flowing their way. We don't need to add more of the same. >>> >>> While i think it might be seen to be a simplistic approach, I believe >>> that we should stick to what our job is and focus on advice to the Board >>> and to PIR- but lets try to be creative about how we advise them, looking >>> at the impacts on end-users from all perspectives. >>> >>> My 2c >>> M >>> >>> >>> - >>> >>> _______________________________________________ >>> CPWG mailing list >>> CPWG(a)icann.org >>> https://mm.icann.org/mailman/listinfo/cpwg >>> >>> _______________________________________________ >>> By submitting your personal data, you consent to the processing of your >>> personal data for purposes of subscribing to this mailing list accordance >>> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) >>> and the website Terms of Service (https://www.icann.org/privacy/tos) >>> You can visit the Mailman link above to change your membership status or >>> configuration, including unsubscribing, setting digest-style delivery or >>> disabling delivery altogether (e.g., for a vacation), and so on. >>> >>> >>> >> _______________________________________________ >> ALT-Plus mailing listALT-Plus@icann.orghttps://mm.icann.org/mailman/listinfo/alt-plus >> >> _______________________________________________ >> 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. >> >> >> -- >> Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html >> >> _______________________________________________ >> CPWG mailing list >> CPWG(a)icann.org >> https://mm.icann.org/mailman/listinfo/cpwg >> >> _______________________________________________ >> By submitting your personal data, you consent to the processing of your >> personal data for purposes of subscribing to this mailing list accordance >> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and >> the website Terms of Service (https://www.icann.org/privacy/tos) You >> can visit the Mailman link above to change your membership status or >> configuration, including unsubscribing, setting digest-style delivery or >> disabling delivery altogether (e.g., for a vacation), and so on. > >

1 0

Re: [ALAC] [CPWG] [ALT-Plus] PIR and Dot Org
by Cheryl Langdon-Orr Jan. 7, 2020

Jan. 7, 2020

Concur! <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_m…> Cheryl Langdon-Orr about.me/cheryl.LangdonOrr <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_m…> On Tue, 7 Jan 2020 at 12:13, Greg Shatan <greg(a)isoc-ny.org> wrote: > Maureen and all, > > I agree with Roberto, and would perhaps go even further. The best > solution would be to have a voting seat on the PIR board, rather than a > non-voting liaison. I'm not sure which Roberto was suggesting. To my mind, > true "representation" comes with a vote.. > > I also agree with everything Jonathan Zuck said -- about the mission, > about Malthouse, about that "editorial." Nasty stuff. An appropriate > response needs to be considered, but I'm not sure what that might be. It > might be a message from someone else in At Large, pointing out that in a > bottom-up organization, it's not the Chair's job to go flying into battle > on their own impetus. Or maybe it can come from a bunch of somebodies.... > > However, I'm concerned that if ALAC and At-large do not speak for > themselves, the "record" is going to be the garbage that is being thrown at > us. > > There are more important things than a pissing match in the toilet of > public opinion. > > We have ALAC's "superpower" -- the mandate to provide formal advice to the > Board. (Not quite as "super" as GAC advice, but it's what we've got, and > if it is exercised properly, it will grow in strength, like a muscle.) > > Then we can go into toilets with Jacob and Nat.... > > Greg > > > > > Greg Shatan > greg(a)isoc-ny.org > President, ISOC-NY > *"The Internet is for everyone"* > > > On Mon, Jan 6, 2020 at 2:10 PM Olivier MJ Crépin-Leblond <ocl(a)gih.com> > wrote: > >> Dear all, >> >> indeed - the DotMobi Liaison was on the DotMobi Policy Advisory Board. >> But IMHO Roberto's suggestion for a Liaison to the PIR Board sounds good. >> For those interested, DotMobi Liaison Reports can be found on: >> https://community.icann.org/display/atlarge/dotMOBI+Liaison+Reports >> >> Kindest regards, >> >> Olivier >> >> >> On 06/01/2020 11:24, Maureen Hilyard wrote: >> >> Excellent points Roberto. >> Your experience on the PIR Board is invaluable in this regard. and your >> recommendations noted. >> >> Maureen >> >> On Mon, Jan 6, 2020 at 12:02 AM Roberto Gaetano < >> mail.roberto.gaetano(a)gmail.com> wrote: >> >>> Hi Maureen. >>> I have been thinking further about this, and came to the conclusion that >>> our proposal would be not to have a representative on the Stewardship >>> Council but on the PIR Board. >>> Here is the rationale for that. >>> The Stewardship Council will play the role that was previously of the >>> Advisory Council. Its purpose was to get multiple voices from different >>> part of the user community, and in particular the NGOs, ensuring diversity >>> of opinions. This body was advisory to a Board that had already built-in >>> the fundamental non-profit, user-community DNA, because it was selected by >>> ISOC. >>> With the changed situation, we can safely assume that the new PIR Board >>> will be selected by Ethos to take care of the interests of the investors, >>> and there is no guarantee that the public interest is being taken care of. >>> This will be a good option for Ethos as well, because it would show in a >>> concrete way the commitment to the public interest beyond mere verbal >>> expression of intents. On the other hand, Ethos and the investors would >>> keep a solid majority that will ensure that their interests are protected. >>> We should remember that while the Advisory Council was surely empowered >>> to provide advice, and was surely listened to, a Director would have access >>> to more information and definitively better opportunities to discuss >>> different ideas and approaches with his/her fellow Directors, therefore >>> presenting the point of view of the public interest more effectively. >>> In short, this person wold play a role that is similar to the one that >>> León plays in ICANN: committed to the fiduciary responsibility to the >>> corporation but able to be a strong voice to the discussion. >>> I think that we should not be shy, all in remaining reasonable with our >>> proposals. I believe that this one is a win-win, bringing the voice of the >>> user community in PIR and being a good opportunity for Ethos to show a >>> commitment while still remaining in control of PIR. >>> Cheers, >>> Roberto >>> >>> PS: As I am not subscribed to the different mailing lists, please >>> forward this if you see fit >>> >>> >>> On 06.01.2020, at 01:40, Maureen Hilyard <maureen.hilyard(a)gmail.com> >>> wrote: >>> >>> >>> http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… >>> >>> Well that is certainly forcing our hand to take some action. But with >>> arrows flying in all sorts of directions it has been difficult to know >>> which one to follow, and I note there has been a break in the conversations >>> on this topic. >>> >>> Interesting and very timely that Roberto raised the .org issue again in >>> an earlier email today. I started a response until JZ reminded us that the >>> thread was about .com >>> >>> I agree with Roberto's approach - that we should focus on our role as >>> the voice of At-Large end-users and offer some creative advice on how we >>> might influence the behaviour of PIR and any future decisions they make >>> that will impact on .org end-users. PIR/Ethos already presented a webinar >>> and said all the right things.. but how can we be assured that they will >>> stick to what they said that they would do in the future? Who will monitor >>> this on behalf of ordinary end-users? Who will be represented on the >>> Stewardship Council? >>> >>> At the same time we may also need to advise the ICANN Board about how >>> they might deal with the ICANN-PIR/Ethos contract - especially Roberto's >>> recommendation of some commitment from ICANN that ethical behaviour >>> towards .org end-users will be built into it. >>> >>> We are aware that the Board is looking into every legal issue relating >>> to how they can deal with matters that are being raised by letters that are >>> flowing their way. We don't need to add more of the same. >>> >>> While i think it might be seen to be a simplistic approach, I believe >>> that we should stick to what our job is and focus on advice to the Board >>> and to PIR- but lets try to be creative about how we advise them, looking >>> at the impacts on end-users from all perspectives. >>> >>> My 2c >>> M >>> >>> >>> - >>> >>> _______________________________________________ >>> CPWG mailing list >>> CPWG(a)icann.org >>> https://mm.icann.org/mailman/listinfo/cpwg >>> >>> _______________________________________________ >>> By submitting your personal data, you consent to the processing of your >>> personal data for purposes of subscribing to this mailing list accordance >>> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) >>> and the website Terms of Service (https://www.icann.org/privacy/tos) >>> You can visit the Mailman link above to change your membership status or >>> configuration, including unsubscribing, setting digest-style delivery or >>> disabling delivery altogether (e.g., for a vacation), and so on. >>> >>> >>> >> _______________________________________________ >> ALT-Plus mailing listALT-Plus@icann.orghttps://mm.icann.org/mailman/listinfo/alt-plus >> >> _______________________________________________ >> 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. >> >> >> -- >> Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html >> >> _______________________________________________ >> CPWG mailing list >> CPWG(a)icann.org >> https://mm.icann.org/mailman/listinfo/cpwg >> >> _______________________________________________ >> By submitting your personal data, you consent to the processing of your >> personal data for purposes of subscribing to this mailing list accordance >> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and >> the website Terms of Service (https://www.icann.org/privacy/tos) You >> can visit the Mailman link above to change your membership status or >> configuration, including unsubscribing, setting digest-style delivery or >> disabling delivery altogether (e.g., for a vacation), and so on. > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Re: [ALAC] [ALAC-Members] [CPWG] PIR and Dot Org
by Matthias M. Hudobnik Jan. 6, 2020

Jan. 6, 2020

Dear all, @Roberto, thank you very much for the very interesting insights and thoughts from an old dinosaurs J. This sounds like a valuable plan from a strategic point of view! Have a nice evening! Best, Matthias _________________________ Ing. Mag. Matthias M. Hudobnik HYPERLINK "mailto:matthias@hudobnik.at"matthias(a)hudobnik.at HYPERLINK "http://www.hudobnik.at/"http://www.hudobnik.at Von: ALAC-Members [mailto:alac-members-bounces@icann.org] Im Auftrag von Roberto Gaetano Gesendet: Montag, 06. Jänner 2020 11:02 An: Maureen Hilyard Cc: ICANN ALAC list; ALAC Members; CPWG; ALT-Plus Betreff: Re: [ALAC-Members] [CPWG] PIR and Dot Org Hi Maureen. I have been thinking further about this, and came to the conclusion that our proposal would be not to have a representative on the Stewardship Council but on the PIR Board. Here is the rationale for that. The Stewardship Council will play the role that was previously of the Advisory Council. Its purpose was to get multiple voices from different part of the user community, and in particular the NGOs, ensuring diversity of opinions. This body was advisory to a Board that had already built-in the fundamental non-profit, user-community DNA, because it was selected by ISOC. With the changed situation, we can safely assume that the new PIR Board will be selected by Ethos to take care of the interests of the investors, and there is no guarantee that the public interest is being taken care of. This will be a good option for Ethos as well, because it would show in a concrete way the commitment to the public interest beyond mere verbal expression of intents. On the other hand, Ethos and the investors would keep a solid majority that will ensure that their interests are protected. We should remember that while the Advisory Council was surely empowered to provide advice, and was surely listened to, a Director would have access to more information and definitively better opportunities to discuss different ideas and approaches with his/her fellow Directors, therefore presenting the point of view of the public interest more effectively. In short, this person wold play a role that is similar to the one that León plays in ICANN: committed to the fiduciary responsibility to the corporation but able to be a strong voice to the discussion. I think that we should not be shy, all in remaining reasonable with our proposals. I believe that this one is a win-win, bringing the voice of the user community in PIR and being a good opportunity for Ethos to show a commitment while still remaining in control of PIR. Cheers, Roberto PS: As I am not subscribed to the different mailing lists, please forward this if you see fit On 06.01.2020, at 01:40, Maureen Hilyard <HYPERLINK "mailto:maureen.hilyard@gmail.com"maureen.hilyard(a)gmail.com> wrote: http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… Well that is certainly forcing our hand to take some action. But with arrows flying in all sorts of directions it has been difficult to know which one to follow, and I note there has been a break in the conversations on this topic. Interesting and very timely that Roberto raised the .org issue again in an earlier email today. I started a response until JZ reminded us that the thread was about .com I agree with Roberto's approach - that we should focus on our role as the voice of At-Large end-users and offer some creative advice on how we might influence the behaviour of PIR and any future decisions they make that will impact on .org end-users. PIR/Ethos already presented a webinar and said all the right things.. but how can we be assured that they will stick to what they said that they would do in the future? Who will monitor this on behalf of ordinary end-users? Who will be represented on the Stewardship Council? At the same time we may also need to advise the ICANN Board about how they might deal with the ICANN-PIR/Ethos contract - especially Roberto's recommendation of some commitment from ICANN that ethical behaviour towards .org end-users will be built into it. We are aware that the Board is looking into every legal issue relating to how they can deal with matters that are being raised by letters that are flowing their way. We don't need to add more of the same. While i think it might be seen to be a simplistic approach, I believe that we should stick to what our job is and focus on advice to the Board and to PIR- but lets try to be creative about how we advise them, looking at the impacts on end-users from all perspectives. My 2c M · _______________________________________________ CPWG mailing list HYPERLINK "mailto:CPWG@icann.org"CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Re: [ALAC] [CPWG] PIR and Dot Org
by Maureen Hilyard Jan. 6, 2020

Jan. 6, 2020

Excellent points Roberto. Your experience on the PIR Board is invaluable in this regard. and your recommendations noted. Maureen On Mon, Jan 6, 2020 at 12:02 AM Roberto Gaetano < mail.roberto.gaetano(a)gmail.com> wrote: > Hi Maureen. > I have been thinking further about this, and came to the conclusion that > our proposal would be not to have a representative on the Stewardship > Council but on the PIR Board. > Here is the rationale for that. > The Stewardship Council will play the role that was previously of the > Advisory Council. Its purpose was to get multiple voices from different > part of the user community, and in particular the NGOs, ensuring diversity > of opinions. This body was advisory to a Board that had already built-in > the fundamental non-profit, user-community DNA, because it was selected by > ISOC. > With the changed situation, we can safely assume that the new PIR Board > will be selected by Ethos to take care of the interests of the investors, > and there is no guarantee that the public interest is being taken care of. > This will be a good option for Ethos as well, because it would show in a > concrete way the commitment to the public interest beyond mere verbal > expression of intents. On the other hand, Ethos and the investors would > keep a solid majority that will ensure that their interests are protected. > We should remember that while the Advisory Council was surely empowered to > provide advice, and was surely listened to, a Director would have access to > more information and definitively better opportunities to discuss different > ideas and approaches with his/her fellow Directors, therefore presenting > the point of view of the public interest more effectively. > In short, this person wold play a role that is similar to the one that > León plays in ICANN: committed to the fiduciary responsibility to the > corporation but able to be a strong voice to the discussion. > I think that we should not be shy, all in remaining reasonable with our > proposals. I believe that this one is a win-win, bringing the voice of the > user community in PIR and being a good opportunity for Ethos to show a > commitment while still remaining in control of PIR. > Cheers, > Roberto > > PS: As I am not subscribed to the different mailing lists, please forward > this if you see fit > > > On 06.01.2020, at 01:40, Maureen Hilyard <maureen.hilyard(a)gmail.com> > wrote: > > > http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… > > Well that is certainly forcing our hand to take some action. But with > arrows flying in all sorts of directions it has been difficult to know > which one to follow, and I note there has been a break in the conversations > on this topic. > > Interesting and very timely that Roberto raised the .org issue again in an > earlier email today. I started a response until JZ reminded us that the > thread was about .com > > I agree with Roberto's approach - that we should focus on our role as the > voice of At-Large end-users and offer some creative advice on how we might > influence the behaviour of PIR and any future decisions they make that will > impact on .org end-users. PIR/Ethos already presented a webinar and said > all the right things.. but how can we be assured that they will stick to > what they said that they would do in the future? Who will monitor this on > behalf of ordinary end-users? Who will be represented on the Stewardship > Council? > > At the same time we may also need to advise the ICANN Board about how they > might deal with the ICANN-PIR/Ethos contract - especially Roberto's > recommendation of some commitment from ICANN that ethical behaviour > towards .org end-users will be built into it. > > We are aware that the Board is looking into every legal issue relating to > how they can deal with matters that are being raised by letters that are > flowing their way. We don't need to add more of the same. > > While i think it might be seen to be a simplistic approach, I believe that > we should stick to what our job is and focus on advice to the Board and to > PIR- but lets try to be creative about how we advise them, looking at the > impacts on end-users from all perspectives. > > My 2c > M > > > - > > _______________________________________________ > CPWG mailing list > CPWG(a)icann.org > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on. > > >

4 3

Fwd: [ICANN Community Leaders] 6 January 2020
by Maureen Hilyard Jan. 6, 2020

Jan. 6, 2020

Monday, 6 January 2020 ICANN Community Leadership Digest The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing - NEW: ATRT3 Draft Report Webinar - REMINDER: Webinars on Two Key ICANN Plans - REMINDER: FY21 SO/AC Additional Budget Request Process - REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning - REMINDER: ICANN67 Publication Support - REMINDER: CROP Deadline for ICANN67 - REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Public Comment - Proposal for Future Root Zone KSK Rollovers - Third Accountability and Transparency Review Team (ATRT3) Draft Report - NEW: Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 - NEW: Proposed Amendment 3 to the .COM Registry Agreement - Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group - Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget Information Sharing NEW: ATRT3 Draft Report Webinar Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives INFORMATION SHARING The Third Accountability and Transparency Review Team (ATRT3) invites the community to participate in a webinar on its draft report. There are two options to participate: - Monday, 13 January 2020 at 20:00 UTC - Tuesday, 14 January 2020 at 12:00 UTC More information about the webinar and how to participate is available here <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…>. REMINDER: Webinars on Two Key ICANN Plans ICANN org Announcement <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> INFORMATION SHARING The Public Comment proceeding for the Draft FY21-FY25 Operating and Financial Plan and Draft FY21 Operating Plan and Budget is now open. In addition, the Public Comment proceeding has been extended by seven days to 58 days (excluding holidays) to give the community more time to review the documents. To learn more and ask questions during the Public Comment window, webinars will be held on: - Thursday, 9 January 2020 at 01:00 UTC https://icann.zoom.us/j/935036343 <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> - Thursday, 9 January 2020 at 16:00 UTC https://icann.zoom.us/j/506858960 <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> - Monday, 14 January 2020 at 16:00 UTC https://icann.zoom.us/j/257109807 <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> ICANN org staff is available to meet with individual community groups to answer questions and help increase understanding about the plans. Please email planning(a)icann.org to request a meeting. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer INFORMATION SHARING The Fiscal Year 2021 (FY21) Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY21 SO/AC Additional Budget Request process, including timeline and request template can be found on the Finance community wiki <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…>. Additional Budget Requests are due Friday, 31 January 2020. Please email any questions that you may have to planning(a)icann.org. We look forward to your continued engagement on the SO/AC Additional Budget Request process for FY21. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> . SOs/ACs should first select their respective Fellowship Program mentor by Friday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning REMINDER: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials required design assistance, please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives INFORMATION SHARING ICANN org will hold Strategic Outlook Trends Identification sessions with the community at ICANN67. To prepare for that exercise, ICANN org will be seeking community feedback on possible formats and arrangements which will be sent through each community group’s leadership. The Strategic Outlook program <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> is a joint effort among ICANN org, the community, and ICANN Board to identify and track trends that relate to ICANN and its mission and to make sure that relating opportunities and challenges are incorporated into ICANN's current and future strategy. New trends or shifts in existing trends impacting the operating plans (five-year or annual), and/or budget, will be factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. Public Comment Proposal for Future Root Zone KSK Rollover <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> Close Date: Friday, 31 January 2020 Third Accountability and Transparency Review Team (ATRT3) Draft Report <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> Close Date: Friday, 31 January 2020 NEW: Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022 <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> Close Date: Tuesday, 11 February 2020 NEW: Proposed Amendment 3 to the .COM Registry Agreement <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> Close Date: Friday, 14 February 2020 Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> Close Date: Friday, 14 February 2020 Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> Close Date: Tuesday, 25 February 2020 Volume 2, Issue 2 | Archive <http://r20.rs6.net/tn.jsp?f=001B0qfx7ii3zI2t9PntvoGX5Z5DnrtQk19dk5-zVDHbQjw…> | Next Issue: Thursday, 9 January 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> | About Constant Contact <http://www.constantcontact.com/legal/about-constant-contact> Sent by david.olive(a)icann.org in collaboration with [image: Trusted Email from Constant Contact - Try it FREE today.] <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> Try email marketing for free today! <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> _______________________________________________ SO-AC-SG-CLeaders mailing list SO-AC-SG-CLeaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders _______________________________________________ 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.

1 0

PIR and Dot Org
by Maureen Hilyard Jan. 6, 2020

Jan. 6, 2020

http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… Well that is certainly forcing our hand to take some action. But with arrows flying in all sorts of directions it has been difficult to know which one to follow, and I note there has been a break in the conversations on this topic. Interesting and very timely that Roberto raised the .org issue again in an earlier email today. I started a response until JZ reminded us that the thread was about .com I agree with Roberto's approach - that we should focus on our role as the voice of At-Large end-users and offer some creative advice on how we might influence the behaviour of PIR and any future decisions they make that will impact on .org end-users. PIR/Ethos already presented a webinar and said all the right things.. but how can we be assured that they will stick to what they said that they would do in the future? Who will monitor this on behalf of ordinary end-users? Who will be represented on the Stewardship Council? At the same time we may also need to advise the ICANN Board about how they might deal with the ICANN-PIR/Ethos contract - especially Roberto's recommendation of some commitment from ICANN that ethical behaviour towards .org end-users will be built into it. We are aware that the Board is looking into every legal issue relating to how they can deal with matters that are being raised by letters that are flowing their way. We don't need to add more of the same. While i think it might be seen to be a simplistic approach, I believe that we should stick to what our job is and focus on advice to the Board and to PIR- but lets try to be creative about how we advise them, looking at the impacts on end-users from all perspectives. My 2c M -

5 5

Re: [ALAC] [CPWG] PIR and Dot Org
by Alan Greenberg Jan. 6, 2020

Jan. 6, 2020

In my view, Jacob has always had a problem understanding what ICANN and particularly At-Large is about. Way back in 2007, Jacob was on ICANN staff and was recruiting ALSes into At-Large. Here is an extract from a much longer 2007 e-mail. The first line quoted is from Jean Armor Polly (who was just recently inducted into the Internet Hall of Fame, and then a just-departed ALAC member). The 2nd is from Jacob. >> You need to know that ICANN has a very narrow, rather geeky, mission. I thought that ICANN's mission was what the Internet Community wants it to be. I also think people need to move beyond discouraging participation on the basis of a restricted mission. I won't quote the response (from John Levine, also a just departed ALAC member) quoting the Bylaws and pointing out that we CANNOT make the mission whatever we want it to be. In this case, I believe he has strongly mis-characterized what At-Large is about. Alan At 05/01/2020 09:58 PM, Jonathan Zuck wrote: Thanks Maureen. Jacob has quickly fallen into the clutches of Godwin's Law. Reductio ad Nazium. The At-Large mandate is specifically NOT to represent organizations but instead individual end users. There is, in fact, an entity within the ICANN community which DOES represent the interests of not for profit organizations, NPOC. I had a long and involved conversation with Jacob, at Evan's behest and was coming around to some of his points and and we concluded he would make other introductions. Comparing us sticking to our remit to being antisemitic is beyond the pale! We need to find our own way on this, with a focus on individual end users, and perhaps some concerns over organizational practices, but we owe SAVEDOTORG absolutely nothing and, after that op-ed, we should tell them to go to Hell. Just my two cents. Jonathan Zuck Executive Director Innovators Network Foundation www.Innovatorsnetwork.org<http://www.Innovatorsnetwork.org> ________________________________ From: ALAC <alac-bounces(a)atlarge-lists.icann.org> on behalf of Olivier MJ Crepin-Leblond <ocl(a)gih.com> Sent: Sunday, January 5, 2020, 8:53 PM To: Maureen Hilyard Cc: ALAC; ALAC Members; CPWG; ALT-Plus Subject: Re: [ALAC] [CPWG] PIR and Dot Org Dear Maureen, Just a thought, historically, when the DotMobi TLD was created, a formal DotMobi liaison with At-Large was mandated. Others will have details. Best wishes, Olivier Sent from my iPad On 6 Jan 2020, at 01:40, Maureen Hilyard < maureen.hilyard(a)gmail.com<mailto:maureen.hilyard@gmail.com>> wrote: http://www.circleid.com/posts/20200105_hilyard_has_a_historic_chance_to_act… Well that is certainly forcing our hand to take some action. But with arrows flying in all sorts of directions it has been difficult to know which one to follow, and I note there has been a break in the conversations on this topic. Interesting and very timely that Roberto raised the .org issue again in an earlier email today. I started a response until JZ reminded us that the thread was about .com I agree with Roberto's approach - that we should focus on our role as the voice of At-Large end-users and offer some creative advice on how we might influence the behaviour of PIR and any future decisions they make that will impact on .org end-users. PIR/Ethos already presented a webinar and said all the right things.. but how can we be assured that they will stick to what they said that they would do in the future? Who will monitor this on behalf of ordinary end-users? Who will be represented on the Stewardship Council? At the same time we may also need to advise the ICANN Board about how they might deal with the ICANN-PIR/Ethos contract - especially Roberto's recommendation of some commitment from ICANN that ethical behaviour towards .org end-users will be built into it. We are aware that the Board is looking into every legal issue relating to how they can deal with matters that are being raised by letters that are flowing their way. We don't need to add more of the same. While i think it might be seen to be a simplistic approach, I believe that we should stick to what our job is and focus on advice to the Board and to PIR- but lets try to be creative about how we advise them, looking at the impacts on end-users from all perspectives. My 2c M _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ( https://www.icann.org/privacy/policy) and the website Terms of Service ( https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ CPWG mailing list CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ( https://www.icann.org/privacy/policy) and the website Terms of Service ( https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Fwd: [ICANN Community Leaders] 2 January 2020
by Maureen Hilyard Jan. 2, 2020

Jan. 2, 2020

Happy New Year to At-Large Community Leaders! Thursday, 2 January 2020 ICANN Community Leadership Digest The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents Information Sharing - NEW: CSC Findings on PTI Performance for November 2019 - REMINDER: Revised Schedule for Public Comment on Two Key ICANN Plans - REMINDER: FY21 SO/AC Additional Budget Request Process - REMINDER: ICANN Fellowship Program Mentors ICANN67 Planning - DESIGN DEADLINE TOMORROW: ICANN67 Publication Support - REMINDER: CROP Deadline for ICANN67 - REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Public Comment - Proposal for Future Root Zone KSK Rollovers - Third Accountability and Transparency Review Team (ATRT3) Draft Report - NEW: Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group - NEW: Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget Information Sharing NEW: CSC Findings on PTI Performance for November 2019 From: Lars-Johan Liman, CSC Chair INFORMATION SHARING As chair of the Customer Standing Committee (CSC), I am providing you with our latest monthly findings on the performance of Public Technical Identifiers (PTI) over November 2019. I am pleased to inform you that the CSC has concluded that PTI’s overall performance over November 2019 was “Excellent” - PTI met 100% of the service level agreements over the month of November 2019. The related PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found here <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> . I am also very pleased to provide you an update on the two outstanding Service Level Agreement (SLA) changes: 1. In accordance with the SLA change procedure, the CSC was informed that PTI has completed implementation of the new SLA on processing times for Internationalized Domain Name Tables and is now recording data accordingly. The performance against this new SLA will be presented in the report over December 2019 and presented to the CSC at its January meeting. 2. With respect to the second SLA listed in the CSC Findings Report, the Country Code Top-Level Domain Creation/Transfer – Validation and Reviews: SLA Amendments, the CSC was informed that based on Public Comment there is no need to adjust the proposed SLA. In accordance with the SLA change process <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…>, PTI and CSC will now have to formally agree on the new SLA and then CSC will request the Councils of the Country Code Names Supporting Organization and Generic Names Supporting Organization to approve the changes. Both SLA changes are explained in more detail in the October 2019 CSC Findings Report. BACKGROUND Generally, the CSC regular meeting is scheduled on or around the 15th every month, and the CSC Findings Report on the PTI performance is sent out shortly after that meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…>. We welcome any comments on our reporting to you. The CSC became effective 1 October 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found here <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> . REMINDER: Revised Schedule for Public Comment on Two Key ICANN Plans ICANN org Announcement <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> INFORMATION SHARING The Public Comment proceeding for the Draft FY21-FY25 Operating and Financial Plan and Draft FY21 Operating Plan and Budget has changed. Originally scheduled for Tuesday, 17 December 2019, drafts of the two plans will now be available beginning Friday, 20 December 2019. This date change may impact previously scheduled meetings intended for the Supporting Organizations and Advisory Committees to begin their review. ICANN org is prepared to provide those groups with the table of contents of the documents and other information that may be helpful prior to the release of the complete drafts. Please email planning(a)icann.org to request. Information also will be published on the Finance community wiki page <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> . In addition, the Public Comment proceeding has been extended by 7 days to 58 days (excluding holidays) to give the community more time to review the documents. To learn more and ask questions during the Public Comment window, webinars will be held on: - Thursday, 9 January 2020 at 01:00 UTC https://icann.zoom.us/j/935036343 <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> - Thursday, 9 January 2020 at 16:00 UTC https://icann.zoom.us/j/506858960 <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> - Monday, 14 January 2020 at 16:00 UTC https://icann.zoom.us/j/257109807 <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> More details about how to join these webinars will be available in January. ICANN org staff is available to meet with individual community groups to answer questions and help increase understanding about the plans. Please email planning(a)icann.org to request a meeting. REMINDER: FY21 SO/AC Additional Budget Request Process Executive: Xavier Calvez, Chief Financial Officer INFORMATION SHARING The Fiscal Year 2021 (FY21) Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY21 SO/AC Additional Budget Request process, including timeline and request template can be found on the Finance community wiki <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…>. Additional Budget Requests are due Friday, 31 January 2020. Please email any questions that you may have to planning(a)icann.org. We look forward to your continued engagement on the SO/AC Additional Budget Request process for FY21. REMINDER: ICANN Fellowship Program Mentors From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement INFORMATION SHARING ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> one individual each (total of seven) to serve as a mentor in the ICANN Fellowship Program. Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN68. They will provide extensive pre-meeting preparation and on-site support for their assigned fellows, as well as complete a survey after each meeting. Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows. They also play an important role to help fellows actively participate in ICANN's work. Mentors will receive travel funding support. Mentors cannot serve on the Fellowship Program Selection Committee <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> at the same time they are serving as mentors. For more information on the guidelines and expectations for mentors, please read about the program here <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> . SOs/ACs should first select their respective Fellowship Program mentor by Friday, 31 January 2020, and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. ICANN67 Planning DESIGN DEADLINE TOMORROW: ICANN67 Publication Support From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING TOMORROW: Design Deadline If you require design assistance for an ICANN67 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 3 January 2020. Please ensure that all materials, new or updated, are evergreen. Translation Deadline If your ICANN67 publication requires translation, please provide the final material(s) by Monday, 27 January 2020. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN67 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 7 February 2020. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. REMINDER: CROP Deadline for ICANN67 From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN67, requests must be submitted no later than Friday, 17 January 2020. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: Trip requests must be approved by the respective community leadership team. For FY20, the trip request must be filled in by the CROP participant via the CROP workspace <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…>. In order to access it, applicants must first have an account; please let the CROP coordinator know if you need an account. All individuals requesting CROP funding must also review the CROP Guidelines <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> prior to submitting a request. Please contact crop-staff(a)icann.org with any questions. REMINDER: Opportunity for Strategic Outlook Trends Identification Sessions at ICANN67 Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives INFORMATION SHARING ICANN org will hold Strategic Outlook Trends Identification sessions with the community at ICANN67. To prepare for that exercise, ICANN org will be seeking community feedback on possible formats and arrangements which will be sent through each community group’s leadership. The Strategic Outlook program <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> is a joint effort among ICANN org, the community, and ICANN Board to identify and track trends that relate to ICANN and its mission and to make sure that relating opportunities and challenges are incorporated into ICANN's current and future strategy. New trends or shifts in existing trends impacting the operating plans (five-year or annual), and/or budget, will be factored into the annual iteration of those plans as appropriate. Significant shifts could also result in adjustments to the strategic plan. Public Comment Proposal for Future Root Zone KSK Rollover <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> Close Date: Friday, 31 January 2020 Third Accountability and Transparency Review Team (ATRT3) Draft Report <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> Close Date: Friday, 31 January 2020 NEW: Proposed Final Report of the New gTLD Auction Proceeds Cross-Community Working Group <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> Close Date: Friday, 14 February 2020 NEW: Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> Close Date: Tuesday, 25 February 2020 Volume 2, Issue 1 | Archive <http://r20.rs6.net/tn.jsp?f=001xZcAZ_eRl75CfC8Z2C7s9qeF8eqSvYJswvpqy67cJGr4…> | Next Issue: Monday, 6 January 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> | About Constant Contact <http://www.constantcontact.com/legal/about-constant-contact> Sent by david.olive(a)icann.org in collaboration with [image: Trusted Email from Constant Contact - Try it FREE today.] <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> Try email marketing for free today! <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> _______________________________________________ SO-AC-SG-CLeaders mailing list SO-AC-SG-CLeaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders _______________________________________________ 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.

1 0