Sorry, direct link to the new section
https://asowiki.atlassian.net/l/c/jCnnUJLD
regards
German
From:
German Valdez Aviles <german@apnic.net>
Date: Tuesday, 14 June 2022 at 1:44 pm
To: Ricardo Patara <patara@registro.br>, procedures@aso.icann.org <procedures@aso.icann.org>
Subject: Re: [ASO-PROCEDURES] ASO Procedures Review Mailing List Created and Members
Hi
As suggested I created a section in the private page in the ASO wiki to start working in procedures review.
Let me know if you’d like to start to populate the section with any document.
You have edit privileges so should able as well to modify it
Regards
German
From:
Procedures <procedures-bounces@aso.icann.org> on behalf of Ricardo Patara <patara@registro.br>
Date: Wednesday, 1 June 2022 at 11:55 pm
To: procedures@aso.icann.org <procedures@aso.icann.org>
Subject: Re: [ASO-PROCEDURES] ASO Procedures Review Mailing List Created and Members
Hi.
Another topic.
I think it should useful to have a section in the Wiki for this work. Right?
If agreed, we can ask German to make that
thanks
On 31/05/22 09:25, herve.clement@orange.com wrote:
> Dear Ricardo, James,
>
> Thanks for your proposals.
> I tend to agree with you and a complete review would be useful.
> We can take the opportunity of this initiative energy to go as far as we can.
> And a remark: yes the quorum issue is solved; I've mentioned it to illustrate my powerpoint and present topics we've discussed.
>
> Tomorrow we can present this first list of topics and actions:
> - review the discussion we had 2 years ago, or so, about some proposed reviews that didn't move forward (I will send to the group these discussions)
> And more specifically:
> - Questions around voting processes (adding the concern brought by German)
> - In-person meetings impossibilities are not taken into account enough
> - adjust the references in our procedures pointing to MoU. And also remove broken references for templates we never had
> - add a discussion to review our selection process. Specifically regarding responsibilities of the AC and IC/QRC, timing and agenda preparation
>
> I suspect that if we decide to deal with all these previous topics we'll have to redefine the structure of the text.
> So to optimize the time needed:
> - List and review all activities individually and collectively (minimise overlaps)
>
> Do we propose to answer this last point for our July meeting ?
>
> Kind regards
>
> Hervé
>
>
>
> Orange Restricted
>
> -----Message d'origine-----
> De : Procedures <procedures-bounces@aso.icann.org> De la part de Ricardo Patara
> Envoyé : lundi 30 mai 2022 21:54
> À : procedures@aso.icann.org
> Objet : Re: [ASO-PROCEDURES] ASO Procedures Review Mailing List Created and Members
>
> Hi Everyone. Hope you are all fine.
>
> I was thinking that we could start discussing a bit about our goals.
>
> Reading Hervé slides we have:
>
> - Questions around voting processes
> (in this we could add the concern brought by German)
>
> - In-person meetings impossibilities are not taken into account enough
>
> - 2018 Quorum re-definition to solve the case where 3 representatives of
> a particular RIR are unable to attend
>
> From the above, I think the last one (quorum) is already solved, right?
>
> "5.2. Quorum.
>
> [...] If all three ASO AC representatives from a particular region are unable to attend an ASO AC meeting, they can specifically request that the meeting is rescheduled, at least 24hrs before the start of the meeting. Unless such a rescheduling request has
been received, a quorum of 4 regions will be accepted for the ASO AC meeting to proceed."
>
> Is this part we are considering or other part of the procedures?
>
>
> And also:
>
> - Fix pointers to updated documents as the ASO MoU and ICANN bylaws Cf. Kevin’s last year proposal related to procedures section 6 (Global Policy Development)
>
> I was reading this document from Kevin and the discussion we had back them.
> The proposed document tried to address the major "problems", i.e., adjust the references in our procedures pointing to MoU. And also remove broken references for templates we never had.
>
> But the discussions highlighted that the complete text in the procedure document was "bad". With grammar errors and sections being not very clear.
>
> The idea here would be a complete review and rewrite this section as whole.
>
> It think this is an important thing and would not demand considerable time from this group.
>
>
> To that, I would add a discussion to review our selection process.
> Specifically regarding responsibilities of the AC and IC/QRC, timing and
> agenda preparation.
>
> thanks!
> regards
>
> On 23/05/22 07:42, James Kennedy wrote:
>> Hi,
>>
>> Thanks for creating this dedicated mailing list German, and for sharing
>> the current procedures Herve.
>>
>> Couple of initial high-level thoughts\suggestions from my side:
>> - List and review all activities individually and collectively (minimise
>> overlaps)
>> - A goal for our review: simplify the procedures where possible, both
>> process and documentation wise
>>
>> Regards,
>> James
>>
>> On Sun, May 22, 2022 at 5:46 PM <herve.clement@orange.com
>> <mailto:herve.clement@orange.com>> wrote:
>>
>> Dear German,____
>>
>> __ __
>>
>> Thanks for your help regarding the creation of this dedicated
>> Procedures Review core team mailing. ____
>>
>> __ __
>>
>> I’ll try to summarize this week (if possible) the discussions we had
>> within the ASO AC on that subject during the 2 or 3 last years.____
>>
>> If everyone can in // have a look to the current procedures: ASO AC
>> Operating Procedures | The Address Supporting Organization (ASO
>> ICANN)
>> <https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faso.icann.org%2Fdocuments%2Foperational-documents%2Foperating-procedures-of-the-address-council-of-the-address-supporting-organization%2F&data=05%7C01%7C%7C51825a04bfd54e13b4a308da43d656dc%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637896885556138976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=f0elKv9MULNIPmCdhMdGrJS55VJmDlY89lyOAiQL7SM%3D&reserved=0>____
>>
>> Our next monthly meeting is planned Wednesday 1^st June. ____
>>
>> I don’t know if we will have time to define precisely at that date
>> the precise scope of our work but can draw the first lines.____
>>
>> __ __
>>
>> Best regards____
>>
>> __ __
>>
>> Hervé ____
>>
>> __ __
>>
>> __ __
>>
>> __ __
>>
>> Orange Restricted____
>>
>> *De :*Procedures <procedures-bounces@aso.icann.org
>> <mailto:procedures-bounces@aso.icann.org>> *De la part de* German
>> Valdez Aviles
>> *Envoyé :* vendredi 20 mai 2022 16:38
>> *À :* procedures@aso.icann.org <mailto:procedures@aso.icann.org>
>> *Cc :* Kevin Blumberg <kevinb@thewire.ca <mailto:kevinb@thewire.ca>>
>> *Objet :* [ASO-PROCEDURES] ASO Procedures Review Mailing List
>> Created and Members____
>>
>> __ __
>>
>> Hi____
>>
>> __ __
>>
>> This is a new mailing list created for the review of the ASO
>> Procedures____
>>
>> __ __
>>
>> Current members are____
>>
>> __ __
>>
>> Esteban Lescano – LACNIC____
>>
>> Herve Clement - RIPE NCC____
>>
>> James Kennedy - RIPE NCC____
>>
>> Ricardo Patara – LACNIC____
>>
>> Sander Steffann - RIPE NCC____
>>
>> Saul Stein – AFRINIC____
>>
>> Mike Silber – AFRINIC____
>>
>> Laureana Pavon – Secretariat____
>>
>> German Valdez - Secretariat____
>>
>> __ __
>>
>> The mailing list has a public archive and only members can submit to
>> it.____
>>
>> __ __
>>
>> Please let me know of any further adjustment.____
>>
>> __ __
>>
>> Regards____
>>
>> __ __
>>
>> German____
>>
>> _________________________________________________________________________________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>>
>> --
>> Procedures mailing list
>> Procedures@aso.icann.org <mailto:Procedures@aso.icann.org>
>>
https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faso.icann.org%2Fmailman%2Flistinfo%2Fprocedures&data=05%7C01%7C%7C51825a04bfd54e13b4a308da43d656dc%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637896885556138976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Dw5aMxrlL32Ku4LLn%2BMNOZThuM6M%2FLOPjcD2eztomPA%3D&reserved=0
>> <https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faso.icann.org%2Fmailman%2Flistinfo%2Fprocedures&data=05%7C01%7C%7C51825a04bfd54e13b4a308da43d656dc%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637896885556138976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Dw5aMxrlL32Ku4LLn%2BMNOZThuM6M%2FLOPjcD2eztomPA%3D&reserved=0>
>>
>>
>
--
Procedures mailing list
Procedures@aso.icann.org
https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faso.icann.org%2Fmailman%2Flistinfo%2Fprocedures&data=05%7C01%7C%7C51825a04bfd54e13b4a308da43d656dc%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637896885556138976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=Dw5aMxrlL32Ku4LLn%2BMNOZThuM6M%2FLOPjcD2eztomPA%3D&reserved=0