Hi Med,

Thank you very much for your new comments and edit suggestions, Linda and I 
have incoporated nealy all of them into the new version. Plus, please see my 
comments inline.

 
From: mohamed.boucadair
Date: 2025-01-31 23:02
To: Chongfeng Xie; neotec
CC: c...@ietf.org; opsawg@ietf.org
Subject: [OPSAWG]Re: [neotec] Welcome to give comments for Neotec charter
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.
[Chongfeng]: We have put the name you suggested into the BOF request and 
charter, it is very straightforward. We plan to specifically discuss its new 
name after the BOF, the name you proposed can be futher discussed. 
 
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**.
[Chongfeng]: Based on you concern, we have updated the background and 
motivation section by adding "While cloud services can scale dynamically using 
mechanisms like ACaaS, network controllers are often unaware of these changes 
timely.", Do you think this can clarify your concern?
 
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. 
[Chongfeng]: Good suggestion, in the new version, we have selected few work 
items initially focused by Neotec(NetOps4Cloud). 
 
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).
[Chongfeng]: We are pleased to hear that you like this point.
 
Some first edits/suggestions can be found at: 
https://github.com/xiechf974/NeoTec/pull/1/files. I also suggested a new name 
:-)

[Chongfeng]: Thank you again for your edit suggestions, they are very helpful 
for improving the charter, we have incoporated them into the new version.
 
Feel free to grab whatever you think useful.
 
Cheers,
Med

Best regards
Chongfeng, Linda
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
 
 
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.
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org

Reply via email to