<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Attached is a set of patches to enable coexistence of FC-SP-2 protocol with IPSec for IKE negotiation. The full codebase is available on a github fork as well:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <a href="https://github.com/cwinkler-marvell/strongswan.git">
https://github.com/cwinkler-marvell/strongswan.git</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Below is detailed information about this request:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Introduction<o:p></o:p></p>
<p class="MsoNormal">============<o:p></o:p></p>
<p class="MsoNormal">FC-SP-2 is a protocol that was developed to implement security in Fibre Channel fabric.
<o:p></o:p></p>
<p class="MsoNormal">FC-SP-2 requires both - end point authentication and data in flight encryption/decryption.
<o:p></o:p></p>
<p class="MsoNormal">Marvell has taken this specification and is progressing towards providing full implementation
<o:p></o:p></p>
<p class="MsoNormal">of this protocol through hardware, firmware, drivers and application layers. Marvell has
<o:p></o:p></p>
<p class="MsoNormal">selected strongSwan as the best choice for negotiating encryption keys using IKEv2 but
<o:p></o:p></p>
<p class="MsoNormal">must extend the capabilities of IPSec into the particular requirements of FC-SP-2 Fibre Channel.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Key Differences between IPSec and FC-SP-2<o:p></o:p></p>
<p class="MsoNormal">========================================<o:p></o:p></p>
<p class="MsoNormal">1. The most obvious difference is that IPSec uses IP as its transport layer where FC-SP-2 uses Fibre Channel.
<o:p></o:p></p>
<p class="MsoNormal"> Fibre Channel does not have an IP address but uses the WWPN and a PID (port ID) to create a tuple for a connection.
<o:p></o:p></p>
<p class="MsoNormal"> This creates two specific needs within strongSwan for the FC-SP-2 plugin that Marvell has developed called auth-els:<o:p></o:p></p>
<p class="MsoNormal"> a. The PID is carried in 3 bytes of the IPv4 address.<o:p></o:p></p>
<p class="MsoNormal"> b. The connections are managed by the auth-els plugin because IP sockets are not used.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2. The second difference is that the encryption keys do not go to the kernel but are managed
<o:p></o:p></p>
<p class="MsoNormal"> by the HW, FW and driver on the PCI-e card for Fibre Channel. This requires all kernel interface calls,
<o:p></o:p></p>
<p class="MsoNormal"> such as add_sa, delete_sa, etc, to be routed to the auth-els plugin and not the kernel.
<o:p></o:p></p>
<p class="MsoNormal"> The routing of these kernel calls is based on the address family (AF_xxx) stored in the host object.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Proposed core changes required to support FC-SP-2<o:p></o:p></p>
<p class="MsoNormal">=================================================<o:p></o:p></p>
<p class="MsoNormal">1. host object: Since there is no AF_FC, identifying Fibre Channel hosts is done with AF_NETLINK which is
<o:p></o:p></p>
<p class="MsoNormal"> not used except in isolated applications. The overloading of AF_NETLINK may be fixed in the future if
<o:p></o:p></p>
<p class="MsoNormal"> an appropriate address family (AF_xxx) is created.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">2. libcharon/network/socket_manager: <o:p></o:p></p>
<p class="MsoNormal"> a. Create separate IP socket and FC socket.<o:p></o:p></p>
<p class="MsoNormal"> b. Route socket calls to the appropriate socket based on AF type.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">3. libcharon/kernel/kernel interface:<o:p></o:p></p>
<p class="MsoNormal"> a. Create a separate fc_sp interface in addition to the ipsec interface.<o:p></o:p></p>
<p class="MsoNormal"> b. Route kernel calls to the appropriate "kernel" based on the AF type.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">4. Other minor changes required to handle the Fibre Channel addressing differences such as changes to the traffic selector.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Status of development<o:p></o:p></p>
<p class="MsoNormal">=====================<o:p></o:p></p>
<p class="MsoNormal">A full implementation of a local version of strongSwan has been developed that supports IPSec and FC-SP-2 where secure traffic<o:p></o:p></p>
<p class="MsoNormal">of both types is running after IKE negotiation completes for each connection type. A suite of tests to insure that IPSec is not<o:p></o:p></p>
<p class="MsoNormal">affected by core changes in anyway has been completed. Set of patches can be provided when requested.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>