Implementation Report for IP Payload Compression Protocol (IPComp) ------------------------------------------------------------------ Date of report: 2001-4-15 The IP Payload Compression Protocol (IPComp) is defined in RFC2393 with clarifications in rfc2393bis I-D. About twenty independent IPComp implementations have been tested for interoperability at two VPN Workshops in San Diego, CA: September 18-22, 2000 January 10-14, 2000 The following implementations take part in the report: Check Point Cisco Efficient Networks HiFn Indus River (Enterasys Networks) IRE KAME Linux FreeS/WAN Lucent NetLOCK SSH VPNet The interoperability report has two parts: * The description of the implementations, ordered by company/organization name. * A table of pairs of interoperability tests and the features the parties tested. Part I: Implementations description ----------------------------------- Note: Implementations in {} did not confirm participation in the report. 1. Check Point Software Technologies Contact: Tamir Zegman Product: VPN-1 IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): N Negotiation method: Manually configured: N IKE: Y Encapsulation Tunnel: Y Transport: N In the environment of IPsec Negotiated with ESP: Y Stand-alone N Interoperated with: IRE {Network Associates} 2. Cisco Systems, Inc. Contact: Scott Fluhrer Product: Cisco IOS IPsec IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): N RFC2395 (LZS): Y Negotiation method: Manually configured: N IKE: Y Encapsulation Tunnel: Y Transport: N In the environment of IPsec Negotiated with ESP: Y Stand-alone: N Interoperated with: HiFn, Indus River Networks, VPNet 3. Efficient Networks, Inc. Contact: Stan Fickes sfickes@efficient.com Product: SpeedStream 5000 routers IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): N RFC2395 (LZS): Y Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone N Interoperated with: HiFn. 4. Hifn Contact: Arvind Chadda Product: IPSECure IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): N RFC2395 (LZS): Y Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of Ipsec Negotiated with ESP: Y Stand-alone: N Interoperated with: Cisco, Efficient Networks, Indus River Networks 5. Indus River Networks Contact: Ben McCann Product: RiverWorks Enterprise VPN Note: Since the VPN Workshops, Indus River Networks was acquired by Enterasys Networks, and the updated details are Enterasys Networks Contact: Ben McCann Product: Aurorean VPN Compression algorithm: LZS Negotiation: IKE IPv4, Tunnel, with IPsec ESP IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): N RFC2395 (LZS): Y Negotiation method: Manually configured: N IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone: N Interoperation with : Cisco, HiFn {Lucent}, {Nortel Networks}, {Nx Networks} 6. IRE Contact: Brian Price or Product: SafeNet IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): Y Negotiation method: Manually configured: N IKE: Y Encapsulation Tunnel: Y Transport: N In the environment of IPsec Negotiated with ESP: Y Stand-alone: N Interoperated with: Check Point, KAME, Lucent {Network Associates Gauntlet}, {Nx Networks} 7. KAME Contact: Jun-ichiro Hagino Product: KAME/*BSD IP protocol version IPv4: Y IPv6: Y Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): N Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone: Y Interoperated with: IRE, SSH 8. LINUX FreeS/WAN Contact: Hugh Daniel Product: LINUX FreeS/WAN IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): N Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone: N Interoperated with: 9. Lucent Technologies Contact: David W. Faucher Product: IPsec/IKE Toolkit IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): N Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone: Y Interoperated with: IRE {IBM OS/400}, {NetLOCK}, {RSA} 10. NetLOCK Technologies Contact: Don Johnson Product: NetLOCK IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): N Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone: Y Interoperated with: {F-Secure} 11. SSH Communications Security Corp Contact: Markku Rossi Product: IPSEC Express 4.0 IP protocol version IPv4: Y IPv6: Y Compression algorithm RFC2394 (DEFLATE): Y RFC2395 (LZS): Y Negotiation method: Manually configured: Y IKE: Y Encapsulation Tunnel: Y Transport: Y In the environment of IPsec Negotiated with ESP: Y Stand-alone: Y Interoperated with: KAME 12. VPNet Contact: Rajesh Mohan Product: VPNOS v3.0 IP protocol version IPv4: Y IPv6: N Compression algorithm RFC2394 (DEFLATE): N RFC2395 (LZS): Y Negotiation method: Manually configured: N IKE: Y Encapsulation Tunnel: Y Transport: N In the environment of IPsec Negotiated with ESP: Y Stand-alone: N Interoperation with : Cisco {Lucent (Xedia)}, {TimeStep (PREMIT Gateway)}, {TimeStep (Client)}, {Network Associates}, {Nortel} Part II: Interoperability tests ------------------------------- | IP version | Algorithm | Encapsulation | | Parties | IPv6 IPv4 | DEFLATE LZS | Tunnel Transport | Note | -------------------|------------|-------------|------------------|------| Check Point | N Y | Y N | Y N | (2) | IRE | | | | | -------------------|------------|-------------|------------------|------| Cisco Systems | N Y | N Y | Y N | | HiFn | | | | | -------------------|------------|-------------|------------------|------| Cisco Systems | N Y | N Y | Y N | | Indus River | | | | | -------------------|------------|-------------|------------------|------| Cisco Systems | N Y | N Y | Y N | | VPNet | | | | | -------------------|------------|-------------|------------------|------| Efficient Networks | N Y | N Y | Y N | | HiFn | | | | | -------------------|------------|-------------|------------------|------| HiFn | N Y | N Y | Y N | | Indus River | | | | | -------------------|------------|-------------|------------------|------| IRE | N Y | Y N | Y N | (2) | KAME | | | | | -------------------|------------|-------------|------------------|------| IRE | N Y | Y N | Y N | (2) | Lucent Technologies| | | | | -------------------|------------|-------------|------------------|------| KAME | Y Y | Y N | N Y | | SSH Communications | | | | | -------------------|------------|-------------|------------------|------| Notes for the above table: (1) All tests were negotiated via IKE as part of an IPsec Protection Suite. i.e. with ESP. (2) IRE reported failures by other parties in passing very large packets.