Update fips notes

diff --git a/docs/fips/fipsnotes.wml b/docs/fips/fipsnotes.wml
index f69f1be4e1b877b70870e68af7ef89eaece95072..efbfa57cfd36da9ee108cdb44e2db7cf05eaba14 100644 (file)
--- a/docs/fips/fipsnotes.wml
+++ b/docs/fips/fipsnotes.wml
@@ -47,8 +47,9 @@ produced from unmodified (or only cosmetically modified) source.
 The OSF would really prefer to work on open source based validations of benefit to the OpenSSL user community at large, but
 financial support for that objective is intermittent at best.  On the other hand many vendors are interested in private label
 validations and the OSF will assist in such efforts on a paid basis.  We've done enough of these to be very cost competitive
-and for uncomplicated validations will work on a fixed price basis.  Contact the <a href="../../support/funding/support-contact.html">OSF</a>
-for more information.
+and for uncomplicated validations will work on a fixed price basis.  A routine private label validation on a single commodity
+platform can cost as little as US$30,000.  Private label validations satsifying the U.S. Army "level 2" requirements are also
+possible.  Contact the <a href="../../support/funding/support-contact.html">OSF</a> for more information.
 
 <p>
 
@@ -62,24 +63,26 @@ The most recent open source based validation is v1.2, FIPS 140-2 certificate
 And did we mention the <a href="UserGuide.pdf">User Guide</a>?
 <p>
 <font color="#cc3333">Inportant Note:</font> Due to upcoming changes in the FIPS 140-2 validation requirements the current v1.2 Module will
-no longer be a suitable for private label validations in its current form.  See the NIST <a href="http://csrc.nist.gov/groups/STM/cmvp/notices.html">Notices</a>
- and 
-<a href=" http://csrc.nist.gov/groups/ST/key_mgmt/documents/Transitioning_CryptoAlgos_070209.pdf">discussion paper</a>.
+no longer be a suitable model for private label validations in its current form past the year 2010.  See the NIST <a href="http://csrc.nist.gov/groups/STM/cmvp/notices.html">Notices</a>,
+<a href="http://csrc.nist.gov/groups/ST/key_mgmt/documents/Transitioning_CryptoAlgos_070209.pdf">discussion paper</a> and
+<a href="http://csrc.nist.gov/publications/drafts/800-131/draft-800-131_transition-paper.pdf">Draft 800-131</a>.
 <p>
 We hope to address these new changes in the next open source based validation (see below).
 
 <h2>Upcoming Validations</h2>
-No open source based validations are currently in progress.
-<p>
-At the present time there are no plans for a new post-v1.2 validation.  The CMVP test lab and filing fees are more
-than pocket change (~USD$25,000 and up) and beyond the financial resources of the OSF.  Past validations have been been funded by
+No open source based validations are currently in progress.  This situation is due not to a lack of interest on our part;
+we labored for years to obtain the first ever groundbreaking open source based validation and we'd dearly love
+to keep it current and available forever.  The obstacle is lack of funding.
+The CMVP test lab and filing fees are more than pocket change (~USD$25,000 and up) and beyond the limited
+financial resources of the OSF.  Past validations have been funded by
 commercial sector and government sponsors, some identified in published acknowledgments and some not (by request).
 <p>
 The OSF assists commercial software vendors with "private label" validations on a regular basis, and in some cases such
 work directly results in FIPS related code improvements.  The income from such work also helps OpenSSL team members eat and pay
-the rent and thus indirectly support all of OpenSSL.  However, unless you are one of the companies directly obtaining a custom
+the rent and thus indirectly supports all of OpenSSL.  However, unless you are one of the companies directly obtaining a custom
 private label validation those improvements don't give you validated cryptography that can be sold in the markets requiring such validation.
 <p>
-If and when sufficient sponsor funding materializes we will obtain a new and updated validation to replace the current vaildation and
-satisfy the validation requirements then in effect.  Any such plans will be posted here.
+If and when sufficient sponsor funding materializes we will move quickly and enthusiastically to obtain a new and updated validation
+to satisfy the validation requirements then in effect.  Any such plans will be posted here.  If you have an interest in sponsoring
+that effort, in whole or in part, please contact the <a href="http://openssl.org/support/funding/support-contact.html">OSF</a>.