[Fiware-oasc-etsi] ToR draft for revision prior submission -- re "royalty free"

[Franck Le Gall]

Hello

I agree with Lindsay approach.

In addition we only have limited options here (and this may be the reason why it has been suppressed from the initial text) as these aspects are already set within the ISG rules:


·         The ISG member agreement (see documents from Hermann) states that: "The Member agrees to the terms of, and shall abide by, the ETSI IPR Policy set forth in Annex 6 of the and their subsequent versions and evolutions (hereinafter, the "ETSI IPR Policy"), and to treat any specifications produced by the ISG as Technical Specifications under the ETSI IPR Policy."

·         The annex 6 of ETSI IPR Policy (http://www.etsi.org/images/files/ipr/etsi-ipr-policy.pdf) states that "the Declarant hereby irrevocably declares that (1) it and its AFFILIATES are prepared to grant irrevocable licenses under its/their IPR(s) on terms and conditions which are in accordance with Clause 6.1 of the ETSI IPR Policy, in respect of the STANDARD(S), TECHNICAL SPECIFICATION(S), or the ETSI Project(s), as identified above, to the extent that the IPR(s) are or become, and remain ESSENTIAL to practice that/those STANDARD(S) or TECHNICAL SPECIFICATION(S) or, as applicable, any STANDARD or TECHNICAL SPECIFICATION resulting from proposals or Work Items within the current scope of the above identified ETSI Project(s), for the field of use of practice of such STANDARD or TECHNICAL SPECIFICATION; and (2) it will comply with Clause 6.1bis of the ETSI IPR Policy with respect to such ESSENTIAL IPR(s)"

·         The clause 6.2 of ETSI IPR policy states that: "When an ESSENTIAL IPR relating to a particular STANDARD or TECHNICAL SPECIFICATION is brought to the attention of ETSI, the Director-General of ETSI shall immediately request the owner to give within three months an irrevocable undertaking in writing that it is prepared to grant irrevocable licences on fair, reasonable and non-discriminatory ("FRAND") terms and conditions under such IPR to at least the following extent:

o   MANUFACTURE, including the right to make or have made customized components and sub-systems to the licensee's own design for use in MANUFACTURE;

o   sell, lease, or otherwise dispose of EQUIPMENT so MANUFACTURED;

o   repair, use, or operate EQUIPMENT; and

o   use METHODS.

The above undertaking may be made subject to the condition that those who seek licences agree to reciprocate."


So my understanding is that these aspects are already covered by ETSI-ISG policy, as being the usual approach for ETSI standards.

Franck

De : fiware-oasc-etsi-bounces at lists.fiware.org [mailto:fiware-oasc-etsi-bounces at lists.fiware.org] De la part de Lindsay Frost
Envoyé : mercredi 10 août 2016 14:26
À : Juanjo Hierro <juanjose.hierro at telefonica.com>; Fiware-oasc-etsi at lists.fiware.org
Objet : Re: [Fiware-oasc-etsi] ToR draft for revision prior submission -- re "royalty free"

To: Juanjo Hierro <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>; Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>

Dear all,

regarding "public and royalty-free", there is a major difficulty in the words "will be" in the wording "Group Specifications will be public and royalty-free" because of course the CIM ISG members cannot guarantee that there is no IPR from any company (member or not) in a spec.

Even if the wording is changed to "CIM Members and Participants explicitly grant royalty-free licensing for any of their company IPR used in the specifications" the ISG will naturally need  to reference or include material from ETSI or OMA specs, which will make a system built according to the combined specs subject to FRAND licensing.

As an example, the OSGi operates according to Apache 2.0 IPR rules (zero royalty) and has enormous difficulty co-operating with other bodies which "only" have FRAND: OSGi just cannot accept technical inputs from such FRAND sources.

What _could_ be done is to insert text "Specifications published by the ISG CIM will be public and with royalty-free licensing,  although users are notified that usage of such specifications may require use of material subject to FRAND licensing."

Juanjo, would that satisfy the intent?

See other ETSI IPR details below.



best wishes

Lindsay





Appendix:  ETSI Rules for ISGs and for IPR Policy


I checked the ETSI ISG RULES in the ETSI Directives<https://portal.etsi.org/directives/36_directives_jun_2016.pdf> Section 3:
page 132 states "In any case, where a Partner is submitting a technical proposal for a Group Specification or a Group Report, it shall, on a bona fide basis, comply with the ETSI IPR Policy and draw the attention of ETSI not only to any of that Partner's IPR which might be essential if that proposal is adopted, but also to any of that Partner's member's IPR, which might be essential if that proposal is adopted."

I checked the ETSI IPR Policy from http://www.etsi.org/about/how-we-work/intellectual-property-rights-iprs available here ETSI IPR Policy<http://www.etsi.org/images/files/IPR/etsi-ipr-policy.pdf>:

" § 3.2 IPR holders whether members of ETSI and their AFFILIATES or third parties, should be adequately and fairly rewarded for the use of their IPRs in the implementation of STANDARDS and TECHNICAL SPECIFICATIONS."



"§ 6.1 When an ESSENTIAL IPR relating to a particular STANDARD or TECHNICAL SPECIFICATION is brought to the attention of ETSI, the Director-General of ETSI shall immediately request the owner to give within three months an irrevocable undertaking in writing that it is prepared to grant irrevocable licences on fair, reasonable and non-discriminatory ("FRAND") terms and conditions under such IPR [...]"





________________________________________

Dr. Lindsay Frost, Chief Standardization Eng.

frost at neclab.eu<mailto:frost at neclab.eu>     Mobile +49.163.275.1734

NEC Laboratories Europe, Kurfürsten-Anlage 36,

D-69115 Heidelberg, Germany.



Reg. Headoffice: NEC Europe Ltd, VAT DE161569151

Athene, Odyssey Business Park, West End Road,

London HA4 6QE, Reg. in England 2832014





-----Original Message-----
From: fiware-oasc-etsi-bounces at lists.fiware.org<mailto:fiware-oasc-etsi-bounces at lists.fiware.org> [mailto:fiware-oasc-etsi-bounces at lists.fiware.org] On Behalf Of Mulligan, Catherine E A
Sent: Mittwoch, 10. August 2016 09:55
To: Juanjo Hierro; Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>
Subject: Re: [Fiware-oasc-etsi] ToR draft for revision prior submission



Hi Juanjo,



I am in client meetings all day - I won¹t be able to look at this until about 3pm so I won¹t make the 4pm deadline.  I¹ll do it as soon as I can after I get out of meetings.



Sorry but I needed this yesterday to get it ready for you by today.



Best,

Cathy



--

Dr Catherine Mulligan

Research Fellow

Associate Director, Imperial College Centre for Cryptocurrency Research and Engineering



OASC Standardisation // oascities.org <http://oascities.org/> Director and Co-Founder of Contextualised // http://www.contextualised.com/

+ 44 753 888 7477

c.mulligan at imperial.ac.uk<mailto:c.mulligan at imperial.ac.uk>













On 10/08/2016, 08:19, "fiware-oasc-etsi-bounces at lists.fiware.org on behalf of Juanjo Hierro<mailto:fiware-oasc-etsi-bounces at lists.fiware.org%20on%20behalf%20of%20Juanjo%20Hierro>" <fiware-oasc-etsi-bounces at lists.fiware.org on behalf of juanjose.hierro at telefonica.com<mailto:fiware-oasc-etsi-bounces at lists.fiware.org%20on%20behalf%20of%20juanjose.hierro at telefonica.com>> wrote:



>

>   It would be nice to send to ETSI the draft today, sometime after

>16:00.   Please try to review the text quickly and bring comments

>earlier so that we can make it.

>

>   Cheers!

>

>-- Juanjo

>

>

>On 10/08/16 09:16, Juanjo Hierro wrote:

>> Dear all,

>>

>>   Please find attached the version of ToR that I believe would be

>> fine for submission to ETSI.

>>

>>   Thanks to Lindsay for his contributions.  I have finalized the ToR

>> draft working on the version he distributed yesterday.   I added his

>> input on liaisons.   I also incorporated the whole text of the action

>> established in the EC 2016 rolling Plan on ICT Standardization as

>> requested by Cathy.   I also incorporate some clarifications about

>> rules that would only apply to physical meetings (not virtual) like

>> distributing the agenda 30 days in advance (this is non-practical in

>> virtual confcalls which may be run more often).   I have clarified

>> that Reports and Specifications will only be approved in physical

>> meetings which I believe is acceptable.  I wonder whether you would

>> agree on that. I have also revised the part of Liasions with FIWARE

>> and give it some formatting here and there.

>>

>>   One important point that I have added is the statement that Group

>> Specifications will be public and royalty-free (check Scope section,

>> phase 2).   This was explicit in the very original drafts but after so

>> many changes I found it got diluted and this was relevant.   Note that

>> such statement would apply not only to the CIM-API but the rest of

>> specs we aim at producing (including information models).   I guess we

>> all agree on that.

>>

>>   I have added Linsay to the FIWARE OASC mailing list to keep the

>> more general discussion also under the list.

>>

>>   The final version to be submitted to the ETSI team will have all

>> those comments we have accepted already as clean revised text, so

>> only our comments on their comments will be highlighted. However, I

>> have kept their comments also highlighted in the version I send now

>> for your convenience.

>>

>>   Cheers,

>>

>> -- Juanjo

>>

>> ______________________________________________________

>>

>> Coordinator and Chief Architect, FIWARE platform IoT Unit, Telefónica

>>

>> email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>

>> twitter: @JuanjoHierro

>>

>> You can follow FIWARE at:

>>   website:  http://www.fiware.org

>>   twitter:  @FIWARE

>>   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

>>   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932

>>

>

>

>________________________________

>

>Este mensaje y sus adjuntos se dirigen exclusivamente a su

>destinatario, puede contener información privilegiada o confidencial y

>es para uso exclusivo de la persona o entidad de destino. Si no es

>usted. el destinatario indicado, queda notificado de que la lectura,

>utilización, divulgación y/o copia sin autorización puede estar

>prohibida en virtud de la legislación vigente. Si ha recibido este

>mensaje por error, le rogamos que nos lo comunique inmediatamente por

>esta misma vía y proceda a su destrucción.

>

>The information contained in this transmission is privileged and

>confidential information intended only for the use of the individual or

>entity named above. If the reader of this message is not the intended

>recipient, you are hereby notified that any dissemination, distribution

>or copying of this communication is strictly prohibited. If you have

>received this transmission in error, do not read it. Please immediately

>reply to the sender that you have received this communication in error

>and then delete it.

>

>Esta mensagem e seus anexos se dirigem exclusivamente ao seu

>destinatário, pode conter informação privilegiada ou confidencial e é

>para uso exclusivo da pessoa ou entidade de destino. Se não é vossa

>senhoria o destinatário indicado, fica notificado de que a leitura,

>utilização, divulgação e/ou cópia sem autorização pode estar proibida

>em virtude da legislação vigente. Se recebeu esta mensagem por erro,

>rogamos-lhe que nos o comunique imediatamente por esta mesma via e

>proceda a sua destruição

>_______________________________________________

>Fiware-oasc-etsi mailing list

>Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>

>https://lists.fiware.org/listinfo/fiware-oasc-etsi



_______________________________________________

Fiware-oasc-etsi mailing list

Fiware-oasc-etsi at lists.fiware.org<mailto:Fiware-oasc-etsi at lists.fiware.org>

https://lists.fiware.org/listinfo/fiware-oasc-etsi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-oasc-etsi/attachments/20160810/5547a184/attachment.html>