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.

Slides:



Advertisements
Similar presentations
Experimental Internet Resource Allocations Philip Smith, Geoff Huston September 2002.
Advertisements

COSTS AGREEMENTS AND DISCLOSURES BAR ASSOCIATION CPD SEMINAR 2 AUGUST 2007 By Roger Traves SC.
COMPLETE IN TEN MINUTES Turn to page 18 in your notes and write down two differences between Balfour and Merritt in terms of legal points. Complete the.
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.
1 Disclosing Student Personal Information to the Queensland Police Service 1-2 July 2008 RED/EDS Business Meeting.
©2015 Paul Read 7.5 Writing Discussion Essays in Part Two /sizes/z/in/photostream/
Acceptance Definition: The final expression of agreement (assent) to the terms of an offer.
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.
Internet Research Task Force Crypto Forum Research Group IETF 89 March 3, 2014 London List: Chairs:
Commercialization of R&D Results: How to Prepare For The Early Stages.
IPR Guidelines for Working Groups draft- Scott Brim
IPR in the IETF Personal Thoughts from an AD Adrian Farrel Thanks to: Dave Ward, Ross Callon, Scott Brander, Jorge Contreras,
IPR Issues: What ’ s New (and a little of what ’ s old) Scott Brim IETF 61.
Submission February 2014 Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AR 20 March 2014 Authors: NameCompanyPhone .
Submission February 2014 Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AR 19 February 2014 Authors: NameCompanyPhone .
Doc.: IEEE /1129r1 Submission July 2006 Harry Worstell, AT&TSlide 1 Appeal Tutorial Notice: This document has been prepared to assist IEEE
CCAMP Working Group Online Agenda and Slides at: Data tracker:
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.
Routing Area WG (rtgwg) IETF 90 – London Chairs: Alvaro Retana Jeff Tantsura
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:
1 Declaration of Affiliation: Understanding Your Disclosure Obligations 1.
Doc.: IEEE /1084r00 Submission September 2015 Adrian Stephens, Intel CorporationSlide WG Chair comments to TGah Date: Authors:
NEWTRK WG Paris, August 5, Agenda 0 – agenda bashing – 10m 1 - introduction & status - chair- 10m discussion on the issues with ISD proposal.
NCRG Network Complexity Research Group Chairs: Michael Behringer, David Meyer 4 Mar 2014, London
Routing Area WG (rtgwg) IETF 86 – Orlando Chairs: Alia Atlas Alvaro Retana
IETF 86 PIM wg meeting. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC.
1 Virtual Router Redundancy Protocol (VRRP) San Francisco IETF VRRP Working Group March 2003 San Francisco IETF Mukesh Gupta / Nokia Chair.
Protocol Privacy Considerations Russ Housley IETF Chair 8 December 2010.
Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AS 18 March 2014 Authors: NameCompanyPhone .
IM NETWORK MEETING 20 TH JULY, 2010 CONSULTATION WITH 3 RD PARTIES.
RADEXT WG IETF 93 Agenda July 20, Please join the Jabber room:
3777 drp 1 Arbiter Report: RFC 3777 Dispute Resolution Jan Scott Bradner 12 March 2008.
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:
DetNet WG 1 ST Meeting Chairs: Lou Berger Pat Thaler Secretary: Jouni Korhonen.
Polling and Voting Adrian Farrel Routing Area Director Maastricht, July 2010.
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 WG (rtgwg) IETF 84 – Vancouver Chairs: Alia Atlas Alvaro Retana
IETF Scott Bradner editor, IPR rules documents.
PAWS Protocol to Access White Space DB IETF 88, Vancouver Gabor Bajko, Brian Rosen.
Agenda Marc Blanchet and Chris Weber July 2011 IRI WG IETF 81 1.
DMM WG IETF 84 DMM WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Julien Laganier.
Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AB 20 March 2014 Authors: NameCompanyPhone .
IETF #73 - NETMOD WG session1 NETMOD WG IETF 73, Minneapolis, MN, USA November 20, David Harrington David Partain.
Management Responsibilities Section Understanding Business and Personal Law Management Responsibilities Section 29.2 Operating a Corporation What.
DICE BOF, IETF-87 Berlin DTLS In Constrained Environments (DICE) BOF Wed 15:10-16:10, Potsdam 3 BOF Chairs: Zach Shelby, Carsten Bormann Responsible AD:
Interface to Network Security Functions (I2NSF) Chairs: Linda Dunbar Adrian Farrel IETF 95, Thursday April 7, 2016,
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.
<draft-bradner-rfc-extracts-00.txt>
IETF 84 Vancouver, BC, CA Wednesday, 1 Aug 2012
TEAS Working Group IETF London Online Agenda and Slides:
MODERN Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers IETF 101.
Sanctions Are Available
TEAS Working Group IETF 97 Seoul Online Agenda and Slide:
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
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.
Presentation transcript:

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 operates What an individual need to know and do What a Working Group needs to understand And, therefore, what WG chairs need to understand This is not legal advice We are not lawyers Read the IPR RFCs & Note Well yourselves Get your own legal advice for your own individual positions

Environment rulesets: IPR - BCP79 a.k.a. RFC 3979 (from RFC 2026) sanctions - RFC 6701 your IPR = patents & patent applications owned, assertable or licenseable by you or your employer or sponsor known (or should be known) by you

Enforcement IETF enforcement possibilities in RFC 6701 kicked off lists, etc. most enforcement by courts (maybe some by trust regulators) can lose power to assert patent

Contribution what the Note Well Note is all about anything you say or write (in any context) that is intended to influence an IETF activity is a contribution you agreed to Note Well Note to register for this meeting & to subscribe to a mailing list rules apply to ALL contributions not just “standards track”

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

Disclosures your IPR in your contribution: MUST disclose your IPR in contribution by fellow employee: they MUST disclose your IPR in another’s contribution & you participate in discussion: you MUST disclose your IPR in another’s contribution and you do not participate: PLEASE disclose you know of someone else’s IPR in a contribution: please disclose

Participate evolving definition of “participate” courts & IETF consensus moving towards including being on the mailing list or in the room normal practice for past disclosures has not been limited to active participation

When as soon as reasonable after you know some delay due to corporate lawyers but should not be long (days or weeks max) note: in most companies the lawyers insist on making any disclosure

Disclosure Details if patent: provide patent number & point to specific parts of IETF contribution same detail not required for patent applications blanket disclosures not permitted unless offering unconditional free license e.g., no reciprocity licensing information not required in disclosure but encouraged

Getting Disclosures: RFC 6702 Use the “Note Well” and make sure it is clear –Don’t just display it – talk about what it means to the meeting Poll the authors for confirmation of IPR status –Before WG adoption –Before/during WG last call –Usually do the poll on the list –Example messages in the RFC Require information in Shepherd Write-up (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? (8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures. Disclosures called out in IETF last call

Use of Disclosures Working Group empowered to think can decide whether to adopt technology with IPR claim(s) or to work around, or drop topic but note that all IPR may not be disclosed e.g., by someone outside IETF also, IPR claim may be “exaggerated”

Use of Disclosures, contd. WG is informed by when a disclosure is made You can also 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

What are the Bad Cases? Disclosures are good things They let us know where we stand They let us choose how to proceed Late disclosures can be disruptive We may have to revisit work They are still better than no disclosure Very late disclosures can be very disruptive We may have to pull a document back for further WG consideration They may mean revisiting an RFC They are still better than no disclosure

Questions?