[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CmnLn Elec Exch: 3/05 Minutes (via listserve)
CommonLine Electronic Exchange subcommittee minutes for 03/05/98.
-
Russ Judd Great Lakes rjudd@glhec.org
Scott Fullerton* Great Lakes(Chair) sfullerton@glhec.org
Karl Ebert SLMA 105502.3154@CompuServe.Com
John Falconer SLMA
Frank Hum SLMA franklin.r.hum.jr@slma.com
Libby Meeker SLMA Libby.Meeker@SLMA.com
Gary Thomas* SLMA 70664.401@compuserve.com
Mike Nolan PHEAA mnolan@pheaa.org
Darwin Peiffer* PHEAA dpeiffer@pheaa.org
Terry Zuch PHEAA tzuch@pheaa.org
John Hall PHEAA
Linda Laub PHEAA llaub@pheaa.org
Jeff Knass USA Group jknass@usagroup.com
Brian Allison* USA Group BALLISON@usagroup.com
Ron Clark USA Group rclark@usagroup.com
Paul Logston* USA Group plogston@usagroup.com
Mike Brannon USA Group MBrannon@usagroup.com
Matt Parrett USA Group mparrett@usagroup.com
Ki Ha NELA kiha@nela.net
Gary Burleson* TGSLC gary.burleson@tgslc.org
Kelly Klipple TGSLC kelly.klipple@tgslc.org
Will Thien TGSLC will.thien@tgslc.org
Warren Sherard Edfund wsherard@edfund.org
Patrick Walters SLFC waltersp@slf.org
Gad Hazum Access ghazum@accessgrp.org
Ed McGowan ESF emcgowan@esfweb.com
Ruth Smith NYHESC rsmith@hesc.com
Kevin Malmberg NYHESC kmalmberg@hesc.com
Mike Schoeppler NYHESC mschoeppler@hesc.com
Betty Hansman* ISAC bhansman@isc016r1.state.il.us
Mike Yip ISAC
Debbie Phillips* ISAC dphillip@isc016r1.state.il.us
Fred Highsmith* Guarantech fhighsmith@guarantec.com
Tim Hearley* KHEAA thearley@kheaa.com
Mark Lifland Nellie Mae mark_lifland@nelliemae.com
Goeff Boisvert Nellie Mae geoff_boisvert@nelliemae.com
Doug McCaleb* Nellie Mae doug_mccaleb@nelliemae.org
Tom Jurado AFSA twjurado@aol.com
Bill Horn* College Foundation whorn@cfi-nc.org
Brian Jackman* Network Associates Incorported (guest) bjackman@pgp.com
(970.491.9555)
* = present
=================
*SUMMARY*
Brian Jackman, manager of OEM sales at Network Associates Inc.(NAI),
attended to answer questions about the NAI offer to CommonLine members.
Following this, the group discussed the matter. Members were unanimously in
favor of proceeding with the offer but noted issues yet to be resolved. The
offer and issues will be discussed at the San Antonio meeting. Next
subcommittee meeting: 3/12/98.
==================
*DISCUSSION WITH BRIAN JACKMAN*
These questions were discussed:
-
1) Support.
Q.
a>
Q. We want some level of confidence that there will be sufficient expertise
available.
A. Howard Fritz and Mike Vernon (who was involved in the development of the
4.x versions) are available for tech support. Howard would be the primary
and Mike, the secondary.
As to assurance of available expertise should they quit, Brian will find out
and get back to us (awaiting answer).
b>
Q. Will NAI support the use of the 16- and 32-bit toolkit(s), Viacrypt
PGP/BE for Windows v4.0 and PGP for Windows V4.5.1.
A. Yes.
c>
Q. Is there a separate cost for support?
A. No. That is included in the licensing. This arrangement will hold until
May 1999.
d>
SBS users will obtain support from SBS vendors and not PGP.
-
2) Distribution of media.
a>
Q. When can we expect media to become available to those still needing it?
A. As soon as NAI gets the list of contacts, they will cut CD’s and send the
media.
b>
Q. Will this include the set of products mentioned above?
A.yes.
-
3) Price for Media/Versions included.
Q. Brian's message indicates the price for the SDK as $130.50. Does this
cover access to the products listed above?
A. Yes. It covers the versions 4.x and toolkits as well as the SDK.
-
4) License Upgrade/Transfer.
Q. Are licenses transferable when upgrading to newer versions. That is,
when we upgrade to the SDK, can we transfer license at no cost?
A. Yes. We can use those licenses to “upgrade” encryption technology
embedded in our software at no extra charge. Their interest is to move us
as quickly as possible to the SDK and Diffie-Hellman (or whatever their
current release happens to be)by May 1999. They are offering free upgrades
as an incentive in this direction.
-
5) Code escrow.
Q. Should support become unavailable before the end of the transition
period, we would like source code to be held in escrow.
A. Brian will find out and let us know (awaiting answer)
-
6) Advance notification of final chance to purchase.
Q. Should it happen that licensing RSA no longer becomes an option (because
of the outcome of negotiations between NAI and RSA DSI or for any other
reason) we would like to be notified in advance to give us the option to
purchase more. Is this possible?
A. We can expect at least two weeks notice. It is more likely we will have
a full quarter (3-months) notice.
-
7) Transfer of licenses.
Q. Could NCHELP or some agency purchase extra licenses to transfer to
late-comers to CommonLine should licensing of RSA products be terminated
before the end of the transition period?
A. Not yet answered.
-
8) How to count licenses.
As we understand it a license is required for each public/private key use.
a>
Q. If an SBS is installed on a LAN with more than one workstation using it,
and if they all are using the same private/public key pair, does this count
as one licensed use or more?
A. That would constitute a single license use.
b>
Q. If a user should replace a key with another, would that still require a
single license?
A. Yes. Users may change their key set and still be in compliance under a
single license.
c>
Q. If a school has branches, could each add a different user-id to the same
key, and would that still require a single license?
A. Yes.
d>
Q. If we were to install the software over multiple physical locations and
all sites were to share the same public/prive key, would that constitute a
single license use?
A. Yes, although to do this may prove impractical and certainly not worth
the effort to save $25.
-
9) Sharing development software among developers.
Q. Will companies need to purchase a CD for each member of a development
team?
A. No. One $130.50 purchase will suffice for all development effort within
a company.
-
10) Follow-on purchases
a>
Q. If NAI is still able to license the RSA algorithm and we want to purchase
more licenses after March, will we be able to do so under the same terms?
A. Yes. As long as it is before May 1999
b>
Q. If during this time we want to purchase license for the SDK. Can we do
so under the same terms?
A. Yes.
c>
Q. Since the license is $20 for PGP and $5 royalties for RSA, if we were to
purchase license for SDK (before May 1999) would it cost $20 or $25?
A. $20
-
11) Duration of terms
These terms are applicable through May 1999. After that time, purchases
would fall under a new arrangement where maintenance would be a percentage
of purchase.
-
12) Products for non-Windows platforms
a>
Q. Are there end-user products available to run on SUN E3000? On Data
General 8500?
A. Brian will find out (awaiting answer)
b>
Q. There is a version for MVS that is a port of 4.x. What will happen to
that in the future?
A. We should check with the vendor of that product (NEON systems?)
-
13) Language support
Q. The SDK only supports C/C++. Does NAI anticipate including support for
other languages?
A. They are hoping to have support for VB, Delphi, and Java.
========================
*SUBCOMMITTEE RESPONSE*
After Brian Jackman signed off, the group discussed the offer. There was
unanimous agreement that it was very attractive, one which we should pursue.
Several indicated a strong interest in the possibility of VB support in
forthcoming releases of the SDK.
-
Members of the group identified several issues requiring resolution.
ISAC
1) We will still have to address the problem of how to (or whether to)
provide for late-comers wanting to join CommonLine after the time when RSA
is no longer available.
2) To proceed with this agreement implies the need to change the encryption
algorithm next year. Since we can’t all change at once, this means that
Service Providers will need to support both PGP with RSA and its successor.
Of course we won’t have to switch come May 1999, but if RSA is no longer
available, there will be a lot of pressure to do so.
KHEAA
Lenders and schools should be informed of their obligation to purchase
end-user software and/or licenses.
========================
*ELECTRONIC EXCHANGE LISTSERVE*
These minutes will go out via the standard distribution list and the
Electronic Exchange listserve. After this, the listserve will be the
exclusive means for delivery.
-
They can be viewed with a browser at the archive site
http://lists.glhec.org/cl-elec-exch (case sensitive).
-
To subscribe to the listserve, send a message to
cl-elec-exch-request@lists.glhec.org.
Put the word subscribe in the body of the message (You may make the subject
anything you want).
-
To post to the listserve send messages to cl-elec-exch@lists.glhec.org (You
must first have subscribed).
--------------------------------
*ADDENDUM REVISION*
Proposed changes so far include the following:
1.) Replace references to PGP Inc. with Network Associates. The first
reference could read Network Associates (formerly PGP Inc.)
.
2.) Change text on page 12 under "Setup: Initial Distribution of Keys"
paragraph 2 bullet 2. Where it reads CL COMM UPDATE <recipient name>, it
should read CL COMM UPDATE <sender name>
.
If you have any further revisions to suggest, please send them to me
(sfullerton@glhec.org)
--------------------------------
*PLEASE BE SURE TO SEND IN BILLING INFORMAITON*
If you haven't already done so, send billing information to Scott, who will
forward it to InPhoneMation. Active members of the subcommittee MUST FILL
THIS OUT. If several members always call in together to the meetings, we
would then only need information for one of them. Please provide the
following.
.
Name (Used to identify yourself upon calling in):
Organization:
Billing Address:
Telephone Number:
e-mail:
Fax:
--------------------------------
NEXT SCHEDULED MEETING:
Thursday 3/12/98 10AM Central Time. The number to call is (800) 374-8567.
When asked for the name of the conference, reply "CommonLine Electronic
Exchange." If asked for the host's name, reply "Scott Fullerton"
------------
Agenda
1 Network Associates: Follow-up from meeting
2 Possible Changes to subject header to reference encryption algorithm type
3 Testing
------------------------------------------------------