Using static routes is fine for small networks, especially if you're using IPv6. That is a big address to be typing repeatedly. Remember that in static routes, the burden is on you to put in or take out any static routes as they change, so dynamic routing is the way to go.
RIPng is the same as in IPv4, when it comes to its characteristics. It is still a distance vector routing protocol, which means it will send periodic updates every 30 seconds. It still has a 15-hop count limitation and the timers are still the same.
What has changed is the multicast address. It is FF02::9 instead of 224.0.0.9, and as far as the configuration of RIPng goes, to be honest, it is much easier. You do not have to be worried about the no auto-summary command and you can enable RIPng on the interface that you want to participate in the RIP routing process. RIPng has a process ID number...
