Dear Jeanpierre, there might be a missunderstanding: - When looking at figure 13, NetIC controls via its southbound interface transport network(s), which is/are composed of routers, switches, crossconnects and so on. This might happen either direct (lower right part of figure 13) or indirect via insertion of a virtual network (lower left part of figure 13; in this case the degree of controllability might depend on the level of controllabiliy offered by the virtual network). Thus, for the networks to be controlled via NetIC, it is NetIC and not S3C which implements the requested QoS features. The control is done via APIs provided for the network elements, e.g. OpenFlow. - For other networks, e.g. legacy networks like 3GPP EPC, S3C might directly interact with this network (as shown in figure 14) Hope that solves your questions,. otherwise don't hesitate to contact me. Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von jeanpierre.lerouzic at orange-ftgroup.com Gesendet: Mittwoch, 29. Juni 2011 13:19 An: pierangelo.garino at telecomitalia.it; fiware-i2nd at lists.fi-ware.eu Betreff: Re: [Fiware-i2nd] R: Summary of comments to the I2ND chapter Hi all, Just writing while thinking... About the 7th bullet I have problems to understand the D2.2a about the following points: * The S3C is above the NetIc in figure 13 and also in figure 4. * I don't know if the NetIc has to manage networks QoS, but the figure 13 shows it is connected to virtual networks, I wonder how it is possible for the NetIC to manage QoS networks (OpenFlow and Forces are mentioned) except if the virtual networks implement a command API that is used by NetIc. * In figure 14 the S3C is connected directly to an LTE EPC and also to the NetIC. So it doesn't seems S3C has anything to do with QoS in routers. Therefore I suggest correcting the figure 13 by showing NetIc to be connected to routers (a transport network, not a command layer). An other options would be that the cloud "virtual networks" would be in fact "virtual routers" such as RouteFlow. But I am not in task 7.3. Best regards, Jean-Pierre ________________________________ De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo Envoyé : mercredi 29 juin 2011 12:05 À : fiware-i2nd at lists.fi-ware.eu Objet : [Fiware-i2nd] R: Summary of comments to the I2ND chapter Dear All, we had yesterday the (periodic) I2ND audioconference with Juanjo, this time to revise the I2ND contribution to deliverable D2.2a. The document is already well in line with expectations, there are however a few points which need some update. Below you'll find the feedback by Juanjo, where I have added the set of actions (and the corresponding owner) we defined in the call to be applied on current release of the document. I 'encourage' the owners of APs to involve other relevant people in the WP who could contribute to complete the action. Please use the attached document to do your changes: have first a look at the few updates already there (in case you have objections to them let me know), then accept the changes and finally insert your modifications. The deadline is providing by tomorrow at noon an updated version of the document, so please distribute you revision no later than tomorrow morning at 11:30 CEST, thanks. Best Regards Pier Da: Juanjo Hierro [mailto:jhierro at tid.es] Inviato: martedì 28 giugno 2011 10:36 A: Garino Pierangelo; Hans.Einsiedler at telekom.de Cc: jhierro >> "Juan J. Hierro" Oggetto: Summary of comments to the I2ND chapter Hi, For your convenience, please find below my comments to the chapter. We already discussed them during our confcall: * I've found the Introduction (text until section 3.6.1.1) a little bit confusing. It was not clear what is the value of introducing the "three stratum" model described there and how it helps to explain the taxonomy of GEs we have finally derived. Things got indeed clear when I started to read the text on page 7 "Figure 4. provides a high level view of the Interface to Network and Devices architecture, composed of the following four Generic Enablers: ...". Before that, I have to confess I was a little bit lost. Please try to improve it. à AP1 Hans * I haven't found any reference to the GSMA standards in the section about CDI (Connected Device Interfacing). Besides, it was not clear what our intention will be regarding the CDI GE ... are we planning to implement the proposed interfaces ? are we going to extend the standard specs providing new specs that can be more complete and valuable to programmers ? We need to provide a clear statement on what we aim to deliver à AP2 Pier * Text below Figure 4 is repeated at the beginning of section 3.6.2.... I suggest to move the beginning of section 3.6.2 to the overview part and merge it with the text that was there below figure 4. The section of Generic Enablers should start sharp with the description of the first one (CDI GE). This is more an editorial comment, trying to avoid repetition and a better alignment in the structure of the different FI-WARE chapters à AP3 Pier * The functionality described below Figure 7 and before section on "High-level Architecture of the CDI GE" is unclear to me. What is the point we intend to make in each of the parapraphs? More or less, a each paragraph corresponds to a problem statement but nothing is said regarding positioning towards that problem statement ... à AP4: Vincenzo/Marco? * Does the CDI GE Architecture description come from any standard effort ? I believe it should be worth mentioning (even if it is compliance to some proposed architecture) à AP5: Pier (Vincenzo/Marco?) * Regarding the Cloud Edge GE, I have detected a relevant degree of overlapping with the description provided in the Cloud Hosting chapter ... we need to fix this. I will come with a proposal on the matter. à Waiting input from Juanjo * Regarding the Net Information and Control (NetIC) I have found that there is no reference to APIs enabling to manage network QoS parameters dynamically ... or is it in the S3C ... It was not clear what would be the GE that would export the API that would deal with dynamic allocation of communication resources and definition QoS parameters à AP3 T7.3/T7.4 Partners? * Regarding the S3C GE, I have found that device localization services are mentioned, as well as generation of context ... we need to coordinate this with twhat is been defined in the Data/Context Management chapter. I will come with a proposal on specific paragraphs to insert in the text that would fix the issue. . à Waiting input from Juanjo There's an additional point I took note of, that is relationship with cloud (and with cloud proxy) for paragraph in the middle of page 10 (I have put a comment on it, see doc attached) . à Joe/Serge? Besides the revision call, I also ask the owners of the APs we defined last week, concerning the analysis of interaction between I2ND and other WP GEs, to provide their comments by tomorrow as well. The interoperability issues between the I2ND GEs and the rest of the Fi-ware GEs should be briefly described, as points to be addressed later by the project, in the 'Question Marks' section (3.6.3). Best regards, -- 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 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. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20110629/ff7e2877/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20110629/ff7e2877/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy