Presentation on theme: "LISP Interoperability Testing Margaret Wasserman IETF 76, Hiroshima, Japan."— Presentation transcript:
LISP Interoperability Testing Margaret Wasserman firstname.lastname@example.org IETF 76, Hiroshima, Japan
Interoperability Tests Held in IETF terminal room on Monday evening Four implementations represented –Most combinations did interoperate –Two implementation bugs found –Other reasons for lack of interoperability are well- understood Some issues were addressed and interoperability verified later in the week
Implementation Status Cisco LISP Cisco NX-OS Control and data planes Static and dynamic map cache entries Echo nonce, RLOC probe, RLOC reachability IPv4, IPv6, Cross-AFI OpenLISP FreeBSD 7.x kernel Data plane only Static map cache entries RLOC reachability, map versioning IPv4, IPv6, Cross AFI
Implementation Status LISP-Click Click Java Framework Data plane only Static map cache entries Echo nonce, RLOC reachability IPv4 only ZLisp Portable C++ (Linux, FreeBSD, MacOS) Control and data planes Dynamic map cache entries Responds to RLOC probes IPv4, IPv6, Cross AFI
Interoperability Matrix Cisco LISPOpenLISPYes , Data only Cisco LISPLISP-ClickYes, Data only, IPv4 only Cisco LISPZLispYes , Data & Control OpenLispLISP-ClickYes , Data only, IPv4 only OpenLispZLispNo  Lisp-ClickZLispNo   After bug fix(es)  After RLOC probe handling added to ZLisp  Incompatible map cache configuration mechanisms, not yet addressed
Possible Specification Issues Should it be mandatory to support RLOC Probes? –If not, flag is needed in map reply to indicate support for RLOC probing Support for map request/map reply needs to be mandatory, or static map cache entries need to be mandatory, or both
Your consent to our cookies if you continue to use this website.