Content deleted Content added
m CheckWiki 61 + General Fixes using AWB |
m Hyperlinked "(...) packet (...)" to the "Network packet" article |
||
Line 21:
Three of these devices are compliant to the HAIPE IS v3.0.2 specification while the remaining devices use the HAIPE IS version 1.3.5, which has a couple of notable limitations: no support for [[routing protocols]] or open [[network management]].
A HAIPE is an IP encryption device, looking up the destination IP address of a [[Network packet|packet]] in its internal Security Association Database (SAD) and picking the encrypted tunnel based on the appropriate entry. For new communications, HAIPEs use the internal Security Policy Database (SPD) to set up new tunnels with the appropriate algorithms and settings. By not supporting routing protocols the HAIPEs must be preprogrammed with [[static routing|static routes]] and cannot adjust to changing network topology. While manufacturers support centralized management of their devices through proprietary software,<ref>[http://www.viasat.com/government-communications/information-assurance/vine-manager-software ViaSat's VINE website]</ref><ref>[http://www.gdc4s.com/gem-x.html General Dynamics's GEM website]</ref> the current devices offer no management functionality through open protocols or standards.
Recently TELEGRID Technologies <ref>[http://www.telegrid.com TELEGRID Technologies]</ref> has produced a non proprietary manager <ref>[http://www.telegrid.com/TELEGRID_SMRT_Flyer.pdf TELEGRID SMRT Multiple HAIPE Remote Manager]</ref> for multiple HAIPE encryptors including the GD KG-175D, ViaSat KG-250 and Harris SecNet54 in addition to the KIV-7M LEF encryptor. Both the HAIPE IS v3 management and HAIPE device implementations are required to be compliant to the HAIPE IS version 3.0 common MIBs. Assurance of cross vendor interoperability may require additional effort. An example of a management application that supports HAIPE IS v3 is the L-3 Common HAIPE Manager.
| |||