on 2004-12-03 9:25 am Harald Tveit Alvestrand said the following: > > --On torsdag, desember 02, 2004 18:02:16 +0100 Henrik Levkowetz > <henrik@xxxxxxxxxxxxx> wrote: > >> I'm not sure if the current text clearly implies that tools created >> for the IASA by a contractor, and data collected for the IASA by a >> contractor shall be openly available. > > I think the IETF needs the power to decide this on a case by case basis. > For instance, we've had multiple rounds of making it more difficult to > extract email addresses from our attendee list - "openly available" means > "available to spammers too". Not to mention that we have records of email > conversations that deal with personnel selection matters. > > "Available for use in the IETF" is obvious; "available to the IETF with no > restriction by the contractor" is sensible. But be careful.... > on 2004-12-03 12:59 am Carl Malamud said the following: > 2.2.6 currently reads: > > The right to use any intellectual property rights created by any IASA-related or > IETF activity may not be withheld or limited in any way by ISOC from the IETF. > > You could simply append: > > As a matter of principle the IAOC and IAD should ensure that any contracts > for IASA clearly designate that any software, databases, and websites should > be openly available, including open source for software and a machine-readable > format for databases, whenever possible. 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." Henrik _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf