On 16-Dec-21 07:44, John Levine wrote:
It appears that Bob Hinden <bob.hinden@xxxxxxxxx> said:
I agree, it not necessary to have a delimiter token. Just say something like:
A suggested algorithm in pseudo code for <foo> is as follows:
in the document. It is essentially just text.
I agree except for the "essentially". It is just text.
We went through a long process to decide what licenses to offer for RFCs and for
computer code in them. The TLP even describes what we consider to be code:
https://trustee.ietf.org/documents/trust-legal-provisions/code-components-list-3/
As has been pointed out off list, that list is incomplete, which would be OK if it was stated to be non-exclusive, but it isn't.
My original concern was different - if an implementer wants to borrow from the pseudocode to make real code, they might be making a derivative work from the RFC in a way that is not allowed by the Trust's legal provisions**.
As far as I know, we have never discussed this issue to see what the community consensus might be.
** Before John says it, the author of the pseudocode is perfectly at liberty to grant any license for it that they want, outside the IETF standards process. But that's more work and may be tricky in a corporate context.
Regards
Brian
