"Spencer Dawkins" <spencer at mcsr-labs.org> writes:>
>>>> I like this, but doesn't it seem incompatible with a document that >>>> invoke section 5.2 of RFC 3978? >>>> >>>> If the Contributor desires to eliminate the IETF's right to make >>>> modifications and derivative works of an IETF Contribution (other >>>> than translations), one of the two of the following notices may be >>>> included in the Status of Memo section of an Internet-Draft and >>>> included in a published RFC: >>>> ... >>>> b. "This document may not be modified, and derivative works of it >>>> may >>>> not be created."
Which prevents the IETF or anyone from implementing this protocol as well.
Was that the intent? Without the derivative works licenseing, the ports
cannot be documented.
Todd, I have to remind you that your issue #1198 was closed with the resolution:
Implementations of IETF standards that incorporate pieces of IETF documents (such as MIBs or data tables) need to have the right to produce derivative works based on those pieces.
Implementations of IETF standards that do not incorporate such pieces do not need the right to produce such derivative works.
Do not attempt to reopen that issue.
_______________________________________________ Ipr-wg mailing list Ipr-wg at ietf.org https://www1.ietf.org/mailman/listinfo/ipr-wg