IPR-WG Discussion Archive - Thread Index

• Re: A simpler idea, (continued)
  • Re: A simpler idea, Simon Josefsson
  • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, todd glassey
  • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Simon Josefsson
    • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Spencer Dawkins
    • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Harald Alvestrand
      • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Simon Josefsson
      • #1169 Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Harald Alvestrand
      • Re: #1169 Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Simon Josefsson
      • Re: #1169 Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Harald Alvestrand
      • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Simon Josefsson
    • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Ted Hardie
      • Re: #1166 Quotations from RFCs and I-Ds - suggested resolution, Simon Josefsson
• Minutes uploaded, Harald Alvestrand
  • Comments on minutes, Simon Josefsson
    • Re: Comments on minutes, Scott Bradner
    • Re: Comments on minutes, Joel M. Halpern
      • Re: Comments on minutes, Simon Josefsson
      • Re: Comments on minutes, todd glassey
• FW: [CNI-(C)] Re: IETF/source code copyright status, Lawrence Rosen
• Draft minutes, IPR WG, Harald Alvestrand
• Re: [CNI-(C)] Copyright status of early Internet RFCs, Lawrence Rosen
  • Re: [CNI-(C)] Copyright status of early Internet RFCs, Don Armstrong
  • Re: [CNI-(C)] Copyright status of early Internet RFCs, John Levine
    • Re: [CNI-(C)] Copyright status of early Internet RFCs, Brian E Carpenter
    • Re: [CNI-(C)] Copyright status of early Internet RFCs, Harald Alvestrand
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, John L
  • Re: [CNI-(C)] Copyright status of early Internet RFCs, Don Armstrong
    • Re: [CNI-(C)] Copyright status of early Internet RFCs, Simon Josefsson
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, Harald Alvestrand
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, Simon Josefsson
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, Tom Petch
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, Don Armstrong
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, todd glassey
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, Joel M. Halpern
      • Re: [CNI-(C)] Copyright status of early Internet RFCs, Harald Alvestrand
  • <Possible follow-ups>
  • RE: [CNI-(C)] Copyright status of early Internet RFCs, Contreras, Jorge
• RE: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Black_David
• Resolution of #1245 - Does describing a technology require a license from the people who originally described it?, Harald Alvestrand
  • Re: Resolution of #1245 - Does describing a technology require a license from the people who originally described it?, todd glassey
• Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Harald Alvestrand
  • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Spencer Dawkins
    • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Simon Josefsson
    • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Harald Alvestrand
  • RE: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, David B Harrington
  • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Thomas Narten
  • RE: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Lawrence Rosen
    • Re: Issue #1238 Shoud secretariat ask for IPR clarification fromIPR holders on 3rd party IPR disclosures, todd glassey
    • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Harald Alvestrand
      • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Ted Hardie
      • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Harald Alvestrand
      • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Thomas Narten
      • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Scott W Brim
      • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Brian E Carpenter
      • Re: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Thomas Narten
      • RE: Issue #1238 Shoud secretariat ask for IPR clarification from IPR holders on 3rd party IPR disclosures, Lawrence Rosen
• SOFTEWARE PATENT Insttiute... Emailing: www.spi.org, todd glassey
• Resolution of tickets 1197, 1240, 1241, 1242, 1243, 1244, Harald Alvestrand
  • Re: Resolution of tickets 1197, 1240, 1241, 1242, 1243, 1244, todd glassey
  • RE: Resolution of tickets 1197, 1240, 1241, 1242, 1243, 1244, John Calhoon \(LCA\)
• A note about copyright notices, Harald Alvestrand
  • Re: A note about copyright notices, Simon Josefsson
    • Re: A note about copyright notices, todd glassey
    • Re: A note about copyright notices, todd glassey
• IPR disclosures for individual submissions, Sam Hartman
  • Re: IPR disclosures for individual submissions, todd glassey
  • Re: IPR disclosures for individual submissions, Harald Alvestrand
    • Re: IPR disclosures for individual submissions, Sam Hartman
      • Re: IPR disclosures for individual submissions, Harald Alvestrand
      • Re: IPR disclosures for individual submissions, todd glassey
      • Re: IPR disclosures for individual submissions, Brian E Carpenter
      • Re: IPR disclosures for individual submissions, todd glassey
      • Re: IPR disclosures for individual submissions, Harald Alvestrand
      • Re: IPR disclosures for individual submissions, todd glassey
      • Re: IPR disclosures for individual submissions, Harald Alvestrand
• Why multiple copyrights notices may be useful, Simon Josefsson
  • Re: Why multiple copyrights notices may be useful, todd glassey
  • Re: Why multiple copyrights notices may be useful, Simon Josefsson
    • Re: Why multiple copyrights notices may be useful, todd glassey
    • Re: Why multiple copyrights notices may be useful, stewe
      • Re: Why multiple copyrights notices may be useful, Simon Josefsson
      • Re: Why multiple copyrights notices may be useful, todd glassey
      • Re: Why multiple copyrights notices may be useful, Simon Josefsson
      • Re: Why multiple copyrights notices may be useful, todd glassey
• [Fwd: Audio Info], Harald Alvestrand
  • Re: Audio Info], George T. Willingmyre
• Todd Glassey's issues list, Harald Alvestrand
  • Re: Todd Glassey's issues list, todd glassey
    • Re: Todd Glassey's issues list, Harald Alvestrand
• Updated agenda, IPR wg, Harald Alvestrand
  • Re: Updated agenda, IPR wg, Simon Josefsson
    • Re: Updated agenda, IPR wg, Harald Alvestrand
      • Re: Updated agenda, IPR wg, Simon Josefsson
    • Re: Updated agenda, IPR wg, todd glassey
• Jorge - I see a federal judge today stopped the Nortious BIG's album today..., todd glassey
• Re: 7th, 8th, 9th, & 10th issues, and commentary on why the other 6 havent been posted to the ISSUES list?, todd . glassey
• 7th, 8th, 9th, & 10th issues, and commentary on why the other 6 havent been posted to the ISSUES list?, todd glassey
  • Re: 7th, 8th, 9th, & 10th issues, and commentary on why the other 6 havent been posted to the ISSUES list?, Harald Tveit Alvestrand
  • Re: 7th, 8th, 9th, & 10th issues, and commentary on why the other 6 havent been posted to the ISSUES list?, Harald Alvestrand
• resend - this did not seem to make it the 1st time, Scott Bradner
• ISSUE - Submission Release Failures... - The Syslog Example., todd glassey
  • Re: ISSUE - Submission Release Failures... - The Syslog Example., Harald Alvestrand
    • Re: ISSUE - Submission Release Failures... - The Syslog Example., todd glassey
      • #1245: Does describing a technology require a license from the people who originally described it?, Harald Alvestrand
      • Re: #1245: Does describing a technology require a license from the people who originally described it?, todd glassey
      • Re: #1245: Does describing a technology require a license from the people who originally described it?, todd glassey
      • Re: #1245: Does describing a technology require a license from the people who originally described it?, Tom Petch
      • Re: #1245: Does describing a technology require a license from thepeople who originally described it?, todd glassey
      • RE: #1245: Does describing a technology require a license fromthepeople who originally described it?, Lawrence Rosen
      • Re: #1245: Does describing a technology require a license fromthepeople who originally described it?, todd glassey
      • the (ir?)relevance of syslogRe: #1245: Does describing a technology require a license from thepeople who originally described it?, Tom Petch
      • Re: the (ir?)relevance of syslogRe: #1245: Does describing a technologyrequire a license from thepeople who originally described it?, todd glassey
• Re: Re; 3rd Party Disclosure problem in RFC 3979, Scott Bradner
  • Re: Re; 3rd Party Disclosure problem in RFC 3979, Scott W Brim
    • Re: Re; 3rd Party Disclosure problem in RFC 3979, Thomas Narten
  • Re: Re; 3rd Party Disclosure problem in RFC 3979, todd glassey
  • Re: Re; 3rd Party Disclosure problem in RFC 3979, Thomas Narten
    • Re: Re; 3rd Party Disclosure problem in RFC 3979, Scott Bradner
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Brian E Carpenter
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Scott Bradner
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Brian E Carpenter
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Spencer Dawkins
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, todd glassey
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Brian E Carpenter
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, bmanning
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Spencer Dawkins
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, todd glassey
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Spencer Dawkins
      • Re: Re; 3rd Party Disclosure problem in RFC 3979, Pekka Savola
  • <Possible follow-ups>
  • Re: Re; 3rd Party Disclosure problem in RFC 3979, todd . glassey
• 3rd Party Disclosure problem in RFC 3979, Thomas Narten
• ISSUES -3 new additions for the ISSUES list., todd glassey
• Fw: #1197 Re: ISSUES How IP is input and Intent..., todd glassey
• Tentative agenda, IPR WG session in Dallas, Harald Alvestrand
  • Re: Tentative agenda, IPR WG session in Dallas, Simon Josefsson
    • Re: Tentative agenda, IPR WG session in Dallas, Harald Alvestrand
      • Re: Tentative agenda, IPR WG session in Dallas, Simon Josefsson
