Hi All,

As some of you are aware, Andrew Gallo and I have been working towards creating a MANRS R&E programme given the unique situations that we as universities, research institutions, local R&E networks, national R&E networks and the wide R&E networks face ranging from:

• How do we provide mutual backups for each other
• How do we secure the R&E global routing table?
• How do we deal with historical IPv4 address space and the creation of ROA’s
• R&E Peering Agreement best practices
• BGP Route Selection process (ROA’s, RIR data, RADB or other options?)
• ASPA (Autonomous System Proivder Authorisation)
• BGPSec
• Could we create a ROA table for customer routes to help do filtering rather than prefix lists?
• uRPF
• Route Object Validation
• Data cleanup some of our data has existed before the RIR’s has
• What tooling do we use (bgpq4, peering manager, in house developed scripts) etc…
• Documentation…
• Many more items.

For those who are hearing this for the first time, we would like to welcome you too if you would to be involved.

Please take a look at the following doodle poll and choose the best times that work for you for the first meeting, we will select it based of which date/time gets the most votes.

https://doodle.com/meeting/participate/id/eX6xq9Vb

The agenda will be:

• Brief overview of the expection of the programme
• Roll call to see who does want to be involved
• Determine the next meeting and agenda etc…

Hope you can make it!

Kind regards,

Warrick Mitchell • Head of Network and Systems Architecture

______________________________________________________

AARNet Pty Ltd

m: +61 416 089 354

e: warrick.mitchell@aarnet.edu.au

w: aarnet.edu.au

______________________________________________________ 

Important:  This email and any files transmitted with it are confidential, and the rights of confidentiality in such information are not waived or lost by its mistaken delivery to you.  Any dissemination, copying, use or disclosure of the email and/or such files without the permission of AARNet, or the sender, is strictly prohibited.  If you have received this email in error, please contact the sender immediately and delete all copies of this transmission.

Kind regards,

Warrick