Hello Routing Working Group,
Here is the recording of the last RWG session September 7, 2021. The slides are attached for additional reference.
https://iu.mediaspace.kaltura.com/media/t/1_l7lu38l5
For additional resources on MANRS please visit https://www.manrs.org/
Please do not hesitate to reach out if you have questions or would like to work with us on a routing case. We appreciate your continued participation in the routing working group.
Thanks!
Brenna Meade
International Networks Indiana University
Reminder of this meeting coming up tomorrow.
From: "Addleman, Hans C" <addlema(a)iu.edu>
Date: Tuesday, August 17, 2021 at 3:18 PM
To: "routing-wg(a)lists.gna-g.net" <routing-wg(a)lists.gna-g.net>
Subject: [Routing-wg] September Routing Working Group Meeting
Greetings all,
Our next meeting will be on September 7 at 8pm EST (September 8 12:00AM UTC). You should have received a calendar invite already, however, I have attached an .ics to this mail just in case.
On this call we will briefly review work the teams are doing to identify and fix “weird” routes and then Steve Wallace will give a presentation on MANRS (https://www.manrs.org/)
Talk abstract: Overview of Mutually Agreed Norms for Routing Security (MANRS) for network operators. What’s required of number resource owners and network operators to benefit from MANRS, including insights into Internet Routing Registry records, the role of RIRs with RPKI route origin validation, and lessons learned in the case of North American R&E networks.
Thanks,
Hans
Hans Addleman is inviting you to a scheduled Zoom@IU meeting.
Topic: Routing Working Group - MANRS
Time: Sep 7, 2021 08:00 PM Indiana (East)
Join from computer or mobile:
https://iu.zoom.us/j/89302424995
Meeting ID: 893 0242 4995
One tap mobile
+16465588656,,89302424995# US (New York)
+13017158592,,89302424995# US (Washington DC)
Dial by your location
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
Meeting ID: 893 0242 4995
IU videoconferencing equipment: 26 893 0242 4995
Videoconferencing equipment outside of IU:
SIP: 89302424995(a)zoomcrc.com
H.323:
162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India Mumbai)
115.114.115.7 (India Hyderabad)
213.19.144.110 (Amsterdam Netherlands)
213.244.140.110 (Germany)
103.122.166.55 (Australia Sydney)
103.122.167.55 (Australia Melbourne)
209.9.211.110 (Hong Kong SAR)
64.211.144.160 (Brazil)
149.137.68.253 (Mexico)
69.174.57.160 (Canada Toronto)
65.39.152.160 (Canada Vancouver)
207.226.132.110 (Japan Tokyo)
149.137.24.110 (Japan Osaka)
Meeting ID: 893 0242 4995
Zoom@IU Team | cthelp(a)iu.edu | https://kb.iu.edu/d/bfqu
Greetings all,
Our next meeting will be on September 7 at 8pm EST (September 8 12:00AM UTC). You should have received a calendar invite already, however, I have attached an .ics to this mail just in case.
On this call we will briefly review work the teams are doing to identify and fix “weird” routes and then Steve Wallace will give a presentation on MANRS (https://www.manrs.org/)
Talk abstract: Overview of Mutually Agreed Norms for Routing Security (MANRS) for network operators. What’s required of number resource owners and network operators to benefit from MANRS, including insights into Internet Routing Registry records, the role of RIRs with RPKI route origin validation, and lessons learned in the case of North American R&E networks.
Thanks,
Hans
Hans Addleman is inviting you to a scheduled Zoom@IU meeting.
Topic: Routing Working Group - MANRS
Time: Sep 7, 2021 08:00 PM Indiana (East)
Join from computer or mobile:
https://iu.zoom.us/j/89302424995
Meeting ID: 893 0242 4995
One tap mobile
+16465588656,,89302424995# US (New York)
+13017158592,,89302424995# US (Washington DC)
Dial by your location
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
Meeting ID: 893 0242 4995
IU videoconferencing equipment: 26 893 0242 4995
Videoconferencing equipment outside of IU:
SIP: 89302424995(a)zoomcrc.com
H.323:
162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India Mumbai)
115.114.115.7 (India Hyderabad)
213.19.144.110 (Amsterdam Netherlands)
213.244.140.110 (Germany)
103.122.166.55 (Australia Sydney)
103.122.167.55 (Australia Melbourne)
209.9.211.110 (Hong Kong SAR)
64.211.144.160 (Brazil)
149.137.68.253 (Mexico)
69.174.57.160 (Canada Toronto)
65.39.152.160 (Canada Vancouver)
207.226.132.110 (Japan Tokyo)
149.137.24.110 (Japan Osaka)
Meeting ID: 893 0242 4995
Zoom@IU Team | cthelp(a)iu.edu | https://kb.iu.edu/d/bfqu
Hello all,
Thank you again for attending the Routing Working Group meeting. We appreciate everyone who participated today,
The link below is to the slides from today’s meeting
2021-08-17 Routing WG
I have also included a link to the RWG master case list for those interested in seeing the cases that we are working on and their status.
https://tinyurl.com/RWG-MCL
If you know anyone who is interested in joining the Routing Working Group please send their information to either me or Hans Addleman - addlema(a)iu.edu
We look forward to meeting you again on at the next meeting September 7, 8pm US Eastern time (12am UTC) for the
MANRS Talk by Steve Wallace. Look for a calendar invite soon for that meeting.
Thanks!
Brenna Meade
Indiana University International Networks
Folks,
I am new to GNA-G Routing WG, and may not have up to date information
on the current available resources.
As my understanding of BGP, it is not easy to give lower preference to
AS-PATHs which hop large oceans more than once by just using BGP
communities.
If there is a list of R&E networks including ASN, Country,
representing pingable IPv4 and IPv6 destinations, date and email of
last update, it may able to write a script to detect possible
suboptimal paths. Does anybody maintain such information?
Additionally, "machine readable" list of R&E links, not in beautiful
maps, may also help. It may need to include AS numbers of both ends,
bandwidth, and distance in km, date and email of last update. IXes can
also be represented by the AS numbers of the route servers with
special tag similar to type-2 OSPF LSA.
RADB may be referable, but it doesn't include all information we
may need. PeeringDB is similar. Moreover, many entries doesn't hold
completed information and may not be well updated.
Sincerely,
-- Akira Kato
