EIDs in configuration commands should be validated
At the moment we do not validate EIDs in contact definitions - the "router" is still able to perform a "dumb" table lookup without caring about the EID scheme. As we now have to implement new EID schemes in the BPv7 parser anyway, we should remove that behavior and reject configuration commands with invalid EIDs with a proper error message.