IETF Scott Bradner editor, IPR rules documents.

Slides:



Advertisements
Similar presentations
Confidentiality: Nondisclosure, Misuse, and Prosecution Bars David Hricik Professor, Mercer Law School Of Counsel, Taylor English Duma LLP.
Advertisements

What is a Working Group ID (and when to adopt one) Adrian Farrel Maastricht, July 2010.
SDN Research Group IETF 92 Chairs Dave Meyer Daniel King In memory of Ping Pan.
OAuth 2.0 Security IETF OAuth WG Conference Call, 14th December 2012.
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:
Beginning January 1, 2014, individuals will have access to insurance coverage through the health insurance exchanges (Exchanges), which are also known.
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.
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
1 Yet Another Mail Working Group IETF 81 July 26, 2011.
Dnssd WG Chairs: Tim Chown Ralph Droms IETF 89, London, 3 rd March 2014.
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.
NCRG Network Complexity Research Group Chairs: Michael Behringer, David Meyer 4 Mar 2014, London
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:
1 TCP Maintenance and Minor Extensions (TCPM) Working Group Pasi Sarolahti Michael Scharf Yoshifumi Nishida IETF 90 – Toronto, Canada July 2014.
CCAMP Working Group Online Agenda and Slides at: Data tracker:
1 Yet Another Mail Working Group IETF 78 July 29, 2010.
DetNet WG 1 ST Meeting Chairs: Lou Berger Pat Thaler Secretary: Jouni Korhonen.
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.
OAuth WG Blaine Cook, Hannes Tschofenig. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
SACM IETF 89, London, UK Dan Romascanu Adam Montville.
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.
Interface to the Routing System (IRS) BOF IETF 85, Atlanta November 2012.
IPR WG IETF 62 Minneapolis. IPR WG: Administrivia Blue sheets Scribes Use the microphones Note Well.
Transport Layer Security (TLS) IETF 73 Thursday, November Chairs: Eric Rescorla Joe Salowey.
IETF #73 - NETMOD WG session1 NETMOD WG IETF 73, Minneapolis, MN, USA November 20, David Harrington David Partain.
RADEXT WG IETF 89 Agenda March 4, Please join the Jabber room:
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:
DetNet WG Chairs: Lou Berger Pat Thaler Secretary: Jouni Korhonen
28 September 2005OMA MEM / IETF LEMONADE Workshop - London, UK 1 OMA MEM IETF LEMONADE joint workshop Jerry Weingarten Eric.
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.
Agenda Wednesday, July 29, :00 – 15:00 Congresshall B Please join the Jabber room: LEDBAT WG IETF 75.
Chairs Daniel King Kohei Shiomoto Secretary Will Liushucheng
<draft-bradner-rfc-extracts-00.txt>
Technology & Maintenance Council
Technology & Maintenance Council
SDN Research Group IETF 93 - Prague
Dirk Kutscher, Sarah Banks
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.
Technology & Maintenance Council
MODERN Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers IETF 101.
IETF 103 pim wg meeting.
Technology & Maintenance Council
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.
Technology & Maintenance Council
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.
Technology & Maintenance Council
Web Authorization Protocol (OAuth) WG Chairs: Hannes Tschofenig, Rifaat Shekh-Yusef, Security AD: Roman.
Web Authorization Protocol (OAuth) WG Chairs: Hannes Tschofenig, Rifaat Shekh-Yusef, Security AD: Roman.
IETF 103 pim wg meeting.
Homomorphic Encryption Standards: Governance Proposal
Scott Bradner & Martin Thomson
IETF 98 pim wg meeting.
Presentation transcript:

IETF Scott Bradner editor, IPR rules documents

From the RTCWEB Charter “The working group will follow BCP 79, and adhere to the spirit of BCP 79.” “The working group cannot explicitly rule out the possibility of adopting encumbered technologies; “ “however, the working group will try to avoid encumbered technologies that require royalties or other encumbrances that would prevent such technologies from being easy to use in web browsers.”

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”

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 “spirit of BCP 79” requires disclosure even if not active participant WG needs IPR information

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

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”

Questions?