From pascal.bisson at thalesgroup.com Wed Feb 1 09:39:06 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 1 Feb 2012 09:39:06 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] First FI-WARE Open Call announced Message-ID: <5348_1328085550_4F28FA2E_5348_9196_1_1b224dd1-369a-4144-b495-3b7d4f67965f@THSONEA01HUB05P.one.grp> Dear All, I'm forwarding you this email I got from Juanjo to let you know that the 1st FI-WARE Open Call has now been published. I invite you to have a look at it especially for what is in scope of Security WP/AT (not that much ) and provide me and Daniel with your feedback. 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? : mercredi 1 f?vrier 2012 08:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] First FI-WARE Open Call announced Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ 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) 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 slim.trabelsi at sap.com Wed Feb 1 14:06:28 2012 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Wed, 1 Feb 2012 14:06:28 +0100 Subject: [Fiware-security] [Fiware-wpl] First FI-WARE Open Call announced In-Reply-To: <5348_1328085550_4F28FA2E_5348_9196_1_1b224dd1-369a-4144-b495-3b7d4f67965f@THSONEA01HUB05P.one.grp> References: <5348_1328085550_4F28FA2E_5348_9196_1_1b224dd1-369a-4144-b495-3b7d4f67965f@THSONEA01HUB05P.one.grp> Message-ID: Hi Pascal, I took a look to the open call that is on my opinion very generic. Then I took a closer look to the section dedicated to security https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.General.Middleware.Security Here is the description : Network connections are the dominant source of security threats and distributed applications are especially vulnerable here. Designing a middleware layer that handles network connection on behalf of the applications offers the opportunity to use this middleware also as a gatekeeper that centrally handles the security requirements as specified by an application. This involves (i) providing message transport according to certain security guarantees, (ii) supporting application so they can use and build on top of these guarantees, and (iii) validating that the middleware itself is secure and implements the security guarantees correctly. This includes integrity and confidentiality of messages, identity management and authentication, access control, accountability, exchange of security (meta-)information such as credentials, and management and enforcement of security policies. Again a very generic description that covers most of the Generic enablers that we are working on ! What does it means ? is that means that some of the proposals will address the same topics already addressed ? Can we have more information about these topics ? Thank you Best Slim ===================================== Dr Slim Trabelsi Senior Researcher Security & Trust SAP Labs France 805, Av du Docteur Maurice Donat 06250 Mougins, France T +33 4 92 28 63 45 M +33 6 11 99 85 79 www.sap.com 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 1 f?vrier 2012 09:39 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] First FI-WARE Open Call announced Dear All, I'm forwarding you this email I got from Juanjo to let you know that the 1st FI-WARE Open Call has now been published. I invite you to have a look at it especially for what is in scope of Security WP/AT (not that much ) and provide me and Daniel with your feedback. 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? : mercredi 1 f?vrier 2012 08:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] First FI-WARE Open Call announced Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ 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) 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 robert.seidl at nsn.com Wed Feb 1 14:46:24 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Wed, 1 Feb 2012 14:46:24 +0100 Subject: [Fiware-security] [Fiware-wpl] First FI-WARE Open Call announced In-Reply-To: A References: <5348_1328085550_4F28FA2E_5348_9196_1_1b224dd1-369a-4144-b495-3b7d4f67965f@THSONEA01HUB05P.one.grp> A Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A668EC99@DEMUEXC027.nsn-intra.net> Hi Slim, I did the same and came as well to the same conclusion as you. I think what is expected by the applicants is to get familiar with the following (took it from the Open Call): Before responding an Open Call, we recommend that you: * Analyze the FI-WARE Vision , where definition of main concepts (GE, FI-WARE Instance, FI-WARE Testbed and Open Innovation Lab, etc) are provided and the current chapters of FI-WARE are described. * Understand how FI-WARE is applying Agile because new beneficiaries joining the FI-WARE Consortium will have to follow defined processes and tools. * Analyze which Generic Enablers FI-WARE partners are currently implementing in their effort towards Materializing the FI-WARE Vision . Here it is expected that they get familiar with our assets before hand. Than they have to analyse what is missing by themselves and in a next step they can apply with their assets. If this approach will work .... My personal view is that it would have been much better to describe in a very concrete manner what is missing and by that what we expect (as we did in our internal Open Call description). Greetings Robert Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von ext TRABELSI, Slim Gesendet: Mittwoch, 1. Februar 2012 14:06 An: BISSON Pascal; fiware-security at lists.fi-ware.eu Betreff: Re: [Fiware-security] [Fiware-wpl] First FI-WARE Open Call announced Hi Pascal, I took a look to the open call that is on my opinion very generic. Then I took a closer look to the section dedicated to security https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.General.Middleware.Security Here is the description : Network connections are the dominant source of security threats and distributed applications are especially vulnerable here. Designing a middleware layer that handles network connection on behalf of the applications offers the opportunity to use this middleware also as a gatekeeper that centrally handles the security requirements as specified by an application. This involves (i) providing message transport according to certain security guarantees, (ii) supporting application so they can use and build on top of these guarantees, and (iii) validating that the middleware itself is secure and implements the security guarantees correctly. This includes integrity and confidentiality of messages, identity management and authentication, access control, accountability, exchange of security (meta-)information such as credentials, and management and enforcement of security policies. Again a very generic description that covers most of the Generic enablers that we are working on ! What does it means ? is that means that some of the proposals will address the same topics already addressed ? Can we have more information about these topics ? Thank you Best Slim ===================================== Dr Slim Trabelsi Senior Researcher Security & Trust SAP Labs France 805, Av du Docteur Maurice Donat 06250 Mougins, France T +33 4 92 28 63 45 M +33 6 11 99 85 79 www.sap.com 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 1 f?vrier 2012 09:39 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] First FI-WARE Open Call announced Dear All, I'm forwarding you this email I got from Juanjo to let you know that the 1st FI-WARE Open Call has now been published. I invite you to have a look at it especially for what is in scope of Security WP/AT (not that much ) and provide me and Daniel with your feedback. 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? : mercredi 1 f?vrier 2012 08:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] First FI-WARE Open Call announced Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ 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) 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 Feb 1 15:10:35 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 1 Feb 2012 15:10:35 +0100 Subject: [Fiware-security] [Fiware-wpl] First FI-WARE Open Call announced In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A668EC99@DEMUEXC027.nsn-intra.net> References: <5348_1328085550_4F28FA2E_5348_9196_1_1b224dd1-369a-4144-b495-3b7d4f67965f@THSONEA01HUB05P.one.grp> A <9739B018F0466A4CAB10A9DABBEBF5A668EC99@DEMUEXC027.nsn-intra.net> Message-ID: <5348_1328105442_4F2947E2_5348_15208_1_4a33d631-8ddd-41d9-bc0e-8b163b43a95a@THSONEA01HUB01P.one.grp> Hi Robert, You are right in the sense that TID decided to put everything in the text of the call now published for responders to based on the FI-WARE Product Vision to figure where we were and how they could join the work and so contribute (focus on assets) what FI-WARE think is most missing at this time. In the meantime and despite the topics each of teams were called to contribute and indeed contributed it was decided to keep those topics for the second open call and to concentrate for the first open call on the most urgent topics resulting from discussion between FI-WARE & UC projects at AB meetings. As such we have now to cope with the call as it is and to prepare ourselves for the second call where are security topics would be pushed. For that call what I would suggest would be to work on the EPIC that relate to Security and maybe contribute some further orientations the way we think it should go in view of what we already initiated. To be in any case re-addressed at our weekly-audio conf on Friday. Best Regards, Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : mercredi 1 f?vrier 2012 14:46 ? : ext TRABELSI, Slim; BISSON Pascal; fiware-security at lists.fi-ware.eu Objet : AW: [Fiware-security] [Fiware-wpl] First FI-WARE Open Call announced Hi Slim, I did the same and came as well to the same conclusion as you. I think what is expected by the applicants is to get familiar with the following (took it from the Open Call): Before responding an Open Call, we recommend that you: * Analyze the FI-WARE Vision, where definition of main concepts (GE, FI-WARE Instance, FI-WARE Testbed and Open Innovation Lab, etc) are provided and the current chapters of FI-WARE are described. * Understand how FI-WARE is applying Agile because new beneficiaries joining the FI-WARE Consortium will have to follow defined processes and tools. * Analyze which Generic Enablers FI-WARE partners are currently implementing in their effort towards Materializing the FI-WARE Vision. Here it is expected that they get familiar with our assets before hand. Than they have to analyse what is missing by themselves and in a next step they can apply with their assets. If this approach will work .... My personal view is that it would have been much better to describe in a very concrete manner what is missing and by that what we expect (as we did in our internal Open Call description). Greetings Robert Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von ext TRABELSI, Slim Gesendet: Mittwoch, 1. Februar 2012 14:06 An: BISSON Pascal; fiware-security at lists.fi-ware.eu Betreff: Re: [Fiware-security] [Fiware-wpl] First FI-WARE Open Call announced Hi Pascal, I took a look to the open call that is on my opinion very generic. Then I took a closer look to the section dedicated to security https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.General.Middleware.Security Here is the description : Network connections are the dominant source of security threats and distributed applications are especially vulnerable here. Designing a middleware layer that handles network connection on behalf of the applications offers the opportunity to use this middleware also as a gatekeeper that centrally handles the security requirements as specified by an application. This involves (i) providing message transport according to certain security guarantees, (ii) supporting application so they can use and build on top of these guarantees, and (iii) validating that the middleware itself is secure and implements the security guarantees correctly. This includes integrity and confidentiality of messages, identity management and authentication, access control, accountability, exchange of security (meta-)information such as credentials, and management and enforcement of security policies. Again a very generic description that covers most of the Generic enablers that we are working on ! What does it means ? is that means that some of the proposals will address the same topics already addressed ? Can we have more information about these topics ? Thank you Best Slim ===================================== Dr Slim Trabelsi Senior Researcher Security & Trust SAP Labs France 805, Av du Docteur Maurice Donat 06250 Mougins, France T +33 4 92 28 63 45 M +33 6 11 99 85 79 www.sap.com 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 1 f?vrier 2012 09:39 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] First FI-WARE Open Call announced Dear All, I'm forwarding you this email I got from Juanjo to let you know that the 1st FI-WARE Open Call has now been published. I invite you to have a look at it especially for what is in scope of Security WP/AT (not that much ) and provide me and Daniel with your feedback. 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? : mercredi 1 f?vrier 2012 08:50 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] First FI-WARE Open Call announced Hi, The first FI-WARE Open Call has already been published. Details can be found at: http://www.fi-ware.eu/open-call/ 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) 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 robert.seidl at nsn.com Wed Feb 1 15:40:26 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Wed, 1 Feb 2012 15:40:26 +0100 Subject: [Fiware-security] FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) In-Reply-To: <20452_1327948396_4F26E26C_20452_4422_1_f655dc30-382f-4093-a0ad-daecc74562d0@THSONEA01HUB03P.one.grp> References: <26505_1327912210_4F265512_26505_16180_1_941209f0-26e4-414e-a4dc-19dfdc06b280@THSONEA01HUB05P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A668E563@DEMUEXC027.nsn-intra.net> <20452_1327948396_4F26E26C_20452_4422_1_f655dc30-382f-4093-a0ad-daecc74562d0@THSONEA01HUB03P.one.grp> Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A668ECDF@DEMUEXC027.nsn-intra.net> Hi Pascal, here are the answers for the NSN enabler (sorry some questions are not crystal clear to me): Q1 Can your HW be virtualised? If "no" why? ? yes (I assume it is also meant SW, not only HW), if it is meant kind of simulating the HW than the answer is no. What will you provide to the testbed? ? The generic enabler will be connected to the test bed via the Internet. For the test bed we provide a link to our enabler. Q2 testbed version 1 (M15) ? preliminary version testbed version 2 (M27) ? functional version testbed version 3 (M36) ? functional version enhanced with additional features Q3 What GEs do you plan to integrate with (inside/outside your FI-WARE Chapter)? ? Privacy Generic Enabler and Data Handling Generic Enabler For which testbed version do you plan the integration? ? Test bed version 2 and 3 Is your GEs dependent on the HW released by other FI-WARE Chapter? ? no Q4 Have you made a preliminary check about the need to execute your GEs in a private local infrastructure? ? It is not clear what is meant with a "private local infrastructure". If it is meant as Intranet than the answer is yes, if it is meant as operator network than the answer is no. Q5 ? No Greetings Robert Von: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Gesendet: Montag, 30. Januar 2012 19:33 An: Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc: GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Betreff: RE: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Robert, Attached is the page. As for the rest I can't figure why not each and every of us is not provided an access. Will discuss this with Stefano ... but ok for the time being you have the questions ... Looking for excel file completed with your answers. Thanks in advance Best Regards, Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : lundi 30 janvier 2012 19:23 ? : BISSON Pascal; Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc : GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Hi, I do not have the permission right to access the link. Error message: "The action you have requested is limited to users in one of the groups: Administrators , Members." To avoid the question: Yes, I'm logged in J The Excel is not too easy to understand, but nevertheless do we have to look on line 60 to 68? Greetings Robert From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: Monday, January 30, 2012 9:30 AM To: Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc: GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Subject: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Importance: High Dear Robert, Gabor, Dear Anja, Michael As a follow-up of the meeting held last week at FI-WARE GA with WP10 (FI-WARE Testbed) lead (Stefano De Panfilis) where each of the Security owners present (i.e. Daniel, Francesco, Antonio, Wolfgang) provided their best answer to the questions raised and that you may find at the following address: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_Testbed_Fact_Finding_Investigation (to access to this web page you should first log in to the repository) I would appreciate if you could urgently complete the attached excel file with your answers to those questions for what concerns the Security GE you own (IDM/NSN and Privacy/IBM). Once completed this excel file please send it back to me and Daniel. Would appreciate if you could have it done asap and by tomorrow EOB (31/01/2012) as it quite urgent information now to deliver from our Security Chapter to WP10. Thanks in advance. Hearing from you. Pascal. PS: I put in cc the other GE owners in case they'd like to make some changes. Without feedback I will assume they are fine with the answers already provided. PS2: I put in the cc the mailing for information -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Feb 1 15:53:08 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 1 Feb 2012 15:53:08 +0100 Subject: [Fiware-security] FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A668ECDF@DEMUEXC027.nsn-intra.net> References: <26505_1327912210_4F265512_26505_16180_1_941209f0-26e4-414e-a4dc-19dfdc06b280@THSONEA01HUB05P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A668E563@DEMUEXC027.nsn-intra.net> <20452_1327948396_4F26E26C_20452_4422_1_f655dc30-382f-4093-a0ad-daecc74562d0@THSONEA01HUB03P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A668ECDF@DEMUEXC027.nsn-intra.net> Message-ID: <30689_1328107991_4F2951D7_30689_9037_1_2d96c661-a313-4bd8-aa23-a611613e6856@THSONEA01HUB05P.one.grp> Thanks Robert to complete the excel file to be sent on behalf of WP8. Regards, Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : mercredi 1 f?vrier 2012 15:40 ? : BISSON Pascal; Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc : GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Objet : AW: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Hi Pascal, here are the answers for the NSN enabler (sorry some questions are not crystal clear to me): Q1 Can your HW be virtualised? If "no" why? --> yes (I assume it is also meant SW, not only HW), if it is meant kind of simulating the HW than the answer is no. What will you provide to the testbed? --> The generic enabler will be connected to the test bed via the Internet. For the test bed we provide a link to our enabler. Q2 testbed version 1 (M15) --> preliminary version testbed version 2 (M27) --> functional version testbed version 3 (M36) --> functional version enhanced with additional features Q3 What GEs do you plan to integrate with (inside/outside your FI-WARE Chapter)? --> Privacy Generic Enabler and Data Handling Generic Enabler For which testbed version do you plan the integration? --> Test bed version 2 and 3 Is your GEs dependent on the HW released by other FI-WARE Chapter? --> no Q4 Have you made a preliminary check about the need to execute your GEs in a private local infrastructure? ? It is not clear what is meant with a "private local infrastructure". If it is meant as Intranet than the answer is yes, if it is meant as operator network than the answer is no. Q5 ? No Greetings Robert Von: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Gesendet: Montag, 30. Januar 2012 19:33 An: Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc: GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Betreff: RE: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Robert, Attached is the page. As for the rest I can't figure why not each and every of us is not provided an access. Will discuss this with Stefano ... but ok for the time being you have the questions ... Looking for excel file completed with your answers. Thanks in advance Best Regards, Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : lundi 30 janvier 2012 19:23 ? : BISSON Pascal; Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc : GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Hi, I do not have the permission right to access the link. Error message: "The action you have requested is limited to users in one of the groups: Administrators, Members." To avoid the question: Yes, I'm logged in :) The Excel is not too easy to understand, but nevertheless do we have to look on line 60 to 68? Greetings Robert From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: Monday, January 30, 2012 9:30 AM To: Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); Anja Lehmann; Michael Osborne Cc: GIDOIN Daniel; DI CERBO, Francesco; Antonio Garcia Vazquez; fiware-security at lists.fi-ware.eu Subject: FI-WARE - Action Point for NSN & IBM (provide your answers to WP10 questions regarding GE you own) Importance: High Dear Robert, Gabor, Dear Anja, Michael As a follow-up of the meeting held last week at FI-WARE GA with WP10 (FI-WARE Testbed) lead (Stefano De Panfilis) where each of the Security owners present (i.e. Daniel, Francesco, Antonio, Wolfgang) provided their best answer to the questions raised and that you may find at the following address: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/FI-WARE_Testbed_Fact_Finding_Investigation (to access to this web page you should first log in to the repository) I would appreciate if you could urgently complete the attached excel file with your answers to those questions for what concerns the Security GE you own (IDM/NSN and Privacy/IBM). Once completed this excel file please send it back to me and Daniel. Would appreciate if you could have it done asap and by tomorrow EOB (31/01/2012) as it quite urgent information now to deliver from our Security Chapter to WP10. Thanks in advance. Hearing from you. Pascal. PS: I put in cc the other GE owners in case they'd like to make some changes. Without feedback I will assume they are fine with the answers already provided. PS2: I put in the cc the mailing for information -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Wed Feb 1 16:57:40 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Wed, 1 Feb 2012 16:57:40 +0100 Subject: [Fiware-security] FI-WARE GE Description Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A668ED49@DEMUEXC027.nsn-intra.net> Hi Pascal, please find under https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/Deliv erable_%22D2.3_FIWARE_Architecture%22_-_Security_Contrib the description of the 3 Generic Security Enabler (IDM, Privacy and Data Handling). Please consider these versions as initial and not final. The description will be enhanced during the integration phase of the enablers and due to the requirements coming from the UC projects. Many thanks to all contributors, especially to Anja, Slim, Francesco and Norbert. Greetings Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Thu Feb 2 12:53:50 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Thu, 2 Feb 2012 12:53:50 +0100 Subject: [Fiware-security] FI-WARE: Security Chapter to D2.3 Architecture Specifications Message-ID: <10680_1328183607_4F2A7937_10680_8194_1_fc53cad8-ce38-4085-b95f-5822a2fb564c@THSONEA01HUB06P.one.grp> Dear All, The most important priority is the due contribution of Security Chapter to D2.3 Architecture Specifications. Thank a lot to complete as our early T8.1 draft: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Security.Security_Monitoring We could discuss about it at our next audio conference on Friday 3rd (10am-12am). Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Feb 2 15:15:05 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 2 Feb 2012 15:15:05 +0100 Subject: [Fiware-security] FI-WARE - Architecture Description deliverable (additional guidance from TID/Juanjo) Message-ID: <1935_1328192106_4F2A9A6A_1935_13018_3_9d099023-3184-45e2-a47f-bd75a30d42ce@THSONEA01HUB03P.one.grp> Dear All, This just to inform you that Juanjo has just published a set of guidelines to be followed for the development of the Architecture Description deliverable: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Counting on you to have a look and make good use of this how-to as it can only help us to align and converge with others (ATs/WPs) Of course to be re-addressed at our audio. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From francesco.di.cerbo at sap.com Thu Feb 2 16:18:26 2012 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Thu, 2 Feb 2012 16:18:26 +0100 Subject: [Fiware-security] SAP participation to tomorrow's CC (3/2/2012) Message-ID: <71C0C7C7A712EE4CA636EDFD663B4E27036B9C32DD@DEWDFECCR09.wdf.sap.corp> Hello Pascal, all, Unfortunately tomorrow Slim and I will have to quit the CC earlier, at about 10.55, due to internal commitments. We apologize for any inconvenience we can cause. Best regards, Francesco ___ Francesco Di Cerbo, PhD 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 Wolfgang.Steigerwald at telekom.de Thu Feb 2 18:21:15 2012 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Thu, 2 Feb 2012 18:21:15 +0100 Subject: [Fiware-security] User Story Message-ID: Hello Pascal, hello Chris, here is the user story we talked about in Madrid. User Story: Managing Service To help users to manage the software on their mobile devices or help to find their lost devices a service provider (SP) offers the "Managing Service" (MS). To use the service an user must register himself and the device to the service. When the user want's later use the service the SP redirect the user to the users Identity Provider (IdP) where the he has to authenticate himself. If the device gets lost the MS can activate the GPS module to locate the device or ask the Telco-Operator where the device is located. Therefore the MS authenticates to the device or the operator and delivers the service. Mit freundlichen Gr??en / Viele Gr??e / Best Regards Wolfgang Deutsche Telekom AG T-Labs (Research & Innovation) Dipl.-Inform. Wolfgang Steigerwald Winterfeldtstr. 21, 10781 Berlin +4930835354287 (Tel.) +4930835358408 (Fax) E-Mail: wolfgang.steigerwald at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Claudia Nemat, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Feb 2 20:04:19 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 2 Feb 2012 20:04:19 +0100 Subject: [Fiware-security] User Story In-Reply-To: References: Message-ID: <518_1328209458_4F2ADE32_518_15182_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206454AD63D@THSONEA01CMS04P.one.grp> Hi Wolfgang, Sounds good let's now consider reporting this user story on the backlog at the right place. Best Regards, Pascal De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : jeudi 2 f?vrier 2012 18:21 ? : BISSON Pascal; chris.woods at intel.com Cc : fiware-security at lists.fi-ware.eu Objet : User Story Hello Pascal, hello Chris, here is the user story we talked about in Madrid. User Story: Managing Service To help users to manage the software on their mobile devices or help to find their lost devices a service provider (SP) offers the "Managing Service" (MS). To use the service an user must register himself and the device to the service. When the user want's later use the service the SP redirect the user to the users Identity Provider (IdP) where the he has to authenticate himself. If the device gets lost the MS can activate the GPS module to locate the device or ask the Telco-Operator where the device is located. Therefore the MS authenticates to the device or the operator and delivers the service. Mit freundlichen Gr??en / Viele Gr??e / Best Regards Wolfgang Deutsche Telekom AG T-Labs (Research & Innovation) Dipl.-Inform. Wolfgang Steigerwald Winterfeldtstr. 21, 10781 Berlin +4930835354287 (Tel.) +4930835358408 (Fax) E-Mail: wolfgang.steigerwald at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Claudia Nemat, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Fri Feb 3 08:50:37 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Fri, 3 Feb 2012 08:50:37 +0100 Subject: [Fiware-security] User Story In-Reply-To: A<518_1328209458_4F2ADE32_518_15182_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206454AD63D@THSONEA01CMS04P.one.grp> References: A<518_1328209458_4F2ADE32_518_15182_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206454AD63D@THSONEA01CMS04P.one.grp> Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A66CE5D4@DEMUEXC027.nsn-intra.net> Hi all, such service is already offered for the IPhones and as well some other brands. So not a very new stuff. Let's discuss this in our telco today. PS: Wolfgang, please look at my emails which I sent to you and received so far no answers L Greetings Robert Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von ext BISSON Pascal Gesendet: Donnerstag, 2. Februar 2012 20:04 An: Wolfgang.Steigerwald at telekom.de; chris.woods at intel.com Cc: fiware-security at lists.fi-ware.eu Betreff: Re: [Fiware-security] User Story Hi Wolfgang, Sounds good let's now consider reporting this user story on the backlog at the right place. Best Regards, Pascal De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : jeudi 2 f?vrier 2012 18:21 ? : BISSON Pascal; chris.woods at intel.com Cc : fiware-security at lists.fi-ware.eu Objet : User Story Hello Pascal, hello Chris, here is the user story we talked about in Madrid. User Story: Managing Service To help users to manage the software on their mobile devices or help to find their lost devices a service provider (SP) offers the "Managing Service" (MS). To use the service an user must register himself and the device to the service. When the user want's later use the service the SP redirect the user to the users Identity Provider (IdP) where the he has to authenticate himself. If the device gets lost the MS can activate the GPS module to locate the device or ask the Telco-Operator where the device is located. Therefore the MS authenticates to the device or the operator and delivers the service. Mit freundlichen Gr??en / Viele Gr??e / Best Regards Wolfgang Deutsche Telekom AG T-Labs (Research & Innovation) Dipl.-Inform. Wolfgang Steigerwald Winterfeldtstr. 21, 10781 Berlin +4930835354287 (Tel.) +4930835358408 (Fax) E-Mail: wolfgang.steigerwald at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Claudia Nemat, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavier.aghina at orange.com Fri Feb 3 09:59:50 2012 From: xavier.aghina at orange.com (xavier.aghina at orange.com) Date: Fri, 3 Feb 2012 09:59:50 +0100 Subject: [Fiware-security] phone call to day Message-ID: Hi all, I must address an urgent problem, unfortunately, I propose to send you next week a proposal to assets for advice and comments. good meeting. Xavier Aghina FT/OLNC/RD/MAPS/STT/NDS Ing?nieur de Recherche en S?curit? t?l. 01 45 29 81 59 xavier.aghina at orange.com -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1081 bytes Desc: image002.gif URL: From pascal.bisson at thalesgroup.com Fri Feb 3 10:03:11 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 3 Feb 2012 10:03:11 +0100 Subject: [Fiware-security] FI-WARE - Audio conf (details) Will start in a minute! Message-ID: <10595_1328259793_4F2BA2D1_10595_2196_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206454ADB24@THSONEA01CMS04P.one.grp> Dear All, Audio conf will start in a minute: On the Agenda: 1. FI-WARE (GA) feedback 2. Review of GE spec status (focus D2.3 input) 3. Answers to teestbed 4. Standardization 5. Dissemination/Exploitation 6. Other points/info Best Regards, Pascal Number to dial to join remain unchanged as well as meeting room number (see below). [Meeting room number (unchanged) : 391581] 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 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: From daniel.gidoin at thalesgroup.com Fri Feb 3 10:04:45 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 3 Feb 2012 10:04:45 +0100 Subject: [Fiware-security] phone call to day In-Reply-To: References: Message-ID: <20921_1328259888_4F2BA330_20921_7241_1_8F1D40232A0E68409E3FC23A30C3266201670B600780@THSONEA01CMS04P.one.grp> Bonjour Xavier, Pourrais-tu contribuer au draft du dossier d'architecture pour lundi soir au plus tard Cordialement Daniel De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de xavier.aghina at orange.com Envoy? : vendredi 3 f?vrier 2012 10:00 ? : fiware-security at lists.fi-ware.eu Objet : [Fiware-security] phone call to day Hi all, I must address an urgent problem, unfortunately, I propose to send you next week a proposal to assets for advice and comments. good meeting. [cid:image001.gif at 01CCE25B.4140AA40] Xavier Aghina FT/OLNC/RD/MAPS/STT/NDS Ing?nieur de Recherche en S?curit? t?l. 01 45 29 81 59 xavier.aghina at orange.com [cid:image002.gif at 01CCE25B.4140AA40] -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1081 bytes Desc: image002.gif URL: From robert.seidl at nsn.com Fri Feb 3 11:21:15 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Fri, 3 Feb 2012 11:21:15 +0100 Subject: [Fiware-security] Link to the reference example for D2.3 Architecture Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A66CE664@DEMUEXC027.nsn-intra.net> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.ph p/FIWARE.OpenSpecification.Data.QueryBroker -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Feb 3 11:25:22 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 3 Feb 2012 11:25:22 +0100 Subject: [Fiware-security] Reference example for D2.3 Message-ID: <28669_1328264723_4F2BB613_28669_1832_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206454FC709@THSONEA01CMS04P.one.grp> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Feb 6 09:42:54 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 6 Feb 2012 09:42:54 +0100 Subject: [Fiware-security] FI-WARE - WP8 - Minutes of last weekly audio conf Message-ID: <16936_1328517775_4F2F928F_16936_15410_1_41d046bf-3cd7-4c14-a837-87324c597f30@THSONEA01HUB01P.one.grp> Dear All, This just to let you know that I've uploaded on the WP8 repository the minutes of our last weekly audio conf (03-02-2012 10am-12am). Here is the link to access them: https://forge.fi-ware.eu/docman/view.php/19/781/Audio-conf+WP8+03-02-2012+minutes.doc As for next audio WP8 audio conf it is planned as usual Friday this week (10-02-2012 10am-12am) [same details as usual] Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Feb 6 20:13:25 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 6 Feb 2012 20:13:25 +0100 Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference example + how to instructions Message-ID: <27549_1328555900_4F30277C_27549_9230_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206455BE6CB@THSONEA01CMS04P.one.grp> Dear All After a quick scan through WP8 input to D2.3 I noticed that most of the inputs reported there were still not conformant to what was expected. This despite reference example and instructions already provided. As such I'd like here to remind you (especially Task leads and GE ownenrs) where to find the reference example to follow for your input. You may find it here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker Please also refer to instructions/guidelines Juanjo provided especially for what concerns content of each of the sections. Available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Counting on you to follow these guidelines and follow reference example. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Tue Feb 7 19:02:14 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Tue, 7 Feb 2012 19:02:14 +0100 Subject: [Fiware-security] FI-WARE T8.2 --> D2.3 WIKI input Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A66CF131@DEMUEXC027.nsn-intra.net> Hi T8.2, I tried to follow as much as possible the template for the api/interface description and applied it for the Identity Enabler. Please have a look here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/security/index.php/Deliv erable_%22D2.3_FIWARE_Architecture%22_-_Security_Contrib @Wolfgang/Alexandra: Could you please add your parts for OpenID. @Anja: Could you do the changes for the Privacy Enabler? @Slim/Francesco: Could you do it for the Data Enabler? Have much fun with WIKI formatting !! It is very time consuming. @all: If some additional input for the 3 Generic Enablers is needed from any partner, please send me an email. Greetings Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From slim.trabelsi at sap.com Wed Feb 8 12:00:29 2012 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Wed, 8 Feb 2012 12:00:29 +0100 Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference examp le + how to instructions In-Reply-To: References: Message-ID: Hi Richard, Just for clarification, the content based security enabler was planned for year two. At least this is what we agreed during the last meetings. In that case there should not be an entry in the D2.3 architecture deliverable. Are you sure that you want to send it in this deliverable knowing that there are no black log entries no planning for this asset ? On my opinion we should keep it for the next release of the generic enable it was planned, we already have two others assets for year two. Thank you Best Slim ===================================== Dr Slim Trabelsi Senior Researcher Security & Trust SAP Labs France 805, Av du Docteur Maurice Donat 06250 Mougins, France T +33 4 92 28 63 45 M +33 6 11 99 85 79 www.sap.com From: Egan, Richard [mailto:Richard.Egan at uk.thalesgroup.com] Sent: mercredi 8 f?vrier 2012 11:13 To: TRABELSI, Slim; DI CERBO, Francesco Cc: fiware-security at lists.fi-ware.eu; Waller, Adrian Subject: RE: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference examp le + how to instructions Slim, Francesco for your information, in preparation for D2.3 and specifically the Optional GEs, TRT UK are preparing a contribution for the content based security OGE on the wiki. There should be a good version available by the end of the week, but here is a link to the work in progress. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Security.Optional_Security_Enablers.Content_Based_Security We will be trying to follow the TID guidelines. As there is not so much time left, if you have any comments on this approach, please let us know as soon as possible 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: 06 February 2012 19:13 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference example + how to instructions Importance: High Dear All After a quick scan through WP8 input to D2.3 I noticed that most of the inputs reported there were still not conformant to what was expected. This despite reference example and instructions already provided. As such I'd like here to remind you (especially Task leads and GE ownenrs) where to find the reference example to follow for your input. You may find it here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.Data.QueryBroker Please also refer to instructions/guidelines Juanjo provided especially for what concerns content of each of the sections. Available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Counting on you to follow these guidelines and follow reference example. Best Regards, Pascal Please consider the environment before printing a hard copy of this e-mail. The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)118 986 8601 and delete it and all copies from your system. Thales Research and Technology (UK) Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 774298 Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Feb 9 09:31:56 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 9 Feb 2012 09:31:56 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] Tutorial: Creation of deliverables with wiki pages Message-ID: <17056_1328776315_4F33847B_17056_18680_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206456948FA@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 Miguel Carrillo Envoy? : mercredi 8 f?vrier 2012 23:58 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Tutorial: Creation of deliverables with wiki pages Dear WPLs/WPAs, Please note that there is a new tutorial to teach everyone to create pdf documents with the wiki. All public deliverables should use this method as all public deliverables will be worked and deposited on the wiki. * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_pdf_deliverables_from_wiki_pages Important: as leaders of your WPs, you have to make sure that all the editors of the documents are aware of this. Do not forget this, if not they get lost. 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From francesco.di.cerbo at sap.com Fri Feb 10 08:55:01 2012 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Fri, 10 Feb 2012 08:55:01 +0100 Subject: [Fiware-security] URGENT: important FI-WARE T8.4 request In-Reply-To: <20120208122919.GA4105@inria.fr> References: <71C0C7C7A712EE4CA636EDFD663B4E27036BBFB0C2@DEWDFECCR09.wdf.sap.corp> <20120208122919.GA4105@inria.fr> Message-ID: <71C0C7C7A712EE4CA636EDFD663B4E27036BEA143A@DEWDFECCR09.wdf.sap.corp> Hello Alexandre, Ok, thanks for this clarification, as long as the service is accessible according to FI-WARE terms and we are compliant with WP10 (Testbed) requests, this should be ok. Best, Francesco > -----Original Message----- > From: Alexandre Boeglin [mailto:alexandre.boeglin at inria.fr] > Sent: mercredi 8 f?vrier 2012 13:29 > To: DI CERBO, Francesco > Cc: Jean-Yves Marion; GASPARD Lucie; LELEU Philippe > (philippe.leleu at thalesgroup.com); BISSON Pascal; TRABELSI, Slim; Guillaume > BONFANTE (Guillaume.Bonfante at loria.fr); Fabrice SABATIER > Subject: Re: URGENT: important FI-WARE T8.4 request > > Le lundi 06 f?vrier 2012 ? 11:42, DI CERBO, Francesco a ?crit: > > @INRIA: during the last GA in Madrid, a number of questions were > > raised about your diagrams; in particular, I was wondering if they > > were depicting correctly the deployment scenario that you are > > proposing for FI-WARE (e.g., an "agent" to be deployed on the testbed, > > and your "real" malware services in your premises) . I kindly ask to > > Alexandre to let us have a clarification on this point, and in case to > > update your diagrams and to upload them on the wiki page. > > Hello, > > I discussed with Guillaume and Fabrice about this, and it appears there > was a misunderstanding. > > The malware detection service will be provided as a SOAP WebService, > deployed in our premises and accessible remotely. > > The only client they will provide will be a Java sample client that will > connect to the WebService, but its main purpose will be to be a demo on > how to interact with the WebService. > > > Best regards, > Alex > > * PGP - S/MIME Signed: 08/02/2012 at 13:29:19 > * Alexandre BOEGLIN > * Issuer: TERENA From pascal.bisson at thalesgroup.com Fri Feb 10 08:56:47 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 10 Feb 2012 08:56:47 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] Further instructions regarding Architecture Description Deliverable Message-ID: <29619_1328860609_4F34CDC1_29619_6043_1_045a84c5-121f-46b5-ab07-770e92031120@THSONEA01HUB02P.one.grp> FYI Please consider this latest changes (also demands) from Juanjo regarding "how to" instructions for D2.3 Architecture specification. Best Regards, Pascal -----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 Juanjo Hierro Envoy??: vendredi 10 f?vrier 2012 08:02 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] Further instructions regarding Architecture Description Deliverable Hi, I have updated the guidelines for developing the Architecture Description deliverable on the wiki. I have essentially added a target extension per section as well as hints about how to deal with the different releases https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Of course, don't hesitate to make comments or ask for any doubt. They may help to enrich the guidelines. 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) 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From pascal.bisson at thalesgroup.com Fri Feb 10 09:01:58 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 10 Feb 2012 09:01:58 +0100 Subject: [Fiware-security] FI-WARE - Weekly audio conference (Agenda) Message-ID: <8569_1328860922_4F34CEFA_8569_17235_1_1f1b88f2-414e-4482-958c-177343046f42@THSONEA01HUB01P.one.grp> Dear All, Here is the Agenda for our weekly audio conference of today at 10am: 1. AP as per last minutes / also GA 2. D2.3 review of contribs from Security Chapter (TL/GE owners) 3. Tracker check status 4. WP10 questions (missing inputs) 5. Update on standardization deliverable 6. Other topics Will open the audio conf at 10am (same details as usual to join) Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Feb 10 10:23:14 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 10 Feb 2012 10:23:14 +0100 Subject: [Fiware-security] (no subject) Message-ID: <10606_1328865796_4F34E204_10606_5885_1_CBBCD6C304123F4AB23FAAE3055C8C0E02064571B527@THSONEA01CMS04P.one.grp> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Feb 13 08:48:34 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 Feb 2012 08:48:34 +0100 Subject: [Fiware-security] TR: [Fiware-cloud] FI-WARE weekly meeting 8/2 -- minutes Message-ID: <21687_1329119316_4F38C054_21687_1456_1_CBBCD6C304123F4AB23FAAE3055C8C0E02064576CF64@THSONEA01CMS04P.one.grp> FYI mainly in scope of T8.1 (so Daniel and his team) De : fiware-cloud-bounces at lists.fi-ware.eu [mailto:fiware-cloud-bounces at lists.fi-ware.eu] De la part de Alex Glikson Envoy? : mercredi 8 f?vrier 2012 17:15 ? : fiware-cloud at lists.fi-ware.eu Objet : [Fiware-cloud] FI-WARE weekly meeting 8/2 -- minutes att: Alex, Andy, Sharon, Pascal, Irina, Juaquin, Fernando agenda: see email below 1. no comments 2. no comments 7 (security-related email). no comments. need to start discussion with WP7 regarding IdM GE. should plan longer-term join work on security monitoring, beyond 1st release. 3. will update the backlog until the end of the week. - IBM: focus areas: capacity management, placement. - Intel: TXT end-to-end integration. OCCI interface for essential management. CDMI interface on top of Swift for essential management. - separate story for TXT-aware placement (joint between IBM and Intel) - Telefonica: working on OpenStack API for Service Manager (essential management). Monitoring, Templates. vApps -- July time frame. - Technicolor: subset of life cycle of virtual appliance. described in open spec. - UPM: build internal testbed. will update the tracker (the technical issue has been resolved). Horizon should be able to work with OpenStack API of Service Manager as is. Should focus on vApps additions, to be ready in July. 4. Juanjo didn't sent guidelines yet, will follow-up over email 5. architecture - in the first release, SM should use Glance API to work with images -- but should be CDMI in the long run (provided by RM) - we may show interaction between DCRM and Object Storage (for images) - Alex will send FMC materials - DCRM: we may delegate the reader to OCCI specification. - Cloud Edge: need to be clear who is invoking the Cloud Proxy APIs. seems that this should be the application provider? - Object Storage: add high-level FMC diagram. point to specific parts of the CDMI spec? how do we map Swift entities to CDMI entities? need an interaction with IdM. Design Principles? - Move generic Cloud design principles to the chapter page. - Portal: transform the general architecture into FMC. Should not be tightly related to OpenStack. Do we really need an open specification on Portal?? need to follow-up with Juanjo. Regards, Alex P.S. FMC materials: ----- Forwarded by Alex Glikson/Haifa/IBM on 08/02/2012 04:06 PM ----- From: Alex Glikson/Haifa/IBM To: fiware-cloud at lists.fi-ware.eu Date: 06/02/2012 02:42 PM Subject: upcoming weekly call on Wednesday -- IMPORTANT ________________________________ Dear all, Please, see below the topics I would like to discuss during our upcoming weekly call on Wednesday. The list is long, so I would suggest to book an additional hour this week (i.e., 3-5pm CET) -- it seemed available in the poll results. Also, there are few things I would like to ask you to do towards the meeting, as specified below. 1. Finalize minutes from the F2F in Madrid [All: please, review the minutes and update as necessary, so that I can upload them to Forge, as required. https://docs.google.com/document/d/1-_DEfDGnexzkOmOoJdbeZCK7z001H-N0TYorvbALPqw/edit] 1. Discuss comments/suggestions regarding the standardization deliverable draft [All: please, review the draft I sent the other day, comment and/or suggest enhancements] 1. Review updated plan for this minor release & sprint [All: make sure Wiki and Tracker are up to date, including status and assignment of items to the corresponding sprint/release] 1. Discuss content of technical roadmap deliverable (pending guidelines to be distributed by Juanjo) 1. Review status of Architecture deliverable (chapter description, individual GEs) [All: please, provide initial content, following the guidelines I forwarded.] 1. BonFIRE [would be good to have someone review & summarize. volunteers?] Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Reference_Sheet-FMC_Block_Diagram.pdf Type: application/octet-stream Size: 28030 bytes Desc: Reference_Sheet-FMC_Block_Diagram.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FMC_PPT_Shapes.ppt Type: application/octet-stream Size: 201728 bytes Desc: FMC_PPT_Shapes.ppt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Mon Feb 13 08:59:15 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 Feb 2012 08:59:15 +0100 Subject: [Fiware-security] FI-WARE - WP8 Minutes of last audio conference Message-ID: <21687_1329119954_4F38C2D2_21687_1620_1_bb711190-908a-4fb7-aa2a-73b60b4a21fd@THSONEA01HUB05P.one.grp> Dear All, This to inform you that I've just uploaded on the FI-Security project repository the minutes of our last audio conference. You could find them at the following address: https://forge.fi-ware.eu/docman/view.php/19/801/Audio-conf+WP8+10-02-2012+minutes.doc As for the rest please check and perform APs as discussed and reported. Bear in mind the deadline for WP8 finalized contribution to D2.3 remains February 17th and as such everything should be settled from our security side by February 16th EOB at the latest. Counting on you all to meet the set deadline Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavier.aghina at orange.com Mon Feb 13 13:43:22 2012 From: xavier.aghina at orange.com (xavier.aghina at orange.com) Date: Mon, 13 Feb 2012 13:43:22 +0100 Subject: [Fiware-security] FI-WARE - WP8 Minutes of last audio conference In-Reply-To: <21687_1329119954_4F38C2D2_21687_1620_1_bb711190-908a-4fb7-aa2a-73b60b4a21fd@THSONEA01HUB05P.one.grp> References: <21687_1329119954_4F38C2D2_21687_1620_1_bb711190-908a-4fb7-aa2a-73b60b4a21fd@THSONEA01HUB05P.one.grp> Message-ID: Hello Pascal, an error in the persons present during last audio conf - 10/02/2012 : I was present, thank you for correction ;) Xavier. 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 f?vrier 2012 08:59 ? : fiware-security at lists.fi-ware.eu Cc : LELEU Philippe Objet : [Fiware-security] FI-WARE - WP8 Minutes of last audio conference Dear All, This to inform you that I've just uploaded on the FI-Security project repository the minutes of our last audio conference. You could find them at the following address: https://forge.fi-ware.eu/docman/view.php/19/801/Audio-conf+WP8+10-02-2012+minutes.doc < ang=EN-US>As for the rest please check and perform APs as discussed and reported. Bear in mind the deadline for WP8 finalized contribution to D2.3 remains February 17th and as such everything should be settled from our security side by February 16th EOB at the latest. Counting on you all to meet the set deadline Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Feb 13 14:43:06 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 13 Feb 2012 14:43:06 +0100 Subject: [Fiware-security] FI-WARE - WP8 Minutes of last audio conference In-Reply-To: References: <21687_1329119954_4F38C2D2_21687_1620_1_bb711190-908a-4fb7-aa2a-73b60b4a21fd@THSONEA01HUB05P.one.grp> Message-ID: <32427_1329140591_4F39136F_32427_6285_1_96059c92-cdd1-4d57-8761-3ad9fd0f80e3@THSONEA01HUB05P.one.grp> Dear Xavier, This has now been corrected. So thanks for the notice. Regards, Pascal De : xavier.aghina at orange.com [mailto:xavier.aghina at orange.com] Envoy? : lundi 13 f?vrier 2012 13:43 ? : BISSON Pascal; fiware-security at lists.fi-ware.eu Cc : LELEU Philippe Objet : RE: [Fiware-security] FI-WARE - WP8 Minutes of last audio conference Hello Pascal, an error in the persons present during last audio conf - 10/02/2012 : I was present, thank you for correction ;) Xavier. 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 f?vrier 2012 08:59 ? : fiware-security at lists.fi-ware.eu Cc : LELEU Philippe Objet : [Fiware-security] FI-WARE - WP8 Minutes of last audio conference Dear All, This to inform you that I've just uploaded on the FI-Security project repository the minutes of our last audio conference. You could find them at the following address: https://forge.fi-ware.eu/docman/view.php/19/801/Audio-conf+WP8+10-02-2012+minutes.doc < ang=EN-US>As for the rest please check and perform APs as discussed and reported. Bear in mind the deadline for WP8 finalized contribution to D2.3 remains February 17th and as such everything should be settled from our security side by February 16th EOB at the latest. Counting on you all to meet the set deadline Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Feb 14 10:14:58 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 14 Feb 2012 10:14:58 +0100 Subject: [Fiware-security] TR: [Fiware] Forge back to normal Message-ID: <10296_1329210899_4F3A2613_10296_12709_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206457FAEC3@THSONEA01CMS04P.one.grp> FYI De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo Envoy? : mardi 14 f?vrier 2012 10:01 ? : fiware at lists.fi-ware.eu Objet : [Fiware] Forge back to normal Dear all, After the maintenance works tonight, eveything should be as expected. You can use the forge normally. Note that: * Any changes in docman or tracker after Thursday at 12:16am are lost (we warned you in advance so this shouldn't be a problem) * Mediawiki and SVN should not be affected by the maintenance operations Please let me know if you detect unexpected behaviour or any kind of data loss or corruption. It should not be the case, this was thoroughly tested beforehand. Needless to say, you can use all the tools normally from now on. Thanks your patience. 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From Richard.Egan at uk.thalesgroup.com Wed Feb 8 11:13:27 2012 From: Richard.Egan at uk.thalesgroup.com (Egan, Richard) Date: Wed, 8 Feb 2012 10:13:27 -0000 Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference examp le + how to instructions Message-ID: Slim, Francesco for your information, in preparation for D2.3 and specifically the Optional GEs, TRT UK are preparing a contribution for the content based security OGE on the wiki. There should be a good version available by the end of the week, but here is a link to the work in progress. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI WARE.OpenSpecification.Security.Optional_Security_Enablers.Content_Based_Sec urity We will be trying to follow the TID guidelines. As there is not so much time left, if you have any comments on this approach, please let us know as soon as possible 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: 06 February 2012 19:13 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference example + how to instructions Importance: High Dear All After a quick scan through WP8 input to D2.3 I noticed that most of the inputs reported there were still not conformant to what was expected. This despite reference example and instructions already provided. As such I'd like here to remind you (especially Task leads and GE ownenrs) where to find the reference example to follow for your input. You may find it here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI WARE.OpenSpecification.Data.QueryBroker Please also refer to instructions/guidelines Juanjo provided especially for what concerns content of each of the sections. Available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/In structions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Counting on you to follow these guidelines and follow reference example. Best Regards, Pascal Please consider the environment before printing a hard copy of this e-mail. The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)118 986 8601 and delete it and all copies from your system. Thales Research and Technology (UK) Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 774298 Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Richard.Egan at uk.thalesgroup.com Wed Feb 8 12:37:22 2012 From: Richard.Egan at uk.thalesgroup.com (Egan, Richard) Date: Wed, 8 Feb 2012 11:37:22 -0000 Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference examp le + how to instructions Message-ID: Slim, actually I did not realise that we should not put Year 2 items in this version, but I agree to leave it out for this version. We can focus on other things for the rest of Year 1 Thanks Richard _____ From: TRABELSI, Slim [mailto:slim.trabelsi at sap.com] Sent: 08 February 2012 11:00 To: Egan, Richard; DI CERBO, Francesco Cc: fiware-security at lists.fi-ware.eu; Waller, Adrian Subject: RE: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference examp le + how to instructions Hi Richard, Just for clarification, the content based security enabler was planned for year two. At least this is what we agreed during the last meetings. In that case there should not be an entry in the D2.3 architecture deliverable. Are you sure that you want to send it in this deliverable knowing that there are no black log entries no planning for this asset ? On my opinion we should keep it for the next release of the generic enable it was planned, we already have two others assets for year two. Thank you Best Slim ===================================== Dr Slim Trabelsi Senior Researcher Security & Trust SAP Labs France 805, Av du Docteur Maurice Donat 06250 Mougins, France T +33 4 92 28 63 45 M +33 6 11 99 85 79 www.sap.com From: Egan, Richard [mailto:Richard.Egan at uk.thalesgroup.com] Sent: mercredi 8 f?vrier 2012 11:13 To: TRABELSI, Slim; DI CERBO, Francesco Cc: fiware-security at lists.fi-ware.eu; Waller, Adrian Subject: RE: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference examp le + how to instructions Slim, Francesco for your information, in preparation for D2.3 and specifically the Optional GEs, TRT UK are preparing a contribution for the content based security OGE on the wiki. There should be a good version available by the end of the week, but here is a link to the work in progress. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI WARE.OpenSpecification.Security.Optional_Security_Enablers.Content_Based_Sec urity We will be trying to follow the TID guidelines. As there is not so much time left, if you have any comments on this approach, please let us know as soon as possible 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: 06 February 2012 19:13 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE - WP8 Input to D2.3 Reference example + how to instructions Importance: High Dear All After a quick scan through WP8 input to D2.3 I noticed that most of the inputs reported there were still not conformant to what was expected. This despite reference example and instructions already provided. As such I'd like here to remind you (especially Task leads and GE ownenrs) where to find the reference example to follow for your input. You may find it here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FI WARE.OpenSpecification.Data.QueryBroker Please also refer to instructions/guidelines Juanjo provided especially for what concerns content of each of the sections. Available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/In structions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions Counting on you to follow these guidelines and follow reference example. Best Regards, Pascal Please consider the environment before printing a hard copy of this e-mail. The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)118 986 8601 and delete it and all copies from your system. Thales Research and Technology (UK) Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 774298 Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273 -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.woods at intel.com Wed Feb 8 10:03:07 2012 From: chris.woods at intel.com (Woods, Chris) Date: Wed, 8 Feb 2012 09:03:07 +0000 Subject: [Fiware-security] User Story In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A66CE5D4@DEMUEXC027.nsn-intra.net> References: A<518_1328209458_4F2ADE32_518_15182_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206454AD63D@THSONEA01CMS04P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A66CE5D4@DEMUEXC027.nsn-intra.net> Message-ID: <6561D414F94B1346BD04F33925F8BFE19E13F0@IRSMSX101.ger.corp.intel.com> Including Pier (WPL WP7), Hans (WPA WP7). Agreed. The scenario presented is simplistic. But the enabling infrastructure is required for other scenarios. CDI Needs a remote management service for devices. This is a method for other GE's to contact a client. In addition to "remote wipe & lock". It also provides: ? Application developers with the ability to execute code remotely on a CDI device ? Management of individual application settings and configuration ? Remote application management - A rogue application is installed on a device and needs to be uninstalled (a mitigation step). ? Statistics - how many devices have application X installed? The following is our working FMC diagram for CDI. Note the Non-CDI GE which communications via a Rest interface to the CDI's remote management component, which in turn communications with a CDI device. This 3 way communication needs to be secured, to ensure that the client device can trust the management service and the management service can trust the device, and the user has given permission for the none CDI GE to communicate directly with the device. [cid:image002.png at 01CCE640.78C3B910] Thanks, Chris From: Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Sent: Friday, February 03, 2012 7:51 AM To: ext BISSON Pascal; Wolfgang.Steigerwald at telekom.de; Woods, Chris Cc: fiware-security at lists.fi-ware.eu Subject: AW: [Fiware-security] User Story Hi all, such service is already offered for the IPhones and as well some other brands. So not a very new stuff. Let's discuss this in our telco today. PS: Wolfgang, please look at my emails which I sent to you and received so far no answers :( Greetings Robert Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von ext BISSON Pascal Gesendet: Donnerstag, 2. Februar 2012 20:04 An: Wolfgang.Steigerwald at telekom.de; chris.woods at intel.com Cc: fiware-security at lists.fi-ware.eu Betreff: Re: [Fiware-security] User Story Hi Wolfgang, Sounds good let's now consider reporting this user story on the backlog at the right place. Best Regards, Pascal De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : jeudi 2 f?vrier 2012 18:21 ? : BISSON Pascal; chris.woods at intel.com Cc : fiware-security at lists.fi-ware.eu Objet : User Story Hello Pascal, hello Chris, here is the user story we talked about in Madrid. User Story: Managing Service To help users to manage the software on their mobile devices or help to find their lost devices a service provider (SP) offers the "Managing Service" (MS). To use the service an user must register himself and the device to the service. When the user want's later use the service the SP redirect the user to the users Identity Provider (IdP) where the he has to authenticate himself. If the device gets lost the MS can activate the GPS module to locate the device or ask the Telco-Operator where the device is located. Therefore the MS authenticates to the device or the operator and delivers the service. Mit freundlichen Gr??en / Viele Gr??e / Best Regards Wolfgang Deutsche Telekom AG T-Labs (Research & Innovation) Dipl.-Inform. Wolfgang Steigerwald Winterfeldtstr. 21, 10781 Berlin +4930835354287 (Tel.) +4930835358408 (Fax) E-Mail: wolfgang.steigerwald at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Claudia Nemat, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.emz Type: application/octet-stream Size: 26253 bytes Desc: image001.emz URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 28774 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oledata.mso Type: application/octet-stream Size: 110230 bytes Desc: oledata.mso URL: From francesco.di.cerbo at sap.com Wed Feb 15 15:17:55 2012 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Wed, 15 Feb 2012 15:17:55 +0100 Subject: [Fiware-security] Urgent Reminder: T8.4 contribution to D2.3 Message-ID: <71C0C7C7A712EE4CA636EDFD663B4E27036C145114@DEWDFECCR09.wdf.sap.corp> Hello all, Just a reminder, the deadline for this activity is TOMORROW 16th EOB. *PLEASE REMEMBER TO USE THE OFFICIAL WIKI PAGE FOR THE SUBMISSION:* https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3 best regards, Francesco > -----Original Message----- > From: DI CERBO, Francesco > Sent: vendredi 10 f?vrier 2012 12:29 > To: 'Jean-Yves Marion'; 'GASPARD Lucie'; LELEU Philippe > (philippe.leleu at thalesgroup.com) > Cc: Alexandre Boeglin > (alexandre.boeglin at inria.fr); BISSON Pascal; TRABELSI, Slim; Guillaume > BONFANTE (Guillaume.Bonfante at loria.fr) > Subject: RE: URGENT: important FI-WARE T8.4 request > > One last information: > > In case of doubt on which contents to include, it is also possible to refer to > other chapter's contributions: > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware- > private/index.php/FiwareDeliverableD2.3 > > > best regards, > > Francesco > > > -----Original Message----- > > From: DI CERBO, Francesco > > Sent: vendredi 10 f?vrier 2012 12:25 > > To: 'Jean-Yves Marion'; 'GASPARD Lucie'; LELEU Philippe > > (philippe.leleu at thalesgroup.com) > > Cc: Alexandre Boeglin > > (alexandre.boeglin at inria.fr); BISSON Pascal; TRABELSI, Slim; Guillaume > > BONFANTE (Guillaume.Bonfante at loria.fr) > > Subject: RE: URGENT: important FI-WARE T8.4 request > > > > Dear T8.4 contributors, > > > > I am writing you to inform that, from the management of FIWARE > > (Telefonica), we received a modification of the original request. For your > > information, a number of complaints have been raised to project > > management/Telefonica during our last CC about this. > > > > Now, coming to the request, we are asked for making a number of actions, > > that are later described. In order to minimize the overall bureaucratic > effort, > > also with respect to the upcoming WP8 D8.1 deliverable at M12, Pascal > Bisson > > proposed a "impact mitigation plan", to better organize our effort. The list > of > > actions that follows, contains indications also coming from this plan: > > > > 0) we should have 2 different versions of our contributions: a "reduced" > text, > > still compliant with the instructions mentioned in #2, but that delivers > > contents in a more synthetic way, and a "complete" text, that should be > kept > > in the private security wiki. The synthetic text shall contain, for instance, > only > > the most relevant API, and if possible, in a "narrative" form. The full > > description shall then be used for our WP8 deliverable. > > > > 1) we should put the synthetic description of our assets in the following > > page, in the respective subpages: > > > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware- > > > private/index.php/FIWARE.OpenSpecification.Security.Optional_Security_En > > ablers > > > > 2) in putting our information, we should follow these instructions (already > > sent by Pascal some days ago, but updated yesterday) > > > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware- > > private/index.php/Instructions_on_how_to_develop_FI- > > WARE_Chapter_Architecture_Descriptions > > > > Hope these instructions are clear enough, in case please do not hesitate to > > contact me again. > > > > Best regards, > > > > Francesco > > > > > -----Original Message----- > > > From: DI CERBO, Francesco > > > Sent: lundi 6 f?vrier 2012 11:42 > > > To: 'Jean-Yves Marion'; 'GASPARD Lucie'; LELEU Philippe > > > (philippe.leleu at thalesgroup.com) > > > Cc: Alexandre Boeglin > > > (alexandre.boeglin at inria.fr); BISSON Pascal; TRABELSI, Slim; Guillaume > > > BONFANTE (Guillaume.Bonfante at loria.fr) > > > Subject: URGENT: important FI-WARE T8.4 request > > > > > > Dear FI-WARE T8.4 contributors, > > > > > > I am writing you with respect to the Action Point "2-WP8 Contrib to D2.3" > > > contained in the attached document; it contains the minutes of the last > CC > > > for FIWARE WP8 chapter. > > > > > > As such, following a request sent by the project board, I inform you that it > > > should be necessary to update the wiki page associated to your services, > > > following the Telefonica-provided QueryBroker template: > > > > > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware- > > > private/index.php/FIWARE.OpenSpecification.Data.QueryBroker > > > > > > As a reminder, your pages can be found under: > > > > > > https://forge.fi- > > > > > > ware.eu/plugins/mediawiki/wiki/security/index.php/FIWARE.OpenSpecificat > > > ion.Security.Optional_Security_Enablers > > > > > > As you can see, I already uploaded your API on the wiki page. It would be > > up > > > to you to fill in the missing parts, following the already mentioned > > > QueryBroker example. In particular, please upload your FMC architecture > > > diagrams (block diagrams, and class, activity and sequence diagrams) > > > together with required descriptions and any other missing information > > (e.g., > > > technical requirements and so on). > > > > > > @INRIA: during the last GA in Madrid, a number of questions were raised > > > about your diagrams; in particular, I was wondering if they were depicting > > > correctly the deployment scenario that you are proposing for FI-WARE > > (e.g., > > > an "agent" to be deployed on the testbed, and your "real" malware > > services > > > in your premises) . I kindly ask to Alexandre to let us have a clarification > on > > > this point, and in case to update your diagrams and to upload them on > the > > > wiki page. > > > > > > Hard deadline for this activity has been set on February 16th EOB, as on > the > > > 17th there will be a final review of all inputs. > > > > > > We are counting on you to pass smoothly this important review. > > > > > > Best regards, > > > > > > Francesco > > > ___ > > > > > > Francesco Di Cerbo, PhD > > > 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 pascal.bisson at thalesgroup.com Wed Feb 15 18:28:01 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 15 Feb 2012 18:28:01 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] IMPORTANT: Reference example on Main Interactions section to be followed Message-ID: <4647_1329326881_4F3BEB21_4647_5915_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206458B8B70@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 Juanjo Hierro Envoy??: mercredi 15 f?vrier 2012 10:52 ??: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet?: [Fiware-wpl] IMPORTANT: Reference example on Main Interactions section to be followed Hi, While reviewing the different drafts of the "Architecture Description" chapters, I have found that many of the descriptions of "Main Interactions" is quite poor. We have developed a good reference example for this kind of sections. You can find it at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 If you have followed the reference example provided initially based on the CORBA specifications as well as the guidelines already provided, you should not have anything too far from this, but unfortunately, I'm discovering that this is not the case in many of the GE Architecture Descriptions. The guidelines for editing the "Architecture Description" deliverable have been updated accordingly. I encourage you to review them carefully and add any question on teh FAQ section you may have. You may find them at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions 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) 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-wpl mailing list Fiware-wpl at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-wpl From pascal.bisson at thalesgroup.com Fri Feb 17 09:38:34 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 Feb 2012 09:38:34 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] Privacy of Documents on the Forge Message-ID: <2680_1329467915_4F3E120B_2680_17448_1_CBBCD6C304123F4AB23FAAE3055C8C0E02064592A7B0@THSONEA01CMS04P.one.grp> FYI. WP8 - FI-WARE Security (all private in this chapter) 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 16 f?vrier 2012 18:03 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Privacy of Documents on the Forge Dear all, As you all know (see tutorial "How to share documents with the FusionForge docman system" ) the docs are uploaded and then have to be marked as private if that's what you wish. If not , they will be public on the internet. I logged out of the forge and checked what an anonymous user would see on the internet and I saw a number of things that I do not know to what extent are intentional. You can verify by yourselves by logging out of the forge and going to the docman of your chapter. I enclose a capture for each one of the chapters for your convenience. If anything has to be changed, try yourselves. Failing this, go to your WPL/WPA, they should be able to change the settings of a given document to private. Conversely, if something should be public and is maked as private now, he can change it as well. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE_Public_doc_visibility.pdf Type: application/pdf Size: 86525 bytes Desc: FIWARE_Public_doc_visibility.pdf URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Fri Feb 17 10:01:44 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 Feb 2012 10:01:44 +0100 Subject: [Fiware-security] WP8 - Today's Weekly audio conf (Agenda) Message-ID: <28909_1329469306_4F3E177A_28909_9077_1_CBBCD6C304123F4AB23FAAE3055C8C0E02064592A8A8@THSONEA01CMS04P.one.grp> Dear All, Here is the Agenda for our weekly audio conference of today: 1. AP as per last minutes / also GA 2. Review of WP8 contrib to D2.3 (per GE) 3. Update on standardization deliverable 4. Tracker (report on achievements and ongoing work) 5. Other topics Will open the audio conf now ! (same details as usual to join) Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Feb 17 11:18:39 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 Feb 2012 11:18:39 +0100 Subject: [Fiware-security] (no subject) Message-ID: <30257_1329473921_4F3E2981_30257_2424_1_CBBCD6C304123F4AB23FAAE3055C8C0E02064592AC1E@THSONEA01CMS04P.one.grp> FYI -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Audio-conf WP8 10-02-2012 minutes.doc Type: application/msword Size: 35840 bytes Desc: Audio-conf WP8 10-02-2012 minutes.doc URL: From pascal.bisson at thalesgroup.com Fri Feb 17 14:44:48 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 17 Feb 2012 14:44:48 +0100 Subject: [Fiware-security] TR: WP8 - Today's Weekly audio conf (Agenda) Message-ID: <16385_1329486292_4F3E59D4_16385_3264_1_a1c53ef6-b551-4c5a-87d6-bde9d3d61e02@THSONEA01HUB05P.one.grp> Short minutes of today's audio conference: Participants: Pascal Bisson (Thales -TS) Richard Egan (Thales - TRT-UK) Slim Trabelsi (SAP) Francesco Di Cerbo (SAP) Wolfgang Steigerwald (DT) Alexandre Boeglin (INRIA) Robert Seidl (NSN) Antonio Garcia Vazquez (ATOS) Michael Osborne (IBM) Anja Lehmann (IBM) Not present : Xavier Aghina (FT-Orange) The audio conference was mainly devoted to review status of Security GEs' architecture specifications contributed by WP8 to D2.3 deliverable attached to WP2 and to be released according to the set deadline (i.e. February 17 so EOB today!). Minutes: ? Review of WP8 contrib to D2.3 (per GE) 1. Security Monitoring GE (THA/Daniel) ? ToC (Table of Content) Ok ? Orange, ATOS to complete with section elements that are still missing (e.g. basic design principles) ? INRIA to urgently contribute their input to each of the sections ? Thales to perform final check by EOB today 2. Context-based security & Compliance (ATOS/Antonio) ? To complete with text missing and perform final check by EOB today 3. IdM GE (NSN/Robert) ? To introduce ToC (used for each and every GE): Overview, Basic concepts, Main interaction, Design principles (see guidelines) ? To follow it for each of the sections to harmonize things among GE description ? To add textual input provided by DT ? To add short text stressing there would be an interface to transparently access to IdM GE (NSN) or IdM (GE) DT ? To perform final check by EOB today 4. Privacy GE (IBM/Anja+Michael) ? Add ToC (in view of sections that can be covered in the context of this GE) ? Add a convincing text to justify why not all sections are covered (being said this GE is not as the others) ? To perform final check by EOB today 5. Data Handling GE ? Check ToC against proposed one with the four subsection (consider to adapt it or not) ? To perform final check by EOB today 6. Optional Security Services ? SSS - Thales (Philippe) to complete with missing elements asap ? Morphus Inria (Alexandre) to provide the requested description as per template and instructions already provided ? SAP to remove Content-based security description from this private FI-WARE wiki and add it o private FI-WARE Security wiki where work would be continued by TRT-UK. ? Update on standardization deliverable ? WP8 contribution was assembled by WPL (Pascal) with input from ALL (especially Task leads and GE owners although not uniquely) and released for internal review. ? It is now considered as final and would be as such sent by EOB today to NEC (Lindsay Frost) in charge of this deliverable in the context of its WP11 involvement. ? Tracker (report on achievements and ongoing work) ? No addressed. AP - Each of the task lead to report on progress in handling tickets by mail addressed to WPL/WPA (Pascal/Daniel). Would be addressed at next audio conference. ? Other topics ? WP8 Plenary Meeting 1. Provisional dates - April 2-3, 2012 (to be confirmed at next audio conference) 2. Location: Paris (ThereSIS - Palaiseau) Best Regards, Pascal De : BISSON Pascal Envoy? : vendredi 17 f?vrier 2012 10:02 ? : fiware-security at lists.fi-ware.eu Objet : WP8 - Today's Weekly audio conf (Agenda) Dear All, Here is the Agenda for our weekly audio conference of today: ? AP as per last minutes / also GA ? Review of WP8 contrib to D2.3 (per GE) ? Update on standardization deliverable ? Tracker (report on achievements and ongoing work) ? Other topics Will open the audio conf now ! (same details as usual to join) Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Feb 21 11:06:52 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 21 Feb 2012 11:06:52 +0100 Subject: [Fiware-security] TR: Comments on Security Architecture Description Chapter Message-ID: <31858_1329818817_4F436CC1_31858_1956_1_bf7a5e61-6d96-4938-a652-0dcec10b36f8@THSONEA01HUB05P.one.grp> Dear Colleagues, I'm just forwarding you this email I got from our Juanjo who as FI-WARE CA reviewed our Security Chapter contribution to D2.3a Architecture Specifications. I'd like here each of the task leads and GE owners to process those comments promptly not to delay any more release of D2.3 from the perspective of our Security Chapter. Comments have been enough detailed by Juanjo to be addressed by each GE owners as follow. 1.1 Monitoring GE (Thales - Daniel/Philippe/Pascal) 1.2 Context-based security & compliance GE (Atos - Antonio) 1.3 Identity Management GE (NSN - Robert) 1.4 Privacy Management GE (IBM - Anja/Michael) 1.5 Data Handling GE (SAP - Slim/Francesco) 1.6 Optional Security Enablers/Services (SAP - Slim/Francesco) Counting now on each Task leads & GE owners to process those comments asap. Best Regards, Pascal De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : mardi 21 f?vrier 2012 05:07 ? : BISSON Pascal; GIDOIN Daniel Cc : jhierro >> "Juan J. Hierro" Objet : Comments on Security Architecture Description Chapter Dear Pascal and Daniel, Please find below the comments on the Security Chapter. While for the rest of the chapter, things are progressing way and you have made a good effort, I have to say that the status of the Description regarding the Identity Management GE worries me a lot. Don't hesitate to formulate any question or doubt you may have. Cheers, -- Juanjo 1. Major comments 1.1 Monitoring GE The Architecture Description is relatively well aligned with the guidelines provided for the Architecture Description deliverable except for the "Design Principles" section (contents placed in that section seems to be there because there was no other good places to place them). Once we fix the contents of the "Design Principles" section, I would start carrying up a final peer review (looking into this GE more closely than what I have been able to). In a first approach, it seems a little bit strange that the structure of the section regarding "Main concepts" equals the one for "Main Interactions". I would expect that the "Main interactions" section would be structured into sections linked to the different processes that take place during Security Monitoring, but maybe their description can be structured in terms of components involved. On the other hand, it seems like description of some main interactions (Service Level SIEM) could be further elaborated including some sequence diagrams. There is also no reference to specific interface names and specific operations but I guess this GE will be mostly used by administrators/operators of a FI-WARE Instance who will make use of the User Interface of related admin tools instead of applications which make use of APIs. Some figures may need to be converted to follow FMC notation. 1.2 Context-based security & compliance It seems like the Architecture Description of this GE follows the guidelines provided but there is a mismatch in the table of contents ... The section titled "Main Interactions" looks like it should be titled "Context-based security & compliance architecture" while the sections under "sequence diagrams" within the "Basic Design Principles" section would actually fit better as contents of the "Main Interactions" section. Contents of the remaining of section "Design Principles" look more like the detailed description of data exchanged in some of the interactions described in the sequence diagrams ... however, the relationship is not so explicit because the text in the descriptions of sequence diagrams does not always include a reference to the request/response being issued. I see to alternatives to deal with this editorially: * Add the names of the specific operation request / responses within the sequence diagram descriptions and then endup the "Main Interactions" sections with a subsection titled "Basic Data Structures", elaborating on the detailed description of arguments linked to operation request/responses being referred in the interactions. * Add the names of the specific operation request / responses within the sequence diagram descriptions and enrich then with text describing the data structures linked to those operation request/responses (e.g., " invokes the request passing the , and as arguments") Probably the first option is easier to implement and I would recommend it. The figure on the Architecture should be converted to follow FMC notation. 1.3 Identity Management GE While this is one of the core GEs in the Security Chapter, the description is rather poor. The "Basic Concepts" section doesn't say anything relevant and the "Main Interactions" section is merely a sequence of pictures with no explanation (btw, figures do not follow FMC conventions) . I don't understand what "Design Principles" we are trying to describe with contents on that section. Improvement of the Architecture Description for this GE requires urgent and immediate attention. 1.4 Privacy Management GE It is stated that this GE doesn't go for the first release, but providing some info about what is expected in future releases is necessary. In this respect, the info provided is helpful and I would consider this GE properly covered. 1.5. Data Handling GE I would review writing of the example scenario. Some comments (part of them editorial, but I have decided to compile all them together here): * First bullet, I guess that explaining that the Clique social network has been developed within the PrimeLife project doesn't add any value. * Also first bullet, we introduce the role of "Data Controller" ... I guess it would be nice to introduce the concept of "Data Controller" someway in the paragraph of the Description section (section previous to the example). Would it match the backend part of the "Data Handling GE" ? * Third bullet: * you refer to the "PrimeLife Privacy Tuner" ... is that a tool linked to the Data Handling GE ? If so, I would use the term "Data Handling Privacy Tuner" instead. Would "PPL Privacy Tuner" work, given the fact that use the term "PPP Privacy Engine" in the fourth bullet ? * you say: "This tuner is a graphical tool used to edit Privacy preferences in PPL language defined in the deliverable" ... is the usage of the term "deliverable" appropiate here or is it the result of copying&pasting from some document in the PrimeLife project ? * my understanding is that one of the things Alice would be able to configure using the Privacy Tuner would be what domain would be allowed to access data ... (or what rules will determine whether a domain would be allowed to access data). If this is correct, I would mention it to establish a better link with what is being said in the fourth bullet. This would make the example easier to follow. * Fourth bullet: * where is the PPL Privacy Engine running ? My understanding is that it runs on Alice's machine but if so, please say it explicitly. * simply editorial: should be "Alice's machine" instead of "Alice machine". * you say: "the engine will enforce the access control rules related to the requested data". If I understand it right, these access control rules would refer to rules setup by Alice using the Privacy Tuner ... If this is correct, I would mention it. Something like: " the engine will enforce the access control rules related to the requested data that were programmed by Alice using the PPL Privacy Tuner" * you say: " If the domain is allowed to access this data the engine match the privacy policy of the website with the preferences of Alice" ... where are the preferences of Alice configured ? My understanding is that it is also through the Privacy Tuner. If this is correct, I would mention it. Something like: "If the domain is allowed to access this data the engine match the privacy policy of the website with the preferences of Alice, also configured through the PPL Privacy Tuner" * Fifth bullet ... It is said: "Alice has the possibility to decide if she accepts or refuses to send her data". If my understanding is correct, it should not only be that. She should also be able to validate the privacy policy of the website (i.e., which data would be sent and what will it be exclusively used for). If so, I would mention it explicitly. * Sixth bullet ... I believe it would be nice to explain where both the sticky policy and Alice's data will be stored. You refer to "the server" but ... what is that server ? Will it be in the server where the backend of the Data Handling GE is running ? If so, mention it explictly. It would be worth mentioning, btw, maybe not in this bullet but somewhere, where can such Data Handling GE backend be running. Does it necessarely have to be collocated in the backend of the Clique portal ? Could be somewhere else, providing its functionality "as a Service" ? If it may go somewhere else, provided "as a Service", then I would explain this is a possibility. * Eight bullet ... (just editorial) You say: " The policy engine of clique.primelife.eu will match the privacy policy of travel.example.com with the sticky policy related to the e-mail of Alice (step 8), and will check if the sticky policy allows to forward for the purpose of statistics for example" ... I guess it would be better to say "... (step 8), checking if the sticky policy allows to forward Alice's e-mail address for the purpose of statistics, for example." * About what we describe in the last bullet ... how it is prevented that the travel agency doesn't make a wrong usage of Alice's data ? Could it be someway ? If so, it would be worth explaining ... There is no section on "Basic Concepts". Probably it would make sense to translate some of the content in the Appendix here (if you decide to move everything, just the reference would be kept at the end). I would also suggest to elaborate on the following concepts: * PPL and PPI * PPL Privacy Tuner tool Figure on Architecture should be adapted to follow FMC notation. On the other hand, it would be nice to illustrate there: * What is the role of the Privacy Tuner ? Please try to illustrate it * Is the left big grey box a description of the architecture linked to the "PPL Privacy Engine" ? If so, name it accordingly. Otherwise ... what components would be linked to the PPL Privacy Engine ? Main interactions after the Architecture figure: * You describe interactions in terms of operations described in some sort of description of a RESTful binding. This doesn't follow the reference example provided as guidelines. As a result, it is too austere and doesn't elaborate on who invokes an operation, for example. Sequence diagrams would be useful. * The suggested structure for the "Main Interactions" section is fine though: * Data subject side: * Managing PII * Managing Preference Groups * Data controller side: * Uploading resource data and policy * Uploading PII * PII downstream usage request for a single PII 1.6 Optional Security Enablers: I understand the Architecture Description of these enablers, and particularly adaption to published guidelines, is under way. Therefore, I will wait until they are more elaborated. 2. Minor comments (some editorial): 2.1 Monitoring GE 2.1.1 Service Level SIEM: * I would recommend explaining what SIEM stands for 2.2 Data Handling GE * I may be wrong but it seems to me like there is something missing or wrong (from an editorial point of view) in the following sentence: "It supports integrated data handling, in particular through two-sided detailed data handling, that takes into account specific preferences/policies expressed using the PPL language, based on XACML". * It would be nice to describe what PPL stands for, the first time this acronym is used. Same for PII. -- 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) 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 Tue Feb 21 17:19:55 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 21 Feb 2012 17:19:55 +0100 Subject: [Fiware-security] FI-WARE Security - Friday 24th Audio conference cancelled Message-ID: <19096_1329841201_4F43C431_19096_11042_1_661913a7-9e20-4496-8ada-3b483a90cc2b@THSONEA01HUB05P.one.grp> Dear All, This just to let you know that our audio conference on Friday is cancelled due to another meeting I'm chairing that day. In the meantime I prefer to have you/us processing comments we got from TID on our security input to D2.3 in order to close it the sooner the better (preferably be end of this week). Next audio conference will thus be next Friday and will be chaired by Daniel. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Tue Feb 21 22:22:32 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Tue, 21 Feb 2012 22:22:32 +0100 Subject: [Fiware-security] FI-WARE Security - Friday 24th Audio conferencecancelled In-Reply-To: A<19096_1329841201_4F43C431_19096_11042_1_661913a7-9e20-4496-8ada-3b483a90cc2b@THSONEA01HUB05P.one.grp> References: A<19096_1329841201_4F43C431_19096_11042_1_661913a7-9e20-4496-8ada-3b483a90cc2b@THSONEA01HUB05P.one.grp> Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A67972E8@DEMUEXC027.nsn-intra.net> HI Pascal, sorry the email is not clear for me. In the first sentence you are saying that the Friday meeting this week is cancelled. The last sentence is saying that the Friday meeting this week will be chaired by Pascal. So, do we have a meeting this week, or is the next meeting next week? Many thanks for the clarification Robert From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext BISSON Pascal Sent: Tuesday, February 21, 2012 5:20 PM To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE Security - Friday 24th Audio conferencecancelled Importance: High Dear All, This just to let you know that our audio conference on Friday is cancelled due to another meeting I'm chairing that day. In the meantime I prefer to have you/us processing comments we got from TID on our security input to D2.3 in order to close it the sooner the better (preferably be end of this week). Next audio conference will thus be next Friday and will be chaired by Daniel. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Feb 22 09:30:09 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 22 Feb 2012 09:30:09 +0100 Subject: [Fiware-security] FI-WARE Security - Friday 24th Audio conferencecancelled In-Reply-To: <9739B018F0466A4CAB10A9DABBEBF5A67972E8@DEMUEXC027.nsn-intra.net> References: A<19096_1329841201_4F43C431_19096_11042_1_661913a7-9e20-4496-8ada-3b483a90cc2b@THSONEA01HUB05P.one.grp> <9739B018F0466A4CAB10A9DABBEBF5A67972E8@DEMUEXC027.nsn-intra.net> Message-ID: <18657_1329899415_4F44A797_18657_6671_1_49cde273-69f5-4013-a950-98f0149cbc65@THSONEA01HUB06P.one.grp> Audio conf this Friday (24/02/2012) is cancelled Next audio conf would be Friday next week 02/03/2012 (this time Chaired by Daniel in cc). Hope I have clarified. Regards, Pascal De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com] Envoy? : mardi 21 f?vrier 2012 22:23 ? : BISSON Pascal; fiware-security at lists.fi-ware.eu Objet : RE: [Fiware-security] FI-WARE Security - Friday 24th Audio conferencecancelled HI Pascal, sorry the email is not clear for me. In the first sentence you are saying that the Friday meeting this week is cancelled. The last sentence is saying that the Friday meeting this week will be chaired by Pascal. So, do we have a meeting this week, or is the next meeting next week? Many thanks for the clarification Robert From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext BISSON Pascal Sent: Tuesday, February 21, 2012 5:20 PM To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] FI-WARE Security - Friday 24th Audio conferencecancelled Importance: High Dear All, This just to let you know that our audio conference on Friday is cancelled due to another meeting I'm chairing that day. In the meantime I prefer to have you/us processing comments we got from TID on our security input to D2.3 in order to close it the sooner the better (preferably be end of this week). Next audio conference will thus be next Friday and will be chaired by Daniel. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavier.aghina at orange.com Fri Feb 24 18:17:51 2012 From: xavier.aghina at orange.com (xavier.aghina at orange.com) Date: Fri, 24 Feb 2012 18:17:51 +0100 Subject: [Fiware-security] vacation Message-ID: Hello everyone, for your information I will be on leave until March 5, good luck to you for the next phone call. BRGDS. Xavier Aghina FT/OLNC/RD/MAPS/STT/NDS Ing?nieur de Recherche en S?curit? t?l. 01 45 29 81 59 xavier.aghina at orange.com -------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1081 bytes Desc: image002.gif URL: