Here are the draft minutes of the routing WG held at the 21th RIPE meeting in Rome. Please give your comments, if any, before June 9. DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- Routing Working Group Minutes RIPE 21 Rome, May 8, 1995 Chairman: Willem v.d. Scheun ---------------------------- 1. Opening and agenda bashing Willem v.d. Scheun opened the session and welcomed everyone to the meeting. The agenda was agreed with some scheduling changes which will be reflected in the minutes. 2. Minutetaker Anne Lord volunteered to take the minutes. 3. Status of the Route Arbiter project, Elise Gerich, Merit 3.1 PRDB -> RADB transition. There was much discussion during and following Elise's presentation. The main points are: - May 8th (day of WG meeting) is the last day that NACR's will be accepted by Merit. After this date, old style NACR's will automatically be translated into ripe-181 compliant route objects. Objects should be sent to : <auto-dbm@ra.net> - If you have registrations in the PRDB your data will automatically be converted. - If you require connectivity to AS690 you will need to register your route in the RADB using the "advisory" tag. As AS690 config files are currently generated from the RADB only. - The "advisory" tag replaces the old-style NACRS but will be short term only The end of May was mentioned as the "short-term". - Global IRR schema means that registering in one RR should be sufficient. However, registering in more than one database will be allowed but not encouraged. Problem of determining priority when there are conflicts in RR data is still not solved. Question was asked concerning how to remove duplicates once priority issue was resolved? There was some discussion, but the problem has yet to be resolved. 3.2 RA Project Project began on July 1st, 1994 as collaboration between Merit, ISI (and IBM). ISI and IBM are responsible for the software development of the Route Server and advanced protocol development. Merit is responsible for development and maintenance of the RADB, network management and routing engineering. Current status: - 6 route servers (RS) are deployed: o 2 Mae East o Sprint NAP o Ameritech o PacBell o Mae West (not fully operational) - Main interconnection-point effort is focussed on Mae East. o 15 ISP's present o 11 peering with primary RS and backup o 6 import and exporting routes from RS. o none is yet fully dependant on RS. o only problems reported have been from Sprint. Elise reported that for the last 10 months RSes have been operational, although the fact has not been communicated since more network management tools were needed and the NOC does not yet have out of band access to the RSes. - Network Management Area development o deployed bi-lingual SNMP agent v.2 o Discovery Rover code - reports on state and topology of net. - NOC formerly ANS, now Merit, University of Michigan. - RADB is implementation of ripe-181. Some extensions to the syntax were necessary. Specifically there are now attributes: o extended-interas-in o entended-interas-out - PGP v.2.6 email authentication added. Development work done by Laurent Joncheray. Description of the mechanism can be found at: o http://www.ra.net o ftp://ftp.ra.net/routing-arbiter/tools/RAToolSet - Software development by Cengiz Alaettinoglu on tools that generate config files for ripe-181 policy expressions. Tools are (available from above URL's): o rtconfig o toolkit There was a question concering duration of project and available resources. The RA project is a 5 year project which will terminate in 1999. 14 people are working on the project. All the software is public domain. 4. Report on the population and usage of the routing registry - RIPE NCC - Maintainence of the RR is a RIPE NCC core activity. - Little time for actual work to date - current resources are 1 hour per day from Mirjam Kuehne and Anne Lord. - 3 stage workplan developed based on BGP dump of amsterdam.ripe.net o chase non-registrations of ripe-181 policy of EU ASes -> nag. o extract AS path and compare with registered policy -> nag. o develop tools to do above work auto-magically Comments: - Question concerning the consistency of route objects and the home AS. Is this part of the RR activity? Answer was yes, but focus of effort prioritised to above. - Registering in the RIPE RR is vital. When "advisory" tag goes away, some EU networks not registered may lose some connectivity. - Ideal end state is to register in one RR only. This should be sufficient for full connectivity. - Should be free (but not encouraged) to make multiple registrations. Currently some RR's require this (MCI & RADB). Seen as short-term (+/- 2 weeks). Advice for now is to make multiple registrations. - Currently RR's mirror each others databases. RIPE NCC will monitor dual registrations. 5. Routing Policy System (RPS) - Importance of ripe-181 acknowledged as document has become rfcxxxx standards track document. - IETF working group formed o rps - Charter o to develop a routing policy description language based on ripe-181. o co-ordinate efforts of various RR's - Co-chaired o Cengiz Alaettinoglu o Daniel Karrenberg. - Mailing list establised. To subscribe send mail to o <rps@isi.edu> o <rps-request@isi.edu> 6. CIDRD wg report (Danvers IETF) - ALE wg merged with CIDRD - ALE is now 2018 +/- 8 years - Analysis of address space utilisation was presented. Stats were taken from amsterdam1.dante.net. Figures showed that in 193/194 blocks there was an average of 4,000 hosts per route. CIDR works! - Routing table growth slowing down. Chief problems now seen to be route update processing and flapping. - Yakov Rekter presented paper which will soon become Internet Draft o "Address Ownership Considered Fatal" Paper discusses problems arising from portable address space. All ISP's encouraged to assign only "provider aggregatable" address space. "Provider independant" address space assigned by Regional Registries will offer no guarantee of routability. (will be determined by ISP's - some of whom claim to be filtering on longer prefixes.) Trade off between renumbering to ISP block when you move provider or paying for ISP to route your prefix. Uncertain how this will develop. Daniel Karrenberg asked for European input to document, which is vitally important. - rfc1597 stands and is on standards track. Comments in rfc1627 will be incorporated. 7. AOB Nothing was reported under AOB so the session was formally closed.