> > Well this is true, but 6833bis discusses RLOC-reachability and there > > is a RLOC-probe cache that will tell the ITR when it last heard from > > the RLOC. > > Just to be clear, it's not "last heard from" that you need, but > rather "last verifiably responded".
Right agree. > > > S 16. > > >> Map-Versioning is a Data-Plane mechanism used to signal a peering xTR > > >> that a local EID-to-RLOC mapping has been updated, so that the > > >> peering xTR uses LISP Control-Plane signaling message to retrieve a > > >> fresh mapping. This can be used by an attacker to forge the map- > > >> versioning field of a LISP encapsulated header and force an excessive > > >> amount of signaling between xTRs that may overload them. > > > > > > Can't I also set a super-high version number, thus gagging updates? > > > > It doesn’t matter the value. All that matters is that it changed and you > > should do to the mapping system to get an updated RLOC-set. > > Hmm... S 5.1 of 6834-bis suggests that you can just discard it. Luigi - what do you think. Do we need rewording? Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
