Inconsistency between MD-SAL and DAO when EID-URI doesn't match mapping or key EID

It is possible to add keys or mappings with different eid URIs using the same actual EID stored in the LispAddressContainer/maskLenght combination. In that case, the MD-SAL config datastore will have multiple mappings, while the DAO only one.

EXAMPLE
-------

PUT http://localhost:8181/restconf/config/lfm-mapping-database:mapping-database/instance-id/0/authentication-key/192.0.2.1/

{
"authentication-key": {
"eid": "192.0.2.1",
"LispAddressContainer": {
"Ipv4Address":

{ "afi": 1, "Ipv4Address": "192.0.2.1" }

},
"mask-length": 32,
"key-type": 1,
"authkey": "password"
}
}

—

PUT http://localhost:8181/restconf/config/lfm-mapping-database:mapping-database/instance-id/0/authentication-key/192.0.2.1bis/

{
"authentication-key": {
"eid": "192.0.2.1bis",
"LispAddressContainer": {
"Ipv4Address":

{ "afi": 1, "Ipv4Address": "192.0.2.1" }

},
"mask-length": 32,
"key-type": 1,
"authkey": "password"
}
}

MD-SAL config datastore will have two mappings, one for '192.0.2.1' and one for '192.0.2.1bis', while the DAO will have single entry for 192.0.2.1/32.