1. RIPv2 is what you would definitely use if you were going to go that way. The vast majority of networks I see are running OSPF, followed by basic static routes, and RIPv2 running last.
2. You can use MD5 authentication, can't remember if ProCurves support this though, quick look through the manual should verify this.
3. Good question, RIP can use auto-summary, so if you did have a large RIP network and you planned it correctly, it shouldn't be an issue. You'll run into other scalability problems before you hit that limit.
3. A single RIP packet can advertise 25 routes. It just sends more packets when there are more routes than this. However the maximum amount of routes is going to depend on the router you're using.
>2. You can use MD5 authentication, can't >remember if ProCurves support this though, >quick look through the manual should verify this.
I did some looking, but could not find any command to enable this. Would that mean that the RIP "password" is just clear text and any device that could send RIP packets could be able to insert incorrect routing entries in the network?
