From jeanpierre.lerouzic at orange.com Fri Feb 8 10:49:10 2013 From: jeanpierre.lerouzic at orange.com (jeanpierre.lerouzic at orange.com) Date: Fri, 8 Feb 2013 09:49:10 +0000 Subject: [Fiware-i2nd] I2ND Tracker tickets to be updated In-Reply-To: References: <234814FCDC8F8F488971895FFAA291CC0167BB2D0B02@HE111543.emea1.cds.t-internal.com> <4195_1360250151_5113C527_4195_2963_1_AE39E5C17FB7AF45883102E30247E3C3049502@PEXCVZYM12.corporate.adroot.infra.ftgroup> Message-ID: <21727_1360316951_5114CA17_21727_580_1_AE39E5C17FB7AF45883102E30247E3C30496C0@PEXCVZYM12.corporate.adroot.infra.ftgroup> Hi all, Just to verify that we are in sync about Orange trackers: There are four of them: Api mediation, SMS/MMS OneAPI, Telecom enabler and WSC. ? There will be no more work on WSC. I changed the workflow state to close. If need arise I can provide the code. https://forge.fi-ware.eu/tracker/?func=detail&aid=249&group_id=10&atid=192 ? The Telecom enabler/easy API, at last is hosted in our premise here in Rennes. It's a matter of a few days/weeks to offer access to Fi-Ware people. There is no sprint assigned to it as I had no news from this team for nearly all of 2012, so I was not sure about what to do about it. Now the situation seems more stable so I suggest that Pier (as you suggest in the email below) you assign this tracker to R2 because it is hosted now here in Orange premise in Rennes and people that I trust, care for it. https://forge.fi-ware.eu/tracker/?func=detail&aid=247&group_id=10&atid=192 ? SMS/MMS OneAPI is also up and running in our premise, therefore it's a matter of days/weeks to give access to it to Fi-Ware people. I trust the people who designed and implemented it so I suggest to let it assigned to R2 as it is now. https://forge.fi-ware.eu/tracker/?func=detail&aid=246&group_id=10&atid=192 ? The API mediation layer is the core business of my old team, there is code but no implementation (even if I ask for one). But it must not be too complicated to set it up (it's an Apache module) and offer access to it to Fi-Ware people. I suggest to let it to R2 as it is right now. I remarked that the workflow is on closed. I think It's a mistake from my side, please someone who have a better understanding of procedures, don't hesitate to change this workflow state. https://forge.fi-ware.eu/tracker/?func=detail&aid=248&group_id=10&atid=192 About documentation. I was asked to provide documentation for Orange's enablers in December. I asked for this internally in December and as for today I didn't received any consistent documentation from the various Orange groups. Probably it has something to do with reluctance to offer business documentation to a collaborative project. I am sorry for that, but we work to improve the situation. Best regards, Jean-Pierre De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Envoy? : jeudi 7 f?vrier 2013 17:29 ? : LE ROUZIC Jean-Pierre OLNC/OLN; Kay.Haensge at telekom.de Cc : Matthias.Baumgart at telekom.de; Mohamed.Salem at telekom.de; Roman.Szczepanski at telekom.de Objet : R: I2ND Tracker tickets to be updated Hi All, this is perhaps a mistake on my side, I dind't find that there were Epics in the tracker for Orange contributions when I sent the file to Kay, and therefore there were those 'missing' items in the excel sheet. After I sent it to Kay I turned the Epics into Features and assigned them to some minor release/Sprint inside R2. The situation is now the following: - Tracker seems ok (Please J.P. confirm it) - I'm going to change back the tech roadmap page to have those features in the R2 table Please don't do anything on your side, but let me know of any problems you can find. This shows up that the main issue for all of us is to take care of our own items (Features, tickets) in a consistent way: the old tickets mentioning Epics had to be turned into Features long time ago, when the activity was under development. However now it seems the alignment is ok. Thanks and BR Pier Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com] Inviato: gioved? 7 febbraio 2013 16:16 A: Kay.Haensge at telekom.de; Garino Pierangelo Cc: Matthias.Baumgart at telekom.de; Mohamed.Salem at telekom.de; Roman.Szczepanski at telekom.de Oggetto: RE: I2ND Tracker tickets to be updated Hi Kay and all, Please can you give any rational why you move the Orange features in R3? Best regards, Jean-Pierre De : Kay.Haensge at telekom.de [mailto:Kay.Haensge at telekom.de] Envoy? : jeudi 7 f?vrier 2013 15:50 ? : pierangelo.garino at telecomitalia.it Cc : Matthias.Baumgart at telekom.de; Mohamed.Salem at telekom.de; LE ROUZIC Jean-Pierre OLNC/OLN; Roman.Szczepanski at telekom.de Objet : RE: I2ND Tracker tickets to be updated Hi Pier, I tried to call you but nevertheless, I have updated the wiki pages als tried to log the changes in the excel sheet. The Orange's Features are moved to R3. Therefore there are out of the Technical Roadmap of R2. I have added the FIWARE.Feature.I2ND.S3C.NetworkPositioningEnabler.PositioningAccuracy and FIWARE.Epic.I2ND.S3C.NetworkLevelDataDelivery to the Materializing page. FIWARE.Feature.I2ND.S3C.SeamlessNetworkConnectivity.FlowController is moved to R3. Regarding the last Feature FIWARE.Feature.I2ND.S3C.SeamlessNetworkConnectivity.NetworkTunnelConnectivity, this one is no longer used in the development process. Therefore it was closed and had no entries in the epic or roadmap list. Shall we delete this? Now, please have a look again and give me some feedback if still something is wrong. Thank you in advance Kay H?nsge Deutsche Telekom AG T-Labs (Research & Innovation) Kay H?nsge Winterfeldtstr. 21, 10781 Berlin +4930835354269 (Tel.) +4930835358408 (Fax) E-Mail: kay.haensge at telekom.de www.telekom.com Erleben, was verbindet. Deutsche Telekom AG Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren? Obermann (Vorsitzender), Reinhard Clemens, Niek Jan van Damme, Timotheus H?ttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr. DE50478376 Gro?e Ver?nderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. Hinweis: Diese E-Mail und/oder die Anh?nge sind vertraulich und ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte unverz?glich den Absender und vernichten Sie die Nachricht und alle Anh?nge. Vielen Dank. From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Donnerstag, 7. Februar 2013 11:45 To: Szczepanski, Roman; H?nsge, Kay Cc: Baumgart, Matthias Subject: R: I2ND Tracker tickets to be updated Hi All, here is an excel sheet (see S3C tab) with the current situation of materialising wiki VS tech roadmap wiki VS I2ND tracker. I have highlighted the points not aligned with yellow and pink (see explanation below the list), if by today you can provide at least the yellow updates to the pages and tracker, it would be great. Thanks and BR Pier Da: Garino Pierangelo Inviato: mercoled? 6 febbraio 2013 16:17 A: Roman.Szczepanski at telekom.de Cc: Kay.Haensge at telekom.de; Matthias.Baumgart at telekom.de Oggetto: I2ND Tracker tickets to be updated Hello Roman, I have to give the ok for the delivery of the backlog and I found that in the I2ND tracker there are tickets with wrong numbering assigned to you (I assume by Matthias). As the OK for the delivery is rather urgent, could you please check them and correct the numbering asap? I provide you below a list (link) of tickets to be managed, along with the following two 'rules of thumb' to update them: - We have to take a snapshot concerning month 21, i.e. Jan 2013 - We are currently in FIWARE.Release.2.2 and FIWARE.Sprint.2.2.2 (corresponding to February, so for January snapshot it was 2.2.1), as shown in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates - I expect that only the release ID is assigned to all the tickets not belonging to current Sprint or the following one. That is: I expect that there are Sprint ID assigned only up to 2.2.3 and no higher, according to the Agile methodology. It there are others, please remove them (but do not remove the Release ID...). Here are the tickets: 3429 3428 3427 3426 3423 3422 3420 3416 (assigned to Kay) 3180 They have ReleaseID = 2.3 but they already have a Sprint ID (to be removed) 3425 3424 3421 3419 3418 3417 (assigned to Kay) 3322 (assigned to Kay) 3301 (assigned to Kay) Inconsistency between ReleaseID and SprintID: they have ReleaseID=2.3 and SprintID=2.2.x, please check whether they are done or under execution, so ReleaseID must be 2.2, otherwise cancel SprintID Thanks a lot for your help! BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From pierangelo.garino at telecomitalia.it Thu Feb 14 09:59:06 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 14 Feb 2013 09:59:06 +0100 Subject: [Fiware-i2nd] Periodic I2ND call Message-ID: Excel to be used in the PhC today. Talk to you in few minutes Pier (new) Reminder for periodic I2ND audioconference. Below are listed the call details: PIN: 075102 Dial-in number: 1 415 363 0833, (International Dial-in Numbers +44 844 4 73 73 73 / +49 1803 001 178). Local numbers are available in the attached pdf. The following shared doc will be used to collect minutes: https://docs.google.com/document/d/1iav3S_KuMDRJ9_ZFYtBct9ZFtQducvVfco5mlh7CLqo/edit Instructions: 1. Dial the conference number at the time indicated above 2. Enter the PIN, when prompted 3. Speak your full name when prompted and then you will join the conference. If you are the first person to arrive on the conference call, you will hear music. As others arrive on the call you will hear them being announced. Find out how much easier your life could be with Powwownow's free conference calling service. Powwownow - get together whenever! http://www.powwownow.com BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5446 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: raw_20130208_i2nd-PG.xlsm Type: application/vnd.ms-excel.sheet.macroenabled.12 Size: 146475 bytes Desc: raw_20130208_i2nd-PG.xlsm URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USA_en_pwn-dial-in-numbers.pdf Type: application/pdf Size: 61516 bytes Desc: USA_en_pwn-dial-in-numbers.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Thu Feb 14 16:22:27 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 14 Feb 2013 16:22:27 +0100 Subject: [Fiware-i2nd] LIne 19 of excel file Message-ID: Hi All, I got the info about how to deal with the issues mentioned at line 19 of the excel file. The 'Chapter' and 'Enabler' fields need to be filled with text, according to the explanation of the guidelines page at link http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki This means that chapter will be I2ND and Enabler will be one of the four we have (CDI, CE, NetIC, S3C)... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Mon Feb 25 08:57:11 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 25 Feb 2013 08:57:11 +0100 Subject: [Fiware-i2nd] I: [Fiware-wpl] Agile Project Manager role in FI-WARE In-Reply-To: <512AB41C.4010308@tid.es> References: <512AB41C.4010308@tid.es> Message-ID: FYI. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: luned? 25 febbraio 2013 01:45 A: fiware at lists.fi-ware.eu Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Agile Project Manager role in FI-WARE Dear partners, This mail is to introduce Manuel Escriche who will play the Agile Project Manager role in FI-WARE. His main mission will be to make sure that activities are progressing well at the level of all the FI-WARE Technical Chapters, adopting an Agile approach as described in [1]. Manuel will make sure that: * The backlog associated to each FI-WARE Chapter is always up to date describing: * functionality and features supported (or to be supported) by each FI-WARE GEi (Generic Enabler implementation) * activities not yet planned but annotated as to be addressed somewhere in the future * activities planned in the current sprint (current month), either development or other kind of activities * activities fulfilled * The FI-WARE Technical Roadmap [2] is up to date regarding the planning of Epics and Features (envisioned mapping into planned releases) Miguel will meet regularly with each Chapter Lead every Sprint to make sure that: * the activities to be carried out regarding each FI-WARE GEi at the start of a Sprint are clear * work items are considered at each Spring mapping to APs at chapter level identified for the sprint (typically APs identified during joint WPLs/WPAs follow-up confcalls or chapter specific confcalls) * progress is made regarding refinement of Epics and Features planned to be addressed in current release * activities planned in a closing/closed Sprint are actually closed, re-planned or deferred Miguel will meet Chapter leaders either this week or the next week to make sure that planning of Sprint 2.2.3 (see [3]) is defined. Note that report on activities (which obviously maps into justification of costs) will be compared against planning of activities. Manuel has an excellent record coordinating EU FP7 projects and also leading projects where Agile has been applied. Therefore, I'm quite excited and happy that he has joined the FI-WARE coordination team. Miguel will continue working on the rest of project management activities as well as activities related the FI-WARE Testbed. [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology [2] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Technical_Roadmap [3] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From pierangelo.garino at telecomitalia.it Tue Feb 26 16:43:05 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 26 Feb 2013 16:43:05 +0100 Subject: [Fiware-i2nd] No PhC this Week and topics to be addressed in I2ND Message-ID: Dear Partners, This week I need to skip the I2ND periodic PhC, as on Thursday I'm traveling to Barcelona to attend the FI-PPP Workshop. You can find more information on the event at the following link: http://www.fi-ppp.eu/ai1ec_event/fi-ppp-large-event/?instance_id=26993 It is however extremely important that I report to you some of the points discussed in the WPL/WPA PhC yesterday, as they have a strong impact on (and hopefully also benefits for) our activities. SW Delivery for second year review meeting We want to avoid the issues arisen in the first official review last year, i.e. the lack of SW deliverables at the time of the review, which turned into a rejection of costs as you all know. The review meeting cannot take place later than June (beginning of July), but the SW delivery inside the testbed, i.e. FI-WARE R2 availability, is planned at the end of July. We therefore agreed on the following action(s): - Provide for the review meeting an initial set of functionalities of (most of) the GEs planned for R2. - Such functionalities will be a subset of the Features of a GE, that will be ready by the end of March at the end of minor release FIWARE.Release.2.2. - The availability for that minor release will be captured in the Tech Roadmap this week, by splitting the Features for R2 major release into minor releases (see Cloud Hosting tech roadmap page as it is already now at Roadmap of Cloud Hosting ). - It is not necessary that all GEs planned for R2 are available at end of March (as initial release), but in my opinion this could reasonably be done e.g. for CDI and S3C, since there are a number of Features which are already implemented (and reflected in the tracker too). CDI: GeoLocation, QoE.APIHandler(?), (camera?); S3C: API Mediation, (other?) - For what concerns CDI, this goes hand in hand with a proposal to use a 'beta' release of the GE during next month, inside the PoC of one of the Phase 1 UCPs i.e. Instant Mobility. The advantage would be twofold: on one hand, we'll have a UCP showing the use(fullness) of a FI-WARE GE, on our side we can gather the feedback from an early adopter of the GE, so that we'll be better prepared later to 'serve' the incoming requests from the users when R2 is available. - AP on GE Owners: agree or propose alternatives to the above mentioned plan by tomorrow afternoon (15:00). If agreed, please plan the (small) revision of Tech roadmap according to Cloud Hosting example asap. Open Specifications deliverable (and deliverables accompanying the SW: inst/admin guide, user guide, unit testing plan) It is assumed that the two steps approach will be followed also for the documentation (thus again relaxing a little the timing, which originally planned the whole Open Specs deliverable ready by end of April): - Those Features available in March will be fully described as Open Specifications by the end of April - Remaining Features will be fully described in the further update of Open Specs by end of July (SW ready by the end of June) Architecture Deliverable As already discussed in the past PhCs, the Architecture deliverable is to be released. Refined Workplan is: 1 First draft of contributions by chapter ready for peer review: end of February 2 Comments on first draft due by March 8th 3 Second draft of chapters ready for peer review: March 15th 4 Comments on second draft due by March 22th 5 Final version: April 5th I'm aware some GE Teams (e.g. S3C) are currently updating their page, but for the others I strongly need there is an update complete according to this plan as well. Global Epics The Android Security Monitoring GE is to be investigated in detail for possible inclusion in CDI. Analysis is on going, it should complete by the end of the week with an outcome to be sent to Security Team. It is proposed to talk to the GE owner, to acquire more information on the GE. Thanks for taking care all the actions required and BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: