A Future Tool Development Project Joachim Schmitz (JS395-RIPE)

Requirements
RIPE NCC Activities and Expenditures 1997
RR Tools
I n t e r n e t +-------------------+ | routers | . . . . . . . . . . . . . + +----------------------> |life configuration| <----------------------+ . | +-------------------+ | . | | | . | monitoring | RtConfig | . | and setup | | . | v | . | | | . v /| v v +-------+ / | aoe, roe +-------+ | | <-----------------+--|------------------------------------> | | | | / | | | | / | | | I S P | <-----------------+---------------------------------------- | I R R | | | pmatch, prtraceroute, IRRv | | | | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > | | | | prpath, prcheck, peval, CIDR advisor | | | | <---------------------------------------------------------- | | +-------+ whois, wais, web +-------+ | ^ | | +---------------------------------------------------------------------+ mail ------> unidirectional relation <-----> bidirectional relation . . . > possible relation
The following dicussion during the Routing WG session at RIPE27 showed that important tools already exist or are currently developed by other parties. It was generally felt that there is no immediate need for a RIPE tool development project. However, this area should be regularly reviewed (see Routing WG minutes).