Hi, earlier I notified Pier, that there might be some overlaps between the connectivity GE of WP5 (IOT) and our WP. We had some internal discussions, and agreed, that we can go on the way it is right now, as the similarities might be the result of the current high level of abstraction. However later on we should pay attention (especially regarding task 7.1) not to collect the same information in both WPs. WP5 is doing the same kind of exercise as we did, but I haven't received any information from them yet. Br, Loci On 07/05/2011 02:40 PM, ext Garino Pierangelo wrote: > > HI Thomas, Hi All, > > One problem was found with the document I sent: probably when saving > the file, a few comments that I deleted disappeared, and the remaining > were renamed. So now the comment numbers should be (hopefully): > > -J19, J20 for 'home' questions > > -Jh21: dropping sentence? > > -Jh22, jh23: revision of interfaces to me moved to Cloud Hosting chapter > > -Jh26, jh27: QoS functionality issue between NetIC and S3C > > Please take note of these numbers in your revision. Thanks Thomas for > your inputs. > > BR > > Pier > > *Da:*BANNIZA, Thomas-Rolf [mailto:Thomas-Rolf.Banniza at alcatel-lucent.com] > *Inviato:* martedì 5 luglio 2011 13:41 > *A:* Garino Pierangelo > *Oggetto:* AW: URGENT: revision of comments on > > Hi Pier, > > are you sure you send the correct file? I feel some doubts: > > - Jh22, JH23 do not deal with 'home' but with shifting text to cloud > hosting chapter (not my work area...) > > - Jh24 does not exist, there is only a PG24: By the way, my answer to > PG24: as far as the open networks are concerned (and not, e.g., the > EPC), the implementation is done by NetIC, in some cases S3C will have > preprocessed the control information to ensure that the resulting > control is inline with the internal rules of the network operator and > the SLA with the customer. But NEtIC has the control connection to the > network... > > - JH25 deals with functions provided by NetIC, which would barely be > shifted to Coud Hosting... Any way, my answer to JH25: path control > and traffic control will deal with implementing QoS, but as the > abstract thing 'QoS' can not be implemented directly, you have to do > this via e.g. assigning flows to paths or priorization of traffic... > Might be we have to stress this a little bit more... > > - JH26 deals with S3C functions, which would barely be shifted to Coud > Hosting... My comment to JH26: see my comment to JH24 > > I will send you an updated file with some corrections and > clarifications related to NetIC section later this afternoon. > > Best regards, > > Thomas > > ------------------------------------------------------------------------ > > *Von:*Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] > *Gesendet:* Dienstag, 5. Juli 2011 12:41 > *An:* Hans.Einsiedler at telekom.de; BANNIZA, Thomas-Rolf; Heijnen Henk > (henk.heijnen at technicolor.com); 'Defrance Serge'; Corici, > Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de); 'Fiedler, > Jens'; Vincenzo Suraci; 'Marco Castrucci'; DONADIO, Pasquale; Lorant > Nemeth (lorant.nemeth at nsn.com) > *Betreff:* URGENT: revision of comments on > > Dear All, > > the latest version of the contribution we uploaded last week has been > revised by Juanjo, who introduced a number of comments and proposed > some changes. We have been asked to check and possibly agree on them > by today, as a first document has to be released to the Use Case projects. > > Can each of you directly involved in the specific comment of Juanjo > check by *this afternoon at 17:00* if there are strong objections (and > possible adjustments) in particular to the following changes: > > -Jh6: TCP/IP vs OSI issue > > -Jh7 and jh10: dumb vs smart pipe > > -Jh11, along with the revision of entire sentence > > -Jh22, jh23: 'in the home' system vs 'at home' > > -Jh24: dropping sentence? > > -Jh25, jh26: revision of interfaces to me moved to Cloud Hosting chapter > > -Missing selling points for Cloud Edge GE > > -Revision of changes to first bullet at page 24 "A cloud hosting > provider has a couple of data..." > > -Jh28, jh29: QoS functionality issue between NetIC and S3C > > For all the other comments, I believe we can accept them as they are, > however there will be time to refine them in the next steps. > > Thanks a lot for your contribution! > > Best Regards > Pier > > P.S.: I have inserted in this version the last modifications we > produced (very few, mainly by Thomas) > > ------------------------------------------------------------------ > *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'ambienteRispetta l'ambiente. Non stampare questa mail se > non è necessario.* > > 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'ambienteRispetta l'ambiente. Non stampare questa mail se > non è necessario.* > > > _______________________________________________ > Fiware-i2nd mailing list > Fiware-i2nd at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-i2nd -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20110705/054fb689/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20110705/054fb689/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy