% Like I said, most (techie) people don't give a hoot, but legal % departments at largish outfits can seriously halt Progress(tm). Although % RIPE and the RIPE NCC are non-profit organisations, most of the members % are most definitely out to make a (euro-)buck. It's only proper that if % these tools are to be hosted/provided/maintained by the RIPE NCC, that % the restrictive license is removed. Replacing it with a RIPE/RIPE NCC % copyright may make non-RIPE members nervous, so I still think a GNU-like % license is the safest and fairest option. I spect that the USC tag still claims that it needs to stay w/ the code so RIPE would need to do a "clean-room" reimplementation to expunge the USC tag. Of course RIPE could also cut a deal w/ USC on broad commercial use of the tools. That has often proved to be the cheapest/easiest course. % % Cheers, % Steven % -- --bill