Your IP Address is: 3.144.97.189
Tip: try using "quotes around your search phrase"
You're viewing an archived page. It is no longer being updated.
RIPE Meeting: |
25 |
Working Group: |
Routing |
Status: |
Final |
Revision Number: |
2 |
Please mail comments/suggestions on:
Further remedial action was needed and the Contributors' Committee supported the NCC in this work. Skilled staff would soon be appointed and they would help ISPs in promoting route aggregation. While neither RIPE nor the NCC could take action against any offenders, the use of peer pressure among the ISPs could be used in a positive manner to improve the position.
The meeting encouraged ISPs to supply BGP data to the NCC on request for the purpose of analysing route aggregation.
New Action: the NCC would report on route aggregation at RIPE 26.
Compiled with C++ in a Tcl/Tk environment, ROE was easy to install. With its GUI it was easy to use. As not all IRRs were aligned in the way they worked, ROE displayed separate route registrations where appropriate.
Joachim found it slow in operation, although Cengiz later indicated that this was probably due to network and server performance and not to the ROE program execution. It was also not clear to Joachim whether live or mirrored IRR data was used.
He suggested that the program could be improved by allowing more configuration options and greater clarity in some of the messages. This and other feedback should be directed to Cengiz.
Overall, he recommended ROE for operational use, particularly for complex routing tasks.
They had encountered many instabilities from peers and found that many ISPs had not deployed CIDR; this gave rise to more flapping as more routes, and particularly more specific ones, were advertised.
Tony explained the parameters used for route dampening on a Cisco router. He had arrived at the following re-use times for various route sizes:
/24 and greater |
~160 minutes |
/23 and /22 |
~60 minutes |
/21 and less |
~30 minutes |
He recommended filtering out all prefixes more specific than /24.
While route dampening consumed router memory, this was more or less balanced by a reduction in routing CPU cycles.
He recommended that if route dampening was to be widely deployed in Europe, consistency was important. In this sense, the Routing WG should agree on guidelines for parameters to be used.
In discussion, the following points were made:
In summary, it was agreed that route dampening was an important topic and that more discussion was needed.
The set of front-end tools used a number of back-end libraries, which made program development easier. It required RAWhoisd v3.0 and had been ported to several operating systems. Cengiz gave details of availability (official reference) and of the mailing list ([email protected], subscription via robot [email protected]). The toolset was made available for demonstration purposes to attenders of RIPE 25.
RtConfig generated the BGP access list part ofrouter configuration from route objects. It was now used in production by some major network operators.
ROE was again shown, with reference to review options before submitting a changed route object.
The AS object editor (AOE) was not implemented, though it was on demo at RIPE 25.
CIDRAdvisor identifies 'safe' aggregates by route originators as well as aggregates for proxies. Cengiz showed the effects of using various radius values for the distance that aggregation should hold.
Mike Norris
23/9/96