git hash: 57fe8fc59843aff7f967bdeca97754d104dfaa9c

With initial following mapping
{
"input": {
"mapping-record": {
"recordTtl": 1440,
"action": "NoAction",
"authoritative": true,
"eid": {
"address-type": "ietf-lisp-address-types:source-dest-key-lcaf",
"source-dest-key":

{ "source": "6.0.1.0/24", "dest": "6.0.2.0/24" }

},
"LocatorRecord": [
{
"locator-id": "ISP1",
"priority": 1,
"weight": 1,
"multicastPriority": 255,
"multicastWeight": 0,
"localLocator": true,
"rlocProbed": false,
"routed": false,
"rloc":

{ "address-type": "ietf-lisp-address-types:ipv4-afi", "ipv4": "6.0.3.2" }

}
]
}
}
}

map-resolver received a src/dst map request triggered by source 6.0.1.2 and replied with the the mapping above as expected.
Then a new negative mapping is installed:

{
"input": {
"mapping-record": {
"recordTtl": 1440,
"action": "NoAction",
"authoritative": true,
"eid": {
"address-type": "ietf-lisp-address-types:source-dest-key-lcaf",
"source-dest-key":

{ "source": "6.0.0.0/16", "dest": "6.0.2.0/24" }

}
}
}
}

Notice that source part of src/dst key is a super-set prefix of the source in the existing mapping.
After this I deleted the old mapping 6.0.1.0/24|6.0.2.0/24 which resulted in SMR. Map resolver eventually received smr triggered map request and replied with negative mapping with 6.0.1.0/24|6.0.2.0/24 key instead of 6.0.0.0/16|6.0.2.0/24 as one would expect.

Apart from that the map-reply contained invalid TTL value - instead of 1440 wireshark showed value 15.