Add the AODVv2 Routing Protocol

This PR depends on #1766.

It contains a minimal implementation of the AODVv2 routing protocol.
*Not* implemented are:

	- AckReqs
	- alternate metrics
	- multiple interfaces
	- clients and Client Networks
	- buffering
	- all addresses, TLVs, and features that are marked as optional

An example application can be found at https://github.com/Lotterleben/RIOT-AODVv2/tree/master/aodvv2_demo.

The implementation relies heavily on a functioning Neighbor Discovery Protocol.
It might be necessary to fill the neighbor cache manually with the current state
of RIOTs NDP implementation.

The value of AODVV2_MAX_UNREACHABLE_NODES has been chosen arbitrarily and will be subject to
future improvement.

Please note that based on my experience, with the default transceiver
buffer size (3) of the native port, about 2/3 of the route discoveries
will fail. This has been addressed in issue #1747. It is advised to increase
the transceiver buffer size when using AODVv2 as a routing protocol.
Ooooh, now I get it (I think)! The 3 stands for Hop Count (see http://tools.ietf.org/html/draft-ietf-manet-aodvv2-04#section-14.3), which should be noted accordingly, correct? With the current code, I came up with this: https://gist.github.com/Lotterleben/53a4c5b86c4be7367949 . Does that make sense?
(having a central metric enum for all routing protocols to use might be an idea as well, though, seeing as RPL uses RFC6551 as well and AODVv2 and OLSR may share metrics in the future...)