Hi Med,
Thank you for your further comments and suggestions. I agree with you that “Connecting a Network Provider to a Cloud Environment” in draft-ietf-opsawg-teas-attachment-circuit-18 can be a prerequisite for NeoTec. I have a question regarding to the two sevice models you proposed for NeoTec, i.e. n2c and c2n, would you say a little about their differece? Best regards Chongfeng 发件人： mohamed.boucadair 发送时间： 2024-12-18 15:00 收件人： Linda Dunbar; Chongfeng Xie 抄送： neotec; opsawg; sunqiong 主题： [neotec] Re: NeoTec：Relation with AC/OPSAWG Hi Linda, (I saw your other message, which I think is not accurate in some parts such as decentralized nature, etc.) Please see inline. Cheers, Med De : Linda Dunbar <linda.dun...@futurewei.com> Envoyé : mercredi 18 décembre 2024 02:04 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; Chongfeng Xie <chongfeng....@foxmail.com> Cc : neotec <neo...@ietf.org>; opsawg <opsawg@ietf.org>; sunqiong <sunqi...@chinatelecom.cn> Objet : RE: [neotec] Re: NeoTec：Relation with AC/OPSAWG Med, Is it correct that the “between peer controllers/orchestrater” depicted in the Figure 3 of draft-ietf-opsawg-teas-attachment-circuit-18 refers to interactions between Customer Controller and Provider controller? [Med] ACK. You can see an applicability example at https://datatracker.ietf.org/doc/html/draft-ietf-teas-5g-ns-ip-mpls-13#figure-7 (with NFs, etc.). Are these models “between peer controllers” only for provisioning? [Med] Can also be used for reporting, etc. “Connecting a Network Provider to a Cloud Environment” described in “draft-ietf-opsawg-teas-attachment-circuit-18#name-connecting-a-virtualized-en” describes the ACs and bearer services that provide the infrastructure for communication. Can this serve as a foundational layer for NeoTec to build upon? [Med] I think that layer is a prerequisite to build neotec. The services will be provided by network to cloud (and vice versa) should be bound to ACs/bearers. “Connectivity of Cloud Network Functions” described in “draft-ietf-opsawg-teas-attachment-circuit-18#name-connectivity-of-cloud-netwo” addresses the connectivity of virtualized/cloud network functions, which aligns with NeoTec's objective of integrating distributed Service Function instances hosted in Cloud DCs. However, it doesn’t include details about exposing real-time environmental status of Service Function instances to assist dynamic network path decisions. [Med] Such exposure is not provided in the ACaaS itself. This is where concrete proposals are needed to exemplify how things can be plugged together in neotec, e.g., * Leverage what CATS WG will produce in term of metrics and their dissemination. * Consider two new service models to model neotec as a service over ACs (n2c, c2n). These service models do not need to augment ACaaS, but at least use the ac-svc-refs. These approaches may not be mutually exclusive. Is draft-ietf-opsawg-teas-attachment-circuit-18 close to WGLC? Or is it still ongoing with more changes to add? [Med] The AC I-Ds passed IETF LC and are scheduled for IESG review in jan 2025. I don’t think we need to touch those for neotec. If an augmentation is needed (which I’m not sure about yet), then this can be done similar to what DMM WG is doing https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/ Thanks, Linda From: mohamed.boucad...@orange.com <mohamed.boucad...@orange.com> Sent: Monday, December 16, 2024 11:41 PM To: Chongfeng Xie <chongfeng....@foxmail.com> Cc: neotec <neo...@ietf.org>; opsawg <opsawg@ietf.org>; sunqiong <sunqi...@chinatelecom.cn> Subject: [neotec] Re: NeoTec：Relation with AC/OPSAWG Hi Chongfeng, Thanks for the follow-up. I expect neotec to produce service models. As you rightfully mentioned, correlating with the underlying ACs will be required to deliver the (bidir?) services. Please note that the ACaaS is not between network devices but between peer controllers/orchestrater. I suggest you look into as this may be useful for neotec: https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-teas-attachment-circuit-18#section-4.3 (Figure 3) https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-teas-attachment-circuit-18#name-connecting-a-virtualized-en (connecting a network provider to a cloud env) https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-teas-attachment-circuit-18#name-connectivity-of-cloud-netwo (connection network functions in the cloud) Cheers, Med De : Chongfeng Xie <chongfeng....@foxmail.com> Envoyé : lundi 16 décembre 2024 11:46 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> Cc : neotec <neo...@ietf.org>; opsawg <opsawg@ietf.org>; sunqiong <sunqi...@chinatelecom.cn> Objet : [neotec] NeoTec：Relation with AC/OPSAWG Hi Med, [Med]: The interconnection between cloud/network can be seen as an AC. You may want elaborate in your WG relationships below the link with OPSAWG. Thank you for your raising AC in cloud/network scenario and suggestion of adding relationship of NeoTec with OPSAWG. I think you are talking about the interconnection between the devices in cloud and network. We are aware of the data model for AC management in OPSAWG. Here we consider the interaction between the controllers of network and cloud, and that with services, they should have a correlation with AC. That said, we will consider the relationship with OPSAWG. Best regards Chongfeng ____________________________________________________________________________________________________________Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent doncpas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signalera 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. ____________________________________________________________________________________________________________ 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
