The specific term is "work for hire". All data, created software, etc must
be considered the result of "work for hire" and as such is the property of
ISOC in trust for the IETF.
At 08:58 AM 12/3/2004, Allison Mankin wrote:
Folks,
Good stuff here, but...
I'd like to put in a plug for making it a mandatory* principle
that the IETF end up in no-restrictions possession of data contents from
the databases and websites from any contractors.
This is different from specifics about what tools are used, open source
etc, and what the public availability of the data is.
So the text below still needs to be teased a little, esp. because it's mixing
the tools and the contents.
Allison
>
> --On fredag, desember 03, 2004 10:19:23 +0100 Henrik Levkowetz
> <henrik(_at_)levkowetz(_dot_)com> wrote:
>
> >
> > What about this text, (added to 2.2.6):
> >
> > "As a matter of principle the IAOC and IAD should ensure that any
> > contracts for IASA clearly designate that any software, databases,
> > and websites developed should be available to the IETF with no
> > restriction by the contractor. Software should be open source and
> > data should be made available to the IETF in machine-readable
> > format, also in cases where it may be inadvisable to make the data
> > openly available."
> >
>
> this works for me (my only problem is stylistic - it's somewhat long for a
> principle, so may fit better in the "details" sections, if a place can be
> found for it).
>
>
>
>
>
> _______________________________________________
> 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
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf