Med, I really like your proposed new name: Networks for Cloud Operations (Net4CloudOps). Since we are talking dynamic policies to the Network controller to accommodate services hosted in clouds, does NetOps4Clouds also work?
Linda On Fri, Jan 31, 2025 at 7:03 AM <mohamed.boucad...@orange.com> wrote: > Hi Chongfeng, Linda, all, > > > > (ccing CATS/OPSAWG as the current proposed scope seems to overlap with the > work in these WGs) > > > > Thank you for starting this proposal. > > > > I thought that the email discussion we had clarified the relationship with > existing WGs, but I’m afraid that the current work description is confusing > and overlaps with the metrics work done in CATS, in particular. > > > > I still don’t understand the issue about cloud scaling and its interaction > with the network. For example, the use of ACaaS allows already to request > on-demand more resourcing ** without revealing the internal service > structure**. > > > > The list of proposed items is TOO long. I reiterate the comment I made in > the past to prioritize those and select few items to start the work. For > example, the UCMP point seems to be more a routing/steering concern. May be > leave out these items for a future work, when the WG will hopefully show > evidence that it can deliver the contracted few items. > > > > I like much the shim point to present APIs that can be readily consumed by > cloud systems based on YANG models. This is important for integration (and > operationalizing the solution given that distinct approaches are used in > network vs. cloud). > > > > Some first edits/suggestions can be found at: > https://github.com/xiechf974/NeoTec/pull/1/files. I also suggested a new > name :-) > > > > Feel free to grab whatever you think useful. > > > > Cheers, > > Med > > > > *De :* Chongfeng Xie <chongfeng....@foxmail.com> > *Envoyé :* mercredi 29 janvier 2025 03:40 > *À :* neotec <neo...@ietf.org> > *Objet :* [neotec] Welcome to give comments for Neotec charter > > > > Hi folks, > > > > We have prepared the initial version of the Neotec charter. Your comments > and suggestions are welcome. > > > > * https://github.com/xiechf974/NeoTec/blob/main/Neotec-charter.md > <https://github.com/xiechf974/NeoTec/blob/main/Neotec-charter.md>* > > > > > > Moreover, Neotec BOF has been changed from Non-WG forming BOF into > WG-forming BOF. The BOF reques is as follows, > > > > > https://datatracker.ietf.org/doc/bofreq-xie-neotec-network-operations-in-telecom-cloud/ > > > > > > Best regards > > Chongfeng, Linda > > > > ____________________________________________________________________________________________________________ > 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, > 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, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > _______________________________________________ > neotec mailing list -- neo...@ietf.org > To unsubscribe send an email to neotec-le...@ietf.org >
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
