1. IPR WG IETF 67, November 7, 2006

2. Agenda 15:20 Administrivia — Agenda bashing, etc. – 5 min 15:25 Outbound Rights — What rights the IETF grants others – 75 min 16:40 Milestones and Goals — What we're going to do and when, including a replacement for 3978 – 35 min 17:15 Wrapup, next steps 17:20 End

3. Outbound rights Draft-ietf-ipr-outbound-rights-01 Believed to represent a possible consensus Calling for issues

4. Outbound rights – Big issues Cite all, translate all, change code –Rough consensus? –For: 12, Against: 0, Confused: 1 Concern: Stability of specification? –“we have shown that we can’t get it right” –Expanding rights requires right to do so

5. Big issues (2) Addressing stability –Need language stating how expanded rights can be granted (process) Special cases: IETF Trust (as requested by the IESG or IAB) Blanket rights: IETF consensus process Yes: 14, No: 0, Don’t know: 0 –Note: The IETF Trust can only grant rights that it has obtained the right to grant –The WG does not wish the IETF to ask for copyright transfer (this is an “inbound” issue, and will be discussed under that agenda point)

6. Copyright issue There have been contexts where the material in an IETF contribution is also available under other license terms. The IETF wishes to be able to include content which is available under such licenses. It is desirable to indicate in the IETF contribution that other licenses are available. However, the IETF does not wish to have IETF Contributions contain additional copyright notices and licenses, as that introduces a number of additional difficulties. Providing the correct legal approach to such indications is left to the IASA, as all legal language is.

7. Outbound rights – Small issues Code vs non-Code: Adequate definition? –Alt 1: Markers (1) – needs text markers –Alt 2: Rules (0) – needs a judge if borderline cases can exist –Alt 3: Do both, as appropriate (17) Do we mention independent submissions? –NO. Current text refers to “IETF contributions” only –Decision should be consistent with 3978bis Section 5.5: Concern about language about copyright notices –Copyright notices, code encumbrances –Do we ban code with more restrictive licenses? –“Documents should not contain text that seems to restrict the IETF-granted rights to use the documents”. Such text may be license text or copyright text beyond the standard IETF text. How do we handle old RFCs? –Request the IETF Trust to do the best they can to get equivalent rights to old RFCs as to new documents. –Pre-IETF documents are a special case; rights may possibly be available from ISI –“Middle” RFCs probably need permission from the authors –They’re already doing it – so we can just applaud the effort

8. 3978bis Two major sections, Philosophy and Boilerplate Scott Bradner will write the first section; Jorge will write the second The IETF Trust will have the explicit right to approve minor boilerplate changes consistent with philosophical goals, to handle special cases and minor errors

9. Inbound rights – issues How is “minor” determined in “minor change”? –“If it’s not obvious, it’s not minor” – but this is tricky How do we maintain “no derivative works” RFCs? –External documents, brought to the IETF for info –Intention was to permit copying, quotation, and translation, but not new work based on it; “NDW” may not match that –Examples: NFS v3; Cabletron….. –The function of providing publication of outside documents with a NDW clause is useful, and should continue. Yes: 9 No: 1 Don’t know: 0

10. Timeline December: Revised –outbound, WG Last Call January: Resolve issues, -outbound to IESG January: 1st draft of 3978bis March: Discuss 3978bis in Prague April: WG Last Call on 3978bis May: Resolve issues, 3978bis to IESG June: Close WG No need to meet in Chicago??????