1. LISP Interoperability Testing Margaret Wasserman mrw@sandstorm.net IETF 76, Hiroshima, Japan

2. 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

3. 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

4. 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

5. Interoperability Matrix Cisco LISPOpenLISPYes [1], Data only Cisco LISPLISP-ClickYes, Data only, IPv4 only Cisco LISPZLispYes [2], Data & Control OpenLispLISP-ClickYes [1], Data only, IPv4 only OpenLispZLispNo [3] Lisp-ClickZLispNo [3] [1] After bug fix(es) [2] After RLOC probe handling added to ZLisp [3] Incompatible map cache configuration mechanisms, not yet addressed

6. 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