From daniel.gidoin at thalesgroup.com Thu May 2 16:03:17 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 2 May 2013 16:03:17 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Audio conference of tomorrow rescheduled from 2:00 pm to 3 p.m. Message-ID: <11875_1367503409_51827231_11875_19034_1_622d854a-3171-4fbf-8d1e-5a2569800f2c@THSONEA01HUB04P.one.grp> Dear All, I will be one vacation tomorrow but Kreshnik will be my replacement. The audio conference has been rescheduled from 2:00 pm to 3 p.m. Our apologies for any inconvenience. Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue May 7 13:05:31 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 07 May 2013 13:05:31 +0200 Subject: [Fiware-security] Fwd: Session about API Access Control on Monday May 13 afternoon In-Reply-To: <5187104B.8070804@tid.es> References: <5187104B.8070804@tid.es> Message-ID: <5188DFFB.8020804@tid.es> Hi, Maybe some of you do not still have the fiware-api-cross mailing list where you are listed "in your radar", so you may have missed this important message. Some reaction would be rather welcome. Cheers, -- Juanjo -------- Original Message -------- Subject: Session about API Access Control on Monday May 13 afternoon Date: Mon, 06 May 2013 04:07:07 +0200 From: Juanjo Hierro To: Fiware-api-cross at lists.fi-ware.eu CC: Pascal Bisson , "daniel.gidoin at thalesgroup.com" Dear colleagues, I would like to have a session on Monday May 13 afternoon (Part II of the weekly joint WPLs/WPAs follow-up confcalls, from 14:30 to 16:00) to push activities related to the API Access Control framework we agree to offer to FI-WARE application developers in Release 2 (attached, for your convenience, the slides we agreed upon with the final reference architecture represented in the last slide). Despite I may come later this week with more details, there are a number of points I would like to tackle during that session which I can anticipate at this point: * @NSN/DT: status regarding support of OAuth messages (steps 4, 6, 7, 11 and 12 in the last slide of the attached presentation illustrating the final reference architecture). Could you point me out where in the IdM GE Open Specifications can I find the specification of the REST API that comprises the operations supporting these steps ? If that REST API specification is a standard specification, it would be nice to see a link to it together with a statement about its support by the IdM GE. It may have passed unadvertised to me, but I couldn't find anything like that ... * @UPM: I would like to see an analysis of the APIs provided by the XACML PDP component (Access Control GE) to be provided by Thales: * APIs to be invoked by the Proxy component * APIs to be used by the FI-WARE OIL Portal, or application-specific portals, to configure access control policies to be enforced by the XACML PDP component (Access Control GE) by Thales * @UPM: status of the implementation of the Proxy component that may interact both with Keystone components from OpenStack and the XACML PDP component (Access Control GE) by Thales * @NSN/DT: status about implementation of APIs enabling creation/deletion/management of users and organization of users as well as the definition of attributes for both ... This would enable application providers or FI-WARE Instance Providers, among others, to define portals for management of application users ... (note that very much related to this, I raise a hot issue below) Please book the proposed slot in your agendas. If you can provide some input to the above questions in advance to the meeting, it would be rather nice. I take this opportunity to raise a number of hot issues I have detected while reviewing contents of the Security Chapter in the FI-WARE Architecture. It would be nice to see some clarifications on your side ASAP: * IdM GE API Open Specifications: Frankly speaking, I can't find any API specification associated to the FI-WARE IdM GE ... what you have there are the URLs of service endpoints linked to concrete instances of the IdM GE, provided by DT and NSN. This might be useful information to publish in the tab "instances" linked to entries in the FI-WARE Catalogue associated to the IdM GEis implemented by NSN and DT ... but why is this stuff published as part of the IdM GE Open Specifications ? I have found that a similar comment was raised by TID/UPM during the peer review but seems like it had been ignored ... If part of the IdM GE API Open Specifications matches a given standard then you should provide a link to the published specs together with comments regarding level of support of the referred spec (e.g., may be not all the operations in the standard API you make a link to are supported in your implementation). Besides, at one point you state: "Additional to the authentication and authorization interfaces the Identity Management GEs delivers a REST API for all functionalities regarding user and profile management" ... however I can't see that REST API specified anywhere ... Where is it ? Last but not least, I have read in one of the comments that some of the examples you provide were related to OAuth 1.0 rather than OAuth 2.0 ... could you confirm that you will support OAuth 2.0 ? * Access Control GE: I read the following as part of the Open Specs and it rather seems inadmissible to me: "The API operations and associated datatypes are fully described in the Access Control GE - Authorization Restful API (fiware.access_control_ge.authz.api.wadl.zip) package available in document folder Cross Topics > APIs access control, monitoring and accounting of project FI-WARE Private". Please, FI-WARE Open Specifications are public ! we cannot deliver something like this ! Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Security 13-02-25.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 136175 bytes Desc: not available URL: From robert.seidl at nsn.com Tue May 7 13:27:10 2013 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Tue, 7 May 2013 11:27:10 +0000 Subject: [Fiware-security] Fwd: Session about API Access Control on Monday May 13 afternoon In-Reply-To: <5188DFFB.8020804@tid.es> References: <5187104B.8070804@tid.es> <5188DFFB.8020804@tid.es> Message-ID: Hi Juanjo, if I get it right the date will be Monday May 13 from 14:30 to 16:00. If this is correct unfortunately NSN can't participate due to a parallel all day work shop. Sorry for that. Greetings Robert From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Tuesday, May 07, 2013 1:06 PM To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] Fwd: Session about API Access Control on Monday May 13 afternoon Hi, Maybe some of you do not still have the fiware-api-cross mailing list where you are listed "in your radar", so you may have missed this important message. Some reaction would be rather welcome. Cheers, -- Juanjo -------- Original Message -------- Subject: Session about API Access Control on Monday May 13 afternoon Date: Mon, 06 May 2013 04:07:07 +0200 From: Juanjo Hierro To: Fiware-api-cross at lists.fi-ware.eu CC: Pascal Bisson , "daniel.gidoin at thalesgroup.com" Dear colleagues, I would like to have a session on Monday May 13 afternoon (Part II of the weekly joint WPLs/WPAs follow-up confcalls, from 14:30 to 16:00) to push activities related to the API Access Control framework we agree to offer to FI-WARE application developers in Release 2 (attached, for your convenience, the slides we agreed upon with the final reference architecture represented in the last slide). Despite I may come later this week with more details, there are a number of points I would like to tackle during that session which I can anticipate at this point: * @NSN/DT: status regarding support of OAuth messages (steps 4, 6, 7, 11 and 12 in the last slide of the attached presentation illustrating the final reference architecture). Could you point me out where in the IdM GE Open Specifications can I find the specification of the REST API that comprises the operations supporting these steps ? If that REST API specification is a standard specification, it would be nice to see a link to it together with a statement about its support by the IdM GE. It may have passed unadvertised to me, but I couldn't find anything like that ... * @UPM: I would like to see an analysis of the APIs provided by the XACML PDP component (Access Control GE) to be provided by Thales: * APIs to be invoked by the Proxy component * APIs to be used by the FI-WARE OIL Portal, or application-specific portals, to configure access control policies to be enforced by the XACML PDP component (Access Control GE) by Thales * @UPM: status of the implementation of the Proxy component that may interact both with Keystone components from OpenStack and the XACML PDP component (Access Control GE) by Thales * @NSN/DT: status about implementation of APIs enabling creation/deletion/management of users and organization of users as well as the definition of attributes for both ... This would enable application providers or FI-WARE Instance Providers, among others, to define portals for management of application users ... (note that very much related to this, I raise a hot issue below) Please book the proposed slot in your agendas. If you can provide some input to the above questions in advance to the meeting, it would be rather nice. I take this opportunity to raise a number of hot issues I have detected while reviewing contents of the Security Chapter in the FI-WARE Architecture. It would be nice to see some clarifications on your side ASAP: * IdM GE API Open Specifications: Frankly speaking, I can't find any API specification associated to the FI-WARE IdM GE ... what you have there are the URLs of service endpoints linked to concrete instances of the IdM GE, provided by DT and NSN. This might be useful information to publish in the tab "instances" linked to entries in the FI-WARE Catalogue associated to the IdM GEis implemented by NSN and DT ... but why is this stuff published as part of the IdM GE Open Specifications ? I have found that a similar comment was raised by TID/UPM during the peer review but seems like it had been ignored ... If part of the IdM GE API Open Specifications matches a given standard then you should provide a link to the published specs together with comments regarding level of support of the referred spec (e.g., may be not all the operations in the standard API you make a link to are supported in your implementation). Besides, at one point you state: "Additional to the authentication and authorization interfaces the Identity Management GEs delivers a REST API for all functionalities regarding user and profile management" ... however I can't see that REST API specified anywhere ... Where is it ? Last but not least, I have read in one of the comments that some of the examples you provide were related to OAuth 1.0 rather than OAuth 2.0 ... could you confirm that you will support OAuth 2.0 ? * Access Control GE: I read the following as part of the Open Specs and it rather seems inadmissible to me: "The API operations and associated datatypes are fully described in the Access Control GE - Authorization Restful API (fiware.access_control_ge.authz.api.wadl.zip) package available in document folder Cross Topics > APIs access control, monitoring and accounting of project FI-WARE Private". Please, FI-WARE Open Specifications are public ! we cannot deliver something like this ! Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From susana.gzarzosa at atosresearch.eu Fri May 10 09:03:30 2013 From: susana.gzarzosa at atosresearch.eu (Susana Gonzalez Zarzosa) Date: Fri, 10 May 2013 09:03:30 +0200 Subject: [Fiware-security] PoSecCo survey on security and compliance process Message-ID: Dear all, I would like to inform you about a current survey of the PoSecCo project. Considering your professional background, you would be a perfect respondent. The survey focuses on security and compliance process, takes about 10 to 15 minutes to complete and is in English. You can access the survey via https://www.soscisurvey.de/posecco2013. It would be highly appreciated, if you would participate in the survey. Certainly, your data is stored anonymized and is analysed only for the purpose of this survey. Additionally, I would also like to inform you about the newsletter of the PoSecCo project. If you want to receive news and information about upcoming events regarding the PoSecCo project, you can subscribe to the newsletter at http://www.posecco.eu/. Best wishes, ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Fri May 10 11:28:00 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Fri, 10 May 2013 11:28:00 +0200 Subject: [Fiware-security] Session about API Access Control on Monday May 13 afternoon In-Reply-To: <5187104B.8070804@tid.es> References: <5187104B.8070804@tid.es> Message-ID: <518CBDA0.6030204@tid.es> Hi, I would like you to confirm your availability for this topic in the agenda of our joint WPLs/WPAs follow-up confcall on Monday May 13 afternoon. Feedback on the several questions would be also welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 06/05/13 04:07, Juanjo Hierro wrote: Dear colleagues, I would like to have a session on Monday May 13 afternoon (Part II of the weekly joint WPLs/WPAs follow-up confcalls, from 14:30 to 16:00) to push activities related to the API Access Control framework we agree to offer to FI-WARE application developers in Release 2 (attached, for your convenience, the slides we agreed upon with the final reference architecture represented in the last slide). Despite I may come later this week with more details, there are a number of points I would like to tackle during that session which I can anticipate at this point: * @NSN/DT: status regarding support of OAuth messages (steps 4, 6, 7, 11 and 12 in the last slide of the attached presentation illustrating the final reference architecture). Could you point me out where in the IdM GE Open Specifications can I find the specification of the REST API that comprises the operations supporting these steps ? If that REST API specification is a standard specification, it would be nice to see a link to it together with a statement about its support by the IdM GE. It may have passed unadvertised to me, but I couldn't find anything like that ... * @UPM: I would like to see an analysis of the APIs provided by the XACML PDP component (Access Control GE) to be provided by Thales: * APIs to be invoked by the Proxy component * APIs to be used by the FI-WARE OIL Portal, or application-specific portals, to configure access control policies to be enforced by the XACML PDP component (Access Control GE) by Thales * @UPM: status of the implementation of the Proxy component that may interact both with Keystone components from OpenStack and the XACML PDP component (Access Control GE) by Thales * @NSN/DT: status about implementation of APIs enabling creation/deletion/management of users and organization of users as well as the definition of attributes for both ... This would enable application providers or FI-WARE Instance Providers, among others, to define portals for management of application users ... (note that very much related to this, I raise a hot issue below) Please book the proposed slot in your agendas. If you can provide some input to the above questions in advance to the meeting, it would be rather nice. I take this opportunity to raise a number of hot issues I have detected while reviewing contents of the Security Chapter in the FI-WARE Architecture. It would be nice to see some clarifications on your side ASAP: * IdM GE API Open Specifications: Frankly speaking, I can't find any API specification associated to the FI-WARE IdM GE ... what you have there are the URLs of service endpoints linked to concrete instances of the IdM GE, provided by DT and NSN. This might be useful information to publish in the tab "instances" linked to entries in the FI-WARE Catalogue associated to the IdM GEis implemented by NSN and DT ... but why is this stuff published as part of the IdM GE Open Specifications ? I have found that a similar comment was raised by TID/UPM during the peer review but seems like it had been ignored ... If part of the IdM GE API Open Specifications matches a given standard then you should provide a link to the published specs together with comments regarding level of support of the referred spec (e.g., may be not all the operations in the standard API you make a link to are supported in your implementation). Besides, at one point you state: "Additional to the authentication and authorization interfaces the Identity Management GEs delivers a REST API for all functionalities regarding user and profile management" ... however I can't see that REST API specified anywhere ... Where is it ? Last but not least, I have read in one of the comments that some of the examples you provide were related to OAuth 1.0 rather than OAuth 2.0 ... could you confirm that you will support OAuth 2.0 ? * Access Control GE: I read the following as part of the Open Specs and it rather seems inadmissible to me: "The API operations and associated datatypes are fully described in the Access Control GE - Authorization Restful API (fiware.access_control_ge.authz.api.wadl.zip) package available in document folder Cross Topics > APIs access control, monitoring and accounting of project FI-WARE Private". Please, FI-WARE Open Specifications are public ! we cannot deliver something like this ! Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon May 13 11:15:39 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 May 2013 11:15:39 +0200 Subject: [Fiware-security] TR: FIWARE - WP8 - Unit Tests - review Message-ID: <18180_1368436539_5190AF3A_18180_113_1_813aaed1-2f7e-4845-a4bf-4ce3ee7e727e@THSONEA01HUB02P.one.grp> Dear Colleagues, I'm forwarding you this review perform by Manuel (TID) of unit tests . Could you please urgently address comments received and perform the actions requested. Also inform me/Daniel/Kreshnik once done. As usual the sooner the better Best Regards, Pascal De : MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Envoy? : mardi 7 mai 2013 11:57 ? : BISSON Pascal Objet : FIWARE - WP8 - Unit Tests - review Hi Pascal, Please, find attached a spreadsheet with comments to the Unit Tests. I would appreciate they were taken into consideration and due action taken to fix them. If any doubt or concern, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP8 - Unit Tests_20130507.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 16222 bytes Desc: WP8 - Unit Tests_20130507.xlsx URL: From pascal.bisson at thalesgroup.com Mon May 13 11:53:55 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 May 2013 11:53:55 +0200 Subject: [Fiware-security] FI-WARE WP8 Weekly audio conf Message-ID: <32752_1368438840_5190B838_32752_11488_3_eb7f1dbd-858b-432a-9921-87b2dbbbc48e@THSONEA01HUB04P.one.grp> Quand : mardi 14 mai 2013 10:00-12:00 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris. Emplacement : Meeting Room Number: 391581 Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Liste des num?ros LocalConnect: Australia Australia Toll Free 1800 005 574 Australia Sydney +61 (0) 282 239 767 Austria Vienna +43 (0) 2682 205 6609 Belgium Brussels +32 (0) 2 789 8678 Denmark Copenhagen +45 3271 4340 Finland Helsinki +358 (0) 923 142 830 France Lyon +33 (0) 426 840 285 France Marseille +33 (0) 488 915 385 France Paris +33 (0) 170 994 816 Germany Berlin +49 (0) 3072 616 7342 Germany D?sseldorf +49 (0) 2115 407 3902 Germany Frankfurt +49 (0) 6971 044 5635 Germany Hamburg +49 (0) 4080 902 0684 Germany Munich +49 (0) 8924 443 2893 Germany Stuttgart +49 (0) 7111 856 2130 Greece Greece Toll Free 0080 012 6344 Hong Kong Hong Kong +852 301 145 59 Hungary Budapest +36 (06) 1-889-3286 Ireland Dublin +353 (0) 14 860 780 Israel Israel Toll Free 1809 245 981 Italy Milan +39 0 230 413 017 Italy Rome +39 0 645 217 056 Italy Turin +39 0 112 179 2159 Japan Japan Toll Free 005 311 212 65 Japan Tokyo +81 (0) 357 675 025 Korea, Republic Of Seoul +82 (0) 234 831 224 Luxembourg Luxemburg City +352 2700 41 42 Malaysia Kuala Lumpur +60 (0) 377 124 640 Netherlands Amsterdam +31 (0) 207 948 529 New Zealand Auckland +64 (0) 9 919 2428 Norway Oslo +47 2153 3919 Poland Poland Toll Free 0080 0121 1304 Portugal Portugal Toll Free 800 814 183 Russia Russia Toll Free 81080 02209 4011 Singapore Singapore +65 6622 1068 Spain Barcelona +34 93 492 3235 Spain Madrid +34 91 788 9908 Sweden Stockholm +46 (0) 850 520 145 Switzerland Geneva +41 (0) 225 927 428 United Kingdom Birmingham +44 (0) 121 260 4686 United Kingdom London +44 (0) 207 153 9902 United Kingdom Manchester +44 (0) 161 250 0679 United States USA & Canada Toll Free 1888 249 0050 United States USA Toll +1 954 334 1559 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4683 bytes Desc: not available URL: From jhierro at tid.es Mon May 13 14:42:22 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 13 May 2013 14:42:22 +0200 Subject: [Fiware-security] Link to minutes of confcall today In-Reply-To: References: <5187104B.8070804@tid.es> Message-ID: <5190DFAE.1070506@tid.es> Here you are: https://docs.google.com/document/d/1_HV97Onfsme-3Ss9iFN-rWakKJNLm0kqXkTFI_wWkYk/edit# Search for section titled "OAuth-based Access Control, Security Monitoring and Accounting of APIs" Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 08/05/13 11:55, Seidl, Robert (NSN - DE/Munich) wrote: Hi Juanjo, please find our comments in the text. One more thing: Please forward us the telco and document sharing details for Monday. We don't have it. Greetings Robert From: fiware-api-cross-bounces at lists.fi-ware.eu [mailto:fiware-api-cross-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Monday, May 06, 2013 4:07 AM To: Fiware-api-cross at lists.fi-ware.eu Subject: [Fiware-api-cross] Session about API Access Control on Monday May 13 afternoon Dear colleagues, I would like to have a session on Monday May 13 afternoon (Part II of the weekly joint WPLs/WPAs follow-up confcalls, from 14:30 to 16:00) to push activities related to the API Access Control framework we agree to offer to FI-WARE application developers in Release 2 (attached, for your convenience, the slides we agreed upon with the final reference architecture represented in the last slide). Despite I may come later this week with more details, there are a number of points I would like to tackle during that session which I can anticipate at this point: * @NSN/DT: status regarding support of OAuth messages (steps 4, 6, 7, 11 and 12 in the last slide of the attached presentation illustrating the final reference architecture). ? Regarding the access control GE and related steps in the message flow we have to check with our technical experts, but our first impression is that it should work. ? We will come back to you. Could you point me out where in the IdM GE Open Specifications can I find the specification of the REST API that comprises the operations supporting these steps ? If that REST API specification is a standard specification, it would be nice to see a link to it together with a statement about its support by the IdM GE. It may have passed unadvertised to me, but I couldn't find anything like that ? In the specification of the IDM GE open specification you will find the standard interface description for SAML2.0, OAuth 2.0, OpenID and eID. ? In addition we provide to interested Use Case projects an example service for SAML2.0 in the case of the One-IDM and a specific document describing the REST api in the case of GCP. ? IN case of GCP we could provide the REST specification if we would know where we could upload it. Wolfgang will write a separate email to you. * @UPM: I would like to see an analysis of the APIs provided by the XACML PDP component (Access Control GE) to be provided by Thales: * APIs to be invoked by the Proxy component * APIs to be used by the FI-WARE OIL Portal, or application-specific portals, to configure access control policies to be enforced by the XACML PDP component (Access Control GE) by Thales * @UPM: status of the implementation of the Proxy component that may interact both with Keystone components from OpenStack and the XACML PDP component (Access Control GE) by Thales * @NSN/DT: status about implementation of APIs enabling creation/deletion/management of users and organization of users as well as the definition of attributes for both ... This would enable application providers or FI-WARE Instance Providers, among others, to define portals for management of application users ... (note that very much related to this, I raise a hot issue below) ? For GCP this is described in the REST api document (Wolfgang will send you an email). ? For One-IDM this has to be done by the admin of the system and can't be done by the user. Please book the proposed slot in your agendas. If you can provide some input to the above questions in advance to the meeting, it would be rather nice. I take this opportunity to raise a number of hot issues I have detected while reviewing contents of the Security Chapter in the FI-WARE Architecture. It would be nice to see some clarifications on your side ASAP: * IdM GE API Open Specifications: Frankly speaking, I can't find any API specification associated to the FI-WARE IdM GE ... what you have there are the URLs of service endpoints linked to concrete instances of the IdM GE, provided by DT and NSN. This might be useful information to publish in the tab "instances" linked to entries in the FI-WARE Catalogue associated to the IdM GEis implemented by NSN and DT ... but why is this stuff published as part of the IdM GE Open Specifications ? I have found that a similar comment was raised by TID/UPM during the peer review but seems like it had been ignored ... If part of the IdM GE API Open Specifications matches a given standard then you should provide a link to the published specs together with comments regarding level of support of the referred spec (e.g., may be not all the operations in the standard API you make a link to are supported in your implementation). Besides, at one point you state: "Additional to the authentication and authorization interfaces the Identity Management GEs delivers a REST API for all functionalities regarding user and profile management" ... however I can't see that REST API specified anywhere ... Where is it ? Last but not least, I have read in one of the comments that some of the examples you provide were related to OAuth 1.0 rather than OAuth 2.0 ... could you confirm that you will support OAuth 2.0 ? ? Please refer to the answer above. ? We have already adapted the description of OAuth1.0 to OAuth2.0. ? The two IDM GE are provided on request, when sending an email to the owners DT and NSN. There is no kind of self deployment for these GE. * Access Control GE: I read the following as part of the Open Specs and it rather seems inadmissible to me: "The API operations and associated datatypes are fully described in the Access Control GE - Authorization Restful API (fiware.access_control_ge.authz.api.wadl.zip) package available in document folder Cross Topics > APIs access control, monitoring and accounting of project FI-WARE Private". Please, FI-WARE Open Specifications are public ! we cannot deliver something like this ! Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Wolfgang.Steigerwald at telekom.de Mon May 13 16:39:05 2013 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Mon, 13 May 2013 16:39:05 +0200 Subject: [Fiware-security] UC projects Message-ID: Hello Pascal, I looked on the FI-PPP Web pages but could not find any hint regarding the new use case projects. Therefore some projects ended and some new have joined, do you have a updated list of the currently running UC projects? Best regards Wolfgang -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon May 13 16:57:49 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 May 2013 16:57:49 +0200 Subject: [Fiware-security] (no subject) Message-ID: <21058_1368457077_5190FF75_21058_15749_1_962ead25-f5a9-4f4f-98de-8ed1e3c75d6e@THSONEA01HUB01P.one.grp> Dear Colleagues, Attached please find the review of GEs' V2 User & Programmer Guides which has been performed by Manuel (TID) Please have a look and make the necessary corrections and also inform me once done. Also to be discussed at tomorrow's audio conf (10am). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP8 - User and Programmer Guides_20130429.xls Type: application/vnd.ms-excel Size: 43008 bytes Desc: WP8 - User and Programmer Guides_20130429.xls URL: From cyril.dangerville at thalesgroup.com Mon May 13 18:48:39 2013 From: cyril.dangerville at thalesgroup.com (DANGERVILLE Cyril) Date: Mon, 13 May 2013 18:48:39 +0200 Subject: [Fiware-security] FIWARE - WP8 - Unit Tests - review In-Reply-To: <18180_1368436539_5190AF3A_18180_113_1_813aaed1-2f7e-4845-a4bf-4ce3ee7e727e@THSONEA01HUB02P.one.grp> References: <18180_1368436539_5190AF3A_18180_113_1_813aaed1-2f7e-4845-a4bf-4ce3ee7e727e@THSONEA01HUB02P.one.grp> Message-ID: <3507_1368463724_5191196B_3507_3194_1_2ad6ceed-5ce4-4814-8250-6b3b0f2daff8@THSONEA01HUB03P.one.grp> Hello Manuel, As the Access Control GE owner, I am reviewing your comment on the Unit Testing Plan for this GE [1]. Could you clarify your first comment? Quote: "KO - structure needs modification (only two level hierarchy) as in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/IaaS_Service_Management_-_Unit_Testing_Plan_and_Report_R2 ". The link you are referring to has a two-level hierarchy as well. So what is missing here? Unless I didn't get what you meant by two-level hierarchy... For the other comment (quote: "Links are stated as internal links - normally they appear in red in the private wiki but they work properly when moved to the public wiki"), I changed the feature links to internal links that work properly when moved to the public wiki. [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Access_Control_-_Unit_Testing_Plan_and_Report_R2 Regards, CD --- Cyril Dangerville Thales Services ThereSIS Innovation lab, ICT Security Unit De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoy? : lundi 13 mai 2013 11:16 ? : fiware-security at lists.fi-ware.eu Objet : [Fiware-security] TR: FIWARE - WP8 - Unit Tests - review Importance : Haute Dear Colleagues, I'm forwarding you this review perform by Manuel (TID) of unit tests . Could you please urgently address comments received and perform the actions requested. Also inform me/Daniel/Kreshnik once done. As usual the sooner the better Best Regards, Pascal De : Envoy? : mardi 7 mai 2013 11:57 ? : BISSON Pascal Objet : FIWARE - WP8 - Unit Tests - review Hi Pascal, Please, find attached a spreadsheet with comments to the Unit Tests. I would appreciate they were taken into consideration and due action taken to fix them. If any doubt or concern, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Mon May 13 19:29:42 2013 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 13 May 2013 19:29:42 +0200 Subject: [Fiware-security] FIWARE - WP8 - Unit Tests - review In-Reply-To: <3507_1368463724_5191196B_3507_3194_1_2ad6ceed-5ce4-4814-8250-6b3b0f2daff8@THSONEA01HUB03P.one.grp> References: <18180_1368436539_5190AF3A_18180_113_1_813aaed1-2f7e-4845-a4bf-4ce3ee7e727e@THSONEA01HUB02P.one.grp> <3507_1368463724_5191196B_3507_3194_1_2ad6ceed-5ce4-4814-8250-6b3b0f2daff8@THSONEA01HUB03P.one.grp> Message-ID: <51912306.1040402@tid.es> Hi It is a local holiday in Valladolid (the site where Manuel is located). I believe that the one he reviewed is this one (I used the history tab): * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php?title=Access_Control_-_Unit_Testing_Plan_and_Report_R2&oldid=13881 Of course, this is wrong as the TOC is rigid (just two section levels, not 3) I took the liberty of editing myself this morning as it was too obvious how to fix it respecting your text and basic layout at the same time. I also scaled down the figure. This is subject to Manuel's comments (he is in charge of this one) Incidentally, all contacts should take place through the WPLs, who should group the request (this what the excel files are for), not the GE owner talking directly to us. Understand us: roughly 60 GE x 4 deliverables per GE = 240 discussions in parallel! :) Best regards, Miguel El 13/05/2013 18:48, DANGERVILLE Cyril escribi?: Hello Manuel, As the Access Control GE owner, I am reviewing your comment on the Unit Testing Plan for this GE [1]. Could you clarify your first comment? Quote: "KO - structure needs modification (only two level hierarchy) as in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/IaaS_Service_Management_-_Unit_Testing_Plan_and_Report_R2 ". The link you are referring to has a two-level hierarchy as well. So what is missing here? Unless I didn't get what you meant by two-level hierarchy... For the other comment (quote: "Links are stated as internal links - normally they appear in red in the private wiki but they work properly when moved to the public wiki"), I changed the feature links to internal links that work properly when moved to the public wiki. [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Access_Control_-_Unit_Testing_Plan_and_Report_R2 Regards, CD --- Cyril Dangerville Thales Services ThereSIS Innovation lab, ICT Security Unit De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoy? : lundi 13 mai 2013 11:16 ? : fiware-security at lists.fi-ware.eu Objet : [Fiware-security] TR: FIWARE - WP8 - Unit Tests - review Importance : Haute Dear Colleagues, I'm forwarding you this review perform by Manuel (TID) of unit tests . Could you please urgently address comments received and perform the actions requested. Also inform me/Daniel/Kreshnik once done. As usual the sooner the better Best Regards, Pascal De : Envoy? : mardi 7 mai 2013 11:57 ? : BISSON Pascal Objet : FIWARE - WP8 - Unit Tests - review Hi Pascal, Please, find attached a spreadsheet with comments to the Unit Tests. I would appreciate they were taken into consideration and due action taken to fix them. If any doubt or concern, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue May 14 09:23:29 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 14 May 2013 09:23:29 +0200 Subject: [Fiware-security] FI-WARE WP8 Weekly audio conf Message-ID: <23460_1368516213_5191E675_23460_4718_1_84f9550b-0f2a-48a5-9061-775d8304e015@THSONEA01HUB02P.one.grp> Quand : mardi 14 mai 2013 10:30-12:30 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris. Emplacement : Meeting Room Number: 391581 Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Liste des num?ros LocalConnect: Australia Australia Toll Free 1800 005 574 Australia Sydney +61 (0) 282 239 767 Austria Vienna +43 (0) 2682 205 6609 Belgium Brussels +32 (0) 2 789 8678 Denmark Copenhagen +45 3271 4340 Finland Helsinki +358 (0) 923 142 830 France Lyon +33 (0) 426 840 285 France Marseille +33 (0) 488 915 385 France Paris +33 (0) 170 994 816 Germany Berlin +49 (0) 3072 616 7342 Germany D?sseldorf +49 (0) 2115 407 3902 Germany Frankfurt +49 (0) 6971 044 5635 Germany Hamburg +49 (0) 4080 902 0684 Germany Munich +49 (0) 8924 443 2893 Germany Stuttgart +49 (0) 7111 856 2130 Greece Greece Toll Free 0080 012 6344 Hong Kong Hong Kong +852 301 145 59 Hungary Budapest +36 (06) 1-889-3286 Ireland Dublin +353 (0) 14 860 780 Israel Israel Toll Free 1809 245 981 Italy Milan +39 0 230 413 017 Italy Rome +39 0 645 217 056 Italy Turin +39 0 112 179 2159 Japan Japan Toll Free 005 311 212 65 Japan Tokyo +81 (0) 357 675 025 Korea, Republic Of Seoul +82 (0) 234 831 224 Luxembourg Luxemburg City +352 2700 41 42 Malaysia Kuala Lumpur +60 (0) 377 124 640 Netherlands Amsterdam +31 (0) 207 948 529 New Zealand Auckland +64 (0) 9 919 2428 Norway Oslo +47 2153 3919 Poland Poland Toll Free 0080 0121 1304 Portugal Portugal Toll Free 800 814 183 Russia Russia Toll Free 81080 02209 4011 Singapore Singapore +65 6622 1068 Spain Barcelona +34 93 492 3235 Spain Madrid +34 91 788 9908 Sweden Stockholm +46 (0) 850 520 145 Switzerland Geneva +41 (0) 225 927 428 United Kingdom Birmingham +44 (0) 121 260 4686 United Kingdom London +44 (0) 207 153 9902 United Kingdom Manchester +44 (0) 161 250 0679 United States USA & Canada Toll Free 1888 249 0050 United States USA Toll +1 954 334 1559 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5189 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Tue May 14 09:26:07 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 14 May 2013 09:26:07 +0200 Subject: [Fiware-security] FI-WARE WP8 Audio conf of today shifted by Half an Hour (will start at 10:30). Message-ID: <23460_1368516368_5191E710_23460_4842_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E5563671@THSONEA01CMS04P.one.grp> Please notice we will start at 10:30 our audio conf of today instead of 10am as initial planned. Talk with you at 10:30. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Tue May 14 13:25:02 2013 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Tue, 14 May 2013 11:25:02 +0000 Subject: [Fiware-security] RBAC Message-ID: Hi all, does someone plan to provide RBAC in FI-WARE? I understood that it was planned by Thales, than decided not to provide it. Right? Is there some other enabler who has RBAC integrated? Background for this questions is that we got an requirement from a use case project. Greetings Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyril.dangerville at thalesgroup.com Tue May 14 18:08:42 2013 From: cyril.dangerville at thalesgroup.com (DANGERVILLE Cyril) Date: Tue, 14 May 2013 18:08:42 +0200 Subject: [Fiware-security] (no subject) In-Reply-To: <21058_1368457077_5190FF75_21058_15749_1_962ead25-f5a9-4f4f-98de-8ed1e3c75d6e@THSONEA01HUB01P.one.grp> References: <21058_1368457077_5190FF75_21058_15749_1_962ead25-f5a9-4f4f-98de-8ed1e3c75d6e@THSONEA01HUB01P.one.grp> Message-ID: <10478_1368547729_51926190_10478_3636_1_fa167472-dee4-4cda-97db-0b011b5aea56@THSONEA01HUB02P.one.grp> Hello, Regarding the Access Control - User and Programmers Guide, I addressed the comment, i.e. the request to have the basic structure pattern: Introduction; User Guide; Programmer Guide. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Access_Control_-_User_and_Programmers_Guide_R2 Regards, CD De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoy? : lundi 13 mai 2013 16:58 ? : fiware-security at lists.fi-ware.eu; Meyer, Gerald (NSN - DE/Munich); Goetze, Norbert (NSN - DE/Munich) Objet : [Fiware-security] (no subject) Dear Colleagues, Attached please find the review of GEs' V2 User & Programmer Guides which has been performed by Manuel (TID) Please have a look and make the necessary corrections and also inform me once done. Also to be discussed at tomorrow's audio conf (10am). Best Regards, Pascal &nbs -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 15 11:21:01 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 15 May 2013 11:21:01 +0200 Subject: [Fiware-security] TR: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Message-ID: <1555_1368609667_51935383_1555_12174_1_710ade93-6a7d-418a-814b-355c1d9214fd@THSONEA01HUB04P.one.grp> Dear Colleagues, Another important email that request our attention and also actions from each of us as member of the Security Chapter Team. - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....Security) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....Security) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Counting on you ALL to check and address/contribute according to your Security GE perspective. Thanks ALL for your collective effort. Another urgent topic for which we will review/assess progress at next WP8 Audio conf (hoping the work would be done at that time since we are once beyond schedule). Hoping you got this email already from Daniel by Chance and that you did some work already in case please work on it and complete asap. Collectively we should make it ! Best Regards, Pascal De : fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : jeudi 9 mai 2013 10:29 ? : fiware-exploitation at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Objet : Re: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Dear Colleagues Please find here enclosed the status of the 3 main contribution identified actions for WP11, please try to complete them ASAP as next week, final deadline next Wednesday EOB, will be the last week to gather all the outputs and individual exploitation plans . - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o Not contributions so far: ? WP3- SAP, Thorsten, confirmed that they are working on that and that they will send their contributions ? WP4- IBM, Alex? ? WP5- TID, takeover the leadership of FT, Carlos? ? WP6- TID, Sergio confirming that he is working on that ? WP7- Telecom Italy, Pier? ? WP8- Thales, Pascal? - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May ? SAP ? Nokia Siemens Networks ? SIEMENS ? NEC ? INTEL ? Atos ? TID confirming is working on it ? Rest??? Thanks for your contribution Juan [cid:image001.png at 01CE4C9E.364C8010] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE4C9E.364C8010] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [cid:image001.png at 01CE4C9E.364C8010] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE4C9E.364C8010] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [cid:image001.png at 01CE4C9E.364C8010] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE4C9E.364C8010] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Thu May 16 12:39:19 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 16 May 2013 12:39:19 +0200 Subject: [Fiware-security] TR: FI-WARE WP8 Open Specs (Now uploaded) Message-ID: <20869_1368700764_5194B75C_20869_3211_1_6783cef9-0331-406e-8d8a-e896b6048799@THSONEA01HUB02P.one.grp> Dear All, Finally I did manage to generate the D8.1.2 (Open Specs GE V2 + Open API). Have All a quick scan to the document for what concerns GE or features you are responsible for (just to check your proper content is there). As for this deliverable D8.1.2 let's now wait now from Peer review comments of Cloud Chapter and concentrate on trying to get completed and delivered this other deliverables (the software + the manuals). As for SoTa, I can only urge Inria to close the work and send me a consolidated version with all inputs. Hearing here from you Alexandre. Tomorrow we will review this and other pending urgent actions. Counting on you all to report good progress ! Best Regards, Pascal De : BISSON Pascal Envoy? : jeudi 16 mai 2013 12:30 ? : Miguel Carrillo; fiware-wpl at lists.fi-ware.eu; JUAN JOSE HIERRO SUREDA Cc : BISSON Pascal; GIDOIN Daniel Objet : FI-WARE WP8 Open Specs (Now uploaded) Dear All, This just to let you know that I generated D8.1.2 (Open Specs GE V2 + Open API) and provided the link through the Open Specs Peer Review cockpit we all shared. As such peer review from WP4 can now start. Apologize for the delay (especially to Alex and his team who was awaiting to perform the peer review). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Thu May 16 16:32:09 2013 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Thu, 16 May 2013 14:32:09 +0000 Subject: [Fiware-security] RBAC In-Reply-To: References: Message-ID: Hi all again, we had one more telco with the use case project and they are really looking for an RBAC system. Since not all partners have answered to my initial email, maybe there is one RBAC solution we could offer? Many thanks Robert From: ext Susana Gonzalez Zarzosa [mailto:susana.gzarzosa at atosresearch.eu] Sent: Tuesday, May 14, 2013 5:15 PM To: Seidl, Robert (NSN - DE/Munich) Subject: RE: [Fiware-security] RBAC Hi Robert, No, our enabler doesn't have RBAC integrated. Best regards, Susana From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: martes, 14 de mayo de 2013 13:25 To: ext BISSON Pascal; ext GIDOIN Daniel Cc: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] RBAC Hi all, does someone plan to provide RBAC in FI-WARE? I understood that it was planned by Thales, than decided not to provide it. Right? Is there some other enabler who has RBAC integrated? Background for this questions is that we got an requirement from a use case project. Greetings Robert ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri May 17 09:27:28 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 May 2013 09:27:28 +0200 Subject: [Fiware-security] WP8 Audio conf WILL START AT 11AM (not 10am) Message-ID: <17317_1368775649_5195DBE0_17317_4399_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E56BAFDE@THSONEA01CMS04P.one.grp> -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri May 17 09:28:04 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 May 2013 09:28:04 +0200 Subject: [Fiware-security] FI-WARE WP8 Weekly audio conf Message-ID: <17317_1368775685_5195DC05_17317_4414_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E56BAFE2@THSONEA01CMS04P.one.grp> Quand : vendredi 17 mai 2013 11:00-12:30 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris. Emplacement : Meeting Room Number: 391581 Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Liste des num?ros LocalConnect: Australia Australia Toll Free 1800 005 574 Australia Sydney +61 (0) 282 239 767 Austria Vienna +43 (0) 2682 205 6609 Belgium Brussels +32 (0) 2 789 8678 Denmark Copenhagen +45 3271 4340 Finland Helsinki +358 (0) 923 142 830 France Lyon +33 (0) 426 840 285 France Marseille +33 (0) 488 915 385 France Paris +33 (0) 170 994 816 Germany Berlin +49 (0) 3072 616 7342 Germany D?sseldorf +49 (0) 2115 407 3902 Germany Frankfurt +49 (0) 6971 044 5635 Germany Hamburg +49 (0) 4080 902 0684 Germany Munich +49 (0) 8924 443 2893 Germany Stuttgart +49 (0) 7111 856 2130 Greece Greece Toll Free 0080 012 6344 Hong Kong Hong Kong +852 301 145 59 Hungary Budapest +36 (06) 1-889-3286 Ireland Dublin +353 (0) 14 860 780 Israel Israel Toll Free 1809 245 981 Italy Milan +39 0 230 413 017 Italy Rome +39 0 645 217 056 Italy Turin +39 0 112 179 2159 Japan Japan Toll Free 005 311 212 65 Japan Tokyo +81 (0) 357 675 025 Korea, Republic Of Seoul +82 (0) 234 831 224 Luxembourg Luxemburg City +352 2700 41 42 Malaysia Kuala Lumpur +60 (0) 377 124 640 Netherlands Amsterdam +31 (0) 207 948 529 New Zealand Auckland +64 (0) 9 919 2428 Norway Oslo +47 2153 3919 Poland Poland Toll Free 0080 0121 1304 Portugal Portugal Toll Free 800 814 183 Russia Russia Toll Free 81080 02209 4011 Singapore Singapore +65 6622 1068 Spain Barcelona +34 93 492 3235 Spain Madrid +34 91 788 9908 Sweden Stockholm +46 (0) 850 520 145 Switzerland Geneva +41 (0) 225 927 428 United Kingdom Birmingham +44 (0) 121 260 4686 United Kingdom London +44 (0) 207 153 9902 United Kingdom Manchester +44 (0) 161 250 0679 United States USA & Canada Toll Free 1888 249 0050 United States USA Toll +1 954 334 1559 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4452 bytes Desc: not available URL: From xavier.aghina at orange.com Fri May 17 09:43:09 2013 From: xavier.aghina at orange.com (xavier.aghina at orange.com) Date: Fri, 17 May 2013 07:43:09 +0000 Subject: [Fiware-security] Audio Conf to day Message-ID: <21766_1368776590_5195DF8E_21766_14322_1_81FF741594681345A3FBB024B01054B906F54550@PEXCVZYM11.corporate.adroot.infra.ftgroup> Hello, I had already leaved the conference call at 11am that day. Good working to you. Xavier. [http://www.francetelecom.com/sirius/logos_mail/orange_logo.gif] Xavier Aghina FT/OLNC/OLPS/ASE/SEC Ing?nieur de Recherche en S?curit? t?l. 01 45 29 81 59 xavier.aghina at orange.com _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1264 bytes Desc: image001.gif URL: From Richard.Egan at uk.thalesgroup.com Fri May 17 11:48:05 2013 From: Richard.Egan at uk.thalesgroup.com (EGAN Richard) Date: Fri, 17 May 2013 10:48:05 +0100 Subject: [Fiware-security] TR: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! In-Reply-To: <1555_1368609667_51935383_1555_12174_1_710ade93-6a7d-418a-814b-355c1d9214fd@THSONEA01HUB04P.one.grp> References: <1555_1368609667_51935383_1555_12174_1_710ade93-6a7d-418a-814b-355c1d9214fd@THSONEA01HUB04P.one.grp> Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA90C653ADB@THSONEP02CMB01P.one-02-priv.grp> Pascal, all, here is the link to the place on forge where the WP11 deliverables are located (to be fair to Juan the link is in one of the emails below) https://forge.fi-ware.eu/docman/index.php?group_id=16 Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 15 May 2013 10:21 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Importance: High Dear Colleagues, Another important email that request our attention and also actions from each of us as member of the Security Chapter Team. - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....Security) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....Security) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Counting on you ALL to check and address/contribute according to your Security GE perspective. Thanks ALL for your collective effort. Another urgent topic for which we will review/assess progress at next WP8 Audio conf (hoping the work would be done at that time since we are once beyond schedule). Hoping you got this email already from Daniel by Chance and that you did some work already in case please work on it and complete asap. Collectively we should make it ! Best Regards, Pascal De : fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : jeudi 9 mai 2013 10:29 ? : fiware-exploitation at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Objet : Re: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Dear Colleagues Please find here enclosed the status of the 3 main contribution identified actions for WP11, please try to complete them ASAP as next week, final deadline next Wednesday EOB, will be the last week to gather all the outputs and individual exploitation plans . - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o Not contributions so far: ? WP3- SAP, Thorsten, confirmed that they are working on that and that they will send their contributions ? WP4- IBM, Alex? ? WP5- TID, takeover the leadership of FT, Carlos? ? WP6- TID, Sergio confirming that he is working on that ? WP7- Telecom Italy, Pier? ? WP8- Thales, Pascal? - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May ? SAP ? Nokia Siemens Networks ? SIEMENS ? NEC ? INTEL ? Atos ? TID confirming is working on it ? Rest??? Thanks for your contribution Juan [cid:image001.png at 01CE52EC.01E5A5F0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE52EC.01E5A5F0] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [cid:image001.png at 01CE52EC.01E5A5F0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE52EC.01E5A5F0] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [cid:image001.png at 01CE52EC.01E5A5F0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE52EC.01E5A5F0] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From robert.seidl at nsn.com Fri May 17 11:56:15 2013 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Fri, 17 May 2013 09:56:15 +0000 Subject: [Fiware-security] FW: [Fiware-exploitation] ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Message-ID: Hi Pascal, as just discussed here is the link where at least some partners provided their input a couple of weeks ago: https://forge.fi-ware.eu/docman/?group_id=16. --> work version --> WP11 final deliverables M24 Here the template for providing information is much longer than in the following (have a look on the word document e.g. from NSN): https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual_Exploitation_Plans#Institut_National_De_Recherche_En_Informatique_Et_En_Automatique Also the content we provided under the first link was unfortunately not taken over to the second by WP11. So I had to do it again. Greetings Robert From: Seidl, Robert (NSN - DE/Munich) Sent: Monday, May 06, 2013 1:00 PM To: 'ext Juan Bare?o Guerenabarrena' Cc: Varga, Jozsef (NSN - HU/Budapest); Nemeth, Lorant (NSN - HU/Budapest) Subject: RE: [Fiware-exploitation] ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Hi Juan, NSN's document is submitted here https://forge.fi-ware.eu/docman/?group_id=16. Actually in pending state due to required approval. Greetings Robert From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of ext Juan Bare?o Guerenabarrena Sent: Monday, May 06, 2013 11:57 AM To: fiware-exploitation at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu Cc: jaimemartin at eprosima.com; antonio.fuentes at rediris.es Subject: Re: [Fiware-exploitation] ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Just 2 exploitation plans updated so far please update them in a separate word template as SIEMENS and Intel did, see folders below Regarding the update please take into account the recommendations form the M18 Review cited below, that summarizing want us to identify: - The main FIWARE outcomes (which concrete GEs and Instances are we going to exploit and how we are going to exploit or sell these concrete ones: Cloud Stack, PaaS, Big Data....) - In which ecosystems are you going to focus or prioritize (M2M, Big Data, PaaS...)including industrial partners as utilities, cities.... ? "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, FI-WARE is in essence a set of independent GEs for "pick-and-choose", rather than a (core) platform. It needs to be positioned as such. The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks Juan [cid:image001.jpg at 01CE4A59.94056790] [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: Juan Bare?o Guerenabarrena Sent: martes, 30 de abril de 2013 13:08 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; Miguel Carrillo (mcp at tid.es) Subject: RE: ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Please update into the Forge, as a separated document, named XXXX Exploitation plan M24 with all the track changes and I will include it into the deliverable Thanks Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: Juan Bare?o Guerenabarrena Sent: lunes, 29 de abril de 2013 16:31 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu); 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu) Cc: 'jaimemartin at eprosima.com'; 'antonio.fuentes at rediris.es'; Miguel Carrillo (mcp at tid.es) Subject: ACTION 3: To Update of the individual exploitation plans, last version from M18- directly into the ANNEX I from D11.2.2 Document Dear Colleagues Regarding ACTION 3: To Update of the individual exploitation plans, last version from M18, please do that directly into the document within the folder "Work Versions", "WP11 Final Deliverables M24" WP11.2.2 Exploitation Plan ANNEX I https://forge.fi-ware.eu/docman/index.php?group_id=16 - Each FI WARE Partner before 3rd of May. Not use the wiki links as the last version do not content the initial questions answered into the M12 Review "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" For the new comers eprosima and red.es please follow the same structure and answer the following questions: * Organization Profile * FI-WARE relevance in your current business model * Identification of main project outcomes * How are you going to exploit the project results in distinct environments? * Which customers do we want to serve? * Which channels will be used to reach the various customer segments? * Which benefits are the participants going to take to the market thanks to FIWARE? * How are the benefits going to be sold? * How will the sales process work? * Globalisation of the exploitation plan * How will make money from FIWARE Platform? Thanks Juan From: Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: 'fiware-exploitation at lists.fi-ware.eu' (fiware-exploitation at lists.fi-ware.eu) Cc: 'fiware-wpl at lists.fi-ware.eu' (fiware-wpl at lists.fi-ware.eu); fiware-pcc at lists.fi-ware.eu Subject: FW: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [Description: cid:image001.png at 01CC3A4E.0D917B80] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [Description: Atos_Olympic_Games_Logo[1]] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 76225 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 339 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 4064 bytes Desc: image003.gif URL: From Richard.Egan at uk.thalesgroup.com Fri May 17 12:12:45 2013 From: Richard.Egan at uk.thalesgroup.com (EGAN Richard) Date: Fri, 17 May 2013 11:12:45 +0100 Subject: [Fiware-security] TR: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! In-Reply-To: <7C80A1EAA66A4F45BA3A574774382B9BA90C653ADB@THSONEP02CMB01P.one-02-priv.grp> References: <1555_1368609667_51935383_1555_12174_1_710ade93-6a7d-418a-814b-355c1d9214fd@THSONEA01HUB04P.one.grp> <7C80A1EAA66A4F45BA3A574774382B9BA90C653ADB@THSONEP02CMB01P.one-02-priv.grp> Message-ID: <7C80A1EAA66A4F45BA3A574774382B9BA90C653B91@THSONEP02CMB01P.one-02-priv.grp> ...and I should have said that the latest documents are in the Work Versions folder Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of EGAN Richard Sent: 17 May 2013 10:48 To: BISSON Pascal; fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] TR: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Pascal, all, here is the link to the place on forge where the WP11 deliverables are located (to be fair to Juan the link is in one of the emails below) https://forge.fi-ware.eu/docman/index.php?group_id=16 Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 15 May 2013 10:21 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Importance: High Dear Colleagues, Another important email that request our attention and also actions from each of us as member of the Security Chapter Team. - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....Security) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....Security) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May Counting on you ALL to check and address/contribute according to your Security GE perspective. Thanks ALL for your collective effort. Another urgent topic for which we will review/assess progress at next WP8 Audio conf (hoping the work would be done at that time since we are once beyond schedule). Hoping you got this email already from Daniel by Chance and that you did some work already in case please work on it and complete asap. Collectively we should make it ! Best Regards, Pascal De : fiware-pcc-bounces at lists.fi-ware.eu [mailto:fiware-pcc-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : jeudi 9 mai 2013 10:29 ? : fiware-exploitation at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Objet : Re: [Fiware-pcc] [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24- KIND REMAINDER!! Dear Colleagues Please find here enclosed the status of the 3 main contribution identified actions for WP11, please try to complete them ASAP as next week, final deadline next Wednesday EOB, will be the last week to gather all the outputs and individual exploitation plans . - D11.1.2-Market and Competition Analysis _M24v2404- ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404- ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o Not contributions so far: ? WP3- SAP, Thorsten, confirmed that they are working on that and that they will send their contributions ? WP4- IBM, Alex? ? WP5- TID, takeover the leadership of FT, Carlos? ? WP6- TID, Sergio confirming that he is working on that ? WP7- Telecom Italy, Pier? ? WP8- Thales, Pascal? - ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May ? SAP ? Nokia Siemens Networks ? SIEMENS ? NEC ? INTEL ? Atos ? TID confirming is working on it ? Rest??? Thanks for your contribution Juan [cid:image001.png at 01CE52EF.733E7EE0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE52EF.733E7EE0] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 24 de abril de 2013 19:40 To: fiware-exploitation at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] FW: WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Please find here enclosed in the following link https://forge.fi-ware.eu/docman/index.php?group_id=16 and within the folder "Work Versions", "WP11 Final Deliverables M24" the following first draft deliverables, pending to complete and fine-tuning: - D11.1.2-Market and Competition Analysis _M24v2404 o The document describe the following: ? Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) ? The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? ? The biggest challenges for app businesses (and what to do about them) ? The success factors for app store-like platform businesses from the perspective of third-party developers ? European Context and trends (barriers, policy...) o ACTION1: Please review Business Opportunities by domain (Cloud, Data, Iot....) and complete the identified missing inputs and provide feedback - Each WPL its domain and the rest helping, before 3rd of May - D11.2.2 Exploitation_Plan,_including_IPR_Managementv_M24v2404 o The document describe the following ? FI-WARE Product Vision by domain: Identify the main Generic Enablers+ FI-WARE Instances with most market potential ? FI WARE Market Positioning: GE Development Prioritization Matrix ? FI WARE IPR Management ? FI WARE Ecosystem Strategy and Business Model ? Individual Exploitation Plans o ACTION 2: Please review it Product Vision by domain (Cloud, Data, Iot....) and complete the identified missing inputs (Use Case Scenarios and Business Canvas) and provide feedback - Each WPL its domain and the rest helping, before 3rd of May o ACTION 3: To Update of the individual exploitation plans, last version from M18, into the document or into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual- Each FI WARE Partner before 3rd of May "Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy o In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project" Thanks for your collaboration Juan [cid:image001.png at 01CE52EF.733E7EE0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE52EF.733E7EE0] From: fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: mi?rcoles, 17 de abril de 2013 19:08 To: fiware-wpl at lists.fi-ware.eu; fiware-exploitation at lists.fi-ware.eu Cc: fiware-pcc at lists.fi-ware.eu Subject: [Fiware-exploitation] WP11 Deliverables Submission Roadmap for M24 Dear Colleagues Following with the submission of Exploitation Deliverables on M24, I enclosed you the following roadmap and the inputs needed to include in each deliverable according to the last comments and recommendations from the last review on M18. Please feel free to suggest some indications or solutions to address the issues identified in each deliverable, based on the recommendations provided by the reviewers. For this work, we are going to leverage on the following draft documents: - 11.1.2- Market Analysis o Rise on 3rd party platforms and Economy of Internet Apps ? Business Opportunities by Tech (Cloud, Big Data, IoT, USDL...and GE combinations) ? Business Opportunities by Sector/Industry (Smart Cities, Smart Industry (Grid, logistics, health....) and Smart Home) o The new basis of competition and the superiority of ecosystem economics ? The superiority of ecosystem economics ? Ecosystems as a new distribution channel ? Ecosystem engineering ? What is the correct service ecosystem approach with startups and first "external" users of an ICT platform? o The biggest challenges for app businesses (and what to do about them) o The success factors for app store-like platform businesses from the perspective of third-party developers o European Context and trends (barriers, policy...) - First Draft of the Whitepaper about Product Vision for identify main use case scenarios and demonstrate the main advantages offered by FI WARE in each domain and identify the main and more potential instances or combinations of GE (PaaS+Big Data, IoT+Big Data.....)- Any advance on this whitepaper? ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? - Exploitation and business modeling position paper prepared together with CONCORD and that will be finished on April this month - Assessment of market traction of the relevant GEs in those specific domains of the emerging FI-PPP Phase 1- Feedback from UC questionnaire sent by FI WARE - Exploring Policy and Regulatory Challenges paper prepared together with CONCORD- Finished - Open Innovation Lab o Terms and Conditions- Status? o Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab- Any advance on this side? - Third party developers' feedback to the available GEs - Third party Enablement deliverable new version- Is there a new version available? - European Patent System- The policy context for IPR, including the latest development on the matter Resubmission Roadmap: All Deliverables sent on the 15th May - Monday 22nd April- I will send you an initial and significant completed draft of the following three deliverables trying to address the following recommendations provided by reviewers on M18: o D11.1.2 Market and Competition Analysis (M24) ? The consortium is urged to keep the parallel segment of Smart Business in dual focus with Smart Cities ? Specifically, ecosystem formation needs to be prioritized strategically ? The challenge for future versions is to apply the new insights to broaden and deepen the analysis of FI-WARE's own business ecosystem, and relate the present high level view of this ecosystem to the more specific analysis within the GE chapters ? Additionally, it would be useful to provide assessment of market traction of the relevant GEs in those specific domains of the FI-PPP Use Case projects ? From the conclusion of this document, it is clear that third party innovation enablement will be critical, and it is also intimately linked to building a critical mass for FI-WARE results. ? This theme should be further developed from a market and competitive perspective, in close synergy with and inputting directly to the forthcoming deliverables D2.5.2 and D2.5.3 regarding third party uptake o D11.2.2 Exploitation Plan, including IPR Management (M24) ? Providing usage scenarios, potential usage patterns (including the 'typical' combined use of GEs), an overview of the status of available GEs including level of Use Case interest, a clear schedule of future GE Releases ? Give due and sufficient business consideration to the competitiveness of the GEs with respect to their market benchmarking, innovation potential and attractiveness) for both business and development communities. ? Focus on applying 'promising' technologies such as USDL and high impact areas such as IoT. ? Provide additional analysis and target promising business ecosystems for GE uptake, beyond Smart Cities. ? Provide clear evidence of business planning in the targeted areas through (combined) implementation of GEs. ? As a specific suggestion, the market potential of the individual GEs or groupings of GEs could be even more sharply indicated, and possibly even contrasted and prioritized ? OIL description ? A significant number of critical issues have to be addressed that will ultimately respond to the third party question "Why and how FI-WARE is going to help me to innovate?" o From a practical standpoint more detail is required relating to access, licensing and utilization rights. o Also not yet appropriately addressed is the topic of packaging in terms of what the application developer can access to build FI solutions, such as a starter-kit. ? The concrete offering and strategy towards attracting relevant communities remains unclear. ? Fostering developer communities fall within the scope of Open Call 3 (launched in December 2012). This however does not mean that present partners can derogate all responsibilities of involving potential users and stakeholders to the future Open Call 3 partners ? IPR Management: Regarding a possible integration strategy, the Month 15 Whitepaper about common usage scenarios (and potential usage patterns) for the GEs is long overdue. The issue was also raised by some of the new Phase 2 projects: ? What GEs can be used in combinations with what other GEs? ? Do certain GEs force you to use other GEs? ? How about interoperability? ? Where is the integration burden, with FI-WARE or the users? ? Establish the strategy and implementation plan to evolve the FI-WARE Testbed into the "backbone" of the Open Innovation Lab, in collaboration and synergy with the upcoming FIPPP Phase 2 Capability Building project. o D11.3.2 Market and Policy Regulation Awareness Report (M24) ? Further development of the issues and themes in Section 4.2 from 11.3.1.b is expected, among others, for the next version. ? The policy context for IPR, including the latest development on the European Patent System, would deserve greater attention in the next version ? It is also encouraging to see more consideration of the platform issues from a regulatory perspective, which should be deepened in the next version o 11.4.3 Standardization (M27) ? Please provide feedback to the NEC requirements as an oral update has to be provided in the next review meeting (M24) - Wednesday 30th April- o To Review or complete the identified missing inputs and provide feedback about the three before mentioned deliverables 11.1.2, 11.2.2 and 11.3.2 o To Update of the individual exploitation plans into the wiki: ? Given that there is apparently no intention of joint exploitation between the industrial partners of FI-WARE, The industrial partners are especially urged to improve their own exploitation planning documentation, taking into account the analysis and conclusions reached at the general level ? Accordingly, Annex I must be fully updated to reflect the more tangible business view of the industrial partner and a lot more substantive in describing the planned integration of the FI-WARE outcomes into the mainstream business of the industrial partners. ? Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FI-WARE instances and other productization opportunities ? Engagement FI WARE outcomes with your corporate strategy ? Also welcomed is the emphasis given on "open model", "open solution", "open services", "open innovation", "open ecosystem" etc. How to start an ecosystem or leverage existing ones remains to be answered though. Equally, what does 'openness' mean beyond marketing, and concretely how it is to be applied in corporate strategy such as on the FI-WARE instances, need to be clarified. ? One good example in this respect is the very specific description provided in the Orange presentation in Seville, which clearly explains how usage of several sets of FI-WARE results is linked to its corporate strategy in engaging with the evolution of the services market. ? In which ecosystems are you going to focus or prioritize. Specifically, ecosystem formation needs to be prioritized strategically. In this respect, we continue to encourage the industrial partners to more actively and extensively engage senior business management to be involved in the exploitation and impact creation activity of the project. - Friday 10th May- I will consolidate all the outputs and feedback received - Monday 13th and Tuesday 14th - Final review and validation will take place - Wednesday 15th May - We will send the final deliverables Thanks for your collaboration Juan [cid:image001.png at 01CE52EF.733E7EE0] Juan Bare?o Group Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CE52EF.733E7EE0] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: From cyril.dangerville at thalesgroup.com Fri May 17 12:37:24 2013 From: cyril.dangerville at thalesgroup.com (DANGERVILLE Cyril) Date: Fri, 17 May 2013 12:37:24 +0200 Subject: [Fiware-security] RBAC In-Reply-To: References: Message-ID: <17317_1368787047_51960867_17317_12767_1_DDCC8EDACD06614C9CE3DFEA2835890070C4474837@THSONEA01CMS10P.one.grp> Hello, Sorry for the late reply, I had to check a few things with my colleagues regarding the current status of RBAC support in our XACML engine. So, in our Thales XACML Asset, we have a preliminary support of the Core and hierarchical role based access control (RBAC) profile of XACML v2.0. I say "preliminary" for the following reasons: 1. The Role Assignment/Enablement part of the profile is not supported. Therefore, you have to provide your own solution for (de-)assigning role to users, and role management in general: Identity Management GE, LDAP directory, etc. Our asset only provides for administration and enforcement of RBAC policies (defining permissions for each role, and role hierarchies). Then, you need to make sure our asset's PDP is able to get the roles of the user when requesting authorization. There are two options: a. The PEP sends the user role attributes directly in the XACML authorization request to the PDP. b. Add a specific connector to the PDP, usually called "attribute finder", that is able to get the user role attributes from your role management solution, based on a user ID attribute sent by the PEP in the XACML request. In this case, there may be some effort involved to develop such a connector. 2. Configuring RBAC policies with the API (RESTful) is supported for Core RBAC but *NOT for Hierarchical RBAC* ; in the latter case, only RPS (Role , see XACML RBAC profile for definition) may be configured via the API, PPS (Permission ) have to be manually added/edited by the administrator locally on the filesystem where the XACML Authorization Service of our asset is deployed. 3. We have tested RBAC policies implementing at most one-level role hierarchy only so far (e.g. Role1 senior to Role2). Depending on your use case, we could test more (Role1 senior to Role2 senior to Role3, etc.) if really necessary. If all this is acceptable for your use case and this is not too urgent (what's the time frame?), you can send me examples of the RBAC policies that you want to implement, in natural or some formal language (easily understandable), so that I can better assess whether it is feasible or not with our asset. Thanks. Regards, CD De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de Seidl, Robert (NSN - DE/Munich) Envoy? : jeudi 16 mai 2013 16:32 ? : Fiware-security at lists.fi-ware.eu Objet : Re: [Fiware-security] RBAC Hi all again, we had one more telco with the use case project and they are really looking for an RBAC system. Since not all partners have answered to my initial email, maybe there is one RBAC solution we could offer? Many thanks Robert From: ext Susana Gonzalez Zarzosa [mailto:susana.gzarzosa at atosresearch.eu] Sent: Tuesday, May 14, 2013 5:15 PM To: Seidl, Robert (NSN - DE/Munich) Subject: RE: [Fiware-security] RBAC Hi Robert, No, our enabler doesn't have RBAC integrated. Best regards, Susana From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: martes, 14 de mayo de 2013 13:25 To: ext BISSON Pascal; ext GIDOIN Daniel Cc: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] RBAC Hi all, does someone plan to provide RBAC in FI-WARE? I understood that it was planned by Thales, than decided not to provide it. Right? Is there some other enabler who has RBAC integrated? Background for this questions is that we got an requirement from a use case project. Greetings Robert ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri May 17 15:25:08 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 May 2013 15:25:08 +0200 Subject: [Fiware-security] TR: FI-WARE-WP8 Consolidated Answer to comments on GEs V2 manuals Message-ID: <3657_1368797115_51962FBB_3657_918_1_e63980b3-c6da-42eb-8fda-afe697feeda5@THSONEA01HUB02P.one.grp> FYI Keep you posted . BR Pascal De : BISSON Pascal Envoy? : vendredi 17 mai 2013 15:24 ? : Miguel Carrillo; MANUEL ESCRICHE VICENTE Cc : BISSON Pascal; GIDOIN Daniel; JUAN JOSE HIERRO SUREDA Objet : FI-WARE-WP8 Consolidated Answer to comments on GEs V2 manuals Dear Miguel, Manuel, Find attached to this email the consolidated Answer at WP8 level following peer review you performed of our GEs V2 manuals. Awaiting now for your final check and feedback. And yes apologize for the delay. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP8 - Unit Tests_WP8-ConsolidatedAnswer.xls Type: application/vnd.ms-excel Size: 94208 bytes Desc: WP8 - Unit Tests_WP8-ConsolidatedAnswer.xls URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP8 - User and Programmer Guides-WP8-ConsolidatedAnswer.xls Type: application/vnd.ms-excel Size: 43520 bytes Desc: WP8 - User and Programmer Guides-WP8-ConsolidatedAnswer.xls URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Review_INS_R2_WP8-ConsolidatedAnswer.xls Type: application/vnd.ms-excel Size: 34304 bytes Desc: Review_INS_R2_WP8-ConsolidatedAnswer.xls URL: From robert.seidl at nsn.com Fri May 17 16:26:20 2013 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Fri, 17 May 2013 14:26:20 +0000 Subject: [Fiware-security] RBAC In-Reply-To: <17317_1368787047_51960867_17317_12767_1_DDCC8EDACD06614C9CE3DFEA2835890070C4474837@THSONEA01CMS10P.one.grp> References: <17317_1368787047_51960867_17317_12767_1_DDCC8EDACD06614C9CE3DFEA2835890070C4474837@THSONEA01CMS10P.one.grp> Message-ID: Hi Cyril, Many thanks for your input. Unfortunately what they are looking for is exactly what you wrote in bold letters under 2. They are looking for hierarchical RBAC. So I assume that your solution would not fit their requirements. In addition they would need it quite soon. Many thanks again Robert From: ext DANGERVILLE Cyril [mailto:cyril.dangerville at thalesgroup.com] Sent: Friday, May 17, 2013 12:37 PM To: Seidl, Robert (NSN - DE/Munich); Fiware-security at lists.fi-ware.eu Subject: RE: [Fiware-security] RBAC Hello, Sorry for the late reply, I had to check a few things with my colleagues regarding the current status of RBAC support in our XACML engine. So, in our Thales XACML Asset, we have a preliminary support of the Core and hierarchical role based access control (RBAC) profile of XACML v2.0. I say "preliminary" for the following reasons: 1. The Role Assignment/Enablement part of the profile is not supported. Therefore, you have to provide your own solution for (de-)assigning role to users, and role management in general: Identity Management GE, LDAP directory, etc. Our asset only provides for administration and enforcement of RBAC policies (defining permissions for each role, and role hierarchies). Then, you need to make sure our asset's PDP is able to get the roles of the user when requesting authorization. There are two options: a. The PEP sends the user role attributes directly in the XACML authorization request to the PDP. b. Add a specific connector to the PDP, usually called "attribute finder", that is able to get the user role attributes from your role management solution, based on a user ID attribute sent by the PEP in the XACML request. In this case, there may be some effort involved to develop such a connector. 2. Configuring RBAC policies with the API (RESTful) is supported for Core RBAC but *NOT for Hierarchical RBAC* ; in the latter case, only RPS (Role , see XACML RBAC profile for definition) may be configured via the API, PPS (Permission ) have to be manually added/edited by the administrator locally on the filesystem where the XACML Authorization Service of our asset is deployed. 3. We have tested RBAC policies implementing at most one-level role hierarchy only so far (e.g. Role1 senior to Role2). Depending on your use case, we could test more (Role1 senior to Role2 senior to Role3, etc.) if really necessary. If all this is acceptable for your use case and this is not too urgent (what's the time frame?), you can send me examples of the RBAC policies that you want to implement, in natural or some formal language (easily understandable), so that I can better assess whether it is feasible or not with our asset. Thanks. Regards, CD De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de Seidl, Robert (NSN - DE/Munich) Envoy? : jeudi 16 mai 2013 16:32 ? : Fiware-security at lists.fi-ware.eu Objet : Re: [Fiware-security] RBAC Hi all again, we had one more telco with the use case project and they are really looking for an RBAC system. Since not all partners have answered to my initial email, maybe there is one RBAC solution we could offer? Many thanks Robert From: ext Susana Gonzalez Zarzosa [mailto:susana.gzarzosa at atosresearch.eu] Sent: Tuesday, May 14, 2013 5:15 PM To: Seidl, Robert (NSN - DE/Munich) Subject: RE: [Fiware-security] RBAC Hi Robert, No, our enabler doesn't have RBAC integrated. Best regards, Susana From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Seidl, Robert (NSN - DE/Munich) Sent: martes, 14 de mayo de 2013 13:25 To: ext BISSON Pascal; ext GIDOIN Daniel Cc: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] RBAC Hi all, does someone plan to provide RBAC in FI-WARE? I understood that it was planned by Thales, than decided not to provide it. Right? Is there some other enabler who has RBAC integrated? Background for this questions is that we got an requirement from a use case project. Greetings Robert ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue May 21 07:30:47 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 21 May 2013 07:30:47 +0200 Subject: [Fiware-security] URGENT Action points derived from architecture session on OAuth 2.0-based Access Control framework in FI-WARE Message-ID: <519B0687.60403@tid.es> Hi all, This mail is a reminder of the several APs identified during our architect session on Monday 13th about the OAuth 2.0-based Access Control framework in FI-WARE. The first point had to do with making the GCP IdM GEi API documentation available to all partners. You can now download the GCP IdM GEi API documentation from the following link at the FI-WARE project. Note that access to this link is private, so you will have to login in your FusionForge account (and be registered as member of the FI-WARE project): https://forge.fi-ware.eu/docman/view.php/7/2369/GCP+API+documentation_v0-2.pdf I have also attached to this email an updated version of the presentation that describes the architecture we are aiming to implement. As a follow-up of the technical session we had on Monday May 13th, I would like to remind the following action points: * @UPM to carry out a revision of the RESTful API specification provided in the referred GCP documentation in order to determine if it will allow them to finish developments under way regarding a FI-WARE OIL portal for management of user accounts and user attributes. I remind to UPM that they should also rely on the available APIs from the Access Control GE to deal with definition of roles and access policies from the same portal. * @UPM and @DT: UPM to provide detailed links to the places in the standard OAuth specs where they believe that the complete OAuth 2.0 RESTFul API to be supported by the IdM GE are specified. DT to respond to UPM so that the whole issue about existence of a complete standard RESTful API is clarified. Don't hesitate to carry out this discussion within the fiware-api-cross mailing list so that we can all follow-up the discussions * @Thales to also carry out a revision of the GCP same documentation and design a proposal to present in our next follow-up confcall about how to manage updates of some attributes of users which may imply rejection of some request tokens (check last slide in the attached presentation) * @UPM to confirm whether all the information is available for them to finalize development of the Proxy * @NSN to confirm whether they plan to support a RESTful API in compliance with the GCP RESTful specification. (note: NSN couldn't attend the confcall on May 13th but this issue was raised: there should be a single IdM GE RESTful API specification so either NSN is happy to implement the one provided by DT or both have to agree on one they will both support) You all are called to attend afternoon session during the next joint WPLs/WPAs follow-up confcall (14:30 to 16:00) on May 27th where we will have the opportunity to follow-up all the above APs (we will start the session addressing these points so that you don't need to stay the whole session if we finish earlier, but please book the whole slot in your agendas). Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Security 13-05-14.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 187888 bytes Desc: not available URL: From jhierro at tid.es Tue May 21 08:02:39 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 21 May 2013 08:02:39 +0200 Subject: [Fiware-security] Public availability of FI-WARE GE Open Specifications Message-ID: <519B0DFF.2050407@tid.es> Hi all, Based on the comments made by DT during our confcall during the joint WPLs/WPAS confcall that took place on May 13th, it seemed like there were some doubts about the public nature of FI-WARE GE Open Specifications. During that same confcall, DT confirmed that the API specifications linked to the IdM GE hadn't still been made publicly available and had been only distributed to interested party upon request. I would like to make it clear that the public and royalty-free nature of the FI-WARE Open Specifications was a very basic fundamental principle adopted in FI-WARE. This principle was agreed among the partners even at FI-WARE proposal time and was not only reflected in our DoW but also in our Consortium Agreement (see details at the end of this message). To reinforce the requirement to make FI-WARE Open Specifications available, please note that the corresponding deliverables are marked as PU (public) in the DoW. Therefore, not making FI-WARE GE Open Specifications public available would be considered, you can take it as granted, an infringement of the contract by the EC. Bottom line, I kindly request that you make the specifications part of the FI-WARE Open Specifications available through the public wiki and also as part of the corresponding FI-WARE Open Specifications deliverable from the Security Chapter to be submitted. Otherwise, we will accompany such submission with a note clarifying that the specifications have not been made publicly available despite the request. We cannot respond on behalf of the EC but I can anticipate that they will consider this an infringement of the contract by the corresponding partners, most probably leading to consequences in the form of rejection of costs among others. I hope this will not become an issue and that specificications of the IdM GE APIs will be finally delivered as public. DT recently explained to me that "Until now we provided it only to those who have requested an instance. I don't want that everybody in the Internet has the possibility to have a try on our (DT) servers". However, any potential issue is solved by means of dropping from the RESTfull specs any reference to the actual service end points linked to the DT GEi provided "as a Service" where the IdM GE RESTful API would be supported. Such service end points indeed should not be part of the FI-WARE IdM GE Open Specifications (allowing other parties to implement the FI-WARE IdM GE Open Specifications, deploy that implementation somewhere and publish the associated service end points that specific deployment). Therefore, I don't see the issue. You just need to check the several examples of Restful API specifications associated to FI-WARE GEs (e.g., the NGSI RESTful specification) to see an example of RESTful API specification not tied to any concrete service end point. Best regards, -- Juanjo Relevant excerpts from the Consortium Agreement: FI-WARE Generic Enabler Specifications are defined in Annex 1 of the Grant Agreement and refer to the set of specifications establishing requirements for the FIWARE Generic Enabler, particularly with respect to Application Programming Interfaces (APIs), interfaces, and interoperable protocols, required to work with FIWARE Generic Enablers of the FI-WARE Project platform or other complementary platform products from third parties. Specifications of APIs, interfaces and interoperable protocols described in such a FI-WARE Generic Enabler Specification shall include a description of behaviour (e.g. methods and parameters or resource endpoints and their digital representation) but would be limited to exhibited behaviour. FI-WARE Generic Enabler Specifications will be made publically available (upon publication in accordance with clause 4.4.1) on royalty free terms. For the sake of clarity, Parties signing this CA as well as any other third party may, subject to additional conditions or agreement where requested by a Party/ the Parties (provided that the right to obtain Access Rights granted under this Agreement must not be negatively affected by such request),develop and release implementations of the FI-WARE Generic Enabler Specifications on a royalty-free basis. clause 4.4.1 (althought it indeed applies to objection of a given party to publication of specs from other party, because no objection by a party to publish its own specs was actually foreseen): A copy of any draft of FIWARE Generic Enabler specifications shall be sent to the Project Coordinator and by the Project Coordinator to the Parties at the earliest time possible. Any of the Parties may object to the publication within 30 days after receipt of a copy of the proposed publication on any of the following grounds: (i) that they consider that the protection of the objecting Party's Foreground would be adversely affected by the proposed publication, (ii) that the proposed publication includes the Confidential Information of the objecting Party, or (iii) the publication of such information would be contrary to the commercial interests of the objecting Party. The proposed publication shall not take place until the expiry of the above period of 30 days. In the absence of any objection within the above mentioned period, it is deemed that the Parties agree to the proposed publication. Following the end of the above mentioned period, the Project Coordinator shall inform the Parties whether or not any objection has been received. Objections to publication of the final specifications of a Generic Enabler Specification will not apply if there were no objections to previously distributed drafts of FIWARE Generic Enabler Specifications, unless the changes between the draft and final version of the FIWARE Generic Enabler Specifications precisely provide the ground for the objection to publish the final version. In the event that an objection is raised on any of the above defined grounds within the above period of 30 days, the Party proposing the publication and the Party objecting shall seek in good faith to agree a solution on a timely basis, that will not exceed of 30 days, whereby such objection is resolved. In case that the objection raised affects the publication of the FIWARE Generic Enabler Specifications (as defined in this Consortium Agreement) if no solution is found within the term established in this paragraph, the parties will submit the controversy to the General Assembly, which decision will be final and binding and in accordance with the confidentiality provisions established in this Consortium Agreement. ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 22 09:59:11 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 May 2013 09:59:11 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Message-ID: <4103_1369209554_519C7AD2_4103_6769_1_140b0282-c34d-4cda-a437-d571633e3068@THSONEA01HUB03P.one.grp> Dear Colleagues, This just to draw your attention to the fact that peer review of our open specs did come already for some of our GEs V2. Hope you already noticed and started to address those comments. At least some comments are there for: Security Monitoring GE - So please Daniel address with support of your team Data Handling GE -> Please Slim address Malware Detection Service, Android Flow Monitoring and Content-based Security -> So please Guillaume, Alexandre and Richard check and address peer review comments for your GEs. As usual let me and Daniel know once you have addressed those comments. As for the rest we still miss peer review of IdM, Context based security & compliance, Access Control, DB Anonimyzer and SSS (but SSS since part of V1 was already reviewed so is assumed ok). For those who owns those GEs please check regularly the Open Specs peer review cockpit and address once uploaded review of your GEs .. As for Privacy that GE is for June so Open Specs will be reviewed once made fully available. Counting on you all -------------- next part -------------- An HTML attachment was scrubbed... URL: From Richard.Egan at uk.thalesgroup.com Wed May 22 10:19:43 2013 From: Richard.Egan at uk.thalesgroup.com (EGAN Richard) Date: Wed, 22 May 2013 09:19:43 +0100 Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) In-Reply-To: <4103_1369209554_519C7AD2_4103_6769_1_140b0282-c34d-4cda-a437-d571633e3068@THSONEA01HUB03P.one.grp> References: <4103_1369209554_519C7AD2_4103_6769_1_140b0282-c34d-4cda-a437-d571633e3068@THSONEA01HUB03P.one.grp> Message-ID: Pascal, as there are no comments on the Content Based Security (Chapter 19 & 20), I think that the reviewer (who was it?) has not reviewed these chapters but has reviewed Context Based Security instead. Can you get in touch with TID and see if it possible to do a quick review as time is short for everybody. Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 22 May 2013 08:59 To: Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; EGAN Richard; Alexandre Boeglin; fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Dear Colleagues, This just to draw your attention to the fact that peer review of our open specs did come already for some of our GEs V2. Hope you already noticed and started to address those comments. At least some comments are there for: Security Monitoring GE - So please Daniel address with support of your team Slim address Malware Detection Service, Android Flow Monitoring and Content-based Security -> So please Guillaume, Alexandre and Richard check and address peer review comments for your GEs. As usual let me and Daniel know once you have addressed those comments. As for the rest we still miss peer review of IdM, Context based security & compliance, Access Control, DB Anonimyzer and SSS (but SSS since part of V1 was already reviewed so is assumed ok). For tho ase check regularly the Open Specs peer review cockpit and address once uploaded review of your GEs .. As for Privacy that GE is for June so Open Specs will be reviewed once made fully available. Counting on you all -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 22 10:26:14 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 May 2013 10:26:14 +0200 Subject: [Fiware-security] TR: FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Message-ID: <24855_1369211178_519C812A_24855_18275_2_6f65fa3a-4826-4cdb-8bb4-77a8337167cc@THSONEA01HUB03P.one.grp> Dear Richard, Dear Susana, Thanks for you check Richard. Overall I'm always a bit surprised with the way these reviews are conducted/performed. But in any case we have to cope with them. So in your case let's assume it is fine but since you noticed that context-based & security could have been reviewed I will ask Susana to have a look and address review comments and update the wiki (public) accordingly. Also inform me once done. Best Regards, Pascal De : EGAN Richard [mailto:Richard.Egan at uk.thalesgroup.com] Envoy? : mercredi 22 mai 2013 10:20 ? : BISSON Pascal; Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; Alexandre Boeglin; fiware-security at lists.fi-ware.eu; PENNINGTON Sarah Objet : RE: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Pascal, as there are no comments on the Content Based Security (Chapter 19 & 20), I think that the reviewer (who was it?) has not reviewed these chapters but has reviewed Context Based Security instead. Can you get in touch with TID and see if it possible to do a quick review as time is short for everybody. Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 22 May 2013 08:59 To: Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; EGAN Richard; Alexandre Boeglin; fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Dear Colleagues, This just to draw your attention to the fact that peer review of our open specs did come already for some of our GEs V2. Hope you already noticed and started to address those comments. At least some comments are there for: Security Monitoring GE - So please Daniel address with support of your team Slim address Malware Detection Service, Android Flow Monitoring and Content-based Security -> So please Guillaume, Alexandre and Richard check and address peer review comments for your GEs. As usual let me and Daniel know once you have addressed those comments. As for the rest we still miss peer review of IdM, Context based security & compliance, Access Control, DB Anonimyzer and SSS (but SSS since part of V1 was already reviewed so is assumed ok). For tho ase check regularly the Open Specs peer review cockpit and address once uploaded review of your GEs .. As for Privacy that GE is for June so Open Specs will be reviewed once made fully available. Counting on you all -------------- next part -------------- An HTML attachment was scrubbed... URL: From susana.gzarzosa at atosresearch.eu Wed May 22 10:35:30 2013 From: susana.gzarzosa at atosresearch.eu (Susana Gonzalez Zarzosa) Date: Wed, 22 May 2013 10:35:30 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) In-Reply-To: <24855_1369211178_519C812A_24855_18275_2_6f65fa3a-4826-4cdb-8bb4-77a8337167cc@THSONEA01HUB03P.one.grp> References: <24855_1369211178_519C812A_24855_18275_2_6f65fa3a-4826-4cdb-8bb4-77a8337167cc@THSONEA01HUB03P.one.grp> Message-ID: Hi, Richard is right, I've just opened the doc included in the Cockpit for the CBS... and the comments are about our Context-based S&C. We'll address them ASAP and inform you. Thanks and best regards, Susana From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: mi?rcoles, 22 de mayo de 2013 10:26 To: EGAN Richard; Susana Gonzalez Zarzosa Cc: fiware-security at lists.fi-ware.eu; Gulden Yilmaz; Antonio Garcia Vazquez Subject: TR: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Dear Richard, Dear Susana, Thanks for you check Richard. Overall I'm always a bit surprised with the way these reviews are conducted/performed. But in any case we have to cope with them. So in your case let's assume it is fine but since you noticed that context-based & security could have been reviewed I will ask Susana to have a look and address review comments and update the wiki (public) accordingly. Also inform me once done. Best Regards, Pascal De : EGAN Richard [mailto:Richard.Egan at uk.thalesgroup.com] Envoy? : mercredi 22 mai 2013 10:20 ? : BISSON Pascal; Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; Alexandre Boeglin; fiware-security at lists.fi-ware.eu; PENNINGTON Sarah Objet : RE: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Pascal, as there are no comments on the Content Based Security (Chapter 19 & 20), I think that the reviewer (who was it?) has not reviewed these chapters but has reviewed Context Based Security instead. Can you get in touch with TID and see if it possible to do a quick review as time is short for everybody. Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 22 May 2013 08:59 To: Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; EGAN Richard; Alexandre Boeglin; fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Dear Colleagues, This just to draw your attention to the fact that peer review of our open specs did come already for some of our GEs V2. Hope you already noticed and started to address those comments. At least some comments are there for: Security Monitoring GE - So please Daniel address with support of your team Slim address Malware Detection Service, Android Flow Monitoring and Content-based Security -> So please Guillaume, Alexandre and Richard check and address peer review comments for your GEs. As usual let me and Daniel know once you have addressed those comments. As for the rest we still miss peer review of IdM, Context based security & compliance, Access Control, DB Anonimyzer and SSS (but SSS since part of V1 was already reviewed so is assumed ok). For tho ase check regularly the Open Specs peer review cockpit and address once uploaded review of your GEs .. As for Privacy that GE is for June so Open Specs will be reviewed once made fully available. Counting on you all ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 22 11:13:10 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 May 2013 11:13:10 +0200 Subject: [Fiware-security] Peer review of Security Chapter GE - Notification & Demand Message-ID: <21665_1369213994_519C8C2A_21665_1985_1_49b091d7-e033-4b4f-ae3c-8eb87ae70fe3@THSONEA01HUB01P.one.grp> Dear Alex, When instructing my team to address review comments made available so far regarding our Security GEs V2 we noticed that TID review hereafter was covering review of as announced Malware Detection Srvice, Android Flow Monitoring but not Content based security. In fact instead it covers review of Context-based Security & Compliance (so that one has also been reviewed by your team). http://www.google.com/url?q=https://forge.fi-ware.eu/docman/view.php/27/2385/D812_WP8_v2_generated%2B20130515_Reviewed_TID.docx&usd=1&usg=ALhdy2-dH_2P6IAyXRo_YRW3xKue9_qRcA So could you please urgently instruct TID to also perform and send us their review of Content Based Security and let me know when other missing GE peer review could be delivered to us. Thanks in advance. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 22 15:09:53 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 May 2013 15:09:53 +0200 Subject: [Fiware-security] [Fiware-wpl] URGENT: Delivery of Open specs TODAY In-Reply-To: <519CB99C.1040807@tid.es> References: <519CB99C.1040807@tid.es> Message-ID: <20567_1369228199_519CC3A7_20567_4164_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E57C0A3A@THSONEA01CMS04P.one.grp> Dear Miguel, Dear Colleagues, To complete Miguel's email and to be precise we (as Security Chapter) can't deliver because we haven't yet received all peer reviews of our Chapter's open-specs. Still some are missing although a few. As for Open-specs review we got. The comments have been addressed (at least the ones on which we could have agreement). Meaning with help of Cloud Chapter delivering us the latest review we could also deliver. So please Miguel/Juanjo consider this. Even more than it would be better for all to deliver altogether. Even more if it is only a matter of a day if not hours. I put in cc the Security team for information. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mercredi 22 mai 2013 14:27 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 22 19:05:35 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 May 2013 19:05:35 +0200 Subject: [Fiware-security] [Fiware-wpl] URGENT: Delivery of Open specs TODAY In-Reply-To: <20567_1369228199_519CC3A7_20567_4164_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E57C0A3A@THSONEA01CMS04P.one.grp> References: <519CB99C.1040807@tid.es> <20567_1369228199_519CC3A7_20567_4164_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E57C0A3A@THSONEA01CMS04P.one.grp> Message-ID: <519CFADF.1000005@tid.es> Dear Pascal, Note that one important matter, regarding the Security chapter, will be to deliver the Open Specifications of the APIs associated to the IdM GE. Please refer to my email on the matter sent this Monday (subject: "Public availability of FI-WARE GE Open Specifications") Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 22/05/13 15:09, BISSON Pascal wrote: Dear Miguel, Dear Colleagues, To complete Miguel's email and to be precise we (as Security Chapter) can't deliver because we haven't yet received all peer reviews of our Chapter's open-specs. Still some are missing although a few. As for Open-specs review we got. The comments have been addressed (at least the ones on which we could have agreement). Meaning with help of Cloud Chapter delivering us the latest review we could also deliver. So please Miguel/Juanjo consider this. Even more than it would be better for all to deliver altogether. Even more if it is only a matter of a day if not hours. I put in cc the Security team for information. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mercredi 22 mai 2013 14:27 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 22 19:15:45 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 May 2013 19:15:45 +0200 Subject: [Fiware-security] [Fiware-wpl] URGENT: Delivery of Open specs TODAY In-Reply-To: <519CFADF.1000005@tid.es> References: <519CB99C.1040807@tid.es> <20567_1369228199_519CC3A7_20567_4164_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E57C0A3A@THSONEA01CMS04P.one.grp> <519CFADF.1000005@tid.es> Message-ID: <4567_1369242951_519CFD47_4567_6544_1_1db47d27-7e2c-4637-8d90-41f1a0691905@THSONEA01HUB01P.one.grp> Hi Juanjo, Have you contacted NSN & DT representatives at PCC level to discuss the matter and ? If not I would suggest/urge you to do so (putting me, Daniel and NSN/DT colleagues in WP8 in cc) to see what can be done with their support to get us out of the rut since so far on the topic we are stuck. Hope you share. Counting on you to proceed. Best Regards, Pascal De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mercredi 22 mai 2013 19:06 ? : BISSON Pascal Cc : Miguel Carrillo; fiware-security at lists.fi-ware.eu Objet : Re: [Fiware-wpl] URGENT: Delivery of Open specs TODAY Dear Pascal, Note that one important matter, regarding the Security chapter, will be to deliver the Open Specifications of the APIs associated to the IdM GE. Please refer to my email on the matter sent this Monday (subject: "Public availability of FI-WARE GE Open Specifications") Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 22/05/13 15:09, BISSON Pascal wrote: Dear Miguel, Dear Colleagues, To complete Miguel's email and to be precise we (as Security Chapter) can't deliver because we haven't yet received all peer reviews of our Chapter's open-specs. Still some are missing although a few. As for Open-specs review we got. The comments have been addressed (at least the ones on which we could have agreement). Meaning with help of Cloud Chapter delivering us the latest review we could also deliver. So please Miguel/Juanjo consider this. Even more than it would be better for all to deliver altogether. Even more if it is only a matter of a day if not hours. I put in cc the Security team for information. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mercredi 22 mai 2013 14:27 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] URGENT: Delivery of Open specs TODAY Dear all, I was checking with Juanjo who is travelling today and he asks for the open specs for delivery today as stated last monday(attached message). What I mean is regenerating them using the wiki cover etc. You can manually trigger the regeneration anytime if needed so you just nedd to tell me or Thorsten and we will look into it. I am going to send them to the EC. As regards the Legal Notice and as Juanjo pointed out in the attached message, I remind you that the respective owners may want to add the link to the new Legal Notice replacing the old interim Legal Notice. There is one exception: security cannot delivered today for reasons that Pascal and we know. Please send me both pdf and word versions of each open specs doc before 5pm. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandre.boeglin at inria.fr Wed May 22 20:18:21 2013 From: alexandre.boeglin at inria.fr (Alexandre Boeglin) Date: Wed, 22 May 2013 20:18:21 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) In-Reply-To: <4103_1369209554_519C7AD2_4103_6769_1_140b0282-c34d-4cda-a437-d571633e3068@THSONEA01HUB03P.one.grp> References: <4103_1369209554_519C7AD2_4103_6769_1_140b0282-c34d-4cda-a437-d571633e3068@THSONEA01HUB03P.one.grp> Message-ID: <20130522181821.GD4982@inria.fr> Dear Pascal, All, I have addressed the comments related to the IoT Fuzzer, Android Vulnerability Assessment and Android Flow Monitoring open specs ; and Fabrice should be currently handling the Malware Detection Service. However, some comments were related to "not following the template", but the proposed fixes were in contradiction with the template available on the wiki (at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Where_and_how_to_publish_Open_Specifications, which was recently advertised as the one to follow, which I believe I did). I had a look at other chapter's open specs, ans it seems not everyone is following the same template? So, could someone please clarify the situation? Best regards, Alexandre Le mercredi 22 mai 2013 ? 09:59, BISSON Pascal a ?crit: > Dear Colleagues, > > This just to draw your attention to the fact that peer review of our open specs did come already for some of our GEs V2. Hope you already noticed and started to address those comments. > > At least some comments are there for: > > Security Monitoring GE - So please Daniel address with support of your team > Data Handling GE -> Please Slim address > Malware Detection Service, Android Flow Monitoring and Content-based Security -> So please Guillaume, Alexandre and Richard check and address peer review comments for your GEs. > > As usual let me and Daniel know once you have addressed those comments. > > As for the rest we still miss peer review of IdM, Context based security & compliance, Access Control, DB Anonimyzer and SSS (but SSS since part of V1 was already reviewed so is assumed ok). For those who owns those GEs please check regularly the Open Specs peer review cockpit and address once uploaded review of your GEs .. > > As for Privacy that GE is for June so Open Specs will be reviewed once made fully available. > > Counting on you all -- Alexandre Boeglin Madynes project-team ? http://madynes.loria.fr/ Inria ? http://www.inria.fr/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3058 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Thu May 23 18:04:44 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 23 May 2013 18:04:44 +0200 Subject: [Fiware-security] Security Chapter - Backlog - Wiki Review from TID (Manuel) Message-ID: <355_1369325089_519E3E21_355_3088_1_a505db16-770a-4b8e-b84d-94e0e102f64a@THSONEA01HUB03P.one.grp> Dear all, Here is the link to the outcomes of the Security Chapter wiki review performed by TID. Please have and consider for further improvements (and yes there is room although I just had a quick and that we may some of the explanations) WP8 - Sec: https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From susana.gzarzosa at atosresearch.eu Thu May 23 18:34:04 2013 From: susana.gzarzosa at atosresearch.eu (Susana Gonzalez Zarzosa) Date: Thu, 23 May 2013 18:34:04 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) In-Reply-To: <24855_1369211178_519C812A_24855_18275_2_6f65fa3a-4826-4cdb-8bb4-77a8337167cc@THSONEA01HUB03P.one.grp> References: <24855_1369211178_519C812A_24855_18275_2_6f65fa3a-4826-4cdb-8bb4-77a8337167cc@THSONEA01HUB03P.one.grp> Message-ID: Dear Pascal, The review comments about the Context-based Security & Compliance have been already addressed in the public wiki. Best regards, Susana From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: mi?rcoles, 22 de mayo de 2013 10:26 To: EGAN Richard; Susana Gonzalez Zarzosa Cc: fiware-security at lists.fi-ware.eu; Gulden Yilmaz; Antonio Garcia Vazquez Subject: TR: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Dear Richard, Dear Susana, Thanks for you check Richard. Overall I'm always a bit surprised with the way these reviews are conducted/performed. But in any case we have to cope with them. So in your case let's assume it is fine but since you noticed that context-based & security could have been reviewed I will ask Susana to have a look and address review comments and update the wiki (public) accordingly. Also inform me once done. Best Regards, Pascal De : EGAN Richard [mailto:Richard.Egan at uk.thalesgroup.com] Envoy? : mercredi 22 mai 2013 10:20 ? : BISSON Pascal; Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; Alexandre Boeglin; fiware-security at lists.fi-ware.eu; PENNINGTON Sarah Objet : RE: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Pascal, as there are no comments on the Content Based Security (Chapter 19 & 20), I think that the reviewer (who was it?) has not reviewed these chapters but has reviewed Context Based Security instead. Can you get in touch with TID and see if it possible to do a quick review as time is short for everybody. Richard From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: 22 May 2013 08:59 To: Alexandre Boeglin; Guillaume BONFANTE; DI CERBO, Francesco; TRABELSI, Slim; EGAN Richard; Alexandre Boeglin; fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 - Peer-review of Open Specs (some already there so please Address in a timely manner !) Dear Colleagues, This just to draw your attention to the fact that peer review of our open specs did come already for some of our GEs V2. Hope you already noticed and started to address those comments. At least some comments are there for: Security Monitoring GE - So please Daniel address with support of your team Slim address Malware Detection Service, Android Flow Monitoring and Content-based Security -> So please Guillaume, Alexandre and Richard check and address peer review comments for your GEs. As usual let me and Daniel know once you have addressed those comments. As for the rest we still miss peer review of IdM, Context based security & compliance, Access Control, DB Anonimyzer and SSS (but SSS since part of V1 was already reviewed so is assumed ok). For tho ase check regularly the Open Specs peer review cockpit and address once uploaded review of your GEs .. As for Privacy that GE is for June so Open Specs will be reviewed once made fully available. Counting on you all ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandre.boeglin at inria.fr Thu May 23 18:52:24 2013 From: alexandre.boeglin at inria.fr (Alexandre Boeglin) Date: Thu, 23 May 2013 18:52:24 +0200 (CEST) Subject: [Fiware-security] Security Chapter - Backlog - Wiki Review from TID (Manuel) In-Reply-To: <355_1369325089_519E3E21_355_3088_1_a505db16-770a-4b8e-b84d-94e0e102f64a@THSONEA01HUB03P.one.grp> Message-ID: <987007614.2900276.1369327944673.JavaMail.root@inria.fr> Hi, One question: what should be done with "not allowed" items? I can remove the references to them from the "Materializing Security in FI-WARE" page. But what should I do with the page itself ? As far as I know, we don't have permissions to delete pages on the wikis. Best regards, Alex ----- Mail original ----- > De: "BISSON Pascal" > ?: fiware-security at lists.fi-ware.eu > Cc: "MANUEL ESCRICHE VICENTE" > Envoy?: Jeudi 23 Mai 2013 18:04:44 > Objet: [Fiware-security] Security Chapter - Backlog - Wiki Review > from TID (Manuel) > Dear all, > Here is the link to the outcomes of the Security Chapter wiki review > performed by TID. > Please have and consider for further improvements (and yes there is > room although I just had a quick and that we may some of the > explanations) > WP8 ? Sec: > https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx > Best Regards, > Pas cal html> > _______________________________________________ > Fiware-security mailing list > Fiware-security at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri May 24 09:21:42 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 24 May 2013 09:21:42 +0200 Subject: [Fiware-security] Security Chapter - Backlog - Wiki Review from TID (Manuel) In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B89050204@EX10-MB2-MAD.hi.inet> References: <355_1369325089_519E3E21_355_3088_1_a505db16-770a-4b8e-b84d-94e0e102f64a@THSONEA01HUB03P.one.grp> <987007614.2900276.1369327944673.JavaMail.root@inria.fr> <65CDBE2E7E5A964BB8BC5F4328FDE90B89050204@EX10-MB2-MAD.hi.inet> Message-ID: <18601_1369380105_519F1509_18601_8118_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E585B37B@THSONEA01CMS04P.one.grp> Thanks Manuel. And yes this is something to further discuss at Mgt Board to get full understanding and answer to WP questions that might have been rasied. As in the case of Alexandre. In the meantime and for us the priority remains to deliver M24 deliverables. So let?s re-address this once delivered and of course starting early next Week. Best Regards, Pascal De : MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Envoy? : jeudi 23 mai 2013 20:52 ? : Alexandre Boeglin; BISSON Pascal Cc : fiware-security at lists.fi-ware.eu Objet : RE: [Fiware-security] Security Chapter - Backlog - Wiki Review from TID (Manuel) Hi Alex, The review checking goes only to the materializing page. So removing it from there would do. The other question can be raised by Pascal to the management board. Kind regards, Manuel From: Alexandre Boeglin [mailto:alexandre.boeglin at inria.fr] Sent: jueves, 23 de mayo de 2013 18:52 To: BISSON Pascal Cc: MANUEL ESCRICHE VICENTE; fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] Security Chapter - Backlog - Wiki Review from TID (Manuel) Hi, One question: what should be done with "not allowed" items? I can remove the references to them from the "Materializing Security in FI-WARE" page. But what should I do with the page itself ? As far as I know, we don't have permissions to delete pages on the wikis. Best regards, Alex ________________________________ De: "BISSON Pascal" > ?: fiware-security at lists.fi-ware.eu Cc: "MANUEL ESCRICHE VICENTE" > Envoy?: Jeudi 23 Mai 2013 18:04:44 Objet: [Fiware-security] Security Chapter - Backlog - Wiki Review from TID (Manuel) Dear all, Here is the link to the outcomes of the Security Chapter wiki review performed by TID. Please have and consider for further improvements (and yes there is room although I just had a quick and that we may some of the explanations) WP8 ? Sec: https://forge.fi-ware.eu/docman/view.php/27/2427/FIWARE.backlog.security.review.20130523-1452.xlsx Best Regards, Pas cal html> _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From francesco.di.cerbo at sap.com Fri May 24 11:06:16 2013 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Fri, 24 May 2013 09:06:16 +0000 Subject: [Fiware-security] mailing list to advertise webminars Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E6070AD41A@DEWDFEMB18B.global.corp.sap> Hello all, The ML for advertising webminars is: fiware-training at lists.fi-ware.eu best, francesco ___ Francesco Di Cerbo, PhD SAP Next Business and Technology Applied Research Security & Trust SAP Labs France 805, avenue Maurice Donat Font de l'Orme BP 1216 06250 Mougins Cedex France Tel. +33 4 92 28 64 45 e-mail: Francesco.Di.Cerbo at sap.com From mcp at tid.es Fri May 24 16:25:20 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 24 May 2013 16:25:20 +0200 Subject: [Fiware-security] mailing list to advertise webminars In-Reply-To: <6D11E010ED8E5B4B9D42045AC71F37E6070AD41A@DEWDFEMB18B.global.corp.sap> References: <6D11E010ED8E5B4B9D42045AC71F37E6070AD41A@DEWDFEMB18B.global.corp.sap> Message-ID: <519F7850.9040105@tid.es> Dear Francesco, The attached email (sent to all) states clearly that: " the fi-ware-training list will not be used for now. Let us leave it dormant." Best regards, Miguel El 24/05/2013 11:06, DI CERBO, Francesco escribi?: Hello all, The ML for advertising webminars is: fiware-training at lists.fi-ware.eu best, francesco ___ Francesco Di Cerbo, PhD SAP Next Business and Technology Applied Research Security & Trust SAP Labs France 805, avenue Maurice Donat Font de l'Orme BP 1216 06250 Mougins Cedex France Tel. +33 4 92 28 64 45 e-mail: Francesco.Di.Cerbo at sap.com _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Miguel Carrillo Subject: [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Date: Thu, 23 May 2013 20:05:05 +0200 Size: 13922 URL: From francesco.di.cerbo at sap.com Fri May 24 16:27:41 2013 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Fri, 24 May 2013 14:27:41 +0000 Subject: [Fiware-security] mailing list to advertise webminars In-Reply-To: <519F7850.9040105@tid.es> References: <6D11E010ED8E5B4B9D42045AC71F37E6070AD41A@DEWDFEMB18B.global.corp.sap> <519F7850.9040105@tid.es> Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E6070AD67D@DEWDFEMB18B.global.corp.sap> Hi Miguel, Indeed, I overlooked the ?PS ? part of the mail ! thanks for the notice! francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo Sent: vendredi 24 mai 2013 16:25 To: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] mailing list to advertise webminars Dear Francesco, The attached email (sent to all) states clearly that: " the fi-ware-training list will not be used for now. Let us leave it dormant." Best regards, Miguel El 24/05/2013 11:06, DI CERBO, Francesco escribi?: Hello all, The ML for advertising webminars is: fiware-training at lists.fi-ware.eu best, francesco ___ Francesco Di Cerbo, PhD SAP Next Business and Technology Applied Research Security & Trust SAP Labs France 805, avenue Maurice Donat Font de l'Orme BP 1216 06250 Mougins Cedex France Tel. +33 4 92 28 64 45 e-mail: Francesco.Di.Cerbo at sap.com _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Fri May 24 16:34:45 2013 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 24 May 2013 16:34:45 +0200 Subject: [Fiware-security] mailing list to advertise webminars In-Reply-To: <519F7850.9040105@tid.es> References: <6D11E010ED8E5B4B9D42045AC71F37E6070AD41A@DEWDFEMB18B.global.corp.sap> <519F7850.9040105@tid.es> Message-ID: <519F7A85.8020704@tid.es> no problem! Have a nice weekend all of you! Miguel El 24/05/2013 16:25, Miguel Carrillo escribi?: Dear Francesco, The attached email (sent to all) states clearly that: " the fi-ware-training list will not be used for now. Let us leave it dormant." Best regards, Miguel El 24/05/2013 11:06, DI CERBO, Francesco escribi?: Hello all, The ML for advertising webminars is: fiware-training at lists.fi-ware.eu best, francesco ___ Francesco Di Cerbo, PhD SAP Next Business and Technology Applied Research Security & Trust SAP Labs France 805, avenue Maurice Donat Font de l'Orme BP 1216 06250 Mougins Cedex France Tel. +33 4 92 28 64 45 e-mail: Francesco.Di.Cerbo at sap.com _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri May 24 17:31:47 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 24 May 2013 17:31:47 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Message-ID: <29713_1369409511_519F87E7_29713_1513_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E60137E2@THSONEA01CMS04P.one.grp> FYI and as discussed this morning a tour audio conf. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : jeudi 23 mai 2013 20:05 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Communication strategy for the coming FI-WARE webminars Dear all, We are organizing the webminars in a more informal an hopefully effective manner. We will use twitter to broadcast the details of the webminars * Each webminar will have a dedicated hashtag * The owner of each webminar will tweet messages with the relevant info to @Fiware from their accounts, also using the GEi hashtag. This could happen before , after and during the webminar. * The attendees will be encouraged to make questions to you via twitter during the presentation. They will use the hashtag for the webminar and will send the tweet to @Fiware - of course, in principle you must reply. If a question arrives while a seminar is ongoing, this gives the presented the ability to decide when to answer or to decide not to do so (if it the answer is provided later in his presentation, for instance) We keep the details publicly updated here: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdF9aeWphSkFkWjJRQ3pPVW1PVURLX3c#gid=8 All GE owners please : * Immediate action point (for now): Add the hashtag you will use for your GEi in column F * It seems obvious but .... make sure that you have a twitter account ready to broadcast your messages! * Add the logistic details there (if needed) * Make sure that you do not forget to announce your webminar via twitter a number of days in advance * Make sure that you publicise your hashtag and that people know that they have to use it to draw your attention to their questions * Make sure that you are ready to reply to questions via twitter during the webminar We are going to publicly announce this to the PPP shortly. Best regards, Miguel P.S.: before anyone asks, the fi-ware-training list will not be used for now. Let us leave it dormant. -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Fri May 24 18:46:50 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 24 May 2013 18:46:50 +0200 Subject: [Fiware-security] WP8 - Content moved from FI-WARE Private Wiki to Public Wiki Message-ID: <941_1369414017_519F9981_941_224_1_2234e23a-442f-4fa5-88a3-5372262f3a71@THSONEA01HUB06P.one.grp> Dear All, This just to let you know that I & Daniel did move content for Deliverables D8.2-5.2 from FI-WARE Private Wiki to Public Wiki. This in order to be in position to generate deliverables. As such and in case of last update to be performed please proceed with an update on the Public Wiki where content has been moved. Even more that Deliverables D8.2-5.2 would be generated from that Wiki. As for the rest I did generate D822 already (and updated cockpit as per instructions received from TID) but as per email you saw from Miguel, TID did want to sent to the EC D822,D832,D842 and D852 as a block and as such will call for latest issues to be solved first. So stay tune to get them solved/fixed. As per review I did get from Firmin I was assuming I could generate D822 at least. So why I did it. In any case and to make final changes please go to the Public Wiki since content was moved there. Also counting on you all to perform a quick check of content we did move from your side and on your behalf. After check we did perform it seems o As for the rest Daniel and I will continue to check and prepare delivery of D832,D842 and D852. Of course deliverable generated could be generated to incorporate latest changes requested. Best Regards, Pascal PS: [@All bear in mind from Tuesday to Thursday next week I would be travelling and that that Daniel will be my replacement] -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon May 27 11:00:02 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 27 May 2013 11:00:02 +0200 Subject: [Fiware-security] [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture In-Reply-To: <51A2F2E5.3020101@tid.es> References: <51A2EFD2.6040106@tid.es> <51A2F2E5.3020101@tid.es> Message-ID: <17822_1369645218_51A3209F_17822_5109_7_ac2b02aa-0439-4d38-9840-4c72ed652341@THSONEA01HUB06P.one.grp> Dear All, I'm forwarding you this email I got from Juanjo. See comments he did provide on architecture specifications and especially ours (aka Security). Please notice they have incorporated in the architecture deliverable he did already submit (as stated in his email). But now we have to perform the necessary adjustments on the wiki for them to be included in the Open Specs deliverable. Being said we are already beyond schedule please update the wiki asap so that we can generate and deliver the open specs. As usual drop me and/Daniel an email once changes have been performed. Counting on your promptness to get this demand addressed Thanks, Regards Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 27 mai 2013 07:45 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Hi, Please find attached the final official submission of the FI-WARE Architecture deliverable. While carrying out a very final cross-chapter revision, I have identified the need to achieve a better consistency between names of sections in the different chapters and even within chapters: * There were some cases where the section titled "Basic Concepts" within the Architecture Description of a given GE was titled as "Main Concepts". I have changed this wherever I found it * There were some cases where the "Main Interactions" section within the Architecture Description of a given GE was titled as "Main Operations". I have changed this wherever I found it. There were GEs in the Security chapter for which the sections related to Copyright and Legal Notices were missing. This also happens regarding Basic Design Principles. Please add these sections asap. Despite I asked for the names of the companies to be added manually, I got no response. It would be nice that you perform a general review of the structure in your chapters and double-check alignment with the standard structure template we defined. I fixed a lot of the issues but this would be only reflected in the final deliverable so I have produced and already sent to you a version with comments that highlighted the changes you should introduce in the public wiki ASAP (note that this document is marked as private). For your convenience, here it goes the structure of sections that should have been adopted: 1. General Architecture Description of a Chapter: * Introduction * Architecture Overview * * Architecture Description of GEs * Interface to other chapters * References 2. Architecture Description of a given GE: * Copyright * Legal Notice * Overview (Target usage should be inside) * Basic Concepts * Architecture (recommended but optional, sometimes you have put this before "Basic concepts" but it would be nice to keep consistency and place it after) * Main Interactions * Basic Design Principles * Detailed Open Specifications (which should contain the links to the rest of Open Specifications) * References There were also A LOT of inconsistencies regarding level of headings. As an example, there were many chapters where there wasn't a second level heading. This was revealed thanks to the automated generation process and should be fixed in the wiki asap to avoid wrong generation next times. I carried out a final spelling checking to all chapters finding also many typos. I have to confess that I got astonished when I saw still those kind of issues in a so late stage of the peer-review ... Didn't nobody notice that? Despite we incurred in a delay, I have now found that it was worth carrying out this final review. Without giving names, when I have asked "how can we still find this issues?" in the draft I had just reviewed, I got the response "honestly, I believe some people hasn't read the contents in that detail". We honestly have to reconsider how we are carrying out our peer-review processes. I have also carried out several changes to improve overall readability. The detailed Open Specifications where not included in all cases, even within the same chapter, so I have had to put a note to the EC and reviewers explaining that we had decided to keep the inclusion by those GEs that decided to include it, because we will adopt that convention finally. Therefore, please do so. In addition, I also found that the copyright notice in many of the cases was only for 2012. This maybe interpreted by the reviewers as "no single line has been touched by the owners this year" when clearly this doesn't apply. Please fix those Copyright Notices where you have to write 2012-2013 (in the case of new GEs, 2013) Last but not least, there are a number of things that I have detected about which we have to reach a final agreement and adopt a convention across all chapters: * Titles, numbering and format (i.e., centered or not) of figures. I believe that we proposed a convention, and asked to avoid using of figure numbers, but apparently hasn't been followed consistently * Architecture section within a GE Architecture Description * Style for references We should address all of them once we finish with the most urgent things we currently have on our plate, but have them ready at the time we will start disseminating this among the wider community of developers. Please share with members of your respective chapters. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Date: Mon, 27 May 2013 07:32:02 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom at ec.europa.eu, dgr at whitestein.com, msli at icfocus.co.uk, renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com CC: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of deliverable D.2.3.2 FI-WARE Architecture. To ease review of its contents, separate files have been produced for the different chapters that made up the whole document. All of these files can be extracted from the .zip file you can download from the following URL: https://forge.fi-ware.eu/docman/view.php/7/2468/D.2.3.2+FI-WARE+Architecture+Official+deliverable.zip Note that the FI-WARE Architecture specification is public and its contents become part of the several FI-WARE GE Open Specifications, therefore you can download this file without logging in your FusionForge account. We haven't delivered it earlier to make sure that it was aligned with the contents of FI-WARE GE Open Specifications that will be delivered along this week (some of them have already been delivered to you). The FI-WARE Architecture has beed produced conducting several peer-reviews and a final whole revision by myself, as chief architect, to ensure overall consistency. You will see that the description of the architecture of some GEs ended with a sections that provides the links to the Detailed Specifications. This doesn't happen in all the cases and will be fixed in subsequent releases of the deliverable. However, we thought it was not critical to add them here because you are going to receive them separately. Note that specifications are still provided together with an interim Legal Notice. This is because the Legal Notice accompanying specifications is still going through a final review by legal representatives of the different partners. This process is about to finish, so we don't expect major issues regarding usage by UC projects within the FI-PPP or impact in the launch of the FI-WARE Open Innovation Lab. Furthermore, differences between the final and interim Legal Notices is rather minor. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us in case you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.3.2 FI-WARE Architecture - Security v5_with_comments.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3168783 bytes Desc: D.2.3.2 FI-WARE Architecture - Security v5_with_comments.docx URL: From alexandre.boeglin at inria.fr Mon May 27 12:20:35 2013 From: alexandre.boeglin at inria.fr (Alexandre Boeglin) Date: Mon, 27 May 2013 12:20:35 +0200 (CEST) Subject: [Fiware-security] [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture In-Reply-To: <17822_1369645218_51A3209F_17822_5109_7_ac2b02aa-0439-4d38-9840-4c72ed652341@THSONEA01HUB06P.one.grp> Message-ID: <1438893548.3574714.1369650035754.JavaMail.root@inria.fr> Hello, For the AndroidFlowMonitoring and MalwareDetectionService parts, the "Copyright" and "Legal Notice" are present in the wiki pages, and they have been for at least a month. Also, there has recently been some changes to these pages on the public wiki, to address comments made during the OpenSpec review (which includes the Architecture Description). And Finally could I get some clarifications about the "Legal Notice" ? A few days ago we got another mail telling us that the licenses were ready and there were two to choose from? P.S.: should'n the "Copyright" section of the Security Monitoring section include every participant as well? Best regards, Alexandre ----- Mail original ----- > De: "BISSON Pascal" > ?: "Juanjo Hierro" > Cc: fiware-security at lists.fi-ware.eu > Envoy?: Lundi 27 Mai 2013 11:00:02 > Objet: Re: [Fiware-security] [Fiware-wpl] Fwd: Submission of FI-WARE > Deliverable D.2.3.2 - FI-WARE Architecture > Dear All, > I?m forwarding you this email I got from Juanjo. See comments he did > provide on architecture specifications and especially ours (aka > Security). > Please notice they have incorporated in the architecture deliverable > he did already submit (as stated in his email). > But now we have to perform the necessary adjustments on the wiki for > them to be included in the Open Specs deliverable. > Being said we are already beyond schedule please update the wiki asap > so that we can generate and deliver the open specs. > As usual drop me and/Daniel an email once changes have been > performed. > Counting on your promptness to get this demand addressed > Thanks, > Regards > Pascal > De : fiware-wpl-bounces at lists.fi-ware.eu > [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo > Hierro > Envoy? : lundi 27 mai 2013 07:45 > ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > Objet : [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - > FI-WARE Architecture > Hi, > Please find attached the final official submission of the FI-WARE > Architecture deliverable. > While carrying out a very final cross-chapter revision, I have > identified the need to achieve a better consistency between names of > sections in the different chapters and even within chapters: > * There were some cases where the section titled "Basic Concepts" > within the Architecture Description of a given GE was titled as > "Main Concepts". I have changed this wherever I found it > * There were some cases where the "Main Interactions" section within > the Architecture Description of a given GE was titled as "Main > Operations". I have changed this wherever I found it. > There were GEs in the Security chapter for which the sections related > to Copyright and Legal Notices were missing. This also happens > regarding Basic Design Principles. Please add these sections asap. > Despite I asked for the names of the companies to be added manually, > I got no response. > It would be nice that you perform a general review of the structure > in your chapters and double-check alignment with the standard > structure template we defined. I fixed a lot of the issues but this > would be only reflected in the final deliverable so I have produced > and already sent to you a version with comments that highlighted the > changes you should introduce in the public wiki ASAP (note that this > document is marked as private). For your convenience, here it goes > the structure of sections that should have been adopted: > 1. General Architecture Description of a Chapter: > 1. Introduction > 2. Architecture Overview > 3. > 4. Architecture Description of GEs > 5. Interface to other chapters > 6. References > 2. > Architecture Description of a given GE: > 1. Copyright > 2. Legal Notice > 3. Overview (Target usage should be inside) > 4. Basic Concepts > 5. Architecture (recommended but optional, sometimes you > have put this before "Basic concepts" but it would be nice to keep > consistency and place it after) > 6. Main Interactions > 7. Basic Design Principles > 8. Detailed Open Specifications (which should contain the links to > the rest of Open Specifications) > 9. References > There were also A LOT of inconsistencies regarding level of headings. > As an example, there were many chapters where there wasn't a second > level heading. This was revealed thanks to the automated generation > process and should be fixed in the wiki asap to avoid wrong > generation next times. > I carried out a final spelling checking to all chapters finding also > many typos. > I have to confess that I got astonished when I saw still those kind > of issues in a so late stage of the peer-review ... Didn't nobody > notice that? Despite we incurred in a delay, I have now found that > it was worth carrying out this final review. Without giving names, > when I have asked "how can we still find this issues?" in the draft > I had just reviewed, I got the response "honestly, I believe some > people hasn't read the contents in that detail". We honestly have to > reconsider how we are carrying out our peer-review processes. > I have also carried out several changes to improve overall > readability. > The detailed Open Specifications where not included in all cases, > even within the same chapter, so I have had to put a note to the EC > and reviewers explaining that we had decided to keep the inclusion > by those GEs that decided to include it, because we will adopt that > convention finally. Therefore, please do so. > In addition, I also found that the copyright notice in many of the > cases was only for 2012. This maybe interpreted by the reviewers as > "no single line has been touched by the owners this year" when > clearly this doesn't apply. Please fix those Copyright Notices where > you have to write 2012-2013 (in the case of new GEs, 2013) > Last but not least, there are a number of things that I have detected > about which we have to reach a final agreement and adopt a > convention across all chapters: > * Titles, numbering and format (i.e., centered or not) of figures. I > believe that we proposed a convention, and asked to avoid using of > figure numbers, but apparently hasn't been followed consistently > * Architecture section within a GE Architecture Description > * Style for references > We should address all of them once we finish with the most urgent > things we currently have on our plate, but have them ready at the > time we will start disseminating this among the wider community of > developers. > Please share with members of your respective chapters. > Best regards, -- Juanjo > ------------- Product Development and Innovation (PDI) - Telefonica > Digital website: www.tid.es email: jhierro at tid.es twitter: > twitter.com/JuanjoHierro FI-WARE (European Future Internet Core > Platform) Coordinator and Chief Architect You can follow FI-WARE at: > website: http://www.fi-ware.eu facebook: > http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: > http://twitter.com/FIware linkedIn: > http://www.linkedin.com/groups/FIWARE-4239932 > -------- Original Message -------- > Subject: > Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture > Date: > Mon, 27 May 2013 07:32:02 +0200 > From: > Juanjo Hierro > To: > Arian.ZWEGERS at ec.europa.eu , > Ragnar.Bergstrom at ec.europa.eu , dgr at whitestein.com , > msli at icfocus.co.uk , renaud.difrancesco at eu.sony.com , > irena.pavlova at isoft-technology.com > CC: > INFSO-ICT-285248 at ec.europa.eu , Vanessa.VANHUMBEECK at ec.europa.eu , > mcp at tid.es , "jhierro >> \"Juan J. Hierro\"" > Dear all, > This is the official submission of deliverable D.2.3.2 FI-WARE > Architecture. To ease review of its contents, separate files have > been produced for the different chapters that made up the whole > document. All of these files can be extracted from the .zip file you > can download from the following URL: > https://forge.fi-ware.eu/docman/view.php/7/2468/D.2.3.2+FI-WARE+Architecture+Official+deliverable.zip > Note that the FI-WARE Architecture specification is public and its > contents become part of the several FI-WARE GE Open Specifications, > therefore you can download this file without logging in your > FusionForge account. We haven't delivered it earlier to make sure > that it was aligned with the contents of FI-WARE GE Open > Specifications that will be delivered along this week (some of them > have already been delivered to you). > The FI-WARE Architecture has beed produced conducting several > peer-reviews and a final whole revision by myself, as chief > architect, to ensure overall consistency. > You will see that the description of the architecture of some GEs > ended with a sections that provides the links to the Detailed > Specifications. This doesn't happen in all the cases and will be > fixed in subsequent releases of the deliverable. However, we thought > it was not critical to add them here because you are going to > receive them separately. > Note that specifications are still provided together with an interim > Legal Notice. This is because the Legal Notice accompanying > specifications is still going through a final review by legal > representatives of the different partners. This process is about to > finish, so we don't expect major issues regarding usage by UC > projects within the FI-PPP or impact in the launch of the FI-WARE > Open Innovation Lab. Furthermore, differences between the final and > interim Legal Notices is rather minor. > As you know, the FI-WARE GE Open Specifications are constantly > updated on the FI-WARE public wiki. You can refer to contents of the > public wiki for the most up-to-date contents of public documentation > associated to the FI-WARE project. > Don't hesitate to contact us in case you have any question. > Best regards, > -- Juanjo Hierro > ------------- Product Development and Innovation (PDI) - Telefonica > Digital website: www.tid.es email: jhierro at tid.es twitter: > twitter.com/JuanjoHierro FI-WARE (European Future Internet Core > Platform) Coordinator and Chief Architect You can follow FI-WARE at: > website: http://www.fi-ware.eu facebook: > http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: > http://twitter.com/FIware linkedIn: > http://www.linkedin.com/groups/FIWARE-4239932 > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra pol?tica de env?o y recepci?n de correo > electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-security mailing list > Fiware-security at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue May 28 07:38:39 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 28 May 2013 07:38:39 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Message-ID: <12788_1369719522_51A442E2_12788_8708_1_8ff59e26-19d9-4d95-867a-4e5933bb7af9@THSONEA01HUB05P.one.grp> Dear Colleagues, I'm forwarding you this email from Juanjo. As you can see there are still issue preventing us to deliver D.8.1.2 Open Specifications. So please fix them asap for us to deliver. 1. Issue about the copyright holder sections. Thought it could have already been fixed with the email I sent you already. So please ALL and add it if missing. 2. At NSN/DT please add the API specifications associated to the Identity Management GE. If you can't get it added please tell us !. Please notice in that case that TID will include a note to the EC clarifying they have not been made publicly available. Counting on your prompt action to fix these remaining issues that prevent us to deliver. ! Don't forget also that from now today till Thursday EOB, Daniel will take over from me and replace me so please keep him posted since he would need you to fix the issues first to re-generate D8.1.2 Open Specs and the other manuals/guides fro which we are still waiting from final green light from TID (so please stay tuned and prompt to react, counting on you all). Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : mardi 28 mai 2013 07:00 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) New one submitted (Cloud). So we have already delivered Apps, Data and Cloud. We expect to deliver all by EOB today, most probably IoT and I2ND along this morning. Regardig the Security specs, note that you should fix the issue about copyrights holder sections and, most importantly, the REST API specifications associated to the Identity Management GE should be part of it, otherwise we will need to include a note to the EC clarifying they have not been made publicly available. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Date: Tue, 28 May 2013 06:51:30 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom at ec.europa.eu, dgr at whitestein.com, msli at icfocus.co.uk, renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com CC: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, Alex Glikson , "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of D.4.1.2 Open Specifications (WP4 - Cloud Chapter). You can download the corresponding file from the following link: * https://forge.fi-ware.eu/docman/view.php/7/2484/D.4.1.2+FI-WARE+GE+Open+Specifications+-+Cloud+vfinal.docx Note that the FI-WARE GE Open Specifications are public, therefore you can download the first of the files without logging in FusionForge. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us if you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From cyril.dangerville at thalesgroup.com Tue May 28 18:39:28 2013 From: cyril.dangerville at thalesgroup.com (DANGERVILLE Cyril) Date: Tue, 28 May 2013 18:39:28 +0200 Subject: [Fiware-security] [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture In-Reply-To: <17822_1369645218_51A3209F_17822_5109_7_ac2b02aa-0439-4d38-9840-4c72ed652341@THSONEA01HUB06P.one.grp> References: <51A2EFD2.6040106@tid.es> <51A2F2E5.3020101@tid.es> <17822_1369645218_51A3209F_17822_5109_7_ac2b02aa-0439-4d38-9840-4c72ed652341@THSONEA01HUB06P.one.grp> Message-ID: <10718_1369759182_51A4DDCC_10718_2456_1_7177f1d1-85a3-4b5d-9c18-c276090c0b57@THSONEA01HUB02P.one.grp> Hello, I have updated the wiki page based on the proposed changes on 7. Access Control, except for one in 7.4.1 and one in 7.4.2 (see my comments in the doc): https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Access_Control_Generic_Enabler regards, CD De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoy? : lundi 27 mai 2013 11:00 ? : Juanjo Hierro Cc : fiware-security at lists.fi-ware.eu Objet : Re: [Fiware-security] [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Importance : Haute Dear All, I'm forwarding you this email I got from Juanjo. See comments he did provide on architecture specifications and especially ours (aka Security). Please notice they have incorporated in the architecture deliverable he did already submit (as stated in his email). But now we have to perform the necessary adjustments on the wiki for them to be included in the Open Specs deliverable. Being said we are already beyond schedule please update the wiki asap so that we can generate and deliver the open specs. As usual drop me and/Daniel an email once changes have been performed. Counting on your promptness to get this demand addressed Thanks, Regards Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoy? : lundi 27 mai 2013 07:45 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Hi, Please find attached the final official submission of the FI-WARE Architecture deliverable. While carrying out a very final cross-chapter revision, I have identified the need to achieve a better consistency between names of sections in the different chapters and even within chapters: * There were some cases where the section titled "Basic Concepts" within the Architecture Description of a given GE was titled as "Main Concepts". I have changed this wherever I found it * There were some cases where the "Main Interactions" section within the Architecture Description of a given GE was titled as "Main Operations". I have changed this wherever I found it. There were GEs in the Security chapter for which the sections related to Copyright and Legal Notices were missing. This also happens regarding Basic Design Principles. Please add these sections asap. Despite I asked for the names of the companies to be added manually, I got no response. It would be nice that you perform a general review of the structure in your chapters and double-check alignment with the standard structure template we defined. I fixed a lot of the issues but this would be only reflected in the final deliverable so I have produced and already sent to you a version with comments that highlighted the changes you should introduce in the public wiki ASAP (note that this document is marked as private). For your convenience, here it goes the structure of sections that should have been adopted: 1. General Architecture Description of a Chapter: * Introduction * Architecture Overview * * Architecture Description of GEs * Interface to other chapters * References 1. Architecture Description of a given GE: * Copyright * Legal Notice * Overview (Target usage should be inside) * Basic Concepts * Architecture (recommended but optional, sometimes you have put this before "Basic concepts" but it would be nice to keep consistency and place it after) * Main Interactions * Basic Design Principles * Detailed Open Specifications (which should contain the links to the rest of Open Specifications) * References There were also A LOT of inconsistencies regarding level of headings. As an example, there were many chapters where there wasn't a second level heading. This was revealed thanks to the automated generation process and should be fixed in the wiki asap to avoid wrong generation next times. I carried out a final spelling checking to all chapters finding also many typos. I have to confess that I got astonished when I saw still those kind of issues in a so late stage of the peer-review ... Didn't nobody notice that? Despite we incurred in a delay, I have now found that it was worth carrying out this final review. Without giving names, when I have asked "how can we still find this issues?" in the draft I had just reviewed, I got the response "honestly, I believe some people hasn't read the contents in that detail". We honestly have to reconsider how we are carrying out our peer-review processes. I have also carried out several changes to improve overall readability. The detailed Open Specifications where not included in all cases, even within the same chapter, so I have had to put a note to the EC and reviewers explaining that we had decided to keep the inclusion by those GEs that decided to include it, because we will adopt that convention finally. Therefore, please do so. In addition, I also found that the copyright notice in many of the cases was only for 2012. This maybe interpreted by the reviewers as "no single line has been touched by the owners this year" when clearly this doesn't apply. Please fix those Copyright Notices where you have to write 2012-2013 (in the case of new GEs, 2013) Last but not least, there are a number of things that I have detected about which we have to reach a final agreement and adopt a convention across all chapters: * Titles, numbering and format (i.e., centered or not) of figures. I believe that we proposed a convention, and asked to avoid using of figure numbers, but apparently hasn't been followed consistently * Architecture section within a GE Architecture Description * Style for references We should address all of them once we finish with the most urgent things we currently have on our plate, but have them ready at the time we will start disseminating this among the wider community of developers. Please share with members of your respective chapters. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 -------- Original Message -------- Subject: Submission of FI-WARE Deliverable D.2.3.2 - FI-WARE Architecture Date: Mon, 27 May 2013 07:32:02 +0200 From: Juanjo Hierro To: Arian.ZWEGERS at ec.europa.eu , Ragnar.Bergstrom at ec.europa.eu, dgr at whitestein.com, msli at icfocus.co.uk, renaud.difrancesco at eu.sony.com, irena.pavlova at isoft-technology.com CC: INFSO-ICT-285248 at ec.europa.eu, Vanessa.VANHUMBEECK at ec.europa.eu, mcp at tid.es, "jhierro >> \"Juan J. Hierro\"" Dear all, This is the official submission of deliverable D.2.3.2 FI-WARE Architecture. To ease review of its contents, separate files have been produced for the different chapters that made up the whole document. All of these files can be extracted from the .zip file you can download from the following URL: https://forge.fi-ware.eu/docman/view.php/7/2468/D.2.3.2+FI-WARE+Architecture+Official+deliverable.zip Note that the FI-WARE Architecture specification is public and its contents become part of the several FI-WARE GE Open Specifications, therefore you can download this file without logging in your FusionForge account. We haven't delivered it earlier to make sure that it was aligned with the contents of FI-WARE GE Open Specifications that will be delivered along this week (some of them have already been delivered to you). The FI-WARE Architecture has beed produced conducting several peer-reviews and a final whole revision by myself, as chief architect, to ensure overall consistency. You will see that the description of the architecture of some GEs ended with a sections that provides the links to the Detailed Specifications. This doesn't happen in all the cases and will be fixed in subsequent releases of the deliverable. However, we thought it was not critical to add them here because you are going to receive them separately. Note that specifications are still provided together with an interim Legal Notice. This is because the Legal Notice accompanying specifications is still going through a final review by legal representatives of the different partners. This process is about to finish, so we don't expect major issues regarding usage by UC projects within the FI-PPP or impact in the launch of the FI-WARE Open Innovation Lab. Furthermore, differences between the final and interim Legal Notices is rather minor. As you know, the FI-WARE GE Open Specifications are constantly updated on the FI-WARE public wiki. You can refer to contents of the public wiki for the most up-to-date contents of public documentation associated to the FI-WARE project. Don't hesitate to contact us in case you have any question. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.3.2 FI-WARE Architecture - Security v5_with_comments_cda.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3139026 bytes Desc: D.2.3.2 FI-WARE Architecture - Security v5_with_comments_cda.docx URL: From daniel.gidoin at thalesgroup.com Tue May 28 19:32:59 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Tue, 28 May 2013 19:32:59 +0200 Subject: [Fiware-security] FI-WARE: D8.1.2 FI-WARE Open Specification delivered Message-ID: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Tue May 28 20:26:47 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Tue, 28 May 2013 20:26:47 +0200 Subject: [Fiware-security] FI-WARE: D8.1.2 FI-WARE Open Specification delivered In-Reply-To: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> References: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> Message-ID: <51A4F6E7.6040200@tid.es> Hi Daniel, I would like to confirm that inclusion of the API specification by DT would mean that those specifications can be made publicly available. Looking at the message from Wolfgang, I don't see it explictly mentioned. Therefore, don't know whether they indeed are asking for delivering the specification but only with private access. Please clarify. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 29 11:04:07 2013 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 29 May 2013 11:04:07 +0200 Subject: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter In-Reply-To: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> References: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> Message-ID: <51A5C487.4030303@tid.es> Daniel, Several questions: * I DO NEED that you pass me the .doc/.docx, not the .pdf. We are performing a number of final formatting changes that we need to carry out. * Are the contents that are common with the FI-WARE Architecture aligned ? Please confirm. I have found that at least some of the changes on the description of the Access Control GE that were proposed in the FI-WARE Architecture deliverable have been incorporated but just wanted to double-check taking advantage that I needed to send you this email asking for the .doc/.docx files * I still don't see the specifications of the IdM GE API. We will submit the deliverable but we will include the note that the specifications of these APIs are not included and we are working with DT and NSN to clarify the picture in this respect. We will make it also clear in the note that we have already made involved partners clear that, following the contract, APIs and protocols linked to interfaces associated to FI-WARE GEs have to be public and royalty-free. Therefore, we are waiting for a clear response by them on the matter. Just to let you know, unless there will be any recent news and DT/NSN go for making those APIs public and royalty-free. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed May 29 13:26:48 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 29 May 2013 13:26:48 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Platform for FI-WARE Webinars Message-ID: <30816_1369826813_51A5E5FD_30816_10968_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E6BE71D3@THSONEA01CMS04P.one.grp> FYI -----Message d'origine----- De?: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Davide Dalle Carbonare Envoy??: mardi 28 mai 2013 13:52 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc?: abel at dit.upm.es; Juan Quemada Vives Objet?: [Fiware-wpl] Platform for FI-WARE Webinars Dear parters, in order to provide FI-WARE webinars I notify you about the possibility of using the MeshMe.tv platform made available by UPM. To understand how this platform works and how to use it, It's possible to attend to a dedicated presentation on these dates: 1) Wednesday 5th of June from 14h to 15h 2) Thursday 6th of June from 14h to 15h To facilitate the organization of these sessions, please, confirm your attendance by sending a message to both: - Juan Quemada Vives - Abel Carril To enter the webinar session click on: http://www.mashme.tv/M/2qvRiO?mode=1 Requirements for accessing the platform: A browser which supports HTML5 must be used. This includes the last versions of Chrome, Firefox, Opera, Internet Explorer 9 or 10, etc. @WPLs, please, circulate this message in your WP mailing lists in order to involve all the potential users. Thank you and Kind Regards, Davide _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-wpl From pascal.bisson at thalesgroup.com Wed May 29 13:41:00 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 29 May 2013 13:41:00 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Webinars scheduled for this week - please, pay attention Message-ID: <30816_1369827662_51A5E94E_30816_11215_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E6BE7234@THSONEA01CMS04P.one.grp> FYI. De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : mardi 28 mai 2013 17:58 ? : fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Webinars scheduled for this week - please, pay attention Dear Partners, Please, have a look at the webinars scheduled for this week. Please, be aware of a number of things: 1. (SECURITY) Data Handling - please, clarify whether it is CEST time 2. (SECURITY) DB Anonimyzer - please, follow the same time format as other partners. a. I see it advertised for 07.June, but not the one scheduled for 31st.May 3. (ALL) - Don't forget to: a. Advertise your webinar by sending at least a twit to . at FIWARE (I've seen some already sent - GOOD!!) b. Put a hashtag which is not in use, check it beforehand. You can easily do it by adding the FIWARE prefix to your enabler acronym. c. Write the logistic details for accessing your session, don't forget to add a presentation, which can be downloaded and followed by your audience. d. When, you have finished, please, mark the date with "-done," if possible annotate the number of attendees. Please be aware of the dot before @FIWARE, . at FIWARE - when you start your twit this way. Well, if anything, please, let me know. Kind regards, Manuel [cid:image001.png at 01CE5BCB.F83848D0] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 37313 bytes Desc: image001.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From daniel.gidoin at thalesgroup.com Wed May 29 14:16:10 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 29 May 2013 14:16:10 +0200 Subject: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter In-Reply-To: <51A5C487.4030303@tid.es> References: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> <51A5C487.4030303@tid.es> Message-ID: <17329_1369829791_51A5F19D_17329_8543_1_69293a2e-40d1-4f2d-beca-a26bc98c8f85@THSONEA01HUB05P.one.grp> Dear Juanjo, Concerning your question 2, I confirm that FI-WARE architecture is now aligned. We have taken into account yours remark in the Word Document (see Document joined) excepted in the sections 7.4.1 and 7.4.2 (see comments pages and 82). The page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Access_Control_Generic_Enabler is also updated. Best regards Daniel De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mercredi 29 mai 2013 11:04 ? : GIDOIN Daniel Cc : Miguel Carrillo; BISSON Pascal; Fiware-security at lists.fi-ware.eu Objet : Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Daniel, Several questions: * I DO NEED that you pass me the .doc/.docx, not the .pdf. We are performing a number of final formatting changes that we need to carry out. * Are the contents that are common with the FI-WARE Architecture aligned ? Please confirm. I have found that at least some of the changes on the description of the Access Control GE that were proposed in the FI-WARE Architecture deliverable have been incorporated but just wanted to double-check taking advantage that I needed to send you this email asking for the .doc/.docx files * I still don't see the specifications of the IdM GE API. We will submit the deliverable but we will include the note that the specifications of these APIs are not included and we are working with DT and NSN to clarify the picture in this respect. We will make it also clear in the note that we have already made involved partners clear that, following the contract, APIs and protocols linked to interfaces associated to FI-WARE GEs have to be public and royalty-free. Therefore, we are waiting for a clear response by them on the matter. Just to let you know, unless there will be any recent news and DT/NSN go for making those APIs public and royalty-free. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D 2 3 2 FI-WARE Architecture - Security v5_with_comments_cda.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 3155253 bytes Desc: D 2 3 2 FI-WARE Architecture - Security v5_with_comments_cda.docx URL: From daniel.gidoin at thalesgroup.com Wed May 29 15:57:00 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 29 May 2013 15:57:00 +0200 Subject: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter In-Reply-To: <51A5C487.4030303@tid.es> References: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> <51A5C487.4030303@tid.es> Message-ID: <17329_1369835824_51A60930_17329_12513_1_14774f0c-aeae-40a1-a748-9575e9e508d6@THSONEA01HUB06P.one.grp> Juanjo, I apologize, Concerning your question 1, I delivered the Word version at the same time of the pdf version: https://forge.fi-ware.eu/docman/view.php/7/2503/D812_WP8_v3_generated.docx Best regards Daniel De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mercredi 29 mai 2013 11:04 ? : GIDOIN Daniel Cc : Miguel Carrillo; BISSON Pascal; Fiware-security at lists.fi-ware.eu Objet : Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Daniel, Several questions: * I DO NEED that you pass me the .doc/.docx, not the .pdf. We are performing a number of final formatting changes that we need to carry out. * Are the contents that are common with the FI-WARE Architecture aligned ? Please confirm. I have found that at least some of the changes on the description of the Access Control GE that were proposed in the FI-WARE Architecture deliverable have been incorporated but just wanted to double-check taking advantage that I needed to send you this email asking for the .doc/.docx files * I still don't see the specifications of the IdM GE API. We will submit the deliverable but we will include the note that the specifications of these APIs are not included and we are working with DT and NSN to clarify the picture in this respect. We will make it also clear in the note that we have already made involved partners clear that, following the contract, APIs and protocols linked to interfaces associated to FI-WARE GEs have to be public and royalty-free. Therefore, we are waiting for a clear response by them on the matter. Just to let you know, unless there will be any recent news and DT/NSN go for making those APIs public and royalty-free. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed May 29 16:09:41 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Wed, 29 May 2013 14:09:41 +0000 Subject: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter In-Reply-To: <17329_1369835824_51A60930_17329_12513_1_14774f0c-aeae-40a1-a748-9575e9e508d6@THSONEA01HUB06P.one.grp> References: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> <51A5C487.4030303@tid.es> <17329_1369835824_51A60930_17329_12513_1_14774f0c-aeae-40a1-a748-9575e9e508d6@THSONEA01HUB06P.one.grp> Message-ID: Ok. I'll carry out final check and formating and deliver this afternoon (together with note on IdM APIs) Cheers Enviado desde mi iPad El 29/05/2013, a las 15:57, "GIDOIN Daniel" > escribi?: Juanjo, I apologize, Concerning your question 1, I delivered the Word version at the same time of the pdf version: https://forge.fi-ware.eu/docman/view.php/7/2503/D812_WP8_v3_generated.docx Best regards Daniel De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mercredi 29 mai 2013 11:04 ? : GIDOIN Daniel Cc : Miguel Carrillo; BISSON Pascal; Fiware-security at lists.fi-ware.eu Objet : Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Daniel, Several questions: * I DO NEED that you pass me the .doc/.docx, not the .pdf. We are performing a number of final formatting changes that we need to carry out. * Are the contents that are common with the FI-WARE Architecture aligned ? Please confirm. I have found that at least some of the changes on the description of the Access Control GE that were proposed in the FI-WARE Architecture deliverable have been incorporated but just wanted to double-check taking advantage that I needed to send you this email asking for the .doc/.docx files * I still don't see the specifications of the IdM GE API. We will submit the deliverable but we will include the note that the specifications of these APIs are not included and we are working with DT and NSN to clarify the picture in this respect. We will make it also clear in the note that we have already made involved partners clear that, following the contract, APIs and protocols linked to interfaces associated to FI-WARE GEs have to be public and royalty-free. Therefore, we are waiting for a clear response by them on the matter. Just to let you know, unless there will be any recent news and DT/NSN go for making those APIs public and royalty-free. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I?m still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary ?. ? https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf ? GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Wolfgang.Steigerwald at telekom.de Wed May 29 16:23:09 2013 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Wed, 29 May 2013 16:23:09 +0200 Subject: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter In-Reply-To: <51A5C487.4030303@tid.es> References: <10718_1369762382_51A4EA4E_10718_3880_1_dc1e8e3e-63eb-4147-8976-fc0e6d808f78@THSONEA01HUB05P.one.grp> <51A5C487.4030303@tid.es> Message-ID: Hello Juanjo, find the find attached the API description as docx file. Best regards Wolfgang Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Mittwoch, 29. Mai 2013 11:04 An: GIDOIN Daniel Cc: Fiware-security at lists.fi-ware.eu Betreff: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Daniel, Several questions: * I DO NEED that you pass me the .doc/.docx, not the .pdf. We are performing a number of final formatting changes that we need to carry out. * Are the contents that are common with the FI-WARE Architecture aligned ? Please confirm. I have found that at least some of the changes on the description of the Access Control GE that were proposed in the FI-WARE Architecture deliverable have been incorporated but just wanted to double-check taking advantage that I needed to send you this email asking for the .doc/.docx files * I still don't see the specifications of the IdM GE API. We will submit the deliverable but we will include the note that the specifications of these APIs are not included and we are working with DT and NSN to clarify the picture in this respect. We will make it also clear in the note that we have already made involved partners clear that, following the contract, APIs and protocols linked to interfaces associated to FI-WARE GEs have to be public and royalty-free. Therefore, we are waiting for a clear response by them on the matter. Just to let you know, unless there will be any recent news and DT/NSN go for making those APIs public and royalty-free. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GCP API documentation_v0-3.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 205781 bytes Desc: GCP API documentation_v0-3.docx URL: From francesco.di.cerbo at sap.com Wed May 29 16:47:50 2013 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Wed, 29 May 2013 14:47:50 +0000 Subject: [Fiware-security] TR: [Fiware-wpl] Webinars scheduled for this week - please, pay attention In-Reply-To: <30816_1369827662_51A5E94E_30816_11215_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E6BE7234@THSONEA01CMS04P.one.grp> References: <30816_1369827662_51A5E94E_30816_11215_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E6BE7234@THSONEA01CMS04P.one.grp> Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E6070AE0B0@DEWDFEMB18B.global.corp.sap> Hello Pascal, Daniel, Manuel, The points raised for Data Handling and DB Anonymizer have been addressed. Best, francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mercredi 29 mai 2013 13:41 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] Webinars scheduled for this week - please, pay attention Importance: High FYI. De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : mardi 28 mai 2013 17:58 ? : fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Webinars scheduled for this week - please, pay attention Dear Partners, Please, have a look at the webinars scheduled for this week. Please, be aware of a number of things: 1. (SECURITY) Data Handling - please, clarify whether it is CEST time 2. (SECURITY) DB Anonimyzer - please, follow the same time format as other partners. a. I see it advertised for 07.June, but not the one scheduled for 31st.May 3. (ALL) - Don't forget to: a. Advertise your webinar by sending at least a twit to . at FIWARE (I've seen some already sent - GOOD!!) b. Put a hashtag which is not in use, check it beforehand. You can easily do it by adding the FIWARE prefix to your enabler acronym. c. Write the logistic details for accessing your session, don't forget to add a presentation, which can be downloaded and followed by your audience. d. When, you have finished, please, mark the date with "-done," if possible annotate the number of attendees. Please be aware of the dot before @FIWARE, . at FIWARE - when you start your twit this way. Well, if anything, please, let me know. Kind regards, Manuel [cid:image001.png at 01CE5C8B.170B5030] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 37313 bytes Desc: image001.png URL: From pascal.bisson at thalesgroup.com Wed May 29 16:50:20 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 29 May 2013 16:50:20 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Webinars scheduled for this week - please, pay attention In-Reply-To: <6D11E010ED8E5B4B9D42045AC71F37E6070AE0B0@DEWDFEMB18B.global.corp.sap> References: <30816_1369827662_51A5E94E_30816_11215_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E6BE7234@THSONEA01CMS04P.one.grp> <6D11E010ED8E5B4B9D42045AC71F37E6070AE0B0@DEWDFEMB18B.global.corp.sap> Message-ID: <17329_1369839032_51A615B8_17329_14672_1_e58ea59e-94a0-4966-8a69-0b894338e81f@THSONEA01HUB01P.one.grp> Excellent, Thanks ! De : DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] Envoy? : mercredi 29 mai 2013 16:48 ? : BISSON Pascal; GIDOIN Daniel; MANUEL ESCRICHE VICENTE (mev at tid.es) Cc : fiware-security at lists.fi-ware.eu; TRABELSI, Slim Objet : RE: [Fiware-security] TR: [Fiware-wpl] Webinars scheduled for this week - please, pay attention Hello Pascal, Daniel, Manuel, The points raised for Data Handling and DB Anonymizer have been addressed. Best, francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: mercredi 29 mai 2013 13:41 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] Webinars scheduled for this week - please, pay attention Importance: High FYI. De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : mardi 28 mai 2013 17:58 ? : fiware-wpl at lists.fi-ware.eu Objet : [Fiware-wpl] Webinars scheduled for this week - please, pay attention Dear Partners, Please, have a look at the webinars scheduled for this week. Please, be aware of a number of things: 1. (SECURITY) Data Handling - please, clarify whether it is CEST time 2. (SECURITY) DB Anonimyzer - please, follow the same time format as other partners. a. I see it advertised for 07.June, but not the one scheduled for 31st.May 3. (ALL) - Don't forget to: a. Advertise your webinar by sending at least a twit to . at FIWARE (I've seen some already sent - GOOD!!) b. Put a hashtag which is not in use, check it beforehand. You can easily do it by adding the FIWARE prefix to your enabler acronym. c. Write the logistic details for accessing your session, don't forget to add a presentation, which can be downloaded and followed by your audience. d. When, you have finished, please, mark the date with "-done," if possible annotate the number of attendees. Please be aware of the dot before @FIWARE, . at FIWARE - when you start your twit this way. Well, if anything, please, let me know. Kind regards, Manuel [cid:image001.png at 01CE5C8C.9AEAA990] ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 37313 bytes Desc: image001.png URL: From FRP at zurich.ibm.com Wed May 29 17:07:25 2013 From: FRP at zurich.ibm.com (Franz-Stefan Preiss) Date: Wed, 29 May 2013 17:07:25 +0200 Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki Message-ID: Dear Pascal, Dear All, do you know whether there exists a tool for converting .doc or .odt files to the FI-Ware Wiki syntax? Best Regards, Franz-Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From francesco.di.cerbo at sap.com Wed May 29 17:10:13 2013 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Wed, 29 May 2013 15:10:13 +0000 Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki In-Reply-To: References: Message-ID: <6D11E010ED8E5B4B9D42045AC71F37E6070AE0E7@DEWDFEMB18B.global.corp.sap> Hello Franz-Stephan, I used some time ago an Open/LibreOffice plugin that exports a document into a MediaWiki-formatted text. Don't have the URL with me, but I believe that I just found it on the OpenOffice website. Best, Francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Franz-Stefan Preiss Sent: mercredi 29 mai 2013 17:07 To: BISSON Pascal Cc: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki Dear Pascal, Dear All, do you know whether there exists a tool for converting .doc or .odt files to the FI-Ware Wiki syntax? Best Regards, Franz-Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed May 29 17:39:00 2013 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 29 May 2013 17:39:00 +0200 Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki In-Reply-To: <6D11E010ED8E5B4B9D42045AC71F37E6070AE0E7@DEWDFEMB18B.global.corp.sap> References: <6D11E010ED8E5B4B9D42045AC71F37E6070AE0E7@DEWDFEMB18B.global.corp.sap> Message-ID: <51A62114.5090901@tid.es> Hi all, Sorry to break into a private WP-list But I think that you may appreciate it. I do not use it myself but some colleagues tested it and told me that although not perfect (you get mistakes with lists and other tricky bits) , it does 90% of the work Take a look at this and see if it works for you. This is for microsoft Word, not Open Office if I am right. * http://en.wikipedia.org/wiki/Help:WordToWiki Best regards, Miguel El 29/05/2013 17:10, DI CERBO, Francesco escribi?: Hello Franz-Stephan, I used some time ago an Open/LibreOffice plugin that exports a document into a MediaWiki-formatted text. Don't have the URL with me, but I believe that I just found it on the OpenOffice website. Best, Francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Franz-Stefan Preiss Sent: mercredi 29 mai 2013 17:07 To: BISSON Pascal Cc: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki Dear Pascal, Dear All, do you know whether there exists a tool for converting .doc or .odt files to the FI-Ware Wiki syntax? Best Regards, Franz-Stefan _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From FRP at zurich.ibm.com Wed May 29 18:21:03 2013 From: FRP at zurich.ibm.com (Franz-Stefan Preiss) Date: Wed, 29 May 2013 18:21:03 +0200 Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki In-Reply-To: <51A62114.5090901@tid.es> References: <6D11E010ED8E5B4B9D42045AC71F37E6070AE0E7@DEWDFEMB18B.global.corp.sap> <51A62114.5090901@tid.es> Message-ID: Dear Francesco, Dear Miguel, awesome, thanks a lot, this was helpful. It even works for LibreOffice (which I'm using), and this out of the box: the extension called Wiki Publisher was already pre-installed in my LibreOffice installation. The extension has two export methods: 1) File -> Export -> choose ?MediaWiki (.txt)?-format 2) File -> Send -> To MediaWiki So far, I was able to create a .txt file from my content with option 1). Now I have to see how the quality of the exported .txt file actually is..... Best Regards, Franz-Stefan From: Miguel Carrillo To: fiware-security at lists.fi-ware.eu, Date: 05/29/2013 05:40 PM Subject: Re: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki Sent by: fiware-security-bounces at lists.fi-ware.eu Hi all, Sorry to break into a private WP-list But I think that you may appreciate it. I do not use it myself but some colleagues tested it and told me that although not perfect (you get mistakes with lists and other tricky bits) , it does 90% of the work Take a look at this and see if it works for you. This is for microsoft Word, not Open Office if I am right. http://en.wikipedia.org/wiki/Help:WordToWiki Best regards, Miguel El 29/05/2013 17:10, DI CERBO, Francesco escribi?: Hello Franz-Stephan, I used some time ago an Open/LibreOffice plugin that exports a document into a MediaWiki-formatted text. Don?t have the URL with me, but I believe that I just found it on the OpenOffice website. Best, Francesco From: fiware-security-bounces at lists.fi-ware.eu [ mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Franz-Stefan Preiss Sent: mercredi 29 mai 2013 17:07 To: BISSON Pascal Cc: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] Convert Doc/Odt to FI-Ware Wiki Dear Pascal, Dear All, do you know whether there exists a tool for converting .doc or .odt files to the FI-Ware Wiki syntax? Best Regards, Franz-Stefan _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu May 30 11:53:19 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 30 May 2013 11:53:19 +0200 Subject: [Fiware-security] TR: AW: Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Message-ID: <25082_1369907619_51A721A3_25082_805_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E6D6591F@THSONEA01CMS04P.one.grp> FYI De : BISSON Pascal Envoy? : jeudi 30 mai 2013 11:53 ? : Miguel Carrillo Cc : Juanjo Hierro; Wolfgang.Steigerwald at telekom.de; GIDOIN Daniel; BISSON Pascal Objet : RE: AW: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Importance : Haute Dear Miguel, Can't figure why this final check didn't come to us already since it was planned to be delivered to us on Monday (or Tuesday) and now you tell us you will look into it tomorrow ! Sorry but this is not good nor satisfactory even more that from my side I did work hard with the team on this and did delegate and instruct Daniel to address and deliver in order to submit our Chapter deliverables D8.2-5.2. So couldn't you have delegated as well the same way I did since also in the Infinity meeting ?. In any case I hope that we all share the fact that Security Chapter deliverables should be delivered at the latest by end of business this week ! For me it has higher priority compared to SoTa for which we did already deliver our contrib. and reviewed the one of SAP. So I can't really figure why it was not handled with the same priority as other Chapters since key to get delivered (even more we recovered and where early this week in a position to get those deliverables finalized and so submitted already!). Counting on you and Juanjo to address the way expected. Best regards, Pascal De : Miguel Carrillo [mailto:mcp at tid.es] Envoy? : jeudi 30 mai 2013 10:57 ? : BISSON Pascal Cc : Juanjo Hierro; Wolfgang.Steigerwald at telekom.de; GIDOIN Daniel Objet : Re: AW: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter As far as my part is concerned, I will look into it tomorrow (for the info of the ones in CC: I am in Zurich now in an Infinity plenary meeting) El 30/05/2013 9:36, BISSON Pascal escribi?: Hi Juanjo, Have you submitted our deliverable on Open specs ? Should be according to email below you sent us, but I can't find any email about your official submission. If done send us that email if not please urgently submit not to penalize us (our Chapter) too much. As for the manuals, Daniel is ready to get them delivered. Here he is just awaiting your green light. Once more we can't wait any longer (even more we haven't heard from you from days now on the manuals). So please provide instructions for the green light we are expecting to come and for Daniel to produce by today final versions that you could submit without any further delays. Let me remind you, that regarding INRIA we discussed already and came to an agreement so it should not be anymore an issue preventing us to deliver. So yes counting on you to hear from you and let Daniel further proceed with submissions of other deliverables (SW + manuals). Best Regards, Pascal De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mercredi 29 mai 2013 19:24 ? : Wolfgang.Steigerwald at telekom.de Cc : GIDOIN Daniel; BISSON Pascal; jhierro >> "Juan J. Hierro" Objet : Re: AW: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Dear Wolfgang, Note that, if I don't receive any response from you to my question about confirmation to make the APIs specs publicly available and public royalty-free by tonight, 23:00pm, I will proceed to submit the FI-WARE Security GE Open Specifications deliverable as follows: * FI-WARE GE Open Specifications document as delivered by Thales, indicating that this deliverable has been made publicly available. * IdM GE API specifications as delivered by you, only privately accessible from the docman system using FusionForge accounts for reviewers * A note explaining that: * it is unclear to us whether DT is delivering the IdM GE API specification as a public and royalty-free specification * we have formulated that question to DT and we are awaiting for an answer * we have informed DT that if a FI-WARE GE API is not delivered to be made public and royalty-free, we consider this an infringement of the contract, subject to any other interpretation by the EC * since we haven't received any response yet, we cannot release the IdM GE AP specifications publicly and we are providing it private, in case that reviewer wish to make progress reviewing the specs while a definitive answer from DT arrives I hope you understand. This is the best we can do and i believe it would not be fair to further delay submitting the deliverable for the rest of the chapter. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 29/05/13 16:59, Juanjo Hierro wrote: Sending me the .docx is nice, but I need, together with it, a explicit confirmation on your side that it is Ok to make the API specs publicly available and that the specification will be royalty-free, as established with the rest of FI-WARE GE APIs. In addition, it would be rather helpful if you can tell us what Legal Notice we should attach to it: * Any of the Interim Legal Notices used so far attached to specifications that were published, while a final Legal Notice was under elaboration: * (with implict patent license): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specifications_Legal_Notice (this was attached to the NGSI API, for example) * (with explicit patent license): http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Open_Specifications_Interim_Legal_Notice * The current draft of the revision of those Legal Notices (almost final in very last days of discussion among legal representatives, if not already closed) which are an evolution of the previous: * with implicit patent license: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(implicit_patents_license) * with explicit patent license: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Open_Specification_Legal_Notice_(essential_patents_license) I would recommend using any of the two current drafts of the almost-to-close revision, but it's actually up to you. Please let me know so that I can proceed with closing the deliverable. I was about to start working on it for its final delivery, but I will wait a couple of hours until I receive your response. Thanks and best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 29/05/13 16:23, Wolfgang.Steigerwald at telekom.de wrote: Hello Juanjo, find the find attached the API description as docx file. Best regards Wolfgang Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro Gesendet: Mittwoch, 29. Mai 2013 11:04 An: GIDOIN Daniel Cc: Fiware-security at lists.fi-ware.eu Betreff: [Fiware-security] Submission of D8.1.2 FI-WARE Open Specification for the Security chapter Daniel, Several questions: * I DO NEED that you pass me the .doc/.docx, not the .pdf. We are performing a number of final formatting changes that we need to carry out. * Are the contents that are common with the FI-WARE Architecture aligned ? Please confirm. I have found that at least some of the changes on the description of the Access Control GE that were proposed in the FI-WARE Architecture deliverable have been incorporated but just wanted to double-check taking advantage that I needed to send you this email asking for the .doc/.docx files * I still don't see the specifications of the IdM GE API. We will submit the deliverable but we will include the note that the specifications of these APIs are not included and we are working with DT and NSN to clarify the picture in this respect. We will make it also clear in the note that we have already made involved partners clear that, following the contract, APIs and protocols linked to interfaces associated to FI-WARE GEs have to be public and royalty-free. Therefore, we are waiting for a clear response by them on the matter. Just to let you know, unless there will be any recent news and DT/NSN go for making those APIs public and royalty-free. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/05/13 19:32, GIDOIN Daniel wrote: Dear Juanjo, I delivered D.8.1.2 Open Specifications: https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf Regarding the API specifications associated to the Identity Management GE from NSN/DT, I received the next mail from Wolfgang Steigerwald: " De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : mardi 28 mai 2013 15:37 ? : GIDOIN Daniel Objet : AW: FI-WARE URGENT API - Submission of FI-WARE Deliverable D.4.1.2 Open Specifications (WP4 - Cloud Chapter) Hello Daniel, I'm still ill and just have a look to my e-mails and restricted access. So find attached the API description. May be you can it put on the wiki and put a link in the specification. Best regards Wolfgang" So, I updated the pdf on the wiki (FI-WARE deliverables/Release 2/Security): https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf and I introduced a link in the Security Management API Open Specifications as: " General Identity Management Generic Enabler API Information Resources Summary .... * https://forge.fi-ware.eu/docman/view.php/7/2498/Identity+Management+GCP+API+Open+Specifications.pdf * GCP API Open Specifications" To see Pdf page 105 (https://forge.fi-ware.eu/docman/view.php/7/2504/D812_WP8_v3_generated.pdf) It is up to you to determine whether you will include a note to the EC clarifying this particular case. Concerning: Installation and Administration guide User and Programmers Guide Unit Testing Plan and Report I am ready but If we have not received your green light to deliver. Best regards Daniel 1, avenue Augustin Fresnel 91767 Palaiseau France ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Thu May 30 15:01:54 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 30 May 2013 15:01:54 +0200 Subject: [Fiware-security] FIWARE: D.8.3.2 Installation and Administration Guide delivered Message-ID: <25082_1369918944_51A74DE0_25082_8777_1_0b414de3-f6c6-462a-a2b3-459b7486d2f1@THSONEA01HUB05P.one.grp> Dear Juanjo, I delivered the D.8.3.2 FI-WARE Installation and Administration Guide: https://forge.fi-ware.eu/docman/view.php/7/2523/D832_WP8_v3_generated.docx The Deliverables cockpit updated: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/WP8_R2 Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Thu May 30 15:04:59 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 30 May 2013 15:04:59 +0200 Subject: [Fiware-security] FIWARE: D.8.4.2 User and Programmers Guide delivered Message-ID: <30816_1369919098_51A74E7A_30816_19723_1_a3c7e5fb-440b-4bc5-92f6-5d9bdd59e126@THSONEA01HUB06P.one.grp> Dear Juanjo, I delivered the D.8.4.2 FI-WARE User and Programmers Guide: https://forge.fi-ware.eu/docman/view.php/7/2525/D842_WP8_v3_generated.docx The Deliverables cockpit updated: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/WP8_R2 Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Thu May 30 15:07:00 2013 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 30 May 2013 15:07:00 +0200 Subject: [Fiware-security] FIWARE: D.8.5.2 Unit testing Plan and Report delivered Message-ID: <12314_1369919218_51A74EF2_12314_7575_1_f8088716-5e26-4579-8ea5-cc2185d14dd5@THSONEA01HUB05P.one.grp> Dear Juanjo, I delivered the D.8.5.2 FI-WARE Unit Testing Plan and Report: https://forge.fi-ware.eu/docman/view.php/7/2527/D852_WP8_v1_generated.docx The Deliverables cockpit updated: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/WP8_R2 Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu May 30 17:42:54 2013 From: jhierro at tid.es (JUAN JOSE HIERRO SUREDA) Date: Thu, 30 May 2013 15:42:54 +0000 Subject: [Fiware-security] FIWARE: D.8.5.2 Unit testing Plan and Report delivered In-Reply-To: <12314_1369919218_51A74EF2_12314_7575_1_f8088716-5e26-4579-8ea5-cc2185d14dd5@THSONEA01HUB05P.one.grp> References: <12314_1369919218_51A74EF2_12314_7575_1_f8088716-5e26-4579-8ea5-cc2185d14dd5@THSONEA01HUB05P.one.grp> Message-ID: Miguel is in charge of carrying out the final review and acceptance of all software and related documentation deliverables. Cheers, -- juanjo Enviado desde mi iPad El 30/05/2013, a las 15:07, "GIDOIN Daniel" > escribi?: Dear Juanjo, I delivered the D.8.5.2 FI-WARE Unit Testing Plan and Report: https://forge.fi-ware.eu/docman/view.php/7/2527/D852_WP8_v1_generated.docx The Deliverables cockpit updated: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/WP8_R2 Best regards Daniel ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri May 31 09:30:49 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 31 May 2013 09:30:49 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Message-ID: <8606_1369985449_51A851A9_8606_13789_1_57a60c9f-6d3b-4048-9100-75500effe565@THSONEA01HUB03P.one.grp> Dear All, FYI - and Yes please perform the necessary actions nicely reminded by Manuel in his email for Security Chapter to be up to date after this Sprint transition. Counting on each of you GE owners to perform update from their side and Task leads to check it has been update the way expected. WPL/WPA to perform final check from their and address issues reported if any. Best Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : jeudi 30 mai 2013 17:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Backlog - Sprint transition - from S2.3.2 to S2.3.3 and new features avaible on trackers Dear Partners, Let me remind you that we are finishing sprint S2.3.2-M25 and about to start S2.3.3-M26. Please, be aware S2.3.3 is the last sprint of the second major release. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your backlog accordingly: * Close the backlog items finished during M25 (if not already done) * Update items under execution not finished to belong to S2.3.3 * Proceed to identify the backlog items for next sprint Let me inform you that the trackers have implemented the new features: * Bug is available as entry type - theme isn't available anymore * You can update sprints and releases by selecting them on a select box. The old release and sprint fields will exist until we transfer data to the new fields. * You have available all states for the backlog items, let me remind: o Open -> defined o Scheduled -> mean those selected for the current sprint and release o Under execution -> developing them o Impeded -> items cannot be progressed because something else prevents you doing it o Under verification -> validating them o Closed -> finished successfully * All chapters have available the GE Implementation field. If you had any doubt, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Fri May 31 13:23:39 2013 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 31 May 2013 13:23:39 +0200 Subject: [Fiware-security] TR: webinar guidelines - first draft Message-ID: <20749_1369999421_51A8883C_20749_470_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206E7D5F51D@THSONEA01CMS04P.one.grp> FYI De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoy? : vendredi 31 mai 2013 12:11 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] webinar guidelines - first draft Dear Partners, Please, have the link to the webinars guidelines. http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_inform_and_adversite_webinars_of_GE This way you have aggregated all relevant information to take into account when informing and advertising the webinars. Please, take into consideration it is the first draft, therefore, feedback or advice on how to improve it is appreciated. If anything, please, don't hesitate to let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: