+1
Hervé
De : ac-discuss-bounces(a)aso.icann.org [mailto:ac-discuss-bounces@aso.icann.org] De la part de Aftab Siddiqui
Envoyé : mardi 8 octobre 2019 04:49
À : Jason Schiller
Cc : ac-discuss(a)aso.icann.org
Objet : [EMAIL SOURCE POSSIBLY UNSAFE] Re: [AC-DISCUSS] Action Item 190904-3
Following Jason's suggestion which is only a minor edit on the website. Here is the final version with Option 2(A).
======
Option 2: Remove "ac-coord" from all 4 references and only mention mailing list along with numbered reference i.e. [1] and at the end clarify the reference
For Example.
7.3. Time Constrained Appointment Requests
The AC Chair may decide to make the appointment by eVote after discussion on the mailing list [1], in order to meet appointment deadline.
....
[1] - "ac-discuss" mailing list. This mailing list is used for ASO-AC Operations. This list has public posting restriction and it is publicly archived.
AND also update the description of "ac-discuss" at following link
https://aso.icann.org/contact/aso-mailing-lists/
ac-discuss
ac-discuss [at] aso [dot] icann [dot] org
This mailing list is used for ASO-AC Operations. This list has public posting restriction and it is publicly archived.
· subscription open to ASO AC members and RIR/ICANN/IANA staff observers
· posts by ASO AC members and designated RIR, ICANN and IANA staff
· publicly archived
=======
Regards,
Aftab A. Siddiqui
On Thu, Oct 3, 2019 at 12:12 AM Jason Schiller <jason-phone(a)schiller.net<mailto:jason-phone@schiller.net>> wrote:
I have a counter proposal for option 2.
Option A: We update the web site text to match the proposed text of option 2
Or
Option B: we use the web site text in our procedural change.
I have no preference just, don’t want different text in our procedures and in the mailing list description.
More detailed proposal below:
Option A:
Use option 2 text and update our website to match:
[1] - ac-discuss mailing list. This list has public posting restriction and it is publicly archived. This mailing list is used for ASO-AC Operations.
And for the web site:
“ac-discuss
ac-discuss [at] aso [dot] icann [dot] org
This mailing list is used for ASO-AC Operations. This list has public posting restriction and it is publicly archived.
· subscription open to ASO AC members and RIR/ICANN/IANA staff observers
· posts by ASO AC members and designated RIR, ICANN and IANA staff
· publicly archived”
Option B:
Use the text from our web site:
[1] - ac-discuss mailing list. Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
For reference ————————-
Here is what is posted on the website:
https://aso.icann.org/contact/aso-mailing-lists/
“ac-discuss
ac-discuss [at] aso [dot] icann [dot] org
Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
· subscription open to ASO AC members and RIR/ICANN/IANA staff observers
· posts by ASO AC members and designated RIR, ICANN and IANA staff
· publicly archived”
On Wed, Oct 2, 2019 at 7:27 AM Aftab Siddiqui <aftab.siddiqui(a)gmail.com<mailto:aftab.siddiqui@gmail.com>> wrote:
Action Item 190904-3 AS to suggest the term to use to replace the references to the AC-COORD list in the ASO procedures. The wording should match the description of the AC-DISCUSS mailing in the ASO website
"ac-coord" has been referenced 4 times in ASO-AC operating procedures.
=============
4.4.1. Nominations
Nominations for the positions of Chair for a particular year must be posted on the AC-COORD mailing list no earlier than 00:00 UTC on 1 December and no later than 24:00 UTC on 14 December of the preceding year. Self-nominations are allowed. Nominations must be seconded by another eligible voter. Confirmation of interest from nominated candidates must be posted on the AC-COORD mailing list no later than 31 December at 24:00 UTC.
7.3. Time Constrained Appointment Requests
The AC Chair may decide to make the appointment by eVote after discussion on the ac-coord mailing list, in order to meet appointment deadline.
8.2. eVote
The AC Chair may decide to hold an eVote after a 7 day discussion on the ac-coord mailing list. eVotes will follow the procedures described in our PROCEDURES TO APPOINT MEMBERS TO VARIOUS BODIES sections 7.4 except as follows in section in the next section:
==============
I suggest the following 2 options
Option 1: Replace "ac-coord" with "ac-discuss"
Option 2: Remove "ac-coord" from all 4 references and only mention mailing list along with numbered reference i.e. [1] and at the end clarify the reference
For Example.
7.3. Time Constrained Appointment Requests
The AC Chair may decide to make the appointment by eVote after discussion on the mailing list [1], in order to meet appointment deadline.
....
[1] - ac-discuss mailing list. This list has public posting restriction and it is publicly archived. This mailing list is used for ASO-AC Operations.
Regards,
Aftab A. Siddiqui
_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS(a)aso.icann.org<mailto:AC-DISCUSS@aso.icann.org>
https://aso.icann.org/mailman/listinfo/ac-discuss
_________________________________________________________________________________________________________________________
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.
Dear ASO AC
Please R.S.V.P to the list AC-DISCUSS list (ac-discuss(a)aso.icann.org).
The November 2019 ASO AC scheduled teleconference will be held in 2 weeks at the following time:
12:00 PM UTC on Wednesday, 13 November 2019
===========================================
Below you will find Zoom information to join the meeting.
The call will be opened 15 minutes prior to the teleconference to work out any potential technical issues.
If you need to be called, send the following information DIRECTLY to ASO Secretariat < secretariat(a)aso.icann.org >
- country in which you are located
- country code (separate from your own telephone number)
- telephone number
** DO NOT SUBMIT PERSONAL INFORMATION IN THIS LIST PUBLICLY ARCHIVED LIST **
When sending in your contact details please verify that they are correct and include the three separate pieces of information specified above.
=====
ASO AC 2019 Teleconference
Wednesday 13 November 2019
12:00 pm (NOON) | UTC | 2 hrs
Join Zoom Meeting
https://apnic.zoom.us/j/335133621
Meeting ID: 335 133 621
Find your local number: https://apnic.zoom.us/u/abv6v2k00E
Regards
German Valdez
ASO Secretariat
Here is the draft agenda for ICANN66.
*Agenda for Monday, 4th Nov. Room: 515C [Open Session]*
*ICANN 66 - Opening Session: 9:00 AM to 10:00 AM*
Start Time: 10:30 AM (after coffee break)
End Time: 2:30 PM (just to block room)
1) ASO-AC 2019 Work plan review
2) RIR Community Outreach
3) Documents review. What are key documents for the ASO, what is missing?
4) ASO-AC Slide deck review for Board Meeting
*Note*: Jan Aart Scholte hasn't confirmed the time slot yet but its most
likely 11:30 AM to 12:00 PM on Monday, 4th Nov.
*Tuesday 9:45 AM to 10:45 AM - ICANN Board - ASO Meeting*
*Agenda for Wednesday, 6th Nov. Room: 515C* *[Closed Session]*
Start Time: 9:00 AM
End Time: 12:00 PM (just to block room)
1) Seat 9/10 election procedure review.
2) Voting Tie Break procedures
3) NomCom appointment review
Regards,
Aftab A. Siddiqui
Hi German, I plan to attend via Webex, as usual.
Regards,
Jorge
El 10/30/19 7:39 a. m., "German Valdez" <ac-discuss-bounces(a)aso.icann.org en nombre de german(a)apnic.net> escribió:
Dear ASO AC
Please R.S.V.P to the list AC-DISCUSS list (ac-discuss(a)aso.icann.org).
The November 2019 ASO AC scheduled teleconference will be held in 2 weeks at the following time:
12:00 PM UTC on Wednesday, 13 November 2019
===========================================
Below you will find Zoom information to join the meeting.
The call will be opened 15 minutes prior to the teleconference to work out any potential technical issues.
If you need to be called, send the following information DIRECTLY to ASO Secretariat < secretariat(a)aso.icann.org >
- country in which you are located
- country code (separate from your own telephone number)
- telephone number
** DO NOT SUBMIT PERSONAL INFORMATION IN THIS LIST PUBLICLY ARCHIVED LIST **
When sending in your contact details please verify that they are correct and include the three separate pieces of information specified above.
=====
ASO AC 2019 Teleconference
Wednesday 13 November 2019
12:00 pm (NOON) | UTC | 2 hrs
Join Zoom Meeting
https://apnic.zoom.us/j/335133621
Meeting ID: 335 133 621
Find your local number: https://apnic.zoom.us/u/abv6v2k00E
Regards
German Valdez
ASO Secretariat
_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS(a)aso.icann.org
https://aso.icann.org/mailman/listinfo/ac-discuss
Hi Carlos
Thanks for the invitation. Even when the NRO EC is the body representing ASO in the ICANN empowered community (an accordingly Axel must be there), it could be very interesting for us (the AC) to see the empowered community in practice.
Regards,
Jorge
De: <ac-discuss-bounces(a)aso.icann.org> en nombre de Carlos Reyes <carlos.reyes(a)icann.org>
Fecha: viernes, 25 de octubre de 2019, 9:55 a. m.
Para: Esteban Lescano <esteban(a)lescano-etcheverry.com.ar>, Filiz Yilmaz <koalafil(a)gmail.com>
CC: "ac-discuss(a)aso.icann.org" <ac-discuss(a)aso.icann.org>
Asunto: Re: [AC-DISCUSS] [Ext] Re: ICANN66 meeting ASO AC Activities agenda/schedule
Hello, all.
The Community Action Approval Forum on Sunday, 3 November, 08:00-09:00 in room 517C will be an opportunity for the ICANN Board and community to discuss a proposed amendment to one of the Fundamental Bylaws. The proposed Fundamental Bylaw change concerns the composition of the community-based team that will be tasked with performing a review of the IANA Naming Function. Read more: https://www.icann.org/en/ec/empowered-community-s-consideration-of-fundamen…
As a Decisional Participant in the Empowered Community, the ASO has to decide whether or not to support the amendment. There was a similar process in June 2017 at ICANN59 in Johannesburg. The ASO procedure is here: https://aso.icann.org/documents/operational-documents/aso-procedures-for-em…
In any case, ASO AC members are not required to attend, though you are certainly welcome to attend. My understanding is that Axel (in his capacity as ASO Secretary and therefore the ASO representative to the Empowered Community Administration) is attending.
The ASO/ICANN Board joint meeting is Tuesday, 5 November, 09:45-10:45 in room 517D. I will defer to Aftab and German about any other meetings/sessions during ICANN66.
Best,
Carlos
Carlos Reyes
Strategic Policy Planning Director
Internet Corporation for Assigned Names and Numbers (ICANN)
+1 202 802 8019
www.icann.org
From: <ac-discuss-bounces(a)aso.icann.org> on behalf of Esteban Lescano <esteban(a)lescano-etcheverry.com.ar>
Date: Friday, October 25, 2019 at 8:55 AM
To: Filiz Yilmaz <koalafil(a)gmail.com>
Cc: "ac-discuss(a)aso.icann.org" <ac-discuss(a)aso.icann.org>
Subject: [Ext] Re: [AC-DISCUSS] ICANN66 meeting ASO AC Activities agenda/schedule
Thank you Filiz. I also suscribe your petition.
Bes regards
Esteban Lescano
LESCANO & ETCHEVERRY ABOGADOS
Montevideo 527- Piso 4° y 9° contrafrente
Ciudad Autónoma de Buenos Aires - CP 1019
Tel: +5411- 6091-1555
info(a)lescano-etcheverry.com.ar
www.lescano-etcheverry.com.ar
El 25 oct. 2019, a las 09:38, Filiz Yilmaz <koalafil(a)gmail.com> escribió:
Hello,
Can we pls get an update on which meetings are planned for those who will be attending ICANN66 in Montreal?
At the moment, ASO AC Activities calendar points me only to the following 3 meetings in my agenda:
Sunday: Approval Action Community Forum [NRO EC Secretary ONLY] : What is this exactly? Are ASO AC Members expected to attend?
Monday: Openning Ceremony
Tuesday: ASO meeting with ICANN Board
Is this all?
Can I pls ask for a full overview of meetings that ASO AC members are expected to attend by mail?
Then I will know if my calendar is missing anything and it will also help me plan my week.
Kind regards
Filiz
_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS(a)aso.icann.org
https://aso.icann.org/mailman/listinfo/ac-discuss
_______________________________________________ AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available. AC-DISCUSS(a)aso.icann.org https://aso.icann.org/mailman/listinfo/ac-discuss
Hello,
Can we pls get an update on which meetings are planned for those who will be attending ICANN66 in Montreal?
At the moment, ASO AC Activities calendar points me only to the following 3 meetings in my agenda:
Sunday: Approval Action Community Forum [NRO EC Secretary ONLY] : What is this exactly? Are ASO AC Members expected to attend?
Monday: Openning Ceremony
Tuesday: ASO meeting with ICANN Board
Is this all?
Can I pls ask for a full overview of meetings that ASO AC members are expected to attend by mail?
Then I will know if my calendar is missing anything and it will also help me plan my week.
Kind regards
Filiz
Dear all,
I'm pleased to share the information that Filiz was re-elected to the NRO NC during the Rotterdam RIPE meeting of this week.
Congrats to Filiz.
Best regards
Hervé
-----Message d'origine-----
De : ripe-list [mailto:ripe-list-bounces@ripe.net] De la part de Axel Pawlik
Envoyé : vendredi 18 octobre 2019 17:12
À : ripe-list(a)ripe.net
Objet : [ripe-list] 2019 NRO NC Election Results
Dear colleagues,
We are pleased to announce that Filiz Yilmaz was re-elected to the
Number Resource Organization Number Council (NRO NC) at a plenary
session of the RIPE 79 Meeting in Rotterdam on 18 October 2019.
After completion of her current term on 31 December 2019, Filiz will
begin another three-year term from 1 January 2020 to 31 December 2022.
Details on the election process and the NRO NC are available online:
https://www.ripe.net/nro/nro-rc/nominations2019
We would like to congratulate Filiz on her appointment.
Best regards
Axel Pawlik
Managing Director
RIPE NCC
_________________________________________________________________________________________________________________________
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.
A brief report about last LACNIC meeting:
More than 500 participants attended the LACNIC 32 LACNOG 2019 event held
from 7 to 11 October at the Hard Rock Hotel in Panama City.
The Second LACNIC Hackathon took place in the runup to the event. There,
participants worked on four different LACNIC projects: the MiLACNIC API,
the UpDown for the Resource Certification System (RPKI), LACNIC's
Internet Routing Registry (IRR) and the organization’s events system.
Additional details and a summary of what took place at the Hackathon are
available here.
Tutorials. The number of tutorials offered during this meeting was
higher than usual. In addition to the tutorials on Advanced IPv6, RPKI
and BGP, Changing Internet Policies, Peering and Resource Management,
this time the agenda also included the tutorials titled Internet
Policies, How to Use the Tools Provided by RIPE NCC for Network
Operators, Best Security Practices for Autonomous Systems, and Wi-Fi and
IPv6.
More info at:
https://www.lacnic.net/3819/2/lacnic/lacnic-32-lacnog-2019:-activity-recap
Regarding policy discussions.
There were 9 proposals presented and discussed and according to the new
PDP the consensus will be determined by chairs 2 weeks after finished
the discussion phase.
ID Proposal discussion phase until
2018-13 Acceptable Use Policy (AUP) for the Policy List 11/11/19
2019-02 IPv4 Mergers, Acquisitions, Reorganizations and Relocations
14/11/2019
2019-03 IPv6 Mergers, Acquisitions, Reorganizations and Relocations
14/11/2019
2019-04 ASN Mergers, Acquisitions, Reorganizations and Relocations
14/11/2019
2019-07 PDP Chair Election Procedure 15/11/2019
2019-09 Update to “Resource Recovery and Return” and consistency with
the rest of the Manual 20/11/2019
2018-05 Registration and validation of abuse contact 21/11/2019
2019-06 Resources Are Assigned in a Unique and Exclusive Capacity
25/11/2019
2019-8 Modification of the Time Required for a Proposal to be Presented
at the Public Policy Forum, already reached the end of discussion phase
and it is now in analysis by chairs.
Regards,
--
Ricardo Patara
Excellent! Congratulations dear Filiz
Regards,
Jorge
El 10/18/19 11:30 a. m., "ac-discuss-bounces(a)aso.icann.org en nombre de herve.clement(a)orange.com" <ac-discuss-bounces(a)aso.icann.org en nombre de herve.clement(a)orange.com> escribió:
Dear all,
I'm pleased to share the information that Filiz was re-elected to the NRO NC during the Rotterdam RIPE meeting of this week.
Congrats to Filiz.
Best regards
Hervé
-----Message d'origine-----
De : ripe-list [mailto:ripe-list-bounces@ripe.net] De la part de Axel Pawlik
Envoyé : vendredi 18 octobre 2019 17:12
À : ripe-list(a)ripe.net
Objet : [ripe-list] 2019 NRO NC Election Results
Dear colleagues,
We are pleased to announce that Filiz Yilmaz was re-elected to the
Number Resource Organization Number Council (NRO NC) at a plenary
session of the RIPE 79 Meeting in Rotterdam on 18 October 2019.
After completion of her current term on 31 December 2019, Filiz will
begin another three-year term from 1 January 2020 to 31 December 2022.
Details on the election process and the NRO NC are available online:
https://www.ripe.net/nro/nro-rc/nominations2019
We would like to congratulate Filiz on her appointment.
Best regards
Axel Pawlik
Managing Director
RIPE NCC
_________________________________________________________________________________________________________________________
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.
_______________________________________________
AC-DISCUSS mailing list - Workspace for ASO AC operations. Posting is restricted, archive is publicly available.
AC-DISCUSS(a)aso.icann.org
https://aso.icann.org/mailman/listinfo/ac-discuss
Dear all,
Fyi
Hervé
https://www.icann.org/news/blog/zoom-security-update
• Author: Ashwin Rangan, SVP Engineering & Chief Information Officer
• 10 Oct 2019
•
• Zoom recently added new settings to increase security and ensure meeting privacy. These new settings will enforce a password on all new meetings scheduled, but will not affect meetings that have been scheduled prior to 29 September 2019.
The only participants who will be required to enter a password are those who join a meeting via the Zoom app and manually type in the meeting ID. Participants who join a meeting via a link in a calendar or e-mail invitation will not be required to enter the password upon joining, as it is included in the URL by default. To learn more about the new settings, please visit the Zoom Help Center and read the FAQ here<https://support.zoom.us/hc/en-us/articles/360033331271>.
At the recommendation of ICANN’s internal InfoSec team, these new settings will be enabled immediately. Because the vast majority of ICANN meeting participants join via invitation links, we expect the impact on community members and staff to be minimal.
Please reply here or contact the Meetings Technical Services team directly at mts(a)icann.org<mailto:mts@icann.org> if you have any questions or concerns regarding this update.
_________________________________________________________________________________________________________________________
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.