• NOTE-WELL Participation..., todd glassey
  • Re: NOTE-WELL Participation..., Harald Tveit Alvestrand
    • Re: NOTE-WELL Participation..., John C Klensin
      • Re: NOTE-WELL Participation..., Harald Alvestrand
      • Re: NOTE-WELL Participation..., todd glassey
      • Re: NOTE-WELL Participation..., John C Klensin
• Does under Title 35, a submission to the IETF constitute an invention?, todd glassey
  • <Possible follow-ups>
  • RE: Does under Title 35, a submission to the IETF constitute an invention?, Contreras, Jorge
• A real-world example of the IETF's screwed up induction process or "Who owns Syslog?" - and why is this important to IPR?, todd glassey
  • Re: A real-world example of the IETF's screwed up induction process or"Who owns Syslog?" - and why is this important to IPR?, todd glassey
  • Re: A real-world example of the IETF's screwed up induction process or "Who owns Syslog?" - and why is this important to IPR?, Harald Alvestrand
    • Re: A real-world example of the IETF's screwed up induction process or "Who owns Syslog?" - and why is this important to IPR?, todd glassey
      • TYPO Correction - Re: A real-world example of the IETF's screwed up induction processor "Who owns Syslog?" - and why is this important to IPR?, todd glassey
• Jorge as the IETF's lawyer, does the merging of the two sets of rights defined in the BCP78 document make an exclusive?, todd glassey
• Re: BCP78's Copyright Statement... may be wrong - all submissions to the IETF are likely exclusive in nature. They have to be!, todd glassey
• BCP78's Copyright Statement... may be wrong - all submissions to the IETF are likely exclusive in nature. They have to be!, todd glassey
• Where's the Contract - Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
• RE: Date clarification [Re: ISSUE? What does the copyright claim in I-D/RFCs mean?], Contreras, Jorge
  • RE: Date clarification [Re: ISSUE? What does the copyright claim in I-D/RFCs mean?], John C Klensin
    • Re: Date clarification [Re: ISSUE? What does the copyright claim in I-D/RFCs mean?], Brian E Carpenter
• WG Action: RECHARTER: Intellectual Property Rights (ipr), IESG Secretary
• If there is no exclusive conveyance agreement then who owns the delta between when an idea was submitted as a ID and when it becones a RFC?, todd glassey
  • Re: If there is no exclusive conveyance agreement then who owns thedelta between when an idea was submitted as a ID and when itbecones a RFC?, todd glassey
• Here is a PDF timeline showing the 5 states of ownership of the IETF's works..., todd glassey
• RE: ISSUE? What does the copyright claim in I-D/RFCs mean?, Contreras, Jorge
  • RE: ISSUE? What does the copyright claim in I-D/RFCs mean?, John C Klensin
    • RE: ISSUE? What does the copyright claim in I-D/RFCs mean?, Joel M. Halpern
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Brian E Carpenter
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Joel M. Halpern
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Joel M. Halpern
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Brian E Carpenter
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Bill Fenner
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
    • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Harald Alvestrand
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, John C Klensin
  • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Brian E Carpenter
    • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Frank Ellermann
  • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Simon Josefsson
  • <Possible follow-ups>
  • RE: ISSUE? What does the copyright claim in I-D/RFCs mean?, Contreras, Jorge
  • RE: ISSUE? What does the copyright claim in I-D/RFCs mean?, Contreras, Jorge
    • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
    • Date clarification [Re: ISSUE? What does the copyright claim in I-D/RFCs mean?], Brian E Carpenter
  • RE: ISSUE? What does the copyright claim in I-D/RFCs mean?, Contreras, Jorge
• I-D ACTION:draft-ietf-ipr-outbound-rights-00.txt, Internet-Drafts
  • Re: I-D ACTION:draft-ietf-ipr-outbound-rights-00.txt, Brian E Carpenter
  • <Possible follow-ups>
  • Fwd: I-D ACTION:draft-ietf-ipr-outbound-rights-00.txt, Joel M. Halpern
    • ISSUE? What does the copyright claim in I-D/RFCs mean?, Simon Josefsson
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Steven M. Bellovin
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Simon Josefsson
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Steven M. Bellovin
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Joel M. Halpern
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Simon Josefsson
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Simon Josefsson
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
      • exclusive vs. non-exlcusive releases... and the requirement for a wet signature on IP submissions., todd glassey
      • Re: exclusive vs. non-exlcusive releases... and the requirement for a wet signature on IP submissions., Steven M. Bellovin
      • Re: exclusive vs. non-exlcusive releases... and the requirement for a wet signature on IP submissions., todd glassey
      • Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
      • #1212 Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, Harald Alvestrand
      • Re: #1212 Re: ISSUE? What does the copyright claim in I-D/RFCs mean?, todd glassey
    • Review of draft-ietf-ipr-outbound-rights-00.txt, Simon Josefsson
      • Re: Review of draft-ietf-ipr-outbound-rights-00.txt, Joel M. Halpern
• I-D ACTION:draft-ietf-ipr-rules-update-04.txt, Internet-Drafts
  • Re: I-D ACTION:draft-ietf-ipr-rules-update-04.txt, Brian E Carpenter
  • Review of draft-ietf-ipr-rules-update-04.txt, Simon Josefsson
    • Re: Review of draft-ietf-ipr-rules-update-04.txt, Scott Bradner
      • Issues - Managing BCP's & Issues with Expiring BCP's when they fail to continue to be the 'BCP', todd glassey
• Re: ADMIN Re: CLOSED #1198 Proposed resolution - Implementationandderivativework, todd glassey
  • Re: ADMIN Re: CLOSED #1198 Proposed resolution - Implementationandderivativework, Steven M. Bellovin
    • Re: ADMIN Re: CLOSED #1198 Proposed resolution -Implementationandderivativework, todd glassey
      • Re: ADMIN Re: CLOSED #1198 Proposed resolution -Implementationandderivativework, Harald Alvestrand
• Rule 107 and the US Copyright Code..., todd glassey
• RE: CLOSED #1198 Proposed resolution - Implementation andderivativework, Contreras, Jorge
  • ADMIN Re: CLOSED #1198 Proposed resolution - Implementation andderivativework, Harald Alvestrand
  • Re: CLOSED #1198 Proposed resolution - Implementationandderivativework, todd glassey
• proposed new charter, Steven M. Bellovin
  • Re: proposed new charter, Bill Fenner
    • Re: proposed new charter, Brian E Carpenter
      • Re: proposed new charter, Bill Fenner
      • Re: proposed new charter, Fred Baker
      • Re: proposed new charter, Brian E Carpenter
      • Re: proposed new charter, Bill Fenner
      • Re: proposed new charter, Brian E Carpenter
  • <Possible follow-ups>
  • Re: proposed new charter, Allison Mankin
  • Re: proposed new charter, Brian E Carpenter
  • Re: proposed new charter, Harald Alvestrand
• Editor for "outgoing rights" document, Harald Tveit Alvestrand
• WG Review: Recharter of Intellectual Property Rights (ipr), IESG Secretary
• #1198 Proposed resolution - Implementation and derivative work, Harald Tveit Alvestrand
  • Re: #1198 Proposed resolution - Implementation and derivative work, Simon Josefsson
    • Re: #1198 Proposed resolution - Implementation and derivative work, Harald Tveit Alvestrand
      • Re: #1198 Proposed resolution - Implementation and derivative work, Simon Josefsson
      • Another proposed #1198 Proposed resolution - Implementation and derivative work, todd glassey
      • Re: #1198 Proposed resolution - Implementation and derivative work, Ted Hardie
      • Re: #1198 Proposed resolution - Implementation and derivative work, Simon Josefsson
      • Re: #1198 Proposed resolution - Implementation and derivative work, Harald Tveit Alvestrand
      • RE: #1198 Proposed resolution - Implementation and derivative work, David B Harrington
  • Re: #1198 Proposed resolution - Implementation and derivative work, Don Armstrong
    • Re: #1198 Proposed resolution - Implementation and derivative work, Harald Tveit Alvestrand
  • CLOSED #1198 Proposed resolution - Implementation and derivative work, Harald Alvestrand
    • Re: CLOSED #1198 Proposed resolution - Implementation and derivative work, todd glassey
      • Re: CLOSED #1198 Proposed resolution - Implementation and derivative work, Simon Josefsson
      • Re: CLOSED #1198 Proposed resolution - Implementation and derivative work, todd glassey
      • Re: CLOSED #1198 Proposed resolution - Implementation and derivative work, Simon Josefsson
      • Re: CLOSED #1198 Proposed resolution - Implementation andderivative work, todd glassey
• Fw: #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), todd glassey
• Reminder: Open issues, Harald Tveit Alvestrand
  • ISSUES How IP is input and Intent..., todd glassey
    • #1197 Re: ISSUES How IP is input and Intent..., Harald Tveit Alvestrand
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Simon Josefsson
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Harald Tveit Alvestrand
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Simon Josefsson
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Harald Tveit Alvestrand
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Simon Josefsson
      • Re: #1197 Re: ISSUES How IP is input and Intent..., todd glassey
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Frank Ellermann
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Simon Josefsson
      • Re: #1197 Re: ISSUES How IP is input and Intent..., todd glassey
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Frank Ellermann
      • Re: #1197 Re: ISSUES How IP is input and Intent..., Simon Josefsson
      • Re: #1197 Re: ISSUES How IP is input and Intent..., todd glassey
      • Righs in mailing list articles (Re: #1197 Re: ISSUES How IP is input and Intent...), Harald Tveit Alvestrand
      • Re: Righs in mailing list articles (Re: #1197 Re: ISSUES How IP is input and Intent...), todd glassey
      • Re: Righs in mailing list articles (Re: #1197 Re: ISSUES How IP is input and Intent...), Harald Tveit Alvestrand
      • Re: Righs in mailing list articles (Re: #1197 Re: ISSUES How IP is input and Intent...), Brian E Carpenter
      • NOTEWELL IS BROKEN - was Re: Rights in mailing list articles Re: #1197, todd glassey
    • #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), Harald Tveit Alvestrand
      • Re: #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), Simon Josefsson
      • Re: #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), todd glassey
      • Re: #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), Simon Josefsson
      • Re: #1198 Implementation = derivative work? (Re: ISSUES How IP isinput and Intent...), todd glassey
      • Re: #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), Brian E Carpenter
      • Re: #1198 Implementation = derivative work? (Re: ISSUES How IP is input and Intent...), todd glassey
  • ISSUE: outbound license on future RFCs, Simon Josefsson
    • #1199 Re: ISSUE: outbound license on future RFCs, Harald Tveit Alvestrand
• Flawed license in document..., Simon Josefsson
  • Re: Flawed license in document..., Ted Hardie
    • Re: Flawed license in document..., Don Armstrong
      • Re: Flawed license in document..., Ted Hardie
    • Re: Flawed license in document..., Simon Josefsson
      • Re: Flawed license in document..., Ted Hardie
      • Re: Flawed license in document..., Simon Josefsson
      • Re: Flawed license in document..., todd glassey
  • Re: Flawed license in document..., Frank Ellermann
• My apologies - there is a PDF file attached to this - 27KB - its a license worth looking at., todd glassey
• RE: License for the Service Data Objects JavaDoc and Interface Definition files, Lawrence Rosen
• Fw: DoC Report on New Internet Protocol, George T. Willingmyre
• How does Torvalds commentary on GPL3 figure into this? - Larry?, todd glassey
  • Re: How does Torvalds commentary on GPL3 figure into this? - Larry?, Don Armstrong
    • RE: How does Torvalds commentary on GPL3 figure into this? - Larry?, Lawrence Rosen
      • Re: How does Torvalds commentary on GPL3 figure into this? - Larry?, todd glassey
  • Re: How does Torvalds commentary on GPL3 figure into this? - Larry?, Harald Tveit Alvestrand
    • Re: How does Torvalds commentary on GPL3 figure into this? - Larry?, Simon Josefsson
  • <Possible follow-ups>
  • Fw: How does Torvalds commentary on GPL3 figure into this? - Larry?, todd glassey
• I-D ACTION:draft-ietf-ipr-rules-update-03.txt, Internet-Drafts
• Proposed updated charter, IPR WG, Harald Tveit Alvestrand
• Re: Code vs text, todd . glassey
  • Re: Code vs text, John C Klensin
    • RE: Code vs text, Lawrence Rosen
  • <Possible follow-ups>
  • Re: Code vs text, todd . glassey
• issue tracker created for IPR wg, Steven M. Bellovin
  • Re: issue tracker created for IPR wg, Simon Josefsson
    • Re: issue tracker created for IPR wg, todd glassey
    • Code vs text (was: Re: issue tracker created for IPR wg), Spencer Dawkins
      • Re: Code vs text, Simon Josefsson
      • Re: Code vs text, John C Klensin
      • Re: Code vs text, Simon Josefsson
      • Re: Code vs text, todd glassey
      • RE: Code vs text, Lawrence Rosen
      • Re: Code vs text, Simon Josefsson
      • Re: Code vs text, Brian E Carpenter
      • Re: Code vs text, Spencer Dawkins
      • Re: Code vs text, John C Klensin
      • Re: Code vs text, Brian E Carpenter
      • Re: Code vs text, Spencer Dawkins
      • Re: Code vs text, John C Klensin
      • Re: Code vs text, Simon Josefsson
      • #1175 Re: Code vs text, Harald Tveit Alvestrand
  • Re: issue tracker created for IPR wg, Frank Ellermann
    • Re: issue tracker created for IPR wg, todd glassey
      • Re: issue tracker created for IPR wg, Frank Ellermann
      • RE: issue tracker created for IPR wg, Christian Huitema
      • Re: issue tracker created for IPR wg, Frank Ellermann
      • Re: issue tracker created for IPR wg, Steven M. Bellovin
      • Re: issue tracker created for IPR wg, Steven M. Bellovin
• draft of GPLv3 release, Steven M. Bellovin
• The Law... Definition of Derivative Claims..., todd glassey
  • Re: The Law... Definition of Derivative Claims..., Harald Tveit Alvestrand
  • <Possible follow-ups>
  • Re: The Law... Definition of Derivative Claims..., todd . glassey
    • Message not available
      • Re: The Law... Definition of Derivative Claims..., Joel M. Halpern
  • Re: The Law... Definition of Derivative Claims..., todd . glassey
    • RE: The Law... Definition of Derivative Claims..., Lawrence Rosen
      • Re: The Law... Definition of Derivative Claims..., Simon Josefsson
      • RE: The Law... Definition of Derivative Claims..., Lawrence Rosen
  • RE: The Law... Definition of Derivative Claims..., todd . glassey
  • RE: The Law... Definition of Derivative Claims..., Contreras, Jorge
    • Re: The Law... Definition of Derivative Claims..., todd glassey
  • RE: The Law... Definition of Derivative Claims..., Kieran Power
• FYI - Legal Definition of a Derivative Work - per Copyright, todd glassey
  • Re: FYI - Legal Definition of a Derivative Work - per Copyright, Harald Tveit Alvestrand
  • <Possible follow-ups>
  • RE: FYI - Legal Definition of a Derivative Work - per Copyright, Contreras, Jorge
    • Re: FYI - Legal Definition of a Derivative Work - per Copyright, todd glassey
    • OFFLIST Re: FYI - Legal Definition of a Derivative Work - per Copyright, todd glassey
• Status summary, IPR WG - Jan 17, 2005, Harald Tveit Alvestrand
  • Re: Status summary, IPR WG - Jan 17, 2005, Frank Ellermann
    • Re: Status summary, IPR WG - Jan 17, 2005, Harald Tveit Alvestrand
      • Re: Status summary, IPR WG - Jan 17, 2005, Frank Ellermann
    • Re: Status summary, IPR WG - Jan 17, 2005, Steven M. Bellovin
      • Re: Status summary, IPR WG - Jan 17, 2005, Frank Ellermann
  • Re: Status summary, IPR WG - Jan 17, 2005, Simon Josefsson
    • Re: Status summary, IPR WG - Jan 17, 2005, Joel M. Halpern
      • Re: Status summary, IPR WG - Jan 17, 2005, Simon Josefsson
  • Re: Status summary, IPR WG - Jan 17, 2005, Thomas Narten
    • MUST/SHOULD ask for rights (Re: Status summary, IPR WG - Jan 17, 2005), Harald Tveit Alvestrand
      • Re: MUST/SHOULD ask for rights (Re: Status summary, IPR WG - Jan 17, 2005), todd glassey
      • Re: MUST/SHOULD ask for rights (Re: Status summary, IPR WG - Jan 17, 2005), Thomas Narten
  • Re: Status summary, IPR WG - Jan 17, 2005, todd glassey
    • Re: Status summary, IPR WG - Jan 17, 2005, Harald Tveit Alvestrand
      • Re: Status summary, IPR WG - Jan 17, 2005, todd glassey
      • in Re 2028 wording, todd glassey
      • Re: in Re 2028 wording, todd glassey
      • Re: Status summary, IPR WG - Jan 17, 2005, Steven M. Bellovin
      • Re: Status summary, IPR WG - Jan 17, 2005, todd glassey
  • Code and notcode was Re: Status summary, IPR WG - Jan 17, 2005, Tom Petch
    • Re: Code and notcode was Re: Status summary, IPR WG - Jan 17, 2005, todd glassey
  • <Possible follow-ups>
  • RE: Status summary, IPR WG - Jan 17, 2005, Contreras, Jorge
• The classes of IETF users... a user and use model analysis, todd glassey
• Would this WG entertain a ID for trademark use rules?, todd glassey
• Re: IETF's IP Trust - how come the ownership of the IETF's Trademarks is still part of CRNI..., todd . glassey
  • Re: IETF's IP Trust - how come the ownership of the IETF's Trademarks is still part of CRNI..., Soininen Jonne (Nokia-NET/Espoo)
    • Re: IETF's IP Trust... in re RFC2026..., todd glassey
    • Re: IETF's IP Trust... in re RFC2026..., todd glassey
      • Re: IETF's IP Trust... in re RFC2026..., Soininen Jonne (Nokia-NET/Espoo)
• RE: IETF's IP Trust - how come the ownership of the IETF's Trademarksis still part of CRNI..., Contreras, Jorge
  • <Possible follow-ups>
  • RE: IETF's IP Trust - how come the ownership of the IETF's Trademarksis still part of CRNI..., todd . glassey
• IETF's IP Trust - how come the ownership of the IETF's Trademarks is still part of CRNI..., todd glassey
  • Re: IETF's IP Trust - how come the ownership of the IETF's Trademarks is still part of CRNI..., Harald Tveit Alvestrand
• Draft charter, IPR WG, Harald Tveit Alvestrand
  • Re: Draft charter, IPR WG, Simon Josefsson
    • Re: Draft charter, IPR WG, Harald Tveit Alvestrand
      • Re: Draft charter, IPR WG, Simon Josefsson
  • Re: Draft charter, IPR WG, Frank Ellermann
  • Re: Draft charter, IPR WG, Brian E Carpenter
  • Re: Draft charter, IPR WG, Soininen Jonne (Nokia-NET/Espoo)
    • Re: Draft charter, IPR WG, Harald Tveit Alvestrand
      • Re: Draft charter, IPR WG, Brian E Carpenter
      • Re: Draft charter, IPR WG, Soininen Jonne (Nokia-NET/Espoo)
      • Re: Draft charter, IPR WG, Simon Josefsson
• Following the IPR WG work for the IETF Trust, Soininen Jonne (Nokia-NET/Espoo)
  • Re: Following the IPR WG work for the IETF Trust, Ted Hardie
    • Re: Following the IPR WG work for the IETF Trust, Soininen Jonne (Nokia-NET/Espoo)
      • Re: Following the IPR WG work for the IETF Trust, Harald Tveit Alvestrand
• GPL and Status summary, IPR WG, Black_David
  • Re: GPL and Status summary, IPR WG, Simon Josefsson
    • Re: GPL and Status summary, IPR WG, Jeremy Hunsinger
    • Re: GPL and Status summary, IPR WG, Harald Tveit Alvestrand
      • Re: GPL and Status summary, IPR WG, Simon Josefsson
      • Re: GPL and Status summary, IPR WG, Harald Tveit Alvestrand
      • Stupid proposal re outgoing license: was RE: GPL and Status summary, IPR WG, Stephan Wenger
      • Re: Stupid proposal re outgoing license: was RE: GPL and Status summary, IPR WG, John C Klensin
      • Re: GPL and Status summary, IPR WG, Simon Josefsson
      • Code/Text (Re: GPL and Status summary, IPR WG), Harald Tveit Alvestrand
      • Re: Code/Text (Re: GPL and Status summary, IPR WG), todd glassey
  • <Possible follow-ups>
  • Re: GPL and Status summary, IPR WG, todd . glassey
    • Re: GPL and Status summary, IPR WG, Jeremy Hunsinger
  • RE: GPL and Status summary, IPR WG, Black_David
    • RE: GPL and Status summary, IPR WG, David B Harrington
  • RE: GPL and Status summary, IPR WG, Black_David
    • RE: GPL and Status summary, IPR WG, David B Harrington
    • Re: GPL and Status summary, IPR WG, todd glassey
• Status summary, IPR WG, Harald Tveit Alvestrand
  • Re: Status summary, IPR WG, Joel M. Halpern
  • Re: Status summary, IPR WG, Ted Hardie
    • Re: Status summary, IPR WG, Harald Tveit Alvestrand
      • Re: Status summary, IPR WG, Ted Hardie
      • Re: Status summary, IPR WG, Joel M. Halpern
      • Re: Status summary, IPR WG, John C Klensin
      • Re: Status summary, IPR WG, Brian E Carpenter
      • Re: Status summary, IPR WG, John C Klensin
  • Re: Status summary, IPR WG, Simon Josefsson
  • Re: Status summary, IPR WG, Tom Petch
    • Re: Status summary, IPR WG, Simon Josefsson
    • Re: Status summary, IPR WG, Harald Tveit Alvestrand
  • <Possible follow-ups>
  • Re: Status summary, IPR WG, todd . glassey
  • Re: Status summary, IPR WG, todd . glassey
  • Re: Status summary, IPR WG, Joel M. Halpern
  • Re: Status summary, IPR WG, todd . glassey
  • Re: Status summary, IPR WG, todd . glassey
  • Re: Status summary, IPR WG, todd . glassey
  • Re: Status summary, IPR WG, todd . glassey
• I-D ACTION:draft-ietf-ipr-rules-update-02.txt, Internet-Drafts
  • Re: I-D ACTION:draft-ietf-ipr-rules-update-02.txt, Simon Josefsson
    • Re: I-D ACTION:draft-ietf-ipr-rules-update-02.txt, Harald Tveit Alvestrand
• IPR WG co-chair and charter, Brian E Carpenter
  • Re: IPR WG co-chair and charter, Spencer Dawkins
    • Re: IPR WG co-chair and charter, Harald Tveit Alvestrand
      • Re: IPR WG co-chair and charter, Brian E Carpenter
      • Re: IPR WG co-chair and charter, Spencer Dawkins
      • Re: IPR WG co-chair and charter, Brian E Carpenter
  • <Possible follow-ups>
  • Re: IPR WG co-chair and charter, todd . glassey
    • Re: IPR WG co-chair and charter, Harald Tveit Alvestrand
  • Re: IPR WG co-chair and charter, todd . glassey
• Minutes from Vancouver, Harald Tveit Alvestrand
• Discussion of Separation of parts, Joel M. Halpern
  • Re: Discussion of Separation of parts, Simon Josefsson
    • Re: Discussion of Separation of parts, Spencer Dawkins
    • RE: Discussion of Separation of parts, David B Harrington
      • Re: Discussion of Separation of parts, Simon Josefsson
      • Re: Discussion of Separation of parts, Spencer Dawkins
    • Re: Discussion of Separation of parts, Ted Hardie
      • RE: Discussion of Separation of parts, David B Harrington
      • Re: Discussion of Separation of parts, todd glassey
  • <Possible follow-ups>
  • Re: Discussion of Separation of parts, todd . glassey
• RE: Copyright issues and authors (was: Re: One copyright issue or Two?), Powers Chuck-RXCP20
• Re: On separating code and text, todd . glassey
• Copyright issues and authors (was: Re: One copyright issue or Two?), John C Klensin
  • Re: Copyright issues and authors (was: Re: One copyright issue or Two?), todd glassey
  • Message not available
    • Re: Copyright issues and authors (was: Re: One copyright issue or Two?), John C Klensin
      • On separating code and text, Simon Josefsson
      • Re: On separating code and text, Joel M. Halpern
      • Re: On separating code and text, Simon Josefsson
      • Re: On separating code and text, Matthew Garrett
      • Re: On separating code and text, Simon Josefsson
      • Re: On separating code and text, John C Klensin
      • Re: On separating code and text, Simon Josefsson
      • Re: On separating code and text, Brian E Carpenter
      • Re: On separating code and text, Matthew Garrett
  • Re: Copyright issues and authors, Frank Ellermann
    • Re: Copyright issues and authors, Simon Josefsson
      • Re: Copyright issues and authors, Frank Ellermann
  • Re: Copyright issues and authors, Simon Josefsson
    • Re: Copyright issues and authors, John C Klensin
      • Re: Copyright issues and authors, Simon Josefsson
• Updated proposed license and another request for a charter update, Simon Josefsson
  • Re: Updated proposed license and another request for a charter update, Brian E Carpenter
    • Re: Updated proposed license and another request for a charter update, Simon Josefsson
      • Re: Updated proposed license and another request for a charterupdate, Spencer Dawkins
• Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Brian E Carpenter
  • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, todd glassey
    • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, todd glassey
  • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Simon Josefsson
    • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Brian E Carpenter
      • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Simon Josefsson
      • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Sam Hartman
      • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Brian E Carpenter
      • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Simon Josefsson
      • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Sam Hartman
      • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Joel M. Halpern
  • <Possible follow-ups>
  • RE: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, Powers Chuck-RXCP20
  • Re: I-D ACTION:draft-josefsson-ipr-rules-update-02.txt, todd . glassey
• Re: Reminder: Some people do not want their input to be widely distributed, todd . glassey
  • Re: Reminder: Some people do not want their input to be widely distributed, Sam Hartman
• Re: Reminder: Some people do not want their input to be widely distributed, todd . glassey
  • <Possible follow-ups>
  • Re: Reminder: Some people do not want their input to be widely distributed, todd . glassey
  • Re: Reminder: Some people do not want their input to be widely distributed, todd . glassey
  • RE: Reminder: Some people do not want their input to be widely distributed, Powers Chuck-RXCP20
    • Re: Reminder: Some people do not want their input to be widelydistributed, todd glassey
• Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing., todd . glassey
  • <Possible follow-ups>
  • Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing., todd . glassey
    • Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing., Lucy E. Lynch
      • Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing., Lucy E. Lynch
      • Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing., todd glassey