1996-07-01 - Re: FTS2000 and Encryption?

Header Data

From: frantz@netcom.com (Bill Frantz)
To: “Mark O. Aldrich” <nson@kpmg.com
Message Hash: c281b4d77a730e159ca471ce3f5183c7df4ecfa7fb841f000d92029e91c58c34
Message ID: <199606302228.PAA19168@netcom7.netcom.com>
Reply To: N/A
UTC Datetime: 1996-07-01 07:45:40 UTC
Raw Date: Mon, 1 Jul 1996 15:45:40 +0800

Raw message

From: frantz@netcom.com (Bill Frantz)
Date: Mon, 1 Jul 1996 15:45:40 +0800
To: "Mark O. Aldrich" <nson@kpmg.com
Subject: Re: FTS2000 and Encryption?
Message-ID: <199606302228.PAA19168@netcom7.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


At  1:57 PM 6/30/96 -0400, Mark O. Aldrich wrote:
>... The [FTS2000 follow-on contract - WSF]
>security policy and RFP materials are on the 'net (I can't get to the web
>right now, or I'd post the URL with this message).

Please post the URL when you can.


>From what I remember,
>the RFP does state that all payload data will be encrypted by the
>Government using NSA-approved crypto and that the vendors are not to
>"worry about" what's in the payloads.  All they have to do is carry it
>from point a to point b.

Given that FTS2000 supports X.25 Packet Assembly Disassembly (PADs), there
is a wide field ahead for screwing up such useful features as 8-bit
transparent characters and data forwarding (i.e. When does the PAD decide
it has a complete packet and actually send it).  Try running emacs without
good data forwarding control.


-------------------------------------------------------------------------
Bill Frantz       | The Internet may fairly be | Periwinkle -- Consulting
(408)356-8506     | regarded as a never-ending | 16345 Englewood Ave.
frantz@netcom.com | worldwide conversation.    | Los Gatos, CA 95032, USA







Thread