Most RFCs do not contain source code. The IESG discussed this
situation, and felt that the explicit licenses was the right thing to
do in this situation. Including source code without any indication
of the authors intent seemed much worse.
Russ
At 11:37 AM 2/7/2006, Pekka Savola wrote:
On Tue, 7 Feb 2006, Simon Josefsson wrote:
NEW:
This document provides the Internet community convenient
access to source code that implements the United States of
America Federal Information Processing Standard Secure Hash
Algorithms (SHAs) [FIPS 180-2] and HMACs based upon these
one-way hash functions. See license in Section 1.1.
The license in section 1.1 reads:
Royalty free license to copy and use this software is granted
provided that this document is identified in all material
mentioning or referencing this software.
The bigger problem with this is IMHO that I don't think RFCs are
supposed to contain IPR disclosures, licenses, or whatever.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf