Re: Flawed license in document...

Simon Josefsson wrote:

> The license text that the draft-eastlake-sha2-02.txt authors
> picked seem to be incompatible with some free software
> licenses and some proprietary license to me.

Maybe they couldn't copy the license for the same "software" in
http://csrc.nist.gov/publications/fips/fips180-2/fips180-2withchangenotice.pdf

| Exports of cryptographic modules implementing this standard
| and technical data regarding them must comply with these
| Federal regulations and be licensed by the Bureau of Export
| Administration of the U.S. Department of Commerce.

In other words RfCs mandating SHA are dubious, no big surprise.

| Implementations of the secure hash standard is this standard
| may be covered by U.S. or foreign patents.

Let's hope that they'll find the IETF page for IPR submissions.

| Only algorithm implementations that are validated by NIST
| will be considered as complying with this standard.
| Information about the planned validation program can be
| obtained at http://csrc.nist.gov/cryptval/
[...]

Several accredited labs for conformance testing.  Cost recovery
fee for NIST to check the conformance test results, and then to
publish the validated algorithm.

It's only an informational RfC, and it's nice to have this info
in plain text format.  Maybe the authors should have copied the
"legalese" from their source instead of using another text (?)

                             Bye, Frank

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg