Sam - I think you're covered under Harald's language. Your worry was "sublicense" ... at the general principle level, that's certainly clear. Needless to say, at the implementation level (the actual contract), the lawyers/IAD/IAOC will want to make sure the principle made it in. The current wording: "perpetual right" ... "all data" .. "IETF activities" is pretty broad. A new contractor, for example, is working in support of IETF activities and would be clearly covered. Regards, Carl > >>>>> "Harald" == Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx> writes: > > Harald> --On tirsdag, desember 07, 2004 04:49:36 -0500 Sam Hartman > Harald> <hartmans-ietf@xxxxxxx> wrote: > > >>>>>>> "Harald" == Harald Tveit Alvestrand <harald@xxxxxxxxxxxxx> > >>>>>>> writes: > >> > Harald> 6. The IETF, through the IASA, shall have a perpetual > Harald> right to use, display, distribute, reproduce, modify and > Harald> create derivatives of all data created in support of IETF > Harald> activities. > >> > Harald> (Jorge liked "perpetual" better than "irrevocable > Harald> permanent" - the stuff after "to" is a well known legal > Harald> incantation). > >> This works for me provided that the legalese gives us the > >> right to sublicense these rights to others. > > Harald> That's more than we currently ask people to assign to the > Harald> IETF when making submissions to the IETF (RFC 3667) - > Harald> there, we ask only for permission to use it within the > Harald> IETF process (which may mean some sublicensing, and may > Harald> not). Not sure what we should write here - I wouldn't want > Harald> to write something here that would require reopening RFC > Harald> 3667 for consistency. > > well, I do happen to think 3667 is broken, but agree with you that we > do not want to open that can of worms at this time. > > However if we change contractors, we need to have the necessary rights > to give the new contractor the rights to use our data. I believe that > is an absolute requirement. > > --Sam > > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf