1 / 6

LISP Interoperability Testing

LISP Interoperability Testing. Margaret Wasserman mrw@sandstorm.net 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

vea
Télécharger la présentation

LISP Interoperability Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  5. Interoperability Matrix [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

More Related