<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 11.00.9600.17842"></HEAD>
<BODY>
<DIV><FONT size=2 face=Arial>Hey Everyone,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>During the Bundle Security telecom last week, I
took the action to wedge the Cryptographic Message Syntax (CMS) into BP,
for use in signing and encryption. Here are the results:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><STRONG><FONT size=2 face=Arial>Software
Implementation:</FONT></STRONG></DIV>
<DIV><FONT size=2 face=Arial>For this testing, I used a random payload, passed
that through the CMS implementation (OpenSSL), using a pre-shared 1024b RSA
key in an X509 certificate. The enveloped data was outputted in DER encoding
(Base64)<STRONG>. </STRONG>It is important to note that this is not S-MIME. The
DER-ified data was added as a bundle payload. </FONT><FONT size=2 face=Arial>For
future testing, it should be possible</FONT> <FONT size=2 face=Arial>to
update (or dynamically generate) the X509 stuff, where we can set the FROM/TO
addressed to the src/dest EID's. </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I ran two tests, signing and
verification...</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><STRONG><FONT size=2 face=Arial>Measurement
Methodology:</FONT></STRONG></DIV>
<DIV><STRONG><FONT size=2 face=Arial></FONT></STRONG> </DIV>
<DIV><FONT size=2 face=Arial>All of the numbers below were taken from the
receiver side. In other words, the "pre-signing/encryption" sizes were based
upon successfully decrypting or verifying the data at the end of the
pipe.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><STRONG><FONT size=2 face=Arial>Results -
Signing:</FONT></STRONG></DIV><IMG src="cid:788143909@30062015-3797">
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>There are two subtests here, one where I carried
the CMS signer cert within the data, and one where I didn't. As you can see, the
overhead isn't terrible, especially when you consider that (in some of the
tests) I was carrying the cert down the wire. You can also stack signer
certificates within a single CMS message, though I opted to not do that (for
simplicity) until we have a further plan for CMS.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><STRONG><FONT size=2 face=Arial>Results - Encryption:</FONT></STRONG></DIV>
<DIV><FONT size=2 face=Arial>I'm going to prefix this by saying that I really
didn't need a graph for this one, but graphs are cool, and if I write enough
here, it will look like a proper headline... So, graphs:</FONT></DIV>
<DIV><IMG src="cid:788143909@30062015-379E"></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Once again, the overhead isn't awful, at
<STRONG>349</STRONG> bytes.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><STRONG><FONT size=2 face=Arial>Where Do We Go From
Here:</FONT></STRONG></DIV>
<DIV><FONT size=2 face=Arial>I have no idea, though I'm tempted to say that this
is a discussion for Darmstadt.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></BODY></HTML>