IPR in the IETF Personal Thoughts from an AD Adrian Farrel Thanks to: Dave Ward, Ross Callon, Scott Brander, Jorge Contreras,

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum Network Services Interface OGF29: Working Group Meeting Guy Roberts, 19 th Jun 2010.
Advertisements

PWG Instructions for the WG Chair At Each Meeting, the Working Group Chair shall: Show slides #2 and #3 of this presentation Advise the WG membership that:
Intellectual Property Rights Policy Mark Palmer – Vice Chair 24 May 2006 U NITED N ATIONS C ENTRE F OR T RADE F ACILITATION A ND E LECTRONIC B USINESS.
Doc.: IEEE /024 Submission January 2001 Jim Carlo, Texas InstrumentsSlide 1 Patents and IEEE 802 Stds IEEE 802 Chair’s Viewpoint Jim Carlo General.
What is a Working Group ID (and when to adopt one) Adrian Farrel Maastricht, July 2010.
Deterministic Networking (DetNet) BoF IETF 91 Monday Afternoon Session II, Coral 1.
L2VPN WG “NVO3” Meeting IETF 82 Taipei, Taiwan. Agenda Administrivia Framing Today’s Discussions (5 minutes) Cloud Networking: Framework and VPN Applicability.
Tcpsecure ipr 1 Cisco IPR Disclosure Relating to tcpsecure Scott Bradner
CCAMP Working Group Online Agenda and Slides at: ccamp Data tracker:
CCAMP Working Group Online Agenda and Slides at: ccamp Data tracker:
1 May 2007 Instructions for the WG Chair The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: l Show slides #1 through #5 of.
Commercialization of R&D Results: How to Prepare For The Early Stages.
Routing Area Open Meeting Paris, March 2012 Area Directors Adrian Farrel Stewart Bryant.
IPR Issues: What ’ s New (and a little of what ’ s old) Scott Brim IETF 61.
CCAMP Working Group Online Agenda and Slides at: Data tracker:
Dime WG Status Update IETF#81, THURSDAY, July 28, Afternoon Session I.
DIME WG IETF 84 DIME WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Lionel Morand.
Indication of Trademarks in IETF Documents Scott Bradner
LMAP WG IETF 89, London, UK Dan Romascanu Jason Weil.
Doc.: IEEE /0803r1 Submission July 2005 TK Tan, Philips Slide 1 WNG SC Closing Report Notice: This document has been prepared to assist IEEE
© 2006 Open Grid Forum Service Level Terms Andrew Grimshaw.
Wed 31 Jul & Fri 2 Aug 2013SIDR IETF 87 Berlin, German1 SIDR Working Group IETF 87 Berlin, Germany Wednesday, 31 Jul 2013 Friday, 2 Aug 2013.
Routing Area Open Meeting Hiroshima, November 2009 Area Directors Ross Callon Adrian Farrel.
CCAMP Working Group Online Agenda and Slides at: Data tracker:
IETF Adrian Farrel & Scott Bradner. Apologies to those who have seen this before It cannot be said often enough It is fundamental to how the IETF.
Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AS 18 March 2014 Authors: NameCompanyPhone .
Delay-tolerant Networking Research Group (DTNRG) 85 th IETF – Atlanta 8 November 2012 Jabber room: Mailing list:
CCAMP Working Group Online Agenda and Slides at: Data tracker:
Moscow, Russia, 10 September 2012 HSE Intellectual Property Policy Aliya Ermakova, Head of IP Department, Innovation and Enterprise Office, HSE
DetNet WG 1 ST Meeting Chairs: Lou Berger Pat Thaler Secretary: Jouni Korhonen.
TIA IPR Standing Committee Report to TIA Technical Committee “Normative References and IPR” October 21, 2005 Paul Vishny, Chair Dan Bart, TIA.
IETF Trust Chair Report Ed Juskevicius November 22, 2008 Minneapolis, MN, USA.
IETF Trust Chair Report Ed Juskevicius November 19, 2008 Minneapolis, MN, USA.
P2PSIP WG IETF 87 P2PSIP WG Agenda & Status Thursday, August 1 st, 2013 Brian Rosen, Carlos J. Bernardos.
Wed 31 Jul & Fri 2 Aug 2013SIDR IETF 87 Berlin, German1 SIDR Working Group IETF 87 Berlin, Germany Wednesday, 31 Jul 2013 Friday, 2 Aug 2013.
Routing Area Open Meeting Vancouver, July/August Area Directors Adrian Farrel Stewart Bryant.
IETF Scott Bradner editor, IPR rules documents.
DMM WG IETF 84 DMM WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Julien Laganier.
RADEXT WG Virtual Interim Agenda Monday, October 11, :00 AM – 10:00 AM PDT Please join the Jabber room:
3/12/20161 Document Title: Agenda and Admin for IEEE WG Meeting on 02 December 2014 Document Date: 25 November 2014 Document No: agen.
IETF Trust Chair Report Marshall Eubanks November 2011.
DetNet WG Chairs: Lou Berger Pat Thaler Secretary: Jouni Korhonen
1 IETF 95 Buenos Aires, AR TEAS Working Group Online Agenda and Slide: Data tracker:
Mon 23 Mar 2015SIDR IETF 92 Dallas, TX, US1 SIDR Working Group IETF 92 Dallas, TX, US Monday, 23 Mar 2015.
Fri 24 Jul 2015SIDR IETF 93 Prague, CZ1 SIDR Working Group IETF 93 Prague, CZ Friday, 24 Jul 2015.
PKCS Contribution Agreement Burt Kaliski, RSA Laboratories PKCS Workshop, 28 September 1999.
Security Events (SecEvent)
DetNet WG Chairs: Lou Berger
RISGE-RG use case template
DetNet WG Chairs: Lou Berger
PAWS Protocol to Access White Space DB
pre8prob BOF Background
TEAS Working Group IETF London Online Agenda and Slides:
MODERN Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers IETF 101.
Activity Delegation Kick Off
DetNet WG Chairs: Lou Berger
Sanctions Are Available
TEAS Working Group IETF 97 Seoul Online Agenda and Slide:
IEEE Contribution Author’s Name Affiliation Address Phone
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Common Operations and Management on network Slices (coms) BoF
TGu Ad Hoc Agenda Date: Authors: February 2007
TGu Ad Hoc Agenda Date: Authors: February 2007
Note Well This is a reminder of IETF policies in effect on various topics such as patents or code of conduct. It is only meant to point you in the right.
IEEE IPR Policy Date: Authors: March 2006 March 2006
TEAS Working Group IETF Prague
Trusted Execution Environment Provisioning (TEEP) WG
DetNet WG Chairs: Lou Berger
RTGWG status update IETF 105 Montreal Chairs:
DetNet WG Chairs: Lou Berger
Presentation transcript:

IPR in the IETF Personal Thoughts from an AD Adrian Farrel Thanks to: Dave Ward, Ross Callon, Scott Brander, Jorge Contreras, Joel Halpern

Apologies to those who have this before –It cannot be said often enough It is fundamental to how the IETF operates –What an individual need to know and do –What a Working Group needs to understand This is not a tutorial and it is not legal advice –I am not a lawyer –Read the IPR RFCs yourselves –Read the Note Well notice in your registration packs and online –Take legal advice

Individuals Have Responsibilities Individuals who participates are “Contributors” You participate if you: –Edit a draft –Co-author a draft –Present at a meeting –Speak at the microphone –Send an to an IETF list The responsibilities are your own personal responsibilities –You cannot hide behind your company or their processes

Authors and Editors Boilerplate is now very simple This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. BCP 78 –RFC 5378 “Rights Contributors Provide to the IETF Trust” BCP 79 –RFC 3979 “Intellectual Property Rights in IETF Technology” –RFC 4879 Third Party Disclosure Procedure By having your name on a draft you are agreeing to conform to these RFCs –It is possible that you are legally liable if you do not –If you violate these RFCs you are breaking the “IETF contract”

Other Contributors The RFCs are phrased wrt “contributors” The RFCs form part of the IETF process –By participating in the IETF you agree to adhere to the process You may work to change the process! The “Note Well” note covers –Participation in IETF meetings –Participation on IETF mailing lists Read the definition in RFC 3979

What Are the Requirements on Contributors? Any Contributor who reasonably and personally knows of IPR meeting the conditions of Section 6.6 [of RFC 3979] which the Contributor believes Covers or may ultimately Cover his or her Contribution, or which the Contributor reasonably and personally knows his or her employer or sponsor may assert against Implementing Technologies based on such Contribution, must make a disclosure

What is a Disclosure? Disclosure is easy – It is a statement that IPR exists It includes a reference any related I-Ds or RFCs It includes a licensing statement –May be a deferral saying terms will follow later –An IPR owner is not required to grant a license Third-party disclosures –RFC 3979 [disclosures] can come from people submitting technical proposals as Internet-Drafts, on mailing lists or at meetings, from other people participating in the working group or from third parties who find out that the work is going or has gone on –That means you have to disclose if you know about someone else’s IPR This can be really hard for contractors –Third-party disclosure is quite vague Named companies/individuals will be contacted by the IETF

When to Disclose RFC 3979 defines: "IPR" or "Intellectual Property Rights": means patent, copyright, utility model, invention registration, database and data rights that may Cover an Implementing Technology, whether such rights arise from a registration or renewal thereof, or an application therefore, in each case anywhere in the world. This means don’t wait until the patent is granted Disclosure is required “as soon as reasonably possible” after publication of an Internet-Draft –But you can disclose sooner! Pay attention! –Failing to disclose on time may possibly Damage your reputation in the IETF Damage your company’s reputation in the IETF Reduce your chance of being able to enforce your patent

What Should a WG Do? WG is informed when a disclosure is made You can search for disclosures at – RFC 2026 lays the foundations for basic principles a)the IETF will make no determination about the validity of any particular IPR claim b)the IETF following normal processes can decide to use technology for which IPR disclosures have been made if it decides that such a use is warranted WG needs to consider IPR as part of the consensus process –Is the WG willing to go ahead with this work in the light of the IPR disclosure? –This is based on individual opinions The WG / IETF / WG chairs MUST NOT –Attempt opinions on the validity of the disclosure –Lead the discussion or give specific advice

Summary IPR is a fact of life We are all bound by the IETF IPR Policy –Read it! We are responsible as individuals –Interaction with our companies or customers may be very difficult –Make sure you understand the IETF’s IPR Policy If we don’t like or cannot conform to the IETF’s IPR Policy our only option is to cease to participate in the work covered by the IPR Get legal advice

References IETF IPR Policy RFC 2026 RFC 3979 RFC 4879 RFC 5378 Dave Ward slides from San Francisco – Plenary slides from San Francisco – 1/plenaryw-1_files/frame.htm