From pascal.bisson at thalesgroup.com Mon Oct 1 09:59:25 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 1 Oct 2012 09:59:25 +0200 Subject: [Fiware-security] FI-WARE - WP8 Message-ID: <31385_1349078368_50694D60_31385_11034_1_e96d8ad6-9585-43d8-a26a-b7c3bc0317ea@THSONEA01HUB06P.one.grp> Dear All, Minutes of last audio conf have now been uploaded. You may reach them at: https://forge.fi-ware.eu/docman/view.php/19/1330/FI-WARE_WP8_Minutes_28_09_12.doc Please check and perform your actions. @Task leads don't forget to update the tracker with work items and user storis in scope of this month Sprint (October). Also drop me and Daniel an email once done with tickets created. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 1 10:56:03 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 1 Oct 2012 10:56:03 +0200 Subject: [Fiware-security] FI-WARE 2nd peer review of Security Chapter (outcomes and request for actions) Message-ID: <7962_1349081772_50695AAC_7962_989_2_f633f5fc-1d2a-43dd-a622-893a1bb34297@THSONEA01HUB05P.one.grp> Dear All, Find attached to this email the outcomes of the 2nd peer review of Security Chapter (Architecture & Open Specifications) which has been performed this time by App Chapter (partner SAP - Andreas Klein - did perform this review). Based on this review report I will ask each of the GE owners under supervision of the task leads to which belong those GEs to address review comments , perform the necessary corrections and let me and Daniel know once done. Deadline to have it done is by Wednesday 3 EOB. SecMon GE (Thales/Daniel) Mulval -> Daniel/Kreshnik OSSIM SIEM/->Susanna SSS GE (Thales/Lucie) IdM GE (NSN/Robert) As for bad assessment we got in view of questions raised on 1.2.4 & 1.2.5 clearly stating that as their our GE description (including Open Spec) are not complete enough to: 1. allow an application developer to develop applications that will be based on the GE 2. allow a 3rd party to implement a product in compliance with the GE specifications It is stated also that "the provided templates are not sufficient to fulfil this purpose. This is not specific problem for this GE, but more a problem which impacts all GEs". This for me confirms the feeling I got that to have D3-8.1.a be accepted we should consider reviewing the template provided for these deliverables by TID. As you know there is an action for TID to deliver a new template to cover the missing points and so EC concerns that led them to reject our deliverables. In the meantime I'd like each of you as WP8 partners and especially Task leads (NSN, SAP, ATOS) and Caretakers (IBM) to contribute your view (asap) on the changes you think are needed to address (1) and (2) at least to an extend we could get our deliverable (D8.1.1) be accepted. Counting on you to address your review actions and send me your suggested changes to D8.1.1 template. Hearing from you. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WAREPeer-ReviewSecurity (2).doc Type: application/msword Size: 261120 bytes Desc: FI-WAREPeer-ReviewSecurity (2).doc URL: From pascal.bisson at thalesgroup.com Wed Oct 3 09:55:54 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 3 Oct 2012 09:55:54 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Sprints need update from partners Message-ID: <31715_1349250987_506BEFAB_31715_5791_1_180b3220-0803-4547-b6bc-f73087cb6979@THSONEA01HUB06P.one.grp> Dear Colleagues, Please, send me by email (by EOB tomorrow at the latest) list of work-items and/or user-stories you have completed during September sprint, and those you are targeting for October sprint. Obviously each of them should be linked to one of our Chapter's GE and should correspond to tickets entered on the Security Chapter (as such assuming everything is already set - documented - on the tracker, providing me with the tickets completed for September and targeted for October could be enough). Many thanks in advance for your cooperation and support. We will discuss and review those tickets at next Audio conf (planned this Friday 10am-12am). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Oct 3 18:13:18 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 3 Oct 2012 18:13:18 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Instructions to follow to restructure D8.1 and have it resubmitted Message-ID: <18552_1349280835_506C6443_18552_5159_1_a4cc45d4-2c71-4124-8aa7-ecc4e64bb334@THSONEA01HUB03P.one.grp> Dear All, Yesterday at WPL/WPA we agreed on the way proposed to re-structure the wiki pages (see presentation below for details on the proposal we all agree to follow and so Security Chapter: https://forge.fi-ware.eu/docman/view.php/7/1335/2012-10-01_FI-WARE_Resubmission_DX11.ppt Every WPL will take care of organizing the work to be done: i.e. of creating the FIWARE.OpenSpecifications.. wiki page per each of the GEs linked to his chapter. This activity should be performed by each of the Security GE owners (as already established) under supervision of the task leads. It should start on Monday October 8th and get finished by October 9th (here I can only encourage each of the Task Leads/GE owners to have this planned in advance to meet the set deadline). To create the FIWARE.OpenSpecifications.. wiki page of a given GE, you should rely on the template defined in: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php?title=Open_specification_resubmission_template That template contains precise instructions about the steps to follow. You will find there a link to an example of how the resulting page may look like. One particular question each of the GE owners should carefully handle is the Copyright section of the specifications of a given GE. That section should contain the list of copyright statements from the companies/organizations authoring the specifications. Of course, that means that Task leads/GE Owners should come with an agreement of who are the companies/organizations that should be listed as authors. On its side TID will generate the part of the wiki that will allow us to navigate directly to the GE specs and generate the FI-WARE GE Open Specifications deliverables to be resubmitted. Once all changes are verified a final peer-review on October 10th should start. TID (CA/Juanjo) will send an email with assignments for this last peer-review previous to WPLs/WPAs joint confcall on Monday October 8th. TID would like to send a note to the PO and reviewers on October 10th updating them on the results of our two first peer-reviews and the fact that they can access a revised version of the FI-WARE GE Open Specifications on the public wiki (however, the final official deliverable, in .pdf format, will be available by end of the month, incorporating results of the last, third peer-review). Because of that, each of the task leads/GE owners are asked to incorporate all changes derived as results of the two first peer-reviews (August and September) by end of this week, October 7th. If you have any particular question or concern, please let me know. If not please proceed according the plan above. IdM GE -> NSN/Robert SecMon GE -> Thales/Daniel Data Handlinge GE SAP/Slim Privacy GE -> IBM/Anja Context-based security & compliance ->ATOS/Susanna Optional Security GE -> SAP/Francesco to organize & supervise DB Anonymizer GE SAP/Francesco Secure Storage Service GE Thales/Lucie ... (other partners committed to support task lead and GE owners in their work) Of course we will further discuss this at our next audio conf (this Friday at 10am). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 4 11:55:43 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 4 Oct 2012 11:55:43 +0200 Subject: [Fiware-security] [Fiware-testbed] I: ***IMPORTANT*** Switch to Testbed V2 cockpit In-Reply-To: References: Message-ID: <23581_1349344581_506D5D44_23581_1074_1_743a46e8-2b2d-42d4-9e27-73288dd9c71e@THSONEA01HUB01P.one.grp> Dear Paolo, For Security Chapter please notice that GEs for Testbed V2 planned are indeed (btw as reported on the Technical Roadmap) I also put into brackets the owner of each of the GEs we have. New release of GEs already delivered for First Major Release: ? Security Monitoring GE [Thales] ? IdM GE [NSN owner for IDM One / DT Owner for IDM GDP] ? Data Handling GE [SAP owner] ? DB Anonymizer (Optional Security GE) [SAP owner] NB: Secure Storage Service GE - V1: pending delivery - Owner [Thales] New GEs (aka the ones due for Second Major Release of FI-WARE): ? Privacy GE (fyi : GE to be used in conjunction with IdM GE and Data Handling GE) [Owner IBM] ? Context-based security & compliance GE [Owner ATOS] A new set of so called Optional Security GEs: ? Malware Detection Service [INRIA owner] ? Android Flow Monitoring [INRIA owner] ? Content Based Security [THALES owner] Last but not least and for your information: in view of demands coming now from Use Case projects and relayed to us by Juanjo (CA) we may add a new one for Release 2: i.e. Access Control GE. Will let you know when final decision would have been made at the level of Security Chapter, since there are still discussion at the level of the team regarding overall design of that GE (that should be owned by Thales). Keep you posted. Best Regards, Pascal De : fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Paolo Zampognaro Envoy? : jeudi 4 octobre 2012 10:56 ? : fiware-testbed at lists.fi-ware.eu Objet : [Fiware-testbed] I: ***IMPORTANT*** Switch to Testbed V2 cockpit Dear All, just to communicate that the list of the new GEs, for the Testbed V2, I circulated yesterday was not complete. Below an updated list. APPS Registry, Store Business Elements & Business Models CLOUD PaaS Management Monitoring Self-Service Interfaces IoT (Backend) Device Management (Backend) Security (Backend) Advanced Connectivity (Backend) Template Handler (Gateway) Advanced Connectivity (Gateway) Security DATA Meta-Data Pre-Processing Middleware I2ND Connected Device Interfacing Network Information and Control Service, Capability, Connectivity and Control SECURITY Privacy Malware Detection Service Android Flow Monitoring Context-based security & compliance Content Based Security TOTAL......22 new GEs Cheers, Paolo ________________________________ Da: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] Per conto di Paolo Zampognaro Inviato: mercoled? 3 ottobre 2012 15.46 A: fiware-testbed at lists.fi-ware.eu Oggetto: [Fiware-testbed] ***IMPORTANT*** Switch to Testbed V2 cockpit Dear All, I want to inform all that the new Testbed cockpit wiki page [1] is up and that, from now, GEs owners have to update their information, about both GEs already installed and new ones, in this page. Basically the structure is not changed excerpt that for a new table field named "Release". In fact, since potentially updates of FI-WARE GEs on the Testbed could occur also after minor release completion or at the end of some sprints, it is useful to indicate which is the actual involved release. In this way, the "progress" field will highlight the installation status of that GE release. Obviously at the end of the Major Release completion (June 30th 2013), we will have to have all GEs, in the release 2.3.3, with progress value = 80%. Below a brief summary about the new GEs we will have to install by chapters: APPS Registry, Store CLOUD PaaS Management Monitoring Self-Service Interfaces IoT (Gateway) Advanced Connectivity DATA Meta-Data Pre-Processing Middelware SECURITY Privacy Malware Detection Service Android Flow Monitoring Content Based Security TOTAL......12 new GEs. BR, Paolo [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Implementation_Cockpit#Cockpit -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 4 14:56:54 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 4 Oct 2012 14:56:54 +0200 Subject: [Fiware-security] [Fiware-testbed] I: ***IMPORTANT*** Switch to Testbed V2 cockpit In-Reply-To: <82C2260C8A6D4538B035469C0E39295B@PAZAMPOGW> References: <23581_1349344581_506D5D44_23581_1074_1_743a46e8-2b2d-42d4-9e27-73288dd9c71e@THSONEA01HUB01P.one.grp> <82C2260C8A6D4538B035469C0E39295B@PAZAMPOGW> Message-ID: <23585_1349355428_506D87A4_23585_13003_1_18133587-16e7-4ee0-ae58-ea446d936570@THSONEA01HUB03P.one.grp> Ok, Thanks. Best Regards, Pascal De : Paolo Zampognaro [mailto:paolo.zampognaro at eng.it] Envoy? : jeudi 4 octobre 2012 12:31 ? : BISSON Pascal Cc : Fiware-security at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu; GIDOIN Daniel; 'Juanjo Hierro'; 'Miguel Carrillo'; 'Stefano De Panfilis' Objet : R: [Fiware-testbed] I: ***IMPORTANT*** Switch to Testbed V2 cockpit Hi Pascal, good your report is perfectly coherent with information reported in the Testbed V2 cockpit wiki page [1] where you can see both GEs already delivered - for which new releases are expected - and completely new GEs (marked with the label "new entry for V2") I have extracted from Roadmap page. In the list put inside the mail I wanted to alert the Testbed team about the amount of "new" GEs exclusively. As for your feedback I'll provide to update the table of cockpit by adding information about the owners and adding an "optional" label for those you call Optional Security GEs. With regard to the Access Control GE I understand that the decision to add it as a new GE is still pending so we'll wait when discussion will be closed. Thanks for your feedbacks. BR, Paolo [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Implementation_Cockpit ________________________________ Da: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Inviato: gioved? 4 ottobre 2012 11.56 A: Paolo Zampognaro Cc: Fiware-security at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu; GIDOIN Daniel; Juanjo Hierro; Miguel Carrillo; Stefano De Panfilis Oggetto: RE: [Fiware-testbed] I: ***IMPORTANT*** Switch to Testbed V2 cockpit Dear Paolo, For Security Chapter please notice that GEs for Testbed V2 planned are indeed (btw as reported on the Technical Roadmap) I also put into brackets the owner of each of the GEs we have. New release of GEs already delivered for First Major Release: ? Security Monitoring GE [Thales] ? IdM GE [NSN owner for IDM One / DT Owner for IDM GDP] ? Data Handling GE [SAP owner] ? DB Anonymizer (Optional Security GE) [SAP owner] NB: Secure Storage Service GE - V1: pending delivery - Owner [Thales] New GEs (aka the ones due for Second Major Release of FI-WARE): ? Privacy GE (fyi : GE to be used in conjunction with IdM GE and Data Handling GE) [Owner IBM] ? Context-based security & compliance GE [Owner ATOS] A new set of so called Optional Security GEs: ? Malware Detection Service [INRIA owner] ? Android Flow Monitoring [INRIA owner] ? Content Based Security [THALES owner] Last but not least and for your information: in view of demands coming now from Use Case projects and relayed to us by Juanjo (CA) we may add a new one for Release 2: i.e. Access Control GE. Will let you know when final decision would have been made at the level of Security Chapter, since there are still discussion at the level of the team regarding overall design of that GE (that should be owned by Thales). Keep you posted. Best Regards, Pascal De : fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] De la part de Paolo Zampognaro Envoy? : jeudi 4 octobre 2012 10:56 ? : fiware-testbed at lists.fi-ware.eu Objet : [Fiware-testbed] I: ***IMPORTANT*** Switch to Testbed V2 cockpit Dear All, just to communicate that the list of the new GEs, for the Testbed V2, I circulated yesterday was not complete. Below an updated list. APPS Registry, Store Business Elements & Business Models CLOUD PaaS Management Monitoring Self-Service Interfaces IoT (Backend) Device Management (Backend) Security (Backend) Advanced Connectivity (Backend) Template Handler (Gateway) Advanced Connectivity (Gateway) Security DATA Meta-Data Pre-Processing Middleware I2ND Connected Device Interfacing Network Information and Control Service, Capability, Connectivity and Control SECURITY Privacy Malware Detection Service Android Flow Monitoring Context-based security & compliance Content Based Security TOTAL......22 new GEs Cheers, Paolo ________________________________ Da: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] Per conto di Paolo Zampognaro Inviato: mercoled? 3 ottobre 2012 15.46 A: fiware-testbed at lists.fi-ware.eu Oggetto: [Fiware-testbed] ***IMPORTANT*** Switch to Testbed V2 cockpit Dear All, I want to inform all that the new Testbed cockpit wiki page [1] is up and that, from now, GEs owners have to update their information, about both GEs already installed and new ones, in this page. Basically the structure is not changed excerpt that for a new table field named "Release". In fact, since potentially updates of FI-WARE GEs on the Testbed could occur also after minor release completion or at the end of some sprints, it is useful to indicate which is the actual involved release. In this way, the "progress" field will highlight the installation status of that GE release. Obviously at the end of the Major Release completion (June 30th 2013), we will have to have all GEs, in the release 2.3.3, with progress value = 80%. Below a brief summary about the new GEs we will have to install by chapters: APPS Registry, Store CLOUD PaaS Management Monitoring Self-Service Interfaces IoT (Gateway) Advanced Connectivity DATA Meta-Data Pre-Processing Middelware SECURITY Privacy Malware Detection Service Android Flow Monitoring Content Based Security TOTAL......12 new GEs. BR, Paolo [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Implementation_Cockpit#Cockpit -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 4 15:40:39 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 4 Oct 2012 15:40:39 +0200 Subject: [Fiware-security] FI-WARE - Next Plenary meeting (Proposed dates) Message-ID: <23585_1349358069_506D91F5_23585_15197_1_8ea2b331-6083-434a-9acb-3e80e54d3e8a@THSONEA01HUB04P.one.grp> Dear All, As told I wanted to have a meeting this fall. Being said I haven't heard from TID regarding a next GA, I would propose to have our next plenary meeting on November 22 & 23 (two full days). Please book those dates confirm me your availability and if not try to find a replacement at the level of your organization. Useless to say that at this meeting I'd like each partners to be there/represented. As for the dates I have chosen there are also good in the sense we will meet before the next EC review meeting that will take place the week after. Best Regards, Pascal PS: At SAP colleagues (Slim/Francesco) please confirm me you could host our meeting in Sophia on those dates if not I would host it in Genevilliers. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 8 15:49:50 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 8 Oct 2012 15:49:50 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of the fi-ware testbed! Message-ID: <5149_1349704192_5072DA00_5149_14787_4_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8AD8802@THSONEA01CMS04P.one.grp> Please all GE owners please check and address (V1 GE owners - as for V2 GE owners please have this in mind). 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 stefano de panfilis Envoy? : lundi 8 octobre 2012 03:21 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Henar Mu?oz; fiware-testbed at lists.fi-ware.eu Objet : [Fiware-wpl] threat for the adoption of the fi-ware testbed! dear all, as you know the uc projects are studying the work we are doing and in many cases, after an initial draft evaluation, really interested in adopting in their prototypes our generic enablers. here it comes a barrier at which we did not put initially too much attention: it this the port on which the ges communicate. in several case the port is not the standad one i.e. by default, a corporate internet proxy will normally allow the standard HTTP/HTTPS ports - 80 and 443. this fact, although cannot be seen as a wrong or incomplete installation per se, basically prevents sevareal uc to effectively use and integrate the generic enablers they are interested in. since the succes of fi-ware is fully based on the adoption of our technologies (please ref. to the last review report), the above circumstance making extremely difficult the validation by the uc projects, basically poses fi-ware on the wrong side of success as the uc projects will issue the concern the testbed is not usable ...!!! to this extent i kindly ask you: 1. to change the communication port to be a standard port; 2. to complete this change by wednesday e.o.b this week (i.e. 10 october); 3. consequently to update the catalogue. this way on thursday the tesbed team can validate the changes and than i can communicate we have fixed this, i.e. to put the uc projects back in front of their responsibility. thank you in advance for your prompt collaboration on the matter. please notify henar, miguel and me when done. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From gerald.meyer at nsn.com Tue Oct 9 11:40:38 2012 From: gerald.meyer at nsn.com (Meyer, Gerald (NSN - DE/Munich)) Date: Tue, 9 Oct 2012 11:40:38 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! In-Reply-To: A<5149_1349704192_5072DA00_5149_14787_4_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8AD8802@THSONEA01CMS04P.one.grp> References: A<5149_1349704192_5072DA00_5149_14787_4_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8AD8802@THSONEA01CMS04P.one.grp> Message-ID: <66F19F4E4DB41F41A3B8A76C77A42AC4ADCFC0@DEMUEXC014.nsn-intra.net> Hi Stefano, currently at NSN we are using 1 single public IP address for a number of different lab services; therefore we have to use non-standard ports for several services. Technically it is possible to have an own IP address for the FI-WARE activities and then use standard ports, but the network rearrangement will take about 2 weeks. BR Gerald 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: Monday, October 08, 2012 3:50 PM To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Importance: High Please all GE owners please check and address (V1 GE owners - as for V2 GE owners please have this in mind). 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 stefano de panfilis Envoy? : lundi 8 octobre 2012 03:21 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Henar Mu?oz; fiware-testbed at lists.fi-ware.eu Objet : [Fiware-wpl] threat for the adoption of the fi-ware testbed! dear all, as you know the uc projects are studying the work we are doing and in many cases, after an initial draft evaluation, really interested in adopting in their prototypes our generic enablers. here it comes a barrier at which we did not put initially too much attention: it this the port on which the ges communicate. in several case the port is not the standad one i.e. by default, a corporate internet proxy will normally allow the standard HTTP/HTTPS ports - 80 and 443. this fact, although cannot be seen as a wrong or incomplete installation per se, basically prevents sevareal uc to effectively use and integrate the generic enablers they are interested in. since the succes of fi-ware is fully based on the adoption of our technologies (please ref. to the last review report), the above circumstance making extremely difficult the validation by the uc projects, basically poses fi-ware on the wrong side of success as the uc projects will issue the concern the testbed is not usable ...!!! to this extent i kindly ask you: 1. to change the communication port to be a standard port; 2. to complete this change by wednesday e.o.b this week (i.e. 10 october); 3. consequently to update the catalogue. this way on thursday the tesbed team can validate the changes and than i can communicate we have fixed this, i.e. to put the uc projects back in front of their responsibility. thank you in advance for your prompt collaboration on the matter. please notify henar, miguel and me when done. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerald.meyer at nsn.com Tue Oct 9 11:54:56 2012 From: gerald.meyer at nsn.com (Meyer, Gerald (NSN - DE/Munich)) Date: Tue, 9 Oct 2012 11:54:56 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! References: A<5149_1349704192_5072DA00_5149_14787_4_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8AD8802@THSONEA01CMS04P.one.grp> Message-ID: <66F19F4E4DB41F41A3B8A76C77A42AC4ADCFE9@DEMUEXC014.nsn-intra.net> Hi Stefano, just as an amendment: at NSN we are hosting the One-IDM GE (Identity Management) at our premises, with open and free access to all FI-WARE partners. BR Gerald From: Meyer, Gerald (NSN - DE/Munich) Sent: Tuesday, October 09, 2012 11:41 AM To: 'ext BISSON Pascal'; Fiware-security at lists.fi-ware.eu Subject: RE: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Hi Stefano, currently at NSN we are using 1 single public IP address for a number of different lab services; therefore we have to use non-standard ports for several services. Technically it is possible to have an own IP address for the FI-WARE activities and then use standard ports, but the network rearrangement will take about 2 weeks. BR Gerald 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: Monday, October 08, 2012 3:50 PM To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Importance: High Please all GE owners please check and address (V1 GE owners - as for V2 GE owners please have this in mind). 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 stefano de panfilis Envoy? : lundi 8 octobre 2012 03:21 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Henar Mu?oz; fiware-testbed at lists.fi-ware.eu Objet : [Fiware-wpl] threat for the adoption of the fi-ware testbed! dear all, as you know the uc projects are studying the work we are doing and in many cases, after an initial draft evaluation, really interested in adopting in their prototypes our generic enablers. here it comes a barrier at which we did not put initially too much attention: it this the port on which the ges communicate. in several case the port is not the standad one i.e. by default, a corporate internet proxy will normally allow the standard HTTP/HTTPS ports - 80 and 443. this fact, although cannot be seen as a wrong or incomplete installation per se, basically prevents sevareal uc to effectively use and integrate the generic enablers they are interested in. since the succes of fi-ware is fully based on the adoption of our technologies (please ref. to the last review report), the above circumstance making extremely difficult the validation by the uc projects, basically poses fi-ware on the wrong side of success as the uc projects will issue the concern the testbed is not usable ...!!! to this extent i kindly ask you: 1. to change the communication port to be a standard port; 2. to complete this change by wednesday e.o.b this week (i.e. 10 october); 3. consequently to update the catalogue. this way on thursday the tesbed team can validate the changes and than i can communicate we have fixed this, i.e. to put the uc projects back in front of their responsibility. thank you in advance for your prompt collaboration on the matter. please notify henar, miguel and me when done. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Tue Oct 9 12:48:13 2012 From: mcp at tid.es (Miguel Carrillo) Date: Tue, 09 Oct 2012 12:48:13 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! In-Reply-To: <66F19F4E4DB41F41A3B8A76C77A42AC4ADCFE9@DEMUEXC014.nsn-intra.net> References: A <5149_1349704192_5072DA00_5149_14787_4_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8AD8802@THSONEA01CMS04P.one.grp> <66F19F4E4DB41F41A3B8A76C77A42AC4ADCFE9@DEMUEXC014.nsn-intra.net> Message-ID: <507400ED.7030203@tid.es> Dear Gerald, Thanks for this, we need this work to be done asap. While I see that this is theoretically simple (2 weeks looks like a lot!) we would appreciate it if you could undertake the necessary steps to get this done internally in your company as soon as you can. One little detail : "with open and free access to all FI-WARE partners" -> can we add a "and all the PPP members (namely, the Use Case Projects)"? :) If not, we would have a problem. Once this is done, please do not forget to update the catalogue. I add Stefano in CC. Best regards, Miguel El 09/10/2012 11:54, Meyer, Gerald (NSN - DE/Munich) escribi?: Hi Stefano, just as an amendment: at NSN we are hosting the One-IDM GE (Identity Management) at our premises, with open and free access to all FI-WARE partners. BR Gerald From: Meyer, Gerald (NSN - DE/Munich) Sent: Tuesday, October 09, 2012 11:41 AM To: 'ext BISSON Pascal'; Fiware-security at lists.fi-ware.eu Subject: RE: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Hi Stefano, currently at NSN we are using 1 single public IP address for a number of different lab services; therefore we have to use non-standard ports for several services. Technically it is possible to have an own IP address for the FI-WARE activities and then use standard ports, but the network rearrangement will take about 2 weeks. BR Gerald 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: Monday, October 08, 2012 3:50 PM To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Importance: High Please all GE owners please check and address (V1 GE owners - as for V2 GE owners please have this in mind). 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 stefano de panfilis Envoy? : lundi 8 octobre 2012 03:21 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Henar Mu?oz; fiware-testbed at lists.fi-ware.eu Objet : [Fiware-wpl] threat for the adoption of the fi-ware testbed! dear all, as you know the uc projects are studying the work we are doing and in many cases, after an initial draft evaluation, really interested in adopting in their prototypes our generic enablers. here it comes a barrier at which we did not put initially too much attention: it this the port on which the ges communicate. in several case the port is not the standad one i.e. by default, a corporate internet proxy will normally allow the standard HTTP/HTTPS ports - 80 and 443. this fact, although cannot be seen as a wrong or incomplete installation per se, basically prevents sevareal uc to effectively use and integrate the generic enablers they are interested in. since the succes of fi-ware is fully based on the adoption of our technologies (please ref. to the last review report), the above circumstance making extremely difficult the validation by the uc projects, basically poses fi-ware on the wrong side of success as the uc projects will issue the concern the testbed is not usable ...!!! to this extent i kindly ask you: 1. to change the communication port to be a standard port; 2. to complete this change by wednesday e.o.b this week (i.e. 10 october); 3. consequently to update the catalogue. this way on thursday the tesbed team can validate the changes and than i can communicate we have fixed this, i.e. to put the uc projects back in front of their responsibility. thank you in advance for your prompt collaboration on the matter. please notify henar, miguel and me when done. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerald.meyer at nsn.com Tue Oct 9 15:39:46 2012 From: gerald.meyer at nsn.com (Meyer, Gerald (NSN - DE/Munich)) Date: Tue, 9 Oct 2012 15:39:46 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! In-Reply-To: <507400ED.7030203@tid.es> References: A <5149_1349704192_5072DA00_5149_14787_4_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8AD8802@THSONEA01CMS04P.one.grp> <66F19F4E4DB41F41A3B8A76C77A42AC4ADCFE9@DEMUEXC014.nsn-intra.net> <507400ED.7030203@tid.es> Message-ID: <66F19F4E4DB41F41A3B8A76C77A42AC4ADD230@DEMUEXC014.nsn-intra.net> Hi Miguel, you are right, this also includes the PPP members, otherwise the use cases could not be established. BR Gerald From: ext Miguel Carrillo [mailto:mcp at tid.es] Sent: Tuesday, October 09, 2012 12:48 PM To: Meyer, Gerald (NSN - DE/Munich) Cc: ext BISSON Pascal; Fiware-security at lists.fi-ware.eu; Stefano De Panfilis Subject: Re: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Dear Gerald, Thanks for this, we need this work to be done asap. While I see that this is theoretically simple (2 weeks looks like a lot!) we would appreciate it if you could undertake the necessary steps to get this done internally in your company as soon as you can. One little detail : "with open and free access to all FI-WARE partners" -> can we add a "and all the PPP members (namely, the Use Case Projects)"? :) If not, we would have a problem. Once this is done, please do not forget to update the catalogue. I add Stefano in CC. Best regards, Miguel El 09/10/2012 11:54, Meyer, Gerald (NSN - DE/Munich) escribi?: Hi Stefano, just as an amendment: at NSN we are hosting the One-IDM GE (Identity Management) at our premises, with open and free access to all FI-WARE partners. BR Gerald From: Meyer, Gerald (NSN - DE/Munich) Sent: Tuesday, October 09, 2012 11:41 AM To: 'ext BISSON Pascal'; Fiware-security at lists.fi-ware.eu Subject: RE: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Hi Stefano, currently at NSN we are using 1 single public IP address for a number of different lab services; therefore we have to use non-standard ports for several services. Technically it is possible to have an own IP address for the FI-WARE activities and then use standard ports, but the network rearrangement will take about 2 weeks. BR Gerald 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: Monday, October 08, 2012 3:50 PM To: Fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: [Fiware-wpl] threat for the adoption of thefi-ware testbed! Importance: High Please all GE owners please check and address (V1 GE owners - as for V2 GE owners please have this in mind). 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 stefano de panfilis Envoy? : lundi 8 octobre 2012 03:21 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Cc : Henar Mu?oz; fiware-testbed at lists.fi-ware.eu Objet : [Fiware-wpl] threat for the adoption of the fi-ware testbed! dear all, as you know the uc projects are studying the work we are doing and in many cases, after an initial draft evaluation, really interested in adopting in their prototypes our generic enablers. here it comes a barrier at which we did not put initially too much attention: it this the port on which the ges communicate. in several case the port is not the standad one i.e. by default, a corporate internet proxy will normally allow the standard HTTP/HTTPS ports - 80 and 443. this fact, although cannot be seen as a wrong or incomplete installation per se, basically prevents sevareal uc to effectively use and integrate the generic enablers they are interested in. since the succes of fi-ware is fully based on the adoption of our technologies (please ref. to the last review report), the above circumstance making extremely difficult the validation by the uc projects, basically poses fi-ware on the wrong side of success as the uc projects will issue the concern the testbed is not usable ...!!! to this extent i kindly ask you: 1. to change the communication port to be a standard port; 2. to complete this change by wednesday e.o.b this week (i.e. 10 october); 3. consequently to update the catalogue. this way on thursday the tesbed team can validate the changes and than i can communicate we have fixed this, i.e. to put the uc projects back in front of their responsibility. thank you in advance for your prompt collaboration on the matter. please notify henar, miguel and me when done. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Oct 10 10:56:39 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 10 Oct 2012 10:56:39 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] New 'Summary of FI-WARE GE Open Specifications' page Message-ID: <24164_1349859401_50753849_24164_2798_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8B82669@THSONEA01CMS04P.one.grp> To all task leads and GE owners (at first place) please check and address. 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 10 octobre 2012 09:03 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] New 'Summary of FI-WARE GE Open Specifications' page Hi all, I have updated the contents of the 'Summary of FI-WARE GE Open Specifications' page on the public wiki so that it will have the links to the new FIWARE.OpenSpecifications.. pages that you should be creating as a result of re-structuring contents of the wiki. You may navigate to it from the home page or directly using the link: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications I have kept another wiki page just summarizing the APIs because I believe it would be convenient for some programmers. This is title as 'Summary of FI-WARE GE Open Specifications' and it is also at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_API_Open_Specifications We asked you to close the task regarding creation of the new FIWARE.OpenSpecifications.. pages EOB yesterday but several of you haven't finished yet. PLEASE do so before 12:00pm. I count with your cooperation. 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 osb at zurich.ibm.com Wed Oct 10 16:16:19 2012 From: osb at zurich.ibm.com (Michael Osborne) Date: Wed, 10 Oct 2012 16:16:19 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] New 'Summary of FI-WARE GE Open Specifications' page In-Reply-To: <24164_1349859401_50753849_24164_2798_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8B82669@THSONEA01CMS04P.one.grp> References: <24164_1349859401_50753849_24164_2798_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8B82669@THSONEA01CMS04P.one.grp> Message-ID: Hi Pascal just to let you know that we have updated quite a bit in the Wiki over the last two days - hopefully we have not broken anything. We have added our Open Specification input and made it clear that it is part of release 2. We have also decided to directly open the lower level privacy interfaces and expose them as an independent GE. The reason that we are doing this is so that we are no longer dependent on any of the other GE providers (IdM,Data handling) to integrate our technology. We will of course support this - but exposing our interfaces directly allows us to contribute without the risk that the other providers are not ready. For this reason we have added a new epic and a number of new work items. regards Mike ==================================================== Michael Osborne Manager Security Group Computer Science IBM Research Division Zurich Research Laboratory, Saeumerstrasse 4, CH 8803, Rueschlikon / Switzerland Phone/FAX (41) ( 44 ) 724 8458 / (41) ( 44 ) 724 8953 Intern : Michael Osborne/Zurich/IBM at IBMCH Extern: osb at zurich.ibm.com From: BISSON Pascal To: "Fiware-security at lists.fi-ware.eu" , Date: 10.10.2012 10:57 Subject: [Fiware-security] TR: [Fiware-wpl] New 'Summary of FI-WARE GE Open Specifications' page Sent by: fiware-security-bounces at lists.fi-ware.eu To all task leads and GE owners (at first place) please check and address. 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 10 octobre 2012 09:03 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] New 'Summary of FI-WARE GE Open Specifications' page Hi all, I have updated the contents of the 'Summary of FI-WARE GE Open Specifications' page on the public wiki so that it will have the links to the new FIWARE.OpenSpecifications.. pages that you should be creating as a result of re-structuring contents of the wiki. You may navigate to it from the home page or directly using the link: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications I have kept another wiki page just summarizing the APIs because I believe it would be convenient for some programmers. This is title as 'Summary of FI-WARE GE Open Specifications' and it is also at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_API_Open_Specifications We asked you to close the task regarding creation of the new FIWARE.OpenSpecifications.. pages EOB yesterday but several of you haven't finished yet. PLEASE do so before 12:00pm. I count with your cooperation. 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[attachment "ATT00001.txt" deleted by Michael Osborne/Zurich/IBM] _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 11 12:13:18 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 11 Oct 2012 12:13:18 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Message-ID: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From kreshnik.musaraj at thalesgroup.com Thu Oct 11 12:57:41 2012 From: kreshnik.musaraj at thalesgroup.com (MUSARAJ Kreshnik) Date: Thu, 11 Oct 2012 12:57:41 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: References: Message-ID: <12421_1349953067_5076A62B_12421_264_1_c4919436-b999-4990-b451-775acd6cdff5@THSONEA01HUB05P.one.grp> Dear Pascal, I had already terminated that task, albeit on another page as indicated by the received instructions. Normally the indicated links were provided in the resubmission cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit Anyway, I added the same content at the http version of the wiki, please review and let us know (NB: both links below point to the same content, redundancy between the two was not automatically assured this time). https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Security_Monitoring http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.SecurityMonitoring Many thanks in advance. Best regards, Kreshnik ---THALES GROUP RESTRICTED--- De : BISSON Pascal Envoy? : jeudi 11 octobre 2012 12:13 ? : GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : BISSON Pascal; Fiware-security at lists.fi-ware.eu Objet : FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance : Haute Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From francesco.di.cerbo at sap.com Thu Oct 11 14:06:19 2012 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Thu, 11 Oct 2012 14:06:19 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> References: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> Message-ID: <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> Hello Pascal, The issue is in the page naming scheme. DB Anonymizer Open Specification has this page name : FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer Which is the one that was tested in the cockpit page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit While in the page you checked, DB Anonymizer Open Specification was referenced with the page name: FIWARE.OpenSpecification.Security.DBAnonymizer Which was indeed a redirect to the Open API specification. Now I copied the same contents in both pages, in order to fix quickly the issue. However, we should take a decision on how to define page names for Optional Security Enablers, in order to avoid such situation in the future. Best, Francesco From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: jeudi 11 octobre 2012 12:13 To: GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: BISSON Pascal; Fiware-security at lists.fi-ware.eu Subject: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance: High Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From susana.gzarzosa at atosresearch.eu Thu Oct 11 14:12:10 2012 From: susana.gzarzosa at atosresearch.eu (Susana Gonzalez Zarzosa) Date: Thu, 11 Oct 2012 14:12:10 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> References: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> Message-ID: Hi all, We have the same issue with the Context-based security & compliance. The one in the cockpit page is: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Context-based_security_&_compliance But in the Summary page it was: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Context-basedSecurityCompliance I changed the link in the Summary page to include the one in the cockpit (instead of copying the same content in two pages) but we should also take a decision on how to define this component for future page names. It includes several "spaces" and the character "&" that can produce several combinations. Regards, Susana From: DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] Sent: jueves, 11 de octubre de 2012 14:06 To: BISSON Pascal; GIDOIN Daniel; Antonio Garcia Vazquez; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: Fiware-security at lists.fi-ware.eu Subject: RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Hello Pascal, The issue is in the page naming scheme. DB Anonymizer Open Specification has this page name : FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer Which is the one that was tested in the cockpit page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit While in the page you checked, DB Anonymizer Open Specification was referenced with the page name: FIWARE.OpenSpecification.Security.DBAnonymizer Which was indeed a redirect to the Open API specification. Now I copied the same contents in both pages, in order to fix quickly the issue. However, we should take a decision on how to define page names for Optional Security Enablers, in order to avoid such situation in the future. Best, Francesco From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: jeudi 11 octobre 2012 12:13 To: GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: BISSON Pascal; Fiware-security at lists.fi-ware.eu Subject: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance: High Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 11 14:25:28 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 11 Oct 2012 14:25:28 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: <5EB8ADB6498522479C5E7381A2C8CF354A4885C31A@THSONEA01CMS10P.one.grp> References: <5EB8ADB6498522479C5E7381A2C8CF354A4885C31A@THSONEA01CMS10P.one.grp> Message-ID: <25848_1349958375_5076BAE7_25848_6375_1_f50e8820-bdaf-4361-95ca-40f71799e68e@THSONEA01HUB05P.one.grp> Hi Kreshnik, Good to see that things are now there and visible also through this link used by TID to also perform assessment of the work done. Also why I did my check using this link (as well). Well sounds good in terms of compliance to the template provided. In the meantime I still see a problem with the link to the catalog entry that points not to the right instance (the link should be http://catalogue.fi-ware.eu/node/316 instead of http://catalogue.fi-ware.eu/node/318 btw that second Security Monitoring GE should no more exist (so please delete it). The former one is one entered by Daniel but is still incomplete in the sense it is missing information (especially for Instances and Documentation sections) about the Service level SIEM feature. As such could you please check with Daniel and complete with information provided by ATOS (Susanna) do think you could re-use here information provided by ATOS in the Service-level SIEM entry they created on the catalog and then discard that entry. This at the end there should be only one entry on the catalog for Security Monitoring GE encompassing both features (Attack path engine and Service level SIEM) at least for V1 and obviously more for V2. Last but not least and for Documentation section at Manual subsection please provide references as well to Manuals accompanying the Security Monitoring GE (e.g. Security Monitoring GE User and Programmer Guide, ...) Thanks in advance for your cooperation and support, Best Regards, Pascal De : MUSARAJ Kreshnik Envoy? : jeudi 11 octobre 2012 12:58 ? : BISSON Pascal; GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : Fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Dear Pascal, I had already terminated that task, albeit on another page as indicated by the received instructions. Normally the indicated links were provided in the resubmission cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit Anyway, I added the same content at the http version of the wiki, please review and let us know (NB: both links below point to the same content, redundancy between the two was not automatically assured this time). https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Security_Monitoring http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.SecurityMonitoring Many thanks in advance. Best regards, Kreshnik ---THALES GROUP RESTRICTED--- De : BISSON Pascal Envoy? : jeudi 11 octobre 2012 12:13 ? : GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : BISSON Pascal; Fiware-security at lists.fi-ware.eu Objet : FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance : Haute Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 11 14:33:31 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 11 Oct 2012 14:33:31 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> References: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> Message-ID: <15047_1349958855_5076BCC7_15047_1869_1_81122af8-3a54-47ef-99f5-2ac7c24ac0b7@THSONEA01HUB03P.one.grp> Ok thanks Francesco for the check, clarification and correction. On my side I would prefer to make clear that DB Anonymizer is an Optional GE. As such I'm in favor to go for FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer. Obviously this is something that would apply also for other Optional GEs (and so Secure Storage Service ...). BR Pascal De : DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] Envoy? : jeudi 11 octobre 2012 14:06 ? : BISSON Pascal; GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : Fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Hello Pascal, The issue is in the page naming scheme. DB Anonymizer Open Specification has this page name : FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer Which is the one that was tested in the cockpit page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit While in the page you checked, DB Anonymizer Open Specification was referenced with the page name: FIWARE.OpenSpecification.Security.DBAnonymizer Which was indeed a redirect to the Open API specification. Now I copied the same contents in both pages, in order to fix quickly the issue. However, we should take a decision on how to define page names for Optional Security Enablers, in order to avoid such situation in the future. Best, Francesco From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: jeudi 11 octobre 2012 12:13 To: GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: BISSON Pascal; Fiware-security at lists.fi-ware.eu Subject: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance: High Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 11 14:36:37 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 11 Oct 2012 14:36:37 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: References: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> Message-ID: <8282_1349959046_5076BD85_8282_4747_2_c8f8e162-becd-42f7-b8d7-4f792e29e8bf@THSONEA01HUB03P.one.grp> Dear Susana, So far we were using Context-based_security_&_compliance for that GE. So I will stay with that naming (meaning I agree with the change you introduced in the Summary page). This also to simply changing numerous pages on the wiki ... BR Pascal De : Susana Gonzalez Zarzosa [mailto:susana.gzarzosa at atosresearch.eu] Envoy? : jeudi 11 octobre 2012 14:12 ? : DI CERBO, Francesco; BISSON Pascal; GIDOIN Daniel; Antonio Garcia Vazquez; MUSARAJ Kreshnik; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : Fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Hi all, We have the same issue with the Context-based security & compliance. The one in the cockpit page is: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Context-based_security_&_compliance But in the Summary page it was: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Context-basedSecurityCompliance I changed the link in the Summary page to include the one in the cockpit (instead of copying the same content in two pages) but we should also take a decision on how to define this component for future page names. It includes several "spaces" and the character "&" that can produce several combinations. Regards, Susana From: DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] Sent: jueves, 11 de octubre de 2012 14:06 To: BISSON Pascal; GIDOIN Daniel; Antonio Garcia Vazquez; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: Fiware-security at lists.fi-ware.eu Subject: RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Hello Pascal, The issue is in the page naming scheme. DB Anonymizer Open Specification has this page name : FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer Which is the one that was tested in the cockpit page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit While in the page you checked, DB Anonymizer Open Specification was referenced with the page name: FIWARE.OpenSpecification.Security.DBAnonymizer Which was indeed a redirect to the Open API specification. Now I copied the same contents in both pages, in order to fix quickly the issue. However, we should take a decision on how to define page names for Optional Security Enablers, in order to avoid such situation in the future. Best, Francesco From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: jeudi 11 octobre 2012 12:13 To: GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: BISSON Pascal; Fiware-security at lists.fi-ware.eu Subject: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance: High Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lucie.gaspard at thalesgroup.com Thu Oct 11 15:16:28 2012 From: lucie.gaspard at thalesgroup.com (GASPARD Lucie) Date: Thu, 11 Oct 2012 15:16:28 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: References: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> <71C0C7C7A712EE4CA636EDFD663B4E270493AEEE72@DEWDFECCR09.wdf.sap.corp> Message-ID: <14494_1349961340_5076C67C_14494_6408_1_b8378a55-2dcf-435f-8e90-294f140fd57a@THSONEA01HUB01P.one.grp> Hi Pascal, I moved the SSS page to http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Security.Optional_Security_Enablers.SecureStorageServiceand changed the link in the Summary page. BR, Lucie [@@THALES GROUP RESTRICTED@@] De : BISSON Pascal Envoy? : jeudi 11 octobre 2012 14:34 ? : DI CERBO, Francesco; GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : Fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Ok thanks Francesco for the check, clarification and correction. On my side I would prefer to make clear that DB Anonymizer is an Optional GE. As such I'm in favor to go for FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer. Obviously this is something that would apply also for other Optional GEs (and so Secure Storage Service ...). BR Pascal De : DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] Envoy? : jeudi 11 octobre 2012 14:06 ? : BISSON Pascal; GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc : Fiware-security at lists.fi-ware.eu Objet : RE: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Hello Pascal, The issue is in the page naming scheme. DB Anonymizer Open Specification has this page name : FIWARE.OpenSpecification.Security.Optional_Security_Enablers.DBAnonymizer Which is the one that was tested in the cockpit page: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_cockpit While in the page you checked, DB Anonymizer Open Specification was referenced with the page name: FIWARE.OpenSpecification.Security.DBAnonymizer Which was indeed a redirect to the Open API specification. Now I copied the same contents in both pages, in order to fix quickly the issue. However, we should take a decision on how to define page names for Optional Security Enablers, in order to avoid such situation in the future. Best, Francesco From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: jeudi 11 octobre 2012 12:13 To: GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: BISSON Pascal; Fiware-security at lists.fi-ware.eu Subject: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance: High Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 11 16:52:41 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 11 Oct 2012 16:52:41 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Message-ID: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> Dear All, This just to confirm our audio conference of tomorrow On the Agenda : * Review of Action Points as per previous audio * FI-WARE testbed / FI-WARE catalog update on status (focus on GE release for V1.2) * Status of new Open Spec * Review of ongoing work (October sprint tickets and the like) * Review of ongoing work with other Chapters and UC projects (especially on handling tickets coming from UC projects) * Events of the week at Consortium level (InfoDay, Access Control GE task force ) * Events to come (preparatory actions - White paper, next peer review, next WP8 plenary ...) Talk with you tomorrow at 10. Best Regards, Pascal PS : As for minutes of our last audio conf you may find them now at: https://forge.fi-ware.eu/docman/view.php/19/1346/FI-WARE_WP8_Minutes_05_10_12.doc PS2: Details to join are the same as usual -------------- next part -------------- An HTML attachment was scrubbed... URL: From Wolfgang.Steigerwald at telekom.de Thu Oct 11 16:56:17 2012 From: Wolfgang.Steigerwald at telekom.de (Wolfgang.Steigerwald at telekom.de) Date: Thu, 11 Oct 2012 16:56:17 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am In-Reply-To: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> References: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> Message-ID: Hello Pascal, I can't attend the conf call tomorrow. I'm out of office the whole day. Best regards Wolfgang Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von BISSON Pascal Gesendet: Donnerstag, 11. Oktober 2012 16:53 An: Fiware-security at lists.fi-ware.eu Cc: Denis Butin Betreff: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Wichtigkeit: Hoch Dear All, This just to confirm our audio conference of tomorrow On the Agenda : * Review of Action Points as per previous audio * FI-WARE testbed / FI-WARE catalog update on status (focus on GE release for V1.2) * Status of new Open Spec * Review of ongoing work (October sprint tickets and the an> * Review of ongoing work with other Chapters and UC projects (especially on handling tickets coming from UC projects) * Events of the week at Consortium level (InfoDay, Access Control GE task force ) * Events to come (preparatory actions - White paper, next peer review, next WP8 plenary ...) Talk with you tomorrow at 10. Best Regards, Pascal PS : As for minutes of our last audio conf you may find them now at:< mal>https://forge.fi-ware.eu/docman/view.php/19/1346/FI-WARE_WP8_Minutes_05_10_12.doc PS2: Details to join are the same as usual -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.seidl at nsn.com Thu Oct 11 19:38:27 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Thu, 11 Oct 2012 19:38:27 +0200 Subject: [Fiware-security] FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) In-Reply-To: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> References: <25848_1349950445_50769BED_25848_4744_1_93f41e62-0c30-46e7-b466-39b4ec08a7af@THSONEA01HUB06P.one.grp> Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A6011B9702@DEMUEXC027.nsn-intra.net> Hi Pascal, I modified it for IDM GE. Please check, if everything is ok. One problem I faced is that there is no entry for IDM GE at the resubmission cockpit. Don't know if this is mandatory. If yes I think only TID can add it. Two remaining issues I noticed: - For IDM there are two GE. Problem is that the template foresees only to have one owner. It is possible to copy/paste the line, but then the format of the template gets corrupted. So question is: How to handle the case of two GE. This is only necessary how to insert two companies and two responsible persons? - Second the legal notice at the open specification section. Is this section equal for everyone, I mean the same context? Or should this be adapted to the special needs of the GE? If the yes our legal department has to check it beforehand, or was this somehow agreed by every partner already? Greetings Robert From: ext BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: Thursday, October 11, 2012 12:13 PM To: GIDOIN Daniel; antonio.garcia at atosresearch.eu; Susana Gonzalez Zarzosa; MUSARAJ Kreshnik; DI CERBO, Francesco; TRABELSI, Slim; Michael Osborne; ext Anja Lehmann; Seidl, Robert (NSN - DE/Munich); Wolfgang.Steigerwald at telekom.de; Goetze, Norbert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); GASPARD Lucie Cc: BISSON Pascal; Fiware-security at lists.fi-ware.eu Subject: FI-WARE Open Specifications - re-structured - Report on status + Request Actions to be performed by some of the task leads/GE owners (so please PROCEED Urgently !) Importance: High Dear All, This message is mainly targeted to Task lead and/or GE owners. It relates to a quick check I did perform the work done by Task leads/GE owners regarding the re-structuring of the contents of the wiki that relate to GEs in our Security chapter. I based my review on what is now made available at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications#Security_Chapter According to quick scan I've performed I noticed that: ? Security Monitoring is pending and as such can't be assessed. @Daniel/@Kreshnik I know you are working on it but please make it available asap and ensure compliance to the template (see other GEs e.g. Data Handling or Privacy GE which followed that template) ? Context-based security and Compliance GE, Data Handling GE, Privacy GE and Secure Storage Optional GE have been entered following instructions provided and are such can be assessed as conformant to the template provided (since they include Copyright section, Legal Notice, etc. So thanks to ATOS/Susana, SAP/Slim,Francesco, IBM/Michael,Anja and Thales(TAI)/Lucie who own those GEs. In the meantime I can only encourage them to perform final check to be sure they are fully conformant to what was requested. ? IdM GE the way it has been entered is not conformant to the established template. So please NSN/Robert (with support of DT/Wolfgang whenever requested) make it conformant asap. ? DB Anonimyzer GE is pending even if we may find a link the Open Spec API (preliminary for that GE). So please SAP/Francesco address and add that GE the way it should be (i.e. following instructions provided and making it compliant to the template provided). Counting on each of the Task leads and GE owners having actions to perform to have them performed by EOB today to close the work on this. This simply because we are already beyond of schedule and have other actions to engage in. Many thanks in advance for your cooperation and support and yes this will be re-assessed tomorrow at our weekly audio conf. Best Regards, Pascal PS: Just to remind you about our goal here and instructions which were already provided to perform the work and comply to the template shared/agreed among each of the Chapters: The goal is to create a wiki page per GE that comprise the complete specification of the GE. Those wiki pages will help to produce the final FI-WARE GE Open Specifications deliverables to be resubmitted. You can easily produce the wiki page associated to a given GE by following the template with instructions provided at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Open_specification_resubmission_template Probably, a first step before generating this page for the GE in Chapter is to modify the Architecture Description wiki page linked to that GE referred as FIWARE.ArchitectureDescription... As indicated in the template+instructions above, you should introduce the following changes in the Architecture Description wiki page: * You should include a Copyright section which lists the copyright holders * You should include a Legal Notice section which incudes a reference to the Legal Notice that applies to your GE specifications * You should include a description of the intended use/role of the GE in the Introduction section of the FI-WARE Architecture Description wiki page itself. You can reuse the information already provided in the FI-WARE_Product_Vision in section "Target usage" of your chapter/GE, but please duplicate the current information. * Create a new page on the wiki named as FIWARE.OpenSpecification.Details.., where the contents of the "Open Specifications" section in the Architecture Description wiki page will be copied. ? Please all GE owners check you duly created that new page. * Drop the section "Open Specifications" that was there within the wiki page associated to the Architecture Description (you have copied its contents now in the new FIWARE.OpenSpecification.Details.. page) * On the RESTful open API specification of your GE the Intended Audience needs to be revised it should be changed to address reimplementers as potential target users: "This specification is intended for both software developers and . For the former, this document provides a full specification of how to "This specification is intended for both software developers and reimplementers of this API. For the former, this document provides a full specification of how to . Making the above changes per Achitecture Description of a given GE and then creating the corresponding wiki page for the complete Open Specifications is a task that may not take more than a few minutes per GE. WPL/WPA takes care of the whole chapter revision himself with the help of Task leads/GE owners. TID already produced the wikipages for the Glossaries of all chapters and fixed their inline inclusion for the current wiki pages of the FI-WARE Product Vision. This to save us some time ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From francesco.di.cerbo at sap.com Fri Oct 12 10:26:23 2012 From: francesco.di.cerbo at sap.com (DI CERBO, Francesco) Date: Fri, 12 Oct 2012 10:26:23 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am In-Reply-To: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> References: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> Message-ID: <71C0C7C7A712EE4CA636EDFD663B4E270493CE7BD1@DEWDFECCR09.wdf.sap.corp> Hello Pascal, all, Do you have issues with the conference call system? Apparently I cannot join... it says that the room is closed... is this correct? Or there are different issues? Best, Francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: jeudi 11 octobre 2012 16:53 To: Fiware-security at lists.fi-ware.eu Cc: Denis Butin Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Importance: High Dear All, This just to confirm our audio conference of tomorrow On the Agenda : * Review of Action Points as per previous audio * FI-WARE testbed / FI-WARE catalog update on status (focus on GE release for V1.2) * Status of new Open Spec * Review of ongoing work (October sprint tickets and the an> * Review of ongoing work with other Chapters and UC projects (especially on handling tickets coming from UC projects) * Events of the week at Consortium level (InfoDay, Access Control GE task force ) * Events to come (preparatory actions - White paper, next peer review, next WP8 plenary ...) Talk with you tomorrow at 10. Best Regards, Pascal PS : As for minutes of our last audio conf you may find them now at:< mal>https://forge.fi-ware.eu/docman/view.php/19/1346/FI-WARE_WP8_Minutes_05_10_12.doc PS2: Details to join are the same as usual -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Fri Oct 12 10:12:45 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 12 Oct 2012 10:12:45 +0200 Subject: [Fiware-security] FI-WARE conf call postponed Message-ID: <14494_1350029611_5077D12B_14494_13925_1_8F1D40232A0E68409E3FC23A30C326620167821F65DB@THSONEA01CMS04P.one.grp> Dear All, I apologize. Owing to transportation issues, the call conf is postponed to 10:00 am today. Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Fri Oct 12 10:14:54 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Fri, 12 Oct 2012 10:14:54 +0200 Subject: [Fiware-security] FI-WARE conf call postponed erratum (10:30 am) Message-ID: <14494_1350029739_5077D1AB_14494_13976_1_8F1D40232A0E68409E3FC23A30C326620167821F65F1@THSONEA01CMS04P.one.grp> To 10 :30 am De : GIDOIN Daniel Envoy? : vendredi 12 octobre 2012 10:13 ? : fiware-security at lists.fi-ware.eu Objet : FI-WARE conf call postponed Dear All, I apologize. Owing to transportation issues, the call conf is postponed to 10:00 am today. Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Oct 12 10:20:19 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 12 Oct 2012 10:20:19 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am In-Reply-To: References: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> Message-ID: <20599_1350030021_5077D2C5_20599_5109_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8C5B338@THSONEA01CMS04P.one.grp> ok De : Wolfgang.Steigerwald at telekom.de [mailto:Wolfgang.Steigerwald at telekom.de] Envoy? : jeudi 11 octobre 2012 16:56 ? : BISSON Pascal Cc : Fiware-security at lists.fi-ware.eu Objet : AW: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Hello Pascal, I can't attend the conf call tomorrow. I'm out of office the whole day. Best regards Wolfgang Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von BISSON Pascal Gesendet: Donnerstag, 11. Oktober 2012 16:53 An: Fiware-security at lists.fi-ware.eu Cc: Denis Butin Betreff: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Wichtigkeit: Hoch Dear All, This just to confirm our audio conference of tomorrow On the Agenda : ? Review of Action Points as per previous audio ? FI-WARE testbed / FI-WARE catalog update on status (focus on GE release for V1.2) ? Status of new Open Spec ? Review of ongoing work (October sprint tickets and the an> ? Review of ongoing work with other Chapters and UC projects (especially on handling tickets coming from UC projects) ? Events of the week at Consortium level (InfoDay, Access Control GE task force ) ? Events to come (preparatory actions - White paper, next peer review, next WP8 plenary ...) Talk with you tomorrow at 10. Best Regards, Pascal PS : As for minutes of our last audio conf you may find them now at:< mal>https://forge.fi-ware.eu/docman/view.php/19/1346/FI-WARE_WP8_Minutes_05_10_12.doc PS2: Details to join are the same as usual -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Oct 12 10:25:51 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 12 Oct 2012 10:25:51 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am In-Reply-To: <5077D38F.4080302@zurich.ibm.com> References: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> <5077D38F.4080302@zurich.ibm.com> Message-ID: <5127_1350030353_5077D411_5127_8501_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8C5B380@THSONEA01CMS04P.one.grp> Dear Anja, All, Apologize but I was stuck in huge traffic jam this morning will open our audio conf in a minute. Apologize since I was thinking you were informed by my colleagues here. But ok let's talk in a minute. BR Pascal -----Message d'origine----- De?: Anja Lehmann [mailto:anj at zurich.ibm.com] Envoy??: vendredi 12 octobre 2012 10:24 ??: BISSON Pascal Cc?: 'Seidl, Robert (NSN - DE/Munich)' Objet?: Re: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Hi Pascal, hi Robert, is the telco cancelled today? I'm in the waiting line for 20min now ... best, Anja Am 10/11/2012 4:52 PM, schrieb BISSON Pascal: > Dear All, > > This just to confirm our audio conference of tomorrow > > On the Agenda : > > ?Review of Action Points as per previous audio > > ?*FI-WARE testbed*/ *FI-WARE catalog update on status* (focus on GE > release for V1.2) > > ?*Status of new Open Spec* > > ?Review of ongoing work (*October sprint ticket! s and the an>* > > *?*/Review of ongoing work with other Chapters and UC projects > (especially on handling tickets coming from UC projects)/** > > *?Events of the week at Consortium level (InfoDay, *Access Control GE > task force* )* > > *?Events to come (preparatory actions - *White paper, next peer > review, next WP8 plenary* .)* > > ** > > ** > > *Talk with you tomorrow at 10.* > > ** > > *Best Regards,* > > *Pascal* > > ** > > ** > > *PS : As for minutes of our last audio conf you may find them now at:< > mal>https://forge.fi-ware.eu/docman/view.php/19/1346/FI-WARE_WP8_Minut > mal>es_05_10_12.doc* > > *PS2: Details to join are the same as usual * > > * > > > _______________________________________________ > Fiware-security mailing list > Fiware-security at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-security > > * -- Dr. Anja Lehmann IBM Research Zurich zurich.ibm.com/~anj tel: +41 44 724 8351 fax: +41 44 724 8953 From pascal.bisson at thalesgroup.com Fri Oct 12 10:27:26 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 12 Oct 2012 10:27:26 +0200 Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am In-Reply-To: <71C0C7C7A712EE4CA636EDFD663B4E270493CE7BD1@DEWDFECCR09.wdf.sap.corp> References: <11030_1349967209_5076DD69_11030_7826_1_c59e977a-6b5d-40fa-9e77-2a68f31018b3@THSONEA01HUB05P.one.grp> <71C0C7C7A712EE4CA636EDFD663B4E270493CE7BD1@DEWDFECCR09.wdf.sap.corp> Message-ID: <22513_1350030447_5077D46F_22513_19425_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8C5B39C@THSONEA01CMS04P.one.grp> Will open it in a minute De : DI CERBO, Francesco [mailto:francesco.di.cerbo at sap.com] Envoy? : vendredi 12 octobre 2012 10:26 ? : BISSON Pascal; Fiware-security at lists.fi-ware.eu Cc : Denis Butin Objet : RE: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Hello Pascal, all, Do you have issues with the conference call system? Apparently I cannot join... it says that the room is closed... is this correct? Or there are different issues? Best, Francesco From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal Sent: jeudi 11 octobre 2012 16:53 To: Fiware-security at lists.fi-ware.eu Cc: Denis Butin Subject: [Fiware-security] FI-WARE - WP8 - Weekly audio conf 12/10/2012 10am-12am Importance: High Dear All, This just to confirm our audio conference of tomorrow On the Agenda : ? Review of Action Points as per previous audio ? FI-WARE testbed / FI-WARE catalog update on status (focus on GE release for V1.2) ? Status of new Open Spec ? Review of ongoing work (October sprint tickets and the an> ? Review of ongoing work with other Chapters and UC projects (especially on handling tickets coming from UC projects) ? Events of the week at Consortium level (InfoDay, Access Control GE task force ) ? Events to come (preparatory actions - White paper, next peer review, next WP8 plenary ...) Talk with you tomorrow at 10. Best Regards, Pascal PS : As for minutes of our last audio conf you may find them now at:< mal>https://forge.fi-ware.eu/docman/view.php/19/1346/FI-WARE_WP8_Minutes_05_10_12.doc PS2: Details to join are the same as usual -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 15 11:22:46 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 15 Oct 2012 11:22:46 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Message-ID: <1361_1350293018_507BD61A_1361_9199_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8CD7103@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 Juanjo Hierro Envoy? : jeudi 11 octobre 2012 08:59 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Hi all, Re-structuring of the wiki is almost done and complete FI-WARE GE Open Specifications can now be easily accessed from: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Thanks to all of you for the great job ! Only the IoT chapter has not done the job. Unfortunately, I'm afraid this was because Thierry was sick and probably the request didn't arrive at the IoT Chapter team. I will take care of this personally and, hopefully, the whole chapter will be fixed by EOB today. The pages of some few FI-WARE GE Open Specifications need to revised because they seem to have found some issue adapting to the proposed template. We will contact you directly for those cases. We should start now the last and third peer review of the Open Specifications. Following is the proposal on assignment of the third peer-reviews: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data I have tried to avoid repeating any previous peer review (you can find the tables summarizing assignment in previous peer-reviews at the end of this message, just fyi). The calendar I propose to follow is this: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Don't forget to use the attached template for comments. Since we have now re-structure the wiki, we have adapted it so that you have to carry out first a peer-review of the Chapter Architecture and then of each of the FI-WARE GE Open Specifications, once again listed at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Our target goal is to have all FI-WARE GE Open Specifications submitted by the end of the week starting October 29th, i.e., deadline would be November 2nd. Deliverables for the chapters do not have to be submitted on exactly the same date, so we will submit deliverables corresponding to the chapters along that week. Please foward to your teams. Cheers, -- Juanjo ====== Appendix: tables with assignments in previous reviews First peer review: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Second peer review: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Peer-Review Form 12-10-11.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 216282 bytes Desc: FI-WARE Peer-Review Form 12-10-11.docx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Mon Oct 15 11:23:18 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 15 Oct 2012 11:23:18 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Message-ID: <2831_1350293050_507BD63A_2831_14286_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8CD710A@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 Juanjo Hierro Envoy? : jeudi 11 octobre 2012 08:59 ? : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] LIGTHS, CAMERA, ACTION!: Peer review of FI-WARE Open Specifications Hi all, Re-structuring of the wiki is almost done and complete FI-WARE GE Open Specifications can now be easily accessed from: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Thanks to all of you for the great job ! Only the IoT chapter has not done the job. Unfortunately, I'm afraid this was because Thierry was sick and probably the request didn't arrive at the IoT Chapter team. I will take care of this personally and, hopefully, the whole chapter will be fixed by EOB today. The pages of some few FI-WARE GE Open Specifications need to revised because they seem to have found some issue adapting to the proposed template. We will contact you directly for those cases. We should start now the last and third peer review of the Open Specifications. Following is the proposal on assignment of the third peer-reviews: Chapter to be reviewed Reviewing chapter Data IoT Cloud Apps Apps Security IoT I2ND I2ND Cloud Security Data I have tried to avoid repeating any previous peer review (you can find the tables summarizing assignment in previous peer-reviews at the end of this message, just fyi). The calendar I propose to follow is this: * deadline for sending peer-review reports with comments: October 23rd EOB * deadline for implementing peer-review comments: October 30th EOB Don't forget to use the attached template for comments. Since we have now re-structure the wiki, we have adapted it so that you have to carry out first a peer-review of the Chapter Architecture and then of each of the FI-WARE GE Open Specifications, once again listed at: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications Our target goal is to have all FI-WARE GE Open Specifications submitted by the end of the week starting October 29th, i.e., deadline would be November 2nd. Deliverables for the chapters do not have to be submitted on exactly the same date, so we will submit deliverables corresponding to the chapters along that week. Please foward to your teams. Cheers, -- Juanjo ====== Appendix: tables with assignments in previous reviews First peer review: Chapter to be reviewed Reviewing chapter Data Security Cloud Data Apps Cloud IoT Apps I2ND IoT Security I2ND Second peer review: Chapter to be reviewed Reviewing chapter Data Cloud Cloud I2ND Apps IoT IoT Data I2ND Security Security Apps ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE Peer-Review Form 12-10-11.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 216282 bytes Desc: FI-WARE Peer-Review Form 12-10-11.docx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From robert.seidl at nsn.com Fri Oct 12 10:18:31 2012 From: robert.seidl at nsn.com (Seidl, Robert (NSN - DE/Munich)) Date: Fri, 12 Oct 2012 10:18:31 +0200 Subject: [Fiware-security] Telco today Message-ID: <9739B018F0466A4CAB10A9DABBEBF5A6011B97E8@DEMUEXC027.nsn-intra.net> Since I was waiting now for 20 min I assume the telco will not happen today. Mit freundlichen Gr??en Best regards Seidl Robert Nokia Siemens Networks Management International GmbH CTO R SWS IDM St.-Martin-Strasse 76 81541 Muenchen phone +49 (0)89 5159 21106 mobile +49 (0)172 3652971 email robert.seidl at nsn.com IDM Homepage incl. Blog & Wiki: https://inside.nokiasiemensnetworks.com/global/Company/Organization/CTO/Research/SWS/ServConIdMgmt/IDMsite/Pages/idm.aspx Nokia Siemens Networks Management International GmbH Gesch?ftsleitung / Board of Directors: Andreas Sauer, Ralf Dietzel Sitz der Gesellschaft: M?nchen / Registered office: Munich Registergericht: M?nchen / Commercial registry: Munich, HRB 198081 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Mon Oct 15 15:24:28 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Mon, 15 Oct 2012 15:24:28 +0200 Subject: [Fiware-security] FI-WARE - Minutes of last Weekly audi conference Message-ID: <1361_1350307521_507C0EC1_1361_19504_1_89e36efc-4310-4c57-98bf-243add66a729@THSONEA01HUB02P.one.grp> Dear All, This just to let you know that I've uploaded on the repository the minutes of our last audio conference. You may find them at: https://forge.fi-ware.eu/docman/view.php/19/1364/FI-WARE_WP8_Minutes_05_10_12.doc Counting on you to have them carefully check and perform your action points. As usual we will review progress on APs at next audio conference planned this week as usual on Friday from 10am to 12am (same details as usual to join). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Tue Oct 16 09:39:22 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 16 Oct 2012 09:39:22 +0200 Subject: [Fiware-security] TR: *** IMPORTANT: Testbed V1: progress values update Message-ID: <7374_1350373178_507D0F3A_7374_6504_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8D0E8D3@THSONEA01CMS04P.one.grp> FYI @GE owners concerned by Testbed V1 please read carefully this email (especially instructions provided to update accordingly your GE information on the Testbed V1 Cockpit wiki page. Confirmed me once done. Best Regards, Pascal De : Paolo Zampognaro [mailto:paolo.zampognaro at eng.it] Envoy? : lundi 15 octobre 2012 18:04 ? : fiware-testbed at lists.fi-ware.eu Cc : 'Riss, Uwe'; GLIKSON at il.ibm.com; thierry.nagellen at orange.com; jhierro at tid.es; pierangelo.garino at telecomitalia.it; BISSON Pascal Objet : *** IMPORTANT: Testbed V1: progress values update Hi All, this mail to inform all about the rules to follow in order to update the GE "progress value" from the 80% to the 100%. in the Testbed V1 Cockpit wiki page. As you can read directly there [1] it is required that the GE owners run the unit tests on the installed GE. If such tests pass, they will update by themselves the value to 90%. Then the testbed team will assign the 100% once they pass also the integration tests the GEs are involved in. If no integration test was defined and executed for this version, the testbed team will update the value to 100% as well (simply because the GEs are not involved in dependencies but they are, anyway, properly running). Then, please, start updating such value as soon as possible. (WPLs, please, forward such request inside your chapter). BR, Paolo [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Implementation_Cockpit#Cockpit Paolo Zampognaro R & D Laboratory paolo.zampognaro at eng.it ________________________________________ Engineering Ingegneria Informatica S.p.a. via Emanuele Gianturco, 15 - 80142 Napoli - (IT) tel.: (+39) 0816103524 mobile.: (+39) 3451227587 www.eng.it -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Wed Oct 17 13:01:41 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 17 Oct 2012 13:01:41 +0200 Subject: [Fiware-security] TR: [FI-PPP All] Solution for access to non-standard ports Message-ID: <2713_1350471755_507E904B_2713_11693_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8DB0490@THSONEA01CMS04P.one.grp> Of interested of all GE owners using non standard. Please see hereafter some news and solution that would be implemented by TID to ease our work. BR Pascal -----Message d'origine----- De?: all-bounces at fi-ppp.eu [mailto:all-bounces at fi-ppp.eu] De la part de Juanjo Hierro Envoy??: mercredi 17 octobre 2012 11:56 ??: ab at fi-ppp.eu; all at fi-ppp.eu Objet?: [FI-PPP All] Solution for access to non-standard ports Dear all Several Use Case Projects have approached us asking for a workaround to access our GEs when do not use the standard HTTP ports. I would like to share with you the solution we are going to implement to ease your work. All the GEs with a non standard HTTP port will keep it but we will also enable an alternative route via a proxy. We will reflect the existence of both ports in the description of the Instance linked to each FI-WARE GE on the catalogue. This alternative route will always use a standard HTTP port. This should be configured by the end of the week at the latest. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) 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 _______________________________________________ All mailing list All at fi-ppp.eu http://lists.fi-ppp.eu/mailman/listinfo/all From pascal.bisson at thalesgroup.com Wed Oct 17 13:02:08 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 17 Oct 2012 13:02:08 +0200 Subject: [Fiware-security] TR: [FI-PPP All] Solution for access to non-standard ports in the FI-WARE Testbed Message-ID: <3886_1350471781_507E9065_3886_16023_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8DB0492@THSONEA01CMS04P.one.grp> FYI -----Message d'origine----- De?: all-bounces at fi-ppp.eu [mailto:all-bounces at fi-ppp.eu] De la part de Juanjo Hierro Envoy??: mercredi 17 octobre 2012 12:00 ??: ab at fi-ppp.eu; all at fi-ppp.eu Objet?: [FI-PPP All] Solution for access to non-standard ports in the FI-WARE Testbed (resent with a more clear subject and additional people in cc) Dear all Several Use Case Projects have approached us asking for a workaround to access our GEs when do not use the standard HTTP ports. I would like to share with you the solution we are going to implement to ease your work. All the GEs with a non standard HTTP port will keep it but we will also enable an alternative route via a proxy. We will reflect the existence of both ports in the description of the Instance linked to each FI-WARE GE on the catalogue. This alternative route will always use a standard HTTP port. This should be configured by the end of the week at the latest. Best regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) 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 _______________________________________________ All mailing list All at fi-ppp.eu http://lists.fi-ppp.eu/mailman/listinfo/all From slim.trabelsi at sap.com Thu Oct 18 11:50:37 2012 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Thu, 18 Oct 2012 09:50:37 +0000 Subject: [Fiware-security] Venue details for the wp8 meeting in Sophia Antipolis (21-22 Nov) Message-ID: <31F2B8F7A6BAD749A28AE406B8EF250906BC0755@DEWDFEMB13A.global.corp.sap> Dear all, Here are the venue details for SAP Labs Sophia-Antipolis. Thank you Best regards 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Sophia-Antipolis.doc Type: application/msword Size: 44544 bytes Desc: Sophia-Antipolis.doc URL: From denis.butin at inria.fr Thu Oct 18 12:02:49 2012 From: denis.butin at inria.fr (Denis Butin) Date: Thu, 18 Oct 2012 12:02:49 +0200 (CEST) Subject: [Fiware-security] Venue details for the wp8 meeting in Sophia Antipolis (21-22 Nov) In-Reply-To: <31F2B8F7A6BAD749A28AE406B8EF250906BC0755@DEWDFEMB13A.global.corp.sap> Message-ID: <1494769486.8921268.1350554569274.JavaMail.root@inria.fr> Hi Slim, I thought the meeting was on Nov 22-23. Did the dates change? Best, Denis ----- Original Message ----- > From: "Slim TRABELSI" > To: fiware-security at lists.fi-ware.eu > Sent: Thursday, 18 October, 2012 11:50:37 AM > Subject: [Fiware-security] Venue details for the wp8 meeting in > Sophia Antipolis (21-22 Nov) > Dear all, > Here are the venue details for SAP Labs Sophia-Antipolis. > Thank you > Best regards > 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 > _______________________________________________ > Fiware-security mailing list > Fiware-security at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: From slim.trabelsi at sap.com Thu Oct 18 12:05:20 2012 From: slim.trabelsi at sap.com (TRABELSI, Slim) Date: Thu, 18 Oct 2012 10:05:20 +0000 Subject: [Fiware-security] Venue details for the wp8 meeting in Sophia Antipolis (22-23 Nov) Message-ID: <31F2B8F7A6BAD749A28AE406B8EF250906BC07D9@DEWDFEMB13A.global.corp.sap> Hi Denis, You are right, it is on 22-23 Nov. Sorry for the mistake. Best Slim From: Denis Butin [mailto:denis.butin at inria.fr] Sent: jeudi 18 octobre 2012 12:03 To: TRABELSI, Slim Cc: fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] Venue details for the wp8 meeting in Sophia Antipolis (21-22 Nov) Hi Slim, I thought the meeting was on Nov 22-23. Did the dates change? Best, Denis ________________________________ From: "Slim TRABELSI" To: fiware-security at lists.fi-ware.eu Sent: Thursday, 18 October, 2012 11:50:37 AM Subject: [Fiware-security] Venue details for the wp8 meeting in Sophia Antipolis (21-22 Nov) Dear all, Here are the venue details for SAP Labs Sophia-Antipolis. Thank you Best regards 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 _______________________________________________ Fiware-security mailing list Fiware-security at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-security -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Oct 19 10:13:59 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 19 Oct 2012 10:13:59 +0200 Subject: [Fiware-security] TR: FI-WARE - Minutes of last Weekly audi conference Message-ID: <32469_1350634441_50810BC9_32469_5967_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8E5F1D1@THSONEA01CMS04P.one.grp> De : BISSON Pascal Envoy? : lundi 15 octobre 2012 15:24 ? : Fiware-security at lists.fi-ware.eu Cc : BISSON Pascal; GIDOIN Daniel Objet : FI-WARE - Minutes of last Weekly audi conference Importance : Haute Dear All, This just to let you know that I've uploaded on the repository the minutes of our last audio conference. You may find them at: https://forge.fi-ware.eu/docman/view.php/19/1364/FI-WARE_WP8_Minutes_05_10_12.doc Counting on you to have them carefully check and perform your action points. As usual we will review progress on APs at next audio conference planned this week as usual on Friday from 10am to 12am (same details as usual to join). Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Oct 19 10:24:59 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 19 Oct 2012 10:24:59 +0200 Subject: [Fiware-security] (no subject) Message-ID: <9353_1350635100_50810E5C_9353_14332_18_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8E5F263@THSONEA01CMS04P.one.grp> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE_Agenda_WP8_2012_10_22-23.doc Type: application/msword Size: 61952 bytes Desc: FI-WARE_Agenda_WP8_2012_10_22-23.doc URL: From pascal.bisson at thalesgroup.com Fri Oct 19 10:38:30 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 19 Oct 2012 10:38:30 +0200 Subject: [Fiware-security] (no subject) Message-ID: <23587_1350635912_50811188_23587_11041_5_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8E5F320@THSONEA01CMS04P.one.grp> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE_WP8_Minutes_12_10_12.doc Type: application/msword Size: 262144 bytes Desc: FI-WARE_WP8_Minutes_12_10_12.doc URL: From jhierro at tid.es Mon Oct 22 06:40:49 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 22 Oct 2012 06:40:49 +0200 Subject: [Fiware-security] Temporary solution designed for the FI-WARE Testbed regarding Controlled Access to FI-WARE GE APIs Message-ID: <5084CE51.2010809@tid.es> Dear Pascal and members of the Security Chapter, As you know, we had to come with a temporal solution to the FI-WARE GE API Access Control issues that the UC projects are facing when trying to use FI-WARE GEs deployed on the FI-WARE Testbed. Such temporary solution would be developed and deployed in parallel to work planned in the Security chapter who is responsible of designing a consolidated solution for the FI-WARE Second Release. As agreed during the Security Chapter confcall where this matter was discussed, I took the responsibility to setup a team involving people from the FI-WARE Testbed team trying come with this temporary solution. Soon we found that we had to involve people from the team at UPM working on the development of the FI-WARE Cloud portal. This was because we found that the OpenStack Keystone component being used in the Cloud chapter would allow us to easily and rather quickly develop a solution that meet the following requirements: * the solution should allow us to re-use FI-WARE Testbed user accounts as user accounts for the FI-WARE Cloud, which would ease the overall management of the FI-WARE Testbed. * the solution should be implementable in two steps as to bring a valid solution for both the very short term (end of October) and the mid-term (end of November) the latter one allowing us to put in place an OAuth 2.0-based controlled access to APIs provided by FI-WARE GEs deployed on the FI-WARE Testbed. During the last two weeks, the above mentioned team has worked hard on the matter as to design a solution that is summarized in the presentation you can download from: https://forge.fi-ware.eu/docman/view.php/7/1398/FI-WARE+Testbed+temporary+Identity+and+Access+Control+solution.pptx One interesting aspect of the short/medium-term solution provided is that it would be delivered as Open Source (not only because OpenStack Keystone solution already is open source but because the UPM team working in the Cloud Portal has agreed to deliver the new components they have to develop as open source). I took the opportunity of sharing this design during the FI-PPP AB virtual meeting last week and the UC projects that were present confirmed it would work them as a temporary solution. I wanted to share the design of this temporary solution with you as to: * Find out whether you believe there is something already delivered by the Security Chapter in the first Release that it may be useful to integrate in the proposed solution (trying to be pragmatic here because we all have to be aware about the timing). I personally wondered whether it would be feasible to use any of the Identity Management GEs here. With the information available, it was difficult for us to find out what could be used in the design but we would be happy to hear any proposal we can evaluate. * Plan the discussions on how we can migrate from the designed solution to the final one planned for the Second Release. My take on this is that we need to find out how the "Keystone" component in slides 7-9-11 could integrate with (or be replaced by) the Identity Management GE and how the "Keystone middleware" component could be replaced by the envisioned Access Control GE (this in case that the Access Control GE is going to be compatible with the support of OAuth 2.0, otherwise we may keep the designed solution just to support OAuth 2.0-based controlled access to APIs). Anyway this would be subject to analysis and the sooner we plan the meetings for discussing this, the better. I would also like to propose having a dedicated confcall where we can present the designed solution to the Security Chapter team. We may even allocate a slot during the weekly meeting of the Security Chapter team (I believe you meet regularly on Fridays) if that is more suitable to you. Just let me know. Your feedback comments, of course, are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) 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 Oct 24 09:46:46 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 24 Oct 2012 09:46:46 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] URGENT but EASY Action Point on FI-WARE GE owners Message-ID: <19250_1351064874_50879D2A_19250_12980_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8F78102@THSONEA01CMS04P.one.grp> To All Security GE owners I'm forwarding you this email with a couple of changes for you to implement according the deadline set by our CA. Counting on you to address the requested changes and implement them. 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 24 octobre 2012 00:16 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] URGENT but EASY Action Point on FI-WARE GE owners Hi, If you are the owner of the reference implementation of any FI-WARE GE, this is an email you should pay special attention to. We need that you implement a couple of APs that are quite easy to implement but relatively urgent (we would need them being implemented by Thursday 10:00am). They were already identified in the joint WPLs/WPAs confcall that took place on October 15th and we asked chapters to implement them by mid last week but little progress has been made. As mentioned, the changes are pretty simple. We need you to: * Change the name of the entry linked to your product (GE implementation) in the FI-WARE Catalogue so that it takes the form: * - (e.g., "Big Data Analysis - SAMSON" or "Complex Event Processing (CEP) - PROTON" * You provide information about the name of your product (GE implementation), accompanied by the name of your organization, in column C of the following shared public spreadsheet: * https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 Besides, you should update documentation that is specific to your product (Unit Testing Plan and the different guides) so that they use the name of the product when you are referring to your product. If you were using the name of the GE it implemented Some of you may argue that your product has currently no name ... if that is the case, this is a good opportunity to give it a name :-) On Thursday 10:00am we will adopt the following decisions regarding GE implementations for which the requested changes above have not been implemented: * We will change the name of the entry linked to your product (GE implementation) in the FI-WARE Catalogue so that it will take the form: * - 's Implementation (e.g., "Cloud Proxy - Technicolor's Implementation) * We will change the information about the name of your product (GE implementation) in column C of the shared public spreadsheet mentioned above so that it reads: * 's implementation With these change we pretend to provide consistent messages to users of FI-WARE, making the distinction between FI-WARE GE Open Specifications and FI-WARE GE Implementations more clear: 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 pascal.bisson at thalesgroup.com Wed Oct 24 09:47:47 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 24 Oct 2012 09:47:47 +0200 Subject: [Fiware-security] TR: [Fiware-wpl] [Fiware] URGENT but EASY Action Point on FI-WARE GE owners Message-ID: <12404_1351064932_50879D64_12404_3836_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D8F78112@THSONEA01CMS04P.one.grp> Add-on to the email previously sent to you about couple of changes Security GE owners would have to address and implement. BR 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 24 octobre 2012 01:44 ? : fiware at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Re: [Fiware-wpl] [Fiware] URGENT but EASY Action Point on FI-WARE GE owners I forgot to complete one paragraph ... On 24/10/12 00:16, Juanjo Hierro wrote: Besides, you should update documentation that is specific to your product (Unit Testing Plan and the different guides) so that they use the name of the product when you are referring to your product. If you were using the name of the GE it implemented Should read: Besides, you should update documentation that is specific to your product (Unit Testing Plan and the different guides) so that they use the name of the product when you are referring to your product. If you were using the name of the GE implemented by your product in this documentation, instead of the product name, we suggest that you add a standard paragraph like the following at the introduction of each document: implements the FI-WARE GE Open Specifications associated to the available at: Whenever the term "" is used, you may assume that we are indeed referring to that implements the Open Specifications or an instance of This just in case you are in a hurry and don't have time to review these documents thoroughly before they are actually submitted now in the release of FI-WARE we plan to deliver by end of this month. Cheers, -- Juanjo ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Wed Oct 24 17:10:13 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 24 Oct 2012 17:10:13 +0200 Subject: [Fiware-security] Temporary solution designed for the FI-WARE Testbed regarding Controlled Access to FI-WARE GE APIs In-Reply-To: <5084CE51.2010809@tid.es> References: <5084CE51.2010809@tid.es> Message-ID: <25878_1351091482_5088051A_25878_1063_1_360f34ab-3490-43a8-96a4-929ea36e600e@THSONEA01HUB02P.one.grp> Dear Juanjo, Thanks for your email. In response I'd like to invite you to an audio conference where we could discuss with you the solution you are proposing hereafter for the short term. This audio conference will take place this Friday from 10am to 11am (our Weekly audio conf at Security Chapter level would start at 11am exceptionally). Please confirm me your participation (hoping you could or would take necessary steps to make it - we are proposing this week simply because some of the requested participants would be off next week due to some bank holidays in countries). As for the rest and in term of participants from our side there would be the following ones: WPL/WPA - Me and Daniel IdM GE owners Robert (NSN) and Wolfgang (DT) Access control GE (under definition and to be released fro V2) owner Cyril /Benoit (THA/TS) and Richard (THA/TRT-UK) (must add to this that Thales participants to this call would also have expertise in Open Stack Keystone which can only help in our discussions. Hearing from you. Best Regards, Pascal PS: We will provide with details to join and webex facility offered by NSN as soon as you confirm your participation De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : lundi 22 octobre 2012 06:41 ? : BISSON Pascal; GIDOIN Daniel Cc : Fiware-security at lists.fi-ware.eu; jhierro >> "Juan J. Hierro" Objet : Temporary solution designed for the FI-WARE Testbed regarding Controlled Access to FI-WARE GE APIs Dear Pascal and members of the Security Chapter, As you know, we had to come with a temporal solution to the FI-WARE GE API Access Control issues that the UC projects are facing when trying to use FI-WARE GEs deployed on the FI-WARE Testbed. Such temporary solution would be developed and deployed in parallel to work planned in the Security chapter who is responsible of designing a consolidated solution for the FI-WARE Second Release. As agreed during the Security Chapter confcall where this matter was discussed, I took the responsibility to setup a team involving people from the FI-WARE Testbed team trying come with this temporary solution. Soon we found that we had to involve people from the team at UPM working on the development of the FI-WARE Cloud portal. This was because we found that the OpenStack Keystone component being used in the Cloud chapter would allow us to easily and rather quickly develop a solution that meet the following requirements: * the solution should allow us to re-use FI-WARE Testbed user accounts as user accounts for the FI-WARE Cloud, which would ease the overall management of the FI-WARE Testbed. * the solution should be implementable in two steps as to bring a valid solution for both the very short term (end of October) and the mid-term (end of November) the latter one allowing us to put in place an OAuth 2.0-based controlled access to APIs provided by FI-WARE GEs deployed on the FI-WARE Testbed. During the last two weeks, the above mentioned team has worked hard on the matter as to design a solution that is summarized in the presentation you can download from: https://forge.fi-ware.eu/docman/view.php/7/1398/FI-WARE+Testbed+temporary+Identity+and+Access+Control+solution.pptx One interesting aspect of the short/medium-term solution provided is that it would be delivered as Open Source (not only because OpenStack Keystone solution already is open source but because the UPM team working in the Cloud Portal has agreed to deliver the new components they have to develop as open source). I took the opportunity of sharing this design during the FI-PPP AB virtual meeting last week and the UC projects that were present confirmed it would work them as a temporary solution. I wanted to share the design of this temporary solution with you as to: * Find out whether you believe there is something already delivered by the Security Chapter in the first Release that it may be useful to integrate in the proposed solution (trying to be pragmatic here because we all have to be aware about the timing). I personally wondered whether it would be feasible to use any of the Identity Management GEs here. With the information available, it was difficult for us to find out what could be used in the design but we would be happy to hear any proposal we can evaluate. * Plan the discussions on how we can migrate from the designed solution to the final one planned for the Second Release. My take on this is that we need to find out how the "Keystone" component in slides 7-9-11 could integrate with (or be replaced by) the Identity Management GE and how the "Keystone middleware" component could be replaced by the envisioned Access Control GE (this in case that the Access Control GE is going to be compatible with the support of OAuth 2.0, otherwise we may keep the designed solution just to support OAuth 2.0-based controlled access to APIs). Anyway this would be subject to analysis and the sooner we plan the meetings for discussing this, the better. I would also like to propose having a dedicated confcall where we can present the designed solution to the Security Chapter team. We may even allocate a slot during the weekly meeting of the Security Chapter team (I believe you meet regularly on Fridays) if that is more suitable to you. Just let me know. Your feedback comments, of course, are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) 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 Oct 24 17:12:29 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Wed, 24 Oct 2012 17:12:29 +0200 Subject: [Fiware-security] FI-WARE - Weekly audio conference - postponed to 11am-12am this Friday Message-ID: <28005_1351091619_508805A3_28005_1393_1_01d2ec34-fe90-47be-9757-ece4f10df5f0@THSONEA01HUB01P.one.grp> Dear All, Please notice this above change in our WP8 weekly audio conf this Friday. It will start at 11am instead of 10am due to another audio conference (some of us) would have to attend with our CA (focus on FI-WARE testbed need for IdM) BR Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Oct 25 10:21:44 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 25 Oct 2012 10:21:44 +0200 Subject: [Fiware-security] Temporary solution designed for the FI-WARE Testbed regarding Controlled Access to FI-WARE GE APIs In-Reply-To: <25878_1351091482_5088051A_25878_1063_1_360f34ab-3490-43a8-96a4-929ea36e600e@THSONEA01HUB02P.one.grp> References: <5084CE51.2010809@tid.es> <25878_1351091482_5088051A_25878_1063_1_360f34ab-3490-43a8-96a4-929ea36e600e@THSONEA01HUB02P.one.grp> Message-ID: <5088F698.5080702@tid.es> Hi Pascal, Yes, I can confirm attendance to this confcall. People from the UPM (in charge of the Cloud Portal and involved in the development of the short/medium term solution) will also participate. What bridge should we use ? I can offer the powwownow we use for the joint WPLs/WPAs follow-up confcalls which allow local dial numbers if that helps. We would definitively need local dial-in numbers. 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 On 24/10/12 17:10, BISSON Pascal wrote: Dear Juanjo, Thanks for your email. In response I'd like to invite you to an audio conference where we could discuss with you the solution you are proposing hereafter for the short term. This audio conference will take place this Friday from 10am to 11am (our Weekly audio conf at Security Chapter level would start at 11am exceptionally). Please confirm me your participation (hoping you could or would take necessary steps to make it - we are proposing this week simply because some of the requested participants would be off next week due to some bank holidays in countries). As for the rest and in term of participants from our side there would be the following ones: WPL/WPA - Me and Daniel IdM GE owners Robert (NSN) and Wolfgang (DT) Access control GE (under definition and to be released fro V2) owner Cyril /Benoit (THA/TS) and Richard (THA/TRT-UK) (must add to this that Thales participants to this call would also have expertise in Open Stack Keystone which can only help in our discussions. Hearing from you. Best Regards, Pascal PS: We will provide with details to join and webex facility offered by NSN as soon as you confirm your participation De : Juanjo Hierro [mailto:jhierro at tid.es] Envoy? : lundi 22 octobre 2012 06:41 ? : BISSON Pascal; GIDOIN Daniel Cc : Fiware-security at lists.fi-ware.eu; jhierro >> "Juan J. Hierro" Objet : Temporary solution designed for the FI-WARE Testbed regarding Controlled Access to FI-WARE GE APIs Dear Pascal and members of the Security Chapter, As you know, we had to come with a temporal solution to the FI-WARE GE API Access Control issues that the UC projects are facing when trying to use FI-WARE GEs deployed on the FI-WARE Testbed. Such temporary solution would be developed and deployed in parallel to work planned in the Security chapter who is responsible of designing a consolidated solution for the FI-WARE Second Release. As agreed during the Security Chapter confcall where this matter was discussed, I took the responsibility to setup a team involving people from the FI-WARE Testbed team trying come with this temporary solution. Soon we found that we had to involve people from the team at UPM working on the development of the FI-WARE Cloud portal. This was because we found that the OpenStack Keystone component being used in the Cloud chapter would allow us to easily and rather quickly develop a solution that meet the following requirements: * the solution should allow us to re-use FI-WARE Testbed user accounts as user accounts for the FI-WARE Cloud, which would ease the overall management of the FI-WARE Testbed. * the solution should be implementable in two steps as to bring a valid solution for both the very short term (end of October) and the mid-term (end of November) the latter one allowing us to put in place an OAuth 2.0-based controlled access to APIs provided by FI-WARE GEs deployed on the FI-WARE Testbed. During the last two weeks, the above mentioned team has worked hard on the matter as to design a solution that is summarized in the presentation you can download from: https://forge.fi-ware.eu/docman/view.php/7/1398/FI-WARE+Testbed+temporary+Identity+and+Access+Control+solution.pptx One interesting aspect of the short/medium-term solution provided is that it would be delivered as Open Source (not only because OpenStack Keystone solution already is open source but because the UPM team working in the Cloud Portal has agreed to deliver the new components they have to develop as open source). I took the opportunity of sharing this design during the FI-PPP AB virtual meeting last week and the UC projects that were present confirmed it would work them as a temporary solution. I wanted to share the design of this temporary solution with you as to: * Find out whether you believe there is something already delivered by the Security Chapter in the first Release that it may be useful to integrate in the proposed solution (trying to be pragmatic here because we all have to be aware about the timing). I personally wondered whether it would be feasible to use any of the Identity Management GEs here. With the information available, it was difficult for us to find out what could be used in the design but we would be happy to hear any proposal we can evaluate. * Plan the discussions on how we can migrate from the designed solution to the final one planned for the Second Release. My take on this is that we need to find out how the "Keystone" component in slides 7-9-11 could integrate with (or be replaced by) the Identity Management GE and how the "Keystone middleware" component could be replaced by the envisioned Access Control GE (this in case that the Access Control GE is going to be compatible with the support of OAuth 2.0, otherwise we may keep the designed solution just to support OAuth 2.0-based controlled access to APIs). Anyway this would be subject to analysis and the sooner we plan the meetings for discussing this, the better. I would also like to propose having a dedicated confcall where we can present the designed solution to the Security Chapter team. We may even allocate a slot during the weekly meeting of the Security Chapter team (I believe you meet regularly on Fridays) if that is more suitable to you. Just let me know. Your feedback comments, of course, are welcome. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Thu Oct 25 20:36:10 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Thu, 25 Oct 2012 20:36:10 +0200 Subject: [Fiware-security] FI-WARE - WP8 Weekly audio will start at 11am not 10am !! Message-ID: <11987_1351190242_508986E2_11987_7966_1_7f4d1554-6a5f-41cc-b347-5345aeadc85f@THSONEA01HUB02P.one.grp> Dear All, Our regular WP8 audio conference will start tomorrow at 11am (and not 10am due to another audio conf some us would have to join). As for Agenda we will as usual review progress on Action Points as per previous minutes (available at: https://forge.fi-ware.eu/docman/view.php/19/1491/FI-WARE_WP8_Minutes_19_10_12.doc) As for the rest will also review progress on some of the new actions triggered this week. Best Regards, Pascal PS: same details as usuals to join -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Oct 26 10:01:45 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 26 Oct 2012 10:01:45 +0200 Subject: [Fiware-security] TR: [Fiware-exploitation] FI WARE Platform- Individual Exploitation Plans into the wiki Message-ID: <11987_1351238513_508A4371_11987_18119_1_7ea55e82-8afb-4f51-8b1f-42a7c4193b25@THSONEA01HUB04P.one.grp> Dear GE owners, I'm forwarding you this emai regarding a number of actions each of the Security GE owners have to perform to better state individual exploitation plan regarding their GE and as such answer a demand from the EC and reviewers we got at last review (also stated in review report). AP each of the GE owners to carefully check the action to be performed and try to have it done according to the set deadline November 1st (by the date information requested should have been entered on the wiki. Another Action we will discuss also at today's audio conf starting at 11am. Best Regards, Pascal De : fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : mardi 23 octobre 2012 12:49 ? : fiware-exploitation at lists.fi-ware.eu Objet : [Fiware-exploitation] FI WARE Platform- Individual Exploitation Plans into the wiki Dear Colleagues Please remember, that apart from review FI WARE Platform Strategy document and send comments, you have to complete the individual exploitation plans answering the main business questions stemming from the review, on the wiki, where each industrial partner has a slot https://forge.fiware.eu/plugins/mediawiki/wiki/exploitation/index.php/Review_M18_Exploitation. Please involve your business departments to provide a detailed answer: o Identify the key segments, to avoid entering in the untenable situation of "FI-WARE is good for everyone and for every task"- "Two sided market"- End Users and Developers o Identify the main channels will be used to reach the various customer segments (Developers and End Users) and the marketing tools should be designed to be usable by the internal sales force. o Identify the right strategy to ecosystem management and consequently attract as much developers as we can o How , Telecom service provider, Network equipment and mobile terminal manufacturers, Software vendors, IT Providers and IT solution integrators will make money individually from FIWARE Platform? Licensing, advertising, selling apps, hosting service, increase data traffic, data storage ? You must indicate your role within the ecosystem and revenue streams. For example Atos provide software, licensing, but we will participate as integrator of FI WARE Instances, in the massive business generation when all the developers join FI WARE - All your contributions for FI WARE Strategy definition document have to be received before next 1st November to prepare a final version to deliver before the 8th November Thanks for your contribution Juan From: Juan Bare?o Guerenabarrena Sent: martes, 23 de octubre de 2012 12:35 To: antonio cimmino (antonio.cimmino at alcatel-lucent.com) Cc: Sandfuchs, Thorsten (thorsten.sandfuchs at sap.com); Nuria De-Lama Sanchez (nuria.delama at atosresearch.eu) Subject: Alcatel-Lucent Italia S.P.A. Alcatel-Lucent Deutschland AG Business questions Dear Antonio Thanks for your inputs provided in the wiki, but we need a more detailed and concrete answers, particularly: how Alcatel in particularly is going to make money? - Licensing, as software provider - Network and data storage capacity provider... - You must indicate your role within the ecosystem and revenue streams. For example Atos provide software, licensing, but we will participate as integrator in the massive business generation when all the developers join FI WARE For example: - On the one hand ATOS, as software component provider to build Generic Enables (GE). In particular, and of especial interest for ATOS, the ones related to security aspects and applications services - On the other hand, ATOS as a big company and integrator has a strong interest in participating in the Phase 3 massive business generation. Atos as integrator of FI WARE Instances, GE+ component developed by an application developer, and increase its portfolio to address main market demands as ATOS itself has no possibility of reaching all the business applications demanded by the customers, however, in collaboration with other business actors (normally SMEs) the range of the full solution to be offered increases dramatically. The integration with other companies also offers our potential solutions a flexibility that sometimes, products and/or services provided by bug companies do not have by themselves. ATOS main interest is therefore to be part of the business explosion that Phase 3 will represent how Alcatel in particularly is going to sell FI WARE Platform? - Own channels, name them...community of developers, final users - Process sale description, for example how to approach smart cities.. - Globalization, where operate Alcatel and where is expected to provide.. Alcatel-Lucent Italia S.P.A. Alcatel-Lucent Deutschland AG ________________________________ ________________________________ * Which customers do we want to serve? The innovations and revolutions on Future Internet are of interest for all types of end users, providers and over the top actors. Taking into account the relevance of the Generic Enablers introduced by FI-WARE in the area of, e.g., IoT, QoS and Cloud, as a first selection in the area of B2B customers, we can identify the public sector and strategic industries within the smart city sector. These market players are always searching for flexible, secure and reliable Internet based infrastructures including smart actuator and sensor networks. As far as QoS and Cloud Internet is concerned, another promising sectors comprise the over the top provisioning of multimedia streaming and content , but also ISPs that can be enabled for new business models based on assured quality (enhancing a business model for which already today end users are already paying and demanding). * Which channels will be used to reach the various customer segments? We will continue to use the existing channels to our customers, but if there will emerge new tools and opportunities provided by the FI-WARE platform these will be explored accordingly, too. Furthermore, new B2B models are likely to emerge among existing and new actors. * Which benefits are the participants going to take to the market thanks to FIWARE? New tools and ICT infrastrutures for the internal R&D activities are expected to be faster on the market. New requirements for systems can be agreed in advance together with customers participating in FI-WARE. * How are the benefits going to be sold? Bearing in mind that most of the benefits can be sold around the the individually generated foreground, the architectures behind the 'open networking and interfaces' developed in I2ND shall be the key aspects. A possible way to monetize them is seen in the commercialization of proprietary systems (network elements) of Alcatel-Lucent , enriched with enhancement from FI-WARE. * How will the sales process work? If we image that the 'end industrialized product' that will be sold will be a new Internet platform for the future then all providers will compete with each other's solutions / value propositions developed for the Future Internet. * Globalisation of the exploitation plan We expect that the FI-WARE dissemination and exploitation shall continue to be global with all interested partners after the project will have ended. This will strenghten the position of FI-WARE proponents and FI-WARE compliant products on the market compared with solutions which have to start from the scratch. * How will make money from FIWARE Platform? IaaS and SaaS shall be target technologies behind the FIWARE platform that may represent source for revenue [cid:image001.png at 01CDB11A.DC121110] Juan Bare?o Global Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CDB11A.DC121110] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Fri Oct 26 10:59:12 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 26 Oct 2012 10:59:12 +0200 Subject: [Fiware-security] FI-WARE - Audio conf of today cancelled (Apologize) Message-ID: <19471_1351242025_508A5129_19471_734_1_aedfc333-89e9-438c-87a0-7e4555b3d8b8@THSONEA01HUB03P.one.grp> Dear All, Being said the audio conference some of us are attending on Access Control solution for the short-term will probably now last more than 1hour I prefer to have our audio conference of today be cancelled to have time the topic fully discussed and clarified between us and Juanjo (and UPM colleagues from the Cloud Chapter team and who have joined the audio). So would suggest you to work on: 1. the actions points stated in previous minutes (link was sent to you yesterday), 2. the actions I requested you (especially GE owners) to perform (see emails I sent this week for specific actions) Once more apologize for cancelling our audio conf of today. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: From pascal.bisson at thalesgroup.com Fri Oct 26 11:00:15 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 26 Oct 2012 11:00:15 +0200 Subject: [Fiware-security] =?utf-8?q?Annul=C3=A9=3A_FI-WARE_WP8_Weekly_aud?= =?utf-8?q?io_conf?= Message-ID: <19471_1351242087_508A5167_19471_775_1_bba02406-d928-4e98-a053-9bb62f12c8d8@THSONEA01HUB05P.one.grp> Quand : vendredi 26 octobre 2012 10:00-12:00 (GMT+01:00) Bruxelles, Copenhague, Madrid, Paris. Emplacement : Meeting Room Number: 391581 Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Liste des num?ros LocalConnect: Australia Australia Toll Free 1800 005 574 Australia Sydney +61 (0) 282 239 767 Austria Vienna +43 (0) 2682 205 6609 Belgium Brussels +32 (0) 2 789 8678 Denmark Copenhagen +45 3271 4340 Finland Helsinki +358 (0) 923 142 830 France Lyon +33 (0) 426 840 285 France Marseille +33 (0) 488 915 385 France Paris +33 (0) 170 994 816 Germany Berlin +49 (0) 3072 616 7342 Germany D?sseldorf +49 (0) 2115 407 3902 Germany Frankfurt +49 (0) 6971 044 5635 Germany Hamburg +49 (0) 4080 902 0684 Germany Munich +49 (0) 8924 443 2893 Germany Stuttgart +49 (0) 7111 856 2130 Greece Greece Toll Free 0080 012 6344 Hong Kong Hong Kong +852 301 145 59 Hungary Budapest +36 (06) 1-889-3286 Ireland Dublin +353 (0) 14 860 780 Israel Israel Toll Free 1809 245 981 Italy Milan +39 0 230 413 017 Italy Rome +39 0 645 217 056 Italy Turin +39 0 112 179 2159 Japan Japan Toll Free 005 311 212 65 Japan Tokyo +81 (0) 357 675 025 Korea, Republic Of Seoul +82 (0) 234 831 224 Luxembourg Luxemburg City +352 2700 41 42 Malaysia Kuala Lumpur +60 (0) 377 124 640 Netherlands Amsterdam +31 (0) 207 948 529 New Zealand Auckland +64 (0) 9 919 2428 Norway Oslo +47 2153 3919 Poland Poland Toll Free 0080 0121 1304 Portugal Portugal Toll Free 800 814 183 Russia Russia Toll Free 81080 02209 4011 Singapore Singapore +65 6622 1068 Spain Barcelona +34 93 492 3235 Spain Madrid +34 91 788 9908 Sweden Stockholm +46 (0) 850 520 145 Switzerland Geneva +41 (0) 225 927 428 United Kingdom Birmingham +44 (0) 121 260 4686 United Kingdom London +44 (0) 207 153 9902 United Kingdom Manchester +44 (0) 161 250 0679 United States USA & Canada Toll Free 1888 249 0050 United States USA Toll +1 954 334 1559 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4362 bytes Desc: not available URL: From pascal.bisson at thalesgroup.com Fri Oct 26 12:13:59 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Fri, 26 Oct 2012 12:13:59 +0200 Subject: [Fiware-security] TR: [Fiware-exploitation] FW: [Fiware-wpl] FI WARE Platform Strategy Validation and ExploitationDeliverables Resubmission Roadmap before 8th November Message-ID: <15336_1351246446_508A626E_15336_3810_1_b8e3e67a-3518-4a74-b0e3-baa32a21eade@THSONEA01HUB02P.one.grp> Dear GE owners, I'm also forwarding you this email in complement of previous. Please check and complete with information requested regarding GE you own. Best Regards Pascal De : fiware-exploitation-bounces at lists.fi-ware.eu [mailto:fiware-exploitation-bounces at lists.fi-ware.eu] De la part de Juan Bare?o Guerenabarrena Envoy? : vendredi 26 octobre 2012 11:56 ? : fiware-exploitation at lists.fi-ware.eu Cc : fiware-wpl at lists.fi-ware.eu Objet : [Fiware-exploitation] FW: [Fiware-wpl] FI WARE Platform Strategy Validation and ExploitationDeliverables Resubmission Roadmap before 8th November Dear Colleagues Following with the Resubmission of Exploitation Deliverables I remind you to review or complete the following missing inputs and provide feedback: - 11.1 Market Analysis o We will include additional inputs from Platform Strategy Market Analysis 2410 including in https://forge.fi-ware.eu/docman/?group_id=16 - 11.2 Exploitation Strategy o We will include the FI WARE Platform Strategy 24 10 document, including the questions from the review , see document, one with SAP comments, in https://forge.fi-ware.eu/docman/?group_id=16 o Additionally please review the FI WARE Platform Value Proposition and Business Canvas in the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Overall o IPRs section has been modified by SAP and will be completed by them according to the current discussion in the review report and the ongoing discussion between the legal departments. Review key principles into the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/IPR_Management o Answer to the main business questions from the review, individually by partner on the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual - 11.3 Market and Policy Regulation Awareness o Please provide some aanalysis relative to the prospective requirement specific to the developments of the future of the Internet, bearing in mind the project vision on the one hand, and dynamic market conditions on the other, which (may) pose regulatory challenges https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Market_and_Policy_Regulation_Awareness#Policiy_and_Regulation_Awareness o Please complete more additional contacts with European cities to wide geographic extension, and intensification for concrete (multi-)localised achievements. o Preliminary contacts with cities (City of Malaga, Chamber of Commerce of Madrid) seem promising. However, a substantiated European dimension to this activity, with additional cities in other Member States, is missing. At the Month 12 project review, Trento was mentioned as a promising contact. https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Market_and_Policy_Regulation_Awareness#Market_Awareness Thanks for your collaboration Juan From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Juan Bare?o Guerenabarrena Sent: viernes, 19 de octubre de 2012 12:47 To: fiware-exploitation at lists.fi-ware.eu Cc: thorsten.sandfuchs at sap.com; antonio.cimmino at alcatel-lucent.com; fiware-wpl at lists.fi-ware.eu Subject: [Fiware-wpl] FI WARE Platform Strategy Validation and ExploitationDeliverables Resubmission Roadmap before 8th November Dear Colleagues Please find here enclosed the following draft documents in which we are going to leverage to complete the exploitation deliverables resubmission: - Platform Strategy Market Analysis, including main regulatory concerns for 11.1 Market Analysis and 11.3 Policy and Regulation issues - FI WARE Platform Strategy, based on the previous analysis and on 3rd party and Vision deliverables for 11.2 Exploitation Strategy, pending to include some inputs from Product Vision deliverable in which 2-3 examples on how FI-WARE is applied in a specific domain (take existing UC projects) will be included Resubmission Roadmap: All Deliverables sent on the 8th November - 11.1 and 11.3 11.1 Market Analysis and 11.3 Policy and Regulation issues - We will include some inputs from Platform Strategy Market Analysis before 29th October and we will circulate them to be validated before 5th November to deliver final versions - 11.2 Exploitation Strategy - We will include the FI WARE Platform Strategy, including the questions from the review and initial Pro Forma Business Plan, with all your support and contributions on the 5th November and we will send it around to validate the final version to properly deliver on the 8th November. Actions required: Please review FI WARE Platform Strategy, initial draft version for discussion, preferably involving your business departments, leveraging on the previous Platform Strategy Analysis and on the questions from the review, and please add/modify what you consider in the document with "Track Changes" option and answer to the main questions from the review individually on the wiki https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Individual - , each industrial partner has a slot: o The objective is validate a common Platform Strategy as a whole and not as a loose collation of GEs- Agree on the value proposition o Identify the key segments, to avoid entering in the untenable situation of "FI-WARE is good for everyone and for every task"- "Two sided market"- End Users and Developers o Identify the main channels will be used to reach the various customer segments (Developers and End Users) and the marketing tools should be designed to be usable by the internal sales force. o Identify the right strategy to ecosystem management and consequently attract as much developers as we can o How , Telecom service provider, Network equipment and mobile terminal manufacturers, Software vendors, IT Providers and IT solution integrators will make money individually from FIWARE Platform? Licensing, advertising, selling apps, hosting service, increase data traffic, data storage o Provide some inputs for a pro forma analysis about potential market estimation and about initial cost estimates based on Test bed configuration - All your contributions for FI WARE Strategy definition document have to be received before next 1st November to prepare a final version to deliver before the 8th November Thanks for your contribution Juan [cid:image001.png at 01CDAD1E.C5572820] Juan Bare?o Global Innovation, Business Development & Strategy Research & Innovation +34 912148859 Calle Albarrac?n 25, 28037 Madrid juan.bareno at atos.net www.atos.net [cid:image002.gif at 01CDAD1E.C5572820] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 339 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 4064 bytes Desc: image002.gif URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Tue Oct 30 20:38:35 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 30 Oct 2012 20:38:35 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] Fwd: Short term solution to provide controlled access to FI-WARE GE APIs on the FI-WARE Testbed Message-ID: <25204_1351625923_50902CC2_25204_8266_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D9180597@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 Juanjo Hierro Envoy? : mardi 30 octobre 2012 10:08 ? : fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Fwd: Short term solution to provide controlled access to FI-WARE GE APIs on the FI-WARE Testbed FYI, -- Juanjo -------- Original Message -------- Subject: Short term solution to provide controlled access to FI-WARE GE APIs on the FI-WARE Testbed Date: Tue, 30 Oct 2012 07:19:04 +0100 From: Juanjo Hierro To: ab at fi-ppp.eu CC: Jos? Ignacio Carretero , HENAR MU?OZ FRUTOS , Miguel Carrillo , "jhierro >> \"Juan J. Hierro\"" Dear colleagues, As promised, the short-term solution to provide controlled access to FI-WARE GEs deployed on the FI-WARE Testbed is already implemented and available. We have written a short guide with instructions about how to administer user accounts for your project and how developers should program their applications to gain access to the FI-WARE Testbed. You can download this guide from the following URL: https://forge.fi-ware.eu/docman/view.php/7/1511/IdM+and+Access+Control+Short+Term+Solution+Guide.docx Please note that, as a very first step, we need to create a number of user accounts with admin privileges associated to each of the UC projects. Admin users will be able to create additional user accounts for their UC projects. We need that you send an email to e.cloud10 at tid.es with the login of your required admin user account so that we can assign it a password and send it back to you (we will support a more sophisticated self-service process as part of the medium term solution to be made available by end of November but hopefully you can live with this approach for the time being). You may indicate what password you would like to be assigned in your email. Once you have been assigned a user account with admin privileges, you will be able to login to the FI-WARE Testbed Login Web Portal and create new accounts for users linked to your UC project. The steps are explained in the short guide. Developers will be able to use a JavaScript code to gain access from a given application. This is also explained in the short guide. We are now working on the medium-term solution described in the presentation we already sent to you (see attached email). It should be ready by end of November. 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 -------- Original Message -------- Subject: Short/Medium terms solution to provide controlled access to FI-WARE GE APIs on the FI-WARE Testbed Date: Mon, 22 Oct 2012 07:42:11 +0200 From: Juanjo Hierro To: ab at fi-ppp.eu Dear colleagues, During our last FI-PPP AB virtual meeting, I had the opportunity to share with you the design of the short and medium term solutions we have devised to deal with Access Control to APIs of FI-WARE GEs deployed on the FI-WARE Testbed. I would like you to update the slides that summarize these solutions by means of downloading the presentation available from: https://forge.fi-ware.eu/docman/view.php/7/1398/FI-WARE+Testbed+temporary+Identity+and+Access+Control+solution.pptx There, I have simply fixed some typos on some of the slides and provided some additional information/descriptions. I have also adapted the slides to the official template ;-) During my presentation at the FI-PPP AB virtual meeting, I mentioned that we will try to get the medium-term solution ready by end of November (this means providing support to an OAuth 2.0-based controlled access to FI-WARE GE APIs). It was an AP on me to provide a target date for the short term solution we have already started to implement. Then, let me inform you that we expect this to be before end of October, probably even end of this week. We will keep you informed. Note that in the short term solution will require that the UC applications running on browsers (e.g., browsers running on smartphones) and intending to invoke FI-WARE GE APIs, use a javascript library that will be provided by FI-WARE which will allow to login and re-login whenever access is denied because the IP assigned to the user device has changed. In the medium short term solution, a standard OAuth 2.0 mechanism will be in place. In any case, we will also consider the ability to configure temporary unrestricted access to FI-WARE GEs on the Testbed, in order to deal with critical short-term demos. This is probably the safest solution for the PoC demo of Safecity during November, for example. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From pascal.bisson at thalesgroup.com Tue Oct 30 20:46:26 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 30 Oct 2012 20:46:26 +0100 Subject: [Fiware-security] TR: [Fiware-wpl] IMPORTANT: Convention regarding figures in deliverables (Open Specifications and FI-WARE Architecture) Message-ID: <25204_1351626391_50902E97_25204_8404_1_CBBCD6C304123F4AB23FAAE3055C8C0E0206D918059C@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 Juanjo Hierro Envoy? : mardi 30 octobre 2012 12:56 ? : fiware at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] IMPORTANT: Convention regarding figures in deliverables (Open Specifications and FI-WARE Architecture) Dear colleagues, Several of you have came to me asking what convention should we follow regarding titles linked to figures in FI-WARE documents, particularly FI-WARE GE Open Specifications or Architecture documents. It seems like there is general agreement in that we should be consistent and adopt a single style and that it should not assume that figures are numbered. I agree with that. Consequently, let's follow this convention: * Titles of figures will NOT be numbered neither will use the prefix "Figure: " (or any sort of similar prefix * You have to find the most suitable formula to refer to figures from the text body of your document. Formulas such as "The figure above", "The figure below", "The figure titled 'xxx'", etc use to work well. Please try to implement this convention for the deliverables to be re-submitted. Cheers, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) 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 pascal.bisson at thalesgroup.com Tue Oct 30 21:04:25 2012 From: pascal.bisson at thalesgroup.com (BISSON Pascal) Date: Tue, 30 Oct 2012 21:04:25 +0100 Subject: [Fiware-security] FI-WARE Security GEs V1 Peer review (please address review comments) Message-ID: <28057_1351627469_509032CD_28057_10521_1_ba845ce4-4f60-4613-880c-580a74934691@THSONEA01HUB03P.one.grp> Dear All As per 3rd review cockpit you may reach at: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdDZhTEVmYTlHenkyR0FHMTg3LUVpSWc#gid=0 most of Security GEs open specification produced so far have reviewed by appointed chapter for 3rd peer review (i.e. Data Chapter). As such I will ask each of the Task lead and GE owners to address review comments received asap. Many thanks in advance. Best Regards, Pascal PS: On cockpit you will find peer review form together with doc (GE open spec) with review comments. PS2: Regarding 3rd peer review of Security Monitoring GE and SSS Opt GE they should be uploaded in the coming day. So please Daniel, Lucie check and address asap once uploaded. -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.gidoin at thalesgroup.com Wed Oct 31 18:51:39 2012 From: daniel.gidoin at thalesgroup.com (GIDOIN Daniel) Date: Wed, 31 Oct 2012 18:51:39 +0100 Subject: [Fiware-security] FI-Ware Security - next friday confcall postponed Message-ID: <17642_1351705977_50916579_17642_1829_1_b487aa4c-a040-4221-a44e-3a56e55cb0a3@THSONEA01HUB01P.one.grp> Dear Colleagues, Friday, we will not have our weekly callconf due to the Toussaint holidays. Our enterprise is closed. Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: