This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] RIPE 71, RIPE 72, and co-chair
- Previous message (by thread): [routing-wg] New on RIPE Labs: Tools to Detect Routing Anomalies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Thu Mar 31 17:06:21 CEST 2016
Hi all, RIPE 72 is approaching, and we're looking for two things. First of all -- content! If you have topics you'd like to see discussed, especially if you'd be willing to lead the discussion or presentation, then please let Joao and myself know via <routing-wg-chairs at ripe.net>. In addition to the scheduled Routing WG session, we also plan to have a joint Routing-DB session to see if we can actually make some progress around the topic of non-authoritative routing registry information in the RIPE DB. Secondly -- co-chair! As I mentioned at the end of our last meeting, it is my turn to stand down as co-chair and we're on the lookout for volunteers to co-chair the WG. A dated document describing the duties of the WG co-chairs is here: <https://www.ripe.net/publications/docs/ripe-542> Since that was published the PC has taken on responsibility for leading the plenary sessions and a sub-group of the WG chairs collective now oversees the policy development process, so it's even easier than it was before. If you have ideas about what we can do in the group, ideas about how to do it, and are able to attend most of the RIPE meetings, please let Joao and myself know via the email address above. We will follow the process that we loosely documented on the list, archived at the following URL, and achieve consensus on a co-chair. <https://www.ripe.net/participate/ripe/wg/routing/routing-wg-chair-selection-process> In a sign that I might be growing increasingly senile, or just drunk-in-charge-of-a-WG, I omitted to forward the draft minutes of RIPE 71 to the list when the NCC sent them around Christmas-time. Please find them appended and let Joao and myself know of any changes. Cheers, Rob Routing Working Group - RIPE 71 Thursday, 19 November 2015, 9:00-10:30 WG Co-Chairs:João Damas, Rob Evans Scribe: Anand Buddhev 1. Administrivia WG co-chair Joao Damas opened the session. Joao asked for comments about the draft minutes of RIPE 70. There were no comments, and he declared them approved. 2. Isolario - Luca Sani The presentation is available at: https://ripe71.ripe.net/presentations/12-pres.pdf Joao Damas asked about the future of this project, and whether it will be supported. Luca answered that his institution plans to support it. A Simple BGP - Alexander Azimov The presentation is available at: https://ripe71.ripe.net/presentations/162-A-Simple-BGP.pdf Warren Kumari (Google) commented that there is a draft by Jared Mauch and Job Snijders that achieves almost all the goals in this presentation. Alexander said that the draft came out around the same time he started his work. He said the draft is about filtering route leaks, whereas his work is about avoiding them. Randy Bush (IIJ) explained in detail about how this proposal is better than Brian Dixon's proposal, because it allows both parties to agree to a policy in the BGP OPEN message, rather than basing the route announcements on a marker applied to routes. This makes it more robust to accidental route leaks. RIS Updates - Colin Petrie, RIPE NCC Kaveh Ranjbar (RIPE NCC) commented to the WG that at the last meeting, the community asked for more RIS collectors to be deployed. He said that the RIPE NCC will certainly expand into areas that are currently not well-covered, such as Australia and New Zealand. He then asked the audience two questions and asked for people to raise hands: 1. What scale should the expansion be at? Would a few more collectors, say 15, be enough, or should be more like 50 to 100? 2. Whether RIPE NCC should deploy collectors in large ISP networks to get a different view. Joao Damas asked whether this was to get a view inside an ISP network, or still get an external view but from an ISP's perspective. Kaveh said he meant the latter. Kaveh asked for a show of hands, and there was little support for this option. Turris - Ondrej Filip The presentation is available at: https://ripe71.ripe.net/presentations/181-Turris-20151119-OF-RIPE.pdf Mick O'Donovan (BT Ireland) commended Ondrej for this project. Joao Damas also added his commendation and hoped that other manufacturers would pick up this work, so that the quality of devices out on the Internet would improve. Csaba Mate (NIIF/Hungarnet) asked whether there were any plans to release just the board, without the switch ports. Ondrej said that they have to produce large volumes to keep the costs reasonable, and so they don't plan on variants at this early stage. He added that the hardware design is open, and said anyone can produce a variant board by themselves. Jen Linkova (Google) asked about IPv6 support. Ondrej said that it was no longer neceesary to talk about IPv6 separately. He implied that it was a given. BGP collector Communities - Randy Bush and Emile Aben The presentation is available at: https://ripe71.ripe.net/presentations/159-151119.ripe-rtg.pdf Jen Linkova (Google) asked why Randy classified a hijack as an intention of misorigination and not as an intentional leak. Randy replied that it was possible to divide the hijacks into categories besed on intent or no intent. Warren Kumari (Google) asked what Randy meant by "route processing time". Randy said he meant the time taken to start sending a full stream. He said they had eliminated the RIB to FIB timing, because that was the classic trap. Peter Hessler (Hostserver) asked how Randy would deal with an organisation that has 32-bit ASN. Randy said he didn't know, and invited Peter to contribute to a draft. Ruediger Volk (Deutsche Telekom) commented that he would be unhappy if someone tried to interfere with his organisation's internal communities setup. He said he would not mind if a route collector asked for specific community tags, as long as they described the whole topology, rather than just something specific to that collector. Randy said that trying to describe how to do the whole topology would be rather difficult. Ruediger then asked whether Randy was asking for these specific communities to sent just to router collectors, or to other peers to. Randy said that these communities needn't be sent to other peers, but one could, if one wished. Ruediger then added that if he tagged his routes with communities and sent them to other peers, who then propagated them to Randy, he would see more interesting stuff. Randy replied that he didn't really want to see that. He said it was always possible to see which ASN a peer has because of the peering relationship. AOB Sander Steffann said that the issue of communities for 32-bit ASNs had come up in the Address Policy WG, and he asked them whether the routing WG should take this to the IETF. There was overwhelming support for this in the APWG, so the Routing WG will now take this to the IETF. He asked for questions. There were none, and there was loud applause. Dario Rossi asked for help with the Anycasters project. He said if anyone could provide BGP feeds, it would be good, and invited people to talk to him. Finally, Rob Evans announced that at the next RIPE Meeting, he would be stepping down as co-chair. He said that if anyone wished to take on this role, they should go and speak with him or Joao.
- Previous message (by thread): [routing-wg] New on RIPE Labs: Tools to Detect Routing Anomalies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]