Board process for GAC Advice
It seems that Board decided to detail how they plan to handle GAC advice: https://www.icann.org/en/system/files/files/gac-advice-process-handbook-06ma... <https://www.icann.org/en/system/files/files/gac-advice-process-handbook-06ma...> As another registry mentioned, "Curious how there is nothing in the new process about consulting the rest of the community if the GAC Advice overlaps with, is inconsistent with, or otherwise also falls into the jurisdiction of, other SOs or ACs." That lacks, for instance, the usual comments from GNSO regarding advice overlapping with GNSO Policy, either existent or in the pipeline. Do we want to make a GNSO Council comment ? Or perhaps including other SOs and ACs ? Rubens
Thank you, Rubens. I wasn't aware of this- anyone else? If you all agree, I think this would be a worthwhile thing to raise when I meet with the other SOAC chairs tomorrow. Best wishes, Heather On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br> wrote:
It seems that Board decided to detail how they plan to handle GAC advice: https://www.icann.org/en/system/files/files/gac-advice- process-handbook-06mar18-en.pdf
As another registry mentioned, "Curious how there is nothing in the new process about consulting the rest of the community if the GAC Advice overlaps with, is inconsistent with, or otherwise also falls into the jurisdiction of, other SOs or ACs." That lacks, for instance, the usual comments from GNSO regarding advice overlapping with GNSO Policy, either existent or in the pipeline.
Do we want to make a GNSO Council comment ? Or perhaps including other SOs and ACs ?
Rubens
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
I think we should consider both Heather! I think Rubens first suggestion on a GNSO comment, in view of the new early engagement of the GAC in the GNSO process, is valid on its own for GNSO derived policies. Even if its only for future cases, the Board should consider in its evaluation phase if a GNSO policy issue has already been discussed between GAC and the GNSO in previous stages. Then, of course, your suggestion to ask other SO/ACs should be pursued ASAP. Safe travels to all Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest <haforrestesq@gmail.com> wrote:
Thank you, Rubens. I wasn't aware of this- anyone else?
If you all agree, I think this would be a worthwhile thing to raise when I meet with the other SOAC chairs tomorrow.
Best wishes, Heather On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br> wrote:
It seems that Board decided to detail how they plan to handle GAC advice: https://www.icann.org/en/system/files/files/gac-advice-proce ss-handbook-06mar18-en.pdf
As another registry mentioned, "Curious how there is nothing in the new process about consulting the rest of the community if the GAC Advice overlaps with, is inconsistent with, or otherwise also falls into the jurisdiction of, other SOs or ACs." That lacks, for instance, the usual comments from GNSO regarding advice overlapping with GNSO Policy, either existent or in the pipeline.
Do we want to make a GNSO Council comment ? Or perhaps including other SOs and ACs ?
Rubens
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Heather - I agree with Rubens and Carlos. Cheers, Erika Sent from my iPhone
On Mar 8, 2018, at 5:03 PM, Carlos Raul Gutierrez <crg@isoc-cr.org> wrote:
I think we should consider both Heather!
I think Rubens first suggestion on a GNSO comment, in view of the new early engagement of the GAC in the GNSO process, is valid on its own for GNSO derived policies. Even if its only for future cases, the Board should consider in its evaluation phase if a GNSO policy issue has already been discussed between GAC and the GNSO in previous stages.
Then, of course, your suggestion to ask other SO/ACs should be pursued ASAP.
Safe travels to all
Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA
On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest <haforrestesq@gmail.com> wrote: Thank you, Rubens. I wasn't aware of this- anyone else?
If you all agree, I think this would be a worthwhile thing to raise when I meet with the other SOAC chairs tomorrow.
Best wishes, Heather
On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br> wrote:
It seems that Board decided to detail how they plan to handle GAC advice: https://www.icann.org/en/system/files/files/gac-advice-process-handbook-06ma...
As another registry mentioned, "Curious how there is nothing in the new process about consulting the rest of the community if the GAC Advice overlaps with, is inconsistent with, or otherwise also falls into the jurisdiction of, other SOs or ACs." That lacks, for instance, the usual comments from GNSO regarding advice overlapping with GNSO Policy, either existent or in the pipeline.
Do we want to make a GNSO Council comment ? Or perhaps including other SOs and ACs ?
Rubens
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Likewise! Julf On 08-03-18 23:58, Erika Mann wrote:
Heather - I agree with Rubens and Carlos. Cheers, Erika
Sent from my iPhone
On Mar 8, 2018, at 5:03 PM, Carlos Raul Gutierrez <crg@isoc-cr.org <mailto:crg@isoc-cr.org>> wrote:
I think we should consider both Heather!
I think Rubens first suggestion on a GNSO comment, in view of the new early engagement of the GAC in the GNSO process, is valid on its own for GNSO derived policies. Even if its only for future cases, the Board should consider in its evaluation phase if a GNSO policy issue has already been discussed between GAC and the GNSO in previous stages.
Then, of course, your suggestion to ask other SO/ACs should be pursued ASAP.
Safe travels to all
Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA
On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest <haforrestesq@gmail.com <mailto:haforrestesq@gmail.com>> wrote:
Thank you, Rubens. I wasn't aware of this- anyone else?
If you all agree, I think this would be a worthwhile thing to raise when I meet with the other SOAC chairs tomorrow.
Best wishes, Heather
On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br <mailto:rubensk@nic.br>> wrote:
It seems that Board decided to detail how they plan to handle GAC advice: https://www.icann.org/en/system/files/files/gac-advice-process-handbook-06ma... <https://www.icann.org/en/system/files/files/gac-advice-process-handbook-06ma...>
As another registry mentioned, "Curious how there is nothing in the new process about consulting the rest of the community if the GAC Advice overlaps with, is inconsistent with, or otherwise also falls into the jurisdiction of, other SOs or ACs." That lacks, for instance, the usual comments from GNSO regarding advice overlapping with GNSO Policy, either existent or in the pipeline.
Do we want to make a GNSO Council comment ? Or perhaps including other SOs and ACs ?
Rubens
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <https://mm.icann.org/mailman/listinfo/council>
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <https://mm.icann.org/mailman/listinfo/council>
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Julf, all It's unclear to me who owns or who drafted this document. Is it the Board, the GAC, ICANN? Is it possible for you to follow up with your GAC counterpart to see if you can get more clarity around the intent of the document and where it came from. I suspect it is the result of a number of consultations whether they be internal to just the GAC or perhaps the result of the Board/GAC Working Group. Before we all go jumping at shadows it would be good to have the context and understand where this came from, its purpose and intended audience. Thanks Donna -----Original Message----- From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Johan Helsingius Sent: Thursday, March 08, 2018 9:03 PM To: council@gnso.icann.org Subject: [EXTERNAL] Re: [council] Board process for GAC Advice Likewise! Julf On 08-03-18 23:58, Erika Mann wrote:
Heather - I agree with Rubens and Carlos. Cheers, Erika
Sent from my iPhone
On Mar 8, 2018, at 5:03 PM, Carlos Raul Gutierrez <crg@isoc-cr.org <mailto:crg@isoc-cr.org>> wrote:
I think we should consider both Heather!
I think Rubens first suggestion on a GNSO comment, in view of the new early engagement of the GAC in the GNSO process, is valid on its own for GNSO derived policies. Even if its only for future cases, the Board should consider in its evaluation phase if a GNSO policy issue has already been discussed between GAC and the GNSO in previous stages.
Then, of course, your suggestion to ask other SO/ACs should be pursued ASAP.
Safe travels to all
Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA
On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest <haforrestesq@gmail.com <mailto:haforrestesq@gmail.com>> wrote:
Thank you, Rubens. I wasn't aware of this- anyone else?
If you all agree, I think this would be a worthwhile thing to raise when I meet with the other SOAC chairs tomorrow.
Best wishes, Heather
On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br <mailto:rubensk@nic.br>> wrote:
It seems that Board decided to detail how they plan to handle GAC advice: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system...
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_e n_system_files_files_gac-2Dadvice-2Dprocess-2Dhandbook-2D06mar18-2Den .pdf&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4y C5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6IyOf4Y&s=Xas05 X2yr3O703La8H8MqiQhHG8kWoPxOU_Kp8WEFCc&e=>
As another registry mentioned, "Curious how there is nothing in the new process about consulting the rest of the community if the GAC Advice overlaps with, is inconsistent with, or otherwise also falls into the jurisdiction of, other SOs or ACs." That lacks, for instance, the usual comments from GNSO regarding advice overlapping with GNSO Policy, either existent or in the pipeline.
Do we want to make a GNSO Council comment ? Or perhaps including other SOs and ACs ?
Rubens
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li...
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_ma ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6 EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzg yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=>
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li...
<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_ma ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6 EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzg yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=>
_______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mai lman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6E kpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgy ZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
_______________________________________________ council mailing list council@gnso.icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mail man_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6Ekp FXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6 IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
_______________________________________________ council mailing list council@gnso.icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li...
Donna, all, Please note that the handbook that has been referenced is part of the Process Mapping work, described at https://www.icann.org/processdocumentation. It is not an adopted process, but an attempt to describe in plain English the process set out in the diagram, available at https://www.icann.org/en/system/files/files/gac-advice-process-flowchart-31a.... If there are items missing from these diagrams, such as the potential for impasse if GAC advice is in conflict with a policy recommendation, or to demonstrate an opportunity for consideration of additional inputs such as the GNSO’s recent work on producing responses to GAC advice, the diagram and handbook can be updated. They are considered living documents, and though staff has tried hard to get them as right as possible and integrate community input, they don’t capture every nuance. I hope this is helpful. Best regards, Marika On 3/9/18, 12:46, "council on behalf of Austin, Donna via council" <council-bounces@gnso.icann.org on behalf of council@gnso.icann.org> wrote: Julf, all It's unclear to me who owns or who drafted this document. Is it the Board, the GAC, ICANN? Is it possible for you to follow up with your GAC counterpart to see if you can get more clarity around the intent of the document and where it came from. I suspect it is the result of a number of consultations whether they be internal to just the GAC or perhaps the result of the Board/GAC Working Group. Before we all go jumping at shadows it would be good to have the context and understand where this came from, its purpose and intended audience. Thanks Donna -----Original Message----- From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Johan Helsingius Sent: Thursday, March 08, 2018 9:03 PM To: council@gnso.icann.org Subject: [EXTERNAL] Re: [council] Board process for GAC Advice Likewise! Julf On 08-03-18 23:58, Erika Mann wrote: > Heather - I agree with Rubens and Carlos. Cheers, Erika > > > Sent from my iPhone > > On Mar 8, 2018, at 5:03 PM, Carlos Raul Gutierrez <crg@isoc-cr.org > <mailto:crg@isoc-cr.org>> wrote: > >> I think we should consider both Heather! >> >> I think Rubens first suggestion on a GNSO comment, in view of the new >> early engagement of the GAC in the GNSO process, is valid on its own >> for GNSO derived policies. Even if its only for future cases, the >> Board should consider in its evaluation phase if a GNSO policy issue >> has already been discussed between GAC and the GNSO in previous stages. >> >> Then, of course, your suggestion to ask other SO/ACs should be >> pursued ASAP. >> >> Safe travels to all >> >> Carlos Raúl Gutiérrez >> ISOC Costa Rica Chapter >> skype carlos.raulg >> +506 8837 7176 >> ________ >> Apartado 1571-1000 >> COSTA RICA >> >> On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest >> <haforrestesq@gmail.com <mailto:haforrestesq@gmail.com>> wrote: >> >> Thank you, Rubens. I wasn't aware of this- anyone else? >> >> If you all agree, I think this would be a worthwhile thing to >> raise when I meet with the other SOAC chairs tomorrow. >> >> Best wishes, >> Heather >> >> On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br >> <mailto:rubensk@nic.br>> wrote: >> >> >> It seems that Board decided to detail how they plan to handle >> GAC advice: >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system... >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_e >> n_system_files_files_gac-2Dadvice-2Dprocess-2Dhandbook-2D06mar18-2Den >> .pdf&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4y >> C5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6IyOf4Y&s=Xas05 >> X2yr3O703La8H8MqiQhHG8kWoPxOU_Kp8WEFCc&e=> >> >> As another registry mentioned, "Curious how there is nothing >> in the new process about consulting the rest of the community >> if the GAC Advice overlaps with, is inconsistent with, or >> otherwise also falls into the jurisdiction of, other SOs or ACs." >> That lacks, for instance, the usual comments from GNSO >> regarding advice overlapping with GNSO Policy, either existent >> or in the pipeline. >> >> Do we want to make a GNSO Council comment ? Or perhaps >> including other SOs and ACs ? >> >> >> Rubens >> >> >> >> _______________________________________________ >> council mailing list >> council@gnso.icann.org <mailto:council@gnso.icann.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_ma >> ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6 >> EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzg >> yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=> >> >> >> _______________________________________________ >> council mailing list >> council@gnso.icann.org <mailto:council@gnso.icann.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_ma >> ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6 >> EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzg >> yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=> >> >> >> _______________________________________________ >> council mailing list >> council@gnso.icann.org <mailto:council@gnso.icann.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mai >> lman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6E >> kpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgy >> ZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e= > > > _______________________________________________ > council mailing list > council@gnso.icann.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mail > man_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6Ekp > FXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6 > IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e= > _______________________________________________ council mailing list council@gnso.icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... _______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
Thanks Marika So I guess the question now for council is whether we want to suggest any changes to the process as written. Donna -----Original Message----- From: Marika Konings [mailto:marika.konings@icann.org] Sent: Friday, March 09, 2018 1:04 PM To: Austin, Donna <Donna.Austin@team.neustar>; Johan Helsingius <julf@julf.com>; council@gnso.icann.org Subject: Re: [council] [EXTERNAL] Re: Board process for GAC Advice Donna, all, Please note that the handbook that has been referenced is part of the Process Mapping work, described at https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_processdo.... It is not an adopted process, but an attempt to describe in plain English the process set out in the diagram, available at https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system.... If there are items missing from these diagrams, such as the potential for impasse if GAC advice is in conflict with a policy recommendation, or to demonstrate an opportunity for consideration of additional inputs such as the GNSO’s recent work on producing responses to GAC advice, the diagram and handbook can be updated. They are considered living documents, and though staff has tried hard to get them as right as possible and integrate community input, they don’t capture every nuance. I hope this is helpful. Best regards, Marika On 3/9/18, 12:46, "council on behalf of Austin, Donna via council" <council-bounces@gnso.icann.org on behalf of council@gnso.icann.org> wrote: Julf, all It's unclear to me who owns or who drafted this document. Is it the Board, the GAC, ICANN? Is it possible for you to follow up with your GAC counterpart to see if you can get more clarity around the intent of the document and where it came from. I suspect it is the result of a number of consultations whether they be internal to just the GAC or perhaps the result of the Board/GAC Working Group. Before we all go jumping at shadows it would be good to have the context and understand where this came from, its purpose and intended audience. Thanks Donna -----Original Message----- From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Johan Helsingius Sent: Thursday, March 08, 2018 9:03 PM To: council@gnso.icann.org Subject: [EXTERNAL] Re: [council] Board process for GAC Advice Likewise! Julf On 08-03-18 23:58, Erika Mann wrote: > Heather - I agree with Rubens and Carlos. Cheers, Erika > > > Sent from my iPhone > > On Mar 8, 2018, at 5:03 PM, Carlos Raul Gutierrez <crg@isoc-cr.org > <mailto:crg@isoc-cr.org>> wrote: > >> I think we should consider both Heather! >> >> I think Rubens first suggestion on a GNSO comment, in view of the new >> early engagement of the GAC in the GNSO process, is valid on its own >> for GNSO derived policies. Even if its only for future cases, the >> Board should consider in its evaluation phase if a GNSO policy issue >> has already been discussed between GAC and the GNSO in previous stages. >> >> Then, of course, your suggestion to ask other SO/ACs should be >> pursued ASAP. >> >> Safe travels to all >> >> Carlos Raúl Gutiérrez >> ISOC Costa Rica Chapter >> skype carlos.raulg >> +506 8837 7176 >> ________ >> Apartado 1571-1000 >> COSTA RICA >> >> On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest >> <haforrestesq@gmail.com <mailto:haforrestesq@gmail.com>> wrote: >> >> Thank you, Rubens. I wasn't aware of this- anyone else? >> >> If you all agree, I think this would be a worthwhile thing to >> raise when I meet with the other SOAC chairs tomorrow. >> >> Best wishes, >> Heather >> >> On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br >> <mailto:rubensk@nic.br>> wrote: >> >> >> It seems that Board decided to detail how they plan to handle >> GAC advice: >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system... >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_e >> n_system_files_files_gac-2Dadvice-2Dprocess-2Dhandbook-2D06mar18-2Den >> .pdf&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4y >> C5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6IyOf4Y&s=Xas05 >> X2yr3O703La8H8MqiQhHG8kWoPxOU_Kp8WEFCc&e=> >> >> As another registry mentioned, "Curious how there is nothing >> in the new process about consulting the rest of the community >> if the GAC Advice overlaps with, is inconsistent with, or >> otherwise also falls into the jurisdiction of, other SOs or ACs." >> That lacks, for instance, the usual comments from GNSO >> regarding advice overlapping with GNSO Policy, either existent >> or in the pipeline. >> >> Do we want to make a GNSO Council comment ? Or perhaps >> including other SOs and ACs ? >> >> >> Rubens >> >> >> >> _______________________________________________ >> council mailing list >> council@gnso.icann.org <mailto:council@gnso.icann.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_ma >> ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6 >> EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzg >> yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=> >> >> >> _______________________________________________ >> council mailing list >> council@gnso.icann.org <mailto:council@gnso.icann.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_ma >> ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6 >> EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzg >> yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=> >> >> >> _______________________________________________ >> council mailing list >> council@gnso.icann.org <mailto:council@gnso.icann.org> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mai >> lman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6E >> kpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgy >> ZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e= > > > _______________________________________________ > council mailing list > council@gnso.icann.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mail > man_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6Ekp > FXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6 > IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e= > _______________________________________________ council mailing list council@gnso.icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... _______________________________________________ council mailing list council@gnso.icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li...
Hi, as those documents being advertised and likely many from the community may refer to them for convenience instead to check lengthy documents, it would make sense to make suggestions from the council. Best, Rafik 2018-03-10 2:32 GMT+09:00 Austin, Donna via council <council@gnso.icann.org> :
Thanks Marika
So I guess the question now for council is whether we want to suggest any changes to the process as written.
Donna
-----Original Message----- From: Marika Konings [mailto:marika.konings@icann.org] Sent: Friday, March 09, 2018 1:04 PM To: Austin, Donna <Donna.Austin@team.neustar>; Johan Helsingius < julf@julf.com>; council@gnso.icann.org Subject: Re: [council] [EXTERNAL] Re: Board process for GAC Advice
Donna, all,
Please note that the handbook that has been referenced is part of the Process Mapping work, described at https://urldefense.proofpoint. com/v2/url?u=https-3A__www.icann.org_processdocumentation&d=DwIGaQ& c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m= e2BAhsTWRvkb8S5gyeqwWJebowJIPuy8fEaLTuUDusQ&s=dx_ RjWjnBD9n7gMh7pWBXgH8LcNJOwOEwK0JTvMNfxk&e=. It is not an adopted process, but an attempt to describe in plain English the process set out in the diagram, available at https://urldefense.proofpoint. com/v2/url?u=https-3A__www.icann.org_en_system_files_ files_gac-2Dadvice-2Dprocess-2Dflowchart-2D31aug17-2Den.pdf&d=DwIGaQ&c= MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m= e2BAhsTWRvkb8S5gyeqwWJebowJIPuy8fEaLTuUDusQ&s=vRXEk_FoWWMKlPe- ZNmKqrv1upidhz7W7oRHUBUG-_s&e=. If there are items missing from these diagrams, such as the potential for impasse if GAC advice is in conflict with a policy recommendation, or to demonstrate an opportunity for consideration of additional inputs such as the GNSO’s recent work on producing responses to GAC advice, the diagram and handbook can be updated. They are considered living documents, and though staff has tried hard to get them as right as possible and integrate community input, they don’t capture every nuance.
I hope this is helpful.
Best regards,
Marika
On 3/9/18, 12:46, "council on behalf of Austin, Donna via council" < council-bounces@gnso.icann.org on behalf of council@gnso.icann.org> wrote:
Julf, all
It's unclear to me who owns or who drafted this document. Is it the Board, the GAC, ICANN?
Is it possible for you to follow up with your GAC counterpart to see if you can get more clarity around the intent of the document and where it came from. I suspect it is the result of a number of consultations whether they be internal to just the GAC or perhaps the result of the Board/GAC Working Group.
Before we all go jumping at shadows it would be good to have the context and understand where this came from, its purpose and intended audience.
Thanks
Donna
-----Original Message-----
From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Johan Helsingius
Sent: Thursday, March 08, 2018 9:03 PM
To: council@gnso.icann.org
Subject: [EXTERNAL] Re: [council] Board process for GAC Advice
Likewise!
Julf
On 08-03-18 23:58, Erika Mann wrote:
> Heather - I agree with Rubens and Carlos. Cheers, Erika
>
>
> Sent from my iPhone
>
> On Mar 8, 2018, at 5:03 PM, Carlos Raul Gutierrez <crg@isoc-cr.org
> <mailto:crg@isoc-cr.org>> wrote:
>
>> I think we should consider both Heather!
>>
>> I think Rubens first suggestion on a GNSO comment, in view of the new
>> early engagement of the GAC in the GNSO process, is valid on its own
>> for GNSO derived policies. Even if its only for future cases, the
>> Board should consider in its evaluation phase if a GNSO policy issue
>> has already been discussed between GAC and the GNSO in previous stages.
>>
>> Then, of course, your suggestion to ask other SO/ACs should be
>> pursued ASAP.
>>
>> Safe travels to all
>>
>> Carlos Raúl Gutiérrez
>> ISOC Costa Rica Chapter
>> skype carlos.raulg
>> +506 8837 7176
>> ________
>> Apartado 1571-1000
>> COSTA RICA
>>
>> On Thu, Mar 8, 2018 at 3:15 PM, Heather Forrest
>> <haforrestesq@gmail.com <mailto:haforrestesq@gmail.com>> wrote:
>>
>> Thank you, Rubens. I wasn't aware of this- anyone else?
>>
>> If you all agree, I think this would be a worthwhile thing to
>> raise when I meet with the other SOAC chairs tomorrow.
>>
>> Best wishes,
>> Heather
>>
>> On 08/03/2018 4:47 PM, "Rubens Kuhl" <rubensk@nic.br
>> <mailto:rubensk@nic.br>> wrote:
>>
>>
>> It seems that Board decided to detail how they plan to handle
>> GAC advice:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www. icann.org_en_system_files_files_gac-2Dadvice-2Dprocess- 2Dhandbook-2D06mar18-2Den.pdf&d=DwIGaQ&c=MOptNlVtIETeDALC_ lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m= zvmfmT_sC8EhMQIikWw2w9-9QPmH1zAzgyZP6IyOf4Y&s= Xas05X2yr3O703La8H8MqiQhHG8kWoPxOU_Kp8WEFCc&e=
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https- 3A__www.icann.org_e
>> n_system_files_files_gac-2Dadvice-2Dprocess-2Dhandbook- 2D06mar18-2Den
>> .pdf&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r= CwipU91YB6EkpFXK9ynnT_QUef4y
>> C5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzgyZP6IyOf4Y&s=Xas05
>> X2yr3O703La8H8MqiQhHG8kWoPxOU_Kp8WEFCc&e=>
>>
>> As another registry mentioned, "Curious how there is nothing
>> in the new process about consulting the rest of the community
>> if the GAC Advice overlaps with, is inconsistent with, or
>> otherwise also falls into the jurisdiction of, other SOs or ACs."
>> That lacks, for instance, the usual comments from GNSO
>> regarding advice overlapping with GNSO Policy, either existent
>> or in the pipeline.
>>
>> Do we want to make a GNSO Council comment ? Or perhaps
>> including other SOs and ACs ?
>>
>>
>> Rubens
>>
>>
>>
>> _______________________________________________
>> council mailing list
>> council@gnso.icann.org <mailto:council@gnso.icann.org>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm. icann.org_mailman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r= CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzgyZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https- 3A__mm.icann.org_ma
>> ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_ lULrw&r=CwipU91YB6
>> EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzg
>> yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=>
>>
>>
>> _______________________________________________
>> council mailing list
>> council@gnso.icann.org <mailto:council@gnso.icann.org>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm. icann.org_mailman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r= CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzgyZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https- 3A__mm.icann.org_ma
>> ilman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_ lULrw&r=CwipU91YB6
>> EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzg
>> yZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=>
>>
>>
>> _______________________________________________
>> council mailing list
>> council@gnso.icann.org <mailto:council@gnso.icann.org>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm. icann.org_mai
>> lman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_ lULrw&r=CwipU91YB6E
>> kpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzgy
>> ZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
>
>
> _______________________________________________
> council mailing list
> council@gnso.icann.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm. icann.org_mail
> man_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r= CwipU91YB6Ekp
> FXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzgyZP6
> IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
>
_______________________________________________
council mailing list
council@gnso.icann.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__mm. icann.org_mailman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r= CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=zvmfmT_sC8EhMQIikWw2w9- 9QPmH1zAzgyZP6IyOf4Y&s=PTgw79BdeghcOFfiv08cv6yb2dswO3MyjcYkkJ_drSU&e=
_______________________________________________
council mailing list
council@gnso.icann.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__mm. icann.org_mailman_listinfo_council&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r= CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m= e2BAhsTWRvkb8S5gyeqwWJebowJIPuy8fEaLTuUDusQ&s=Ne_JEjamzaxryl3zct3_ uL6vG7NtIBE7h39gwxGrOBQ&e=
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
On 09-03-18 17:45, Austin, Donna via council wrote:
It's unclear to me who owns or who drafted this document. Is it the Board, the GAC, ICANN?
My apologies for not responding sooner, but I was travelling to ICANN61, and while there had been some scaremongering about power outages in Puerto Rico, I wasn't prepared to find out, as I landed in Atlanta on my way, that a large part of Amsterdam had been without power for more than 8 hours (taking down, among other things, my mail server). As has become clear, it is an informal staff document. I agree with the view expressed by several people here that we should take some effort to get it improved just in case it gets used as a shorthand for the proper procedure. Julf
Agree we should discuss some clarifications/improvements and address any missing steps. I notice there's no mention of how the Board receives and considers input from other SO/ACs about GAC's advice, which has been a problem for the GNSO in the past. Darcy On Sat, Mar 10, 2018 at 6:22 AM, Johan Helsingius <julf@julf.com> wrote:
On 09-03-18 17:45, Austin, Donna via council wrote:
It's unclear to me who owns or who drafted this document. Is it the Board, the GAC, ICANN?
My apologies for not responding sooner, but I was travelling to ICANN61, and while there had been some scaremongering about power outages in Puerto Rico, I wasn't prepared to find out, as I landed in Atlanta on my way, that a large part of Amsterdam had been without power for more than 8 hours (taking down, among other things, my mail server).
As has become clear, it is an informal staff document. I agree with the view expressed by several people here that we should take some effort to get it improved just in case it gets used as a shorthand for the proper procedure.
Julf
_______________________________________________ council mailing list council@gnso.icann.org https://mm.icann.org/mailman/listinfo/council
participants (9)
-
Austin, Donna -
Carlos Raul Gutierrez -
Darcy Southwell -
Erika Mann -
Heather Forrest -
Johan Helsingius -
Marika Konings -
Rafik Dammak -
Rubens Kuhl