Yes, whatever rights we plan to grant for outbound have to
be granted
to us on the inbound side.
If we stick with the rough consensus that all code may be
used and
modified in any fashion, than anyone including code in an
IETF
contribution has to grant us the right to do that, including
the
ability to let others do that.
And yes, that may mean that some existing code can not
appear in
RFCs. If doing this in the sensible fashion means that 1 or
2 RFCs
per thousand face some production obstacle, but everyone
knows
clearly what they can do, and we don't need to argue about
whether
specific uses are permitted, then that is a (very) good
trade off.
Yours,
Joel M. Halpern
At 09:54 AM 10/6/2006, Brian E Carpenter wrote:
>(Sorry, this gets into inbound rights but that seems to
be our
>problem here.) I'm beginning to wonder if we shouldn't
be rather
>hard headed and say to authors:
>
>Code embedded in IETF Contributions MUST NOT be subject
to
>any conditions that prevent the IETF from granting
unrestricted
>rights to use, republish or modify it. It is the
Contributor's
>responsibility to ensure that contributed code is free
>of such restrictions.
>
>IMHO if someone puts the cart before the horse by
putting
>code under an irrevocable license before contributing it
>to the IETF, they should build their own clean room and
rewrite
>the code for us.
>
>After the code has already become an IETF Contribution,
a copy
>of it could be put under any license; we wouldn't care.
>
> Brian
>
>_______________________________________________
>Ipr-wg mailing list
>Ipr-wg ietf.org
>https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
|