Re: draft-bradner-rfc-extracts-00.txt

sob@harvard.edu (Scott Bradner) writes:

> I've just published draft-bradner-rfc-extracts-00.txt 
>
> this ID addresses the issues of extracting RFCs and derivative works

Thanks!

The proposed RFC 3667 update in section 2 looks like an improvement to
me.  It is clear we disagree on permitting unrestricted derivate
works.  Let me try to rebut your arguments:

Re 3: The fact that W3C, ITU etc behave similar to IETF is not a
convincing argument to me.  The Unicode Consortium permit modified
versions of their standards to be published (again, kudos to them!),
see <http://www.unicode.org/copyright.html>.

Re 3.2.1: I don't buy that this will create any significant confusion.
I think you need to show that confusion exists in other areas where
modified derived works are permitted.  I.e., for Unicode or for RFCs
before RFC 2026.  I further think that Larry Rosen's suggestion is too
complex and too costly to implement for the IETF.

Re 3.2.2: Working groups typically close after they are done with a
core specification.  Further, WGs are not required to review or help
anyone modify the product of a WG.  Thus, I challenge that the "best
place" to extend a standard is within the WG that created it.  One of
my examples has been StringPrep/IDN, that WG doesn't exist any more.

Re the second 3.2.2 (the section numbering seem off): This appear to
be the same argument as 3.2.1, i.e., that permitting modified
documents would create confusion or problems.

Re 3.2.3: The requirement to be able to modify documents come from
free software developers like myself.  It may be the case that the
open source community do not need this requirement, but I don't see
the relevance.  Further, the argument that the free software community
could come to the IETF if they want to extend standards is weak: there
is nothing that guarantee that the IETF will be around forever or that
it will welcome the free software community.  It must be possible to
modify free software without talking to the IETF about it.

Thanks,
Simon

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