Support the adoption. This draft give the overall view for the different layers of Yang modules that defined within IETF(also applicable for Yang defined by other STD). What I wondering is the that necessaries of the network layer model. More layers means more conversions between different layers, increased complex for the service automation management system and the relationship management between these models. Is there any way or mechanism to manage these interleaved modules in more automatic manners?
Can the above concerns be described in the updated version after its adoption? Best Regards. Aijun Wang China Telecom -----邮件原件----- 发件人: opsawg-boun...@ietf.org [mailto:opsawg-boun...@ietf.org] 代表 Tianran Zhou 发送时间: 2019年10月29日 9:44 收件人: opsawg@ietf.org 抄送: draft-wu-model-driven-management-virtualization.auth...@ietf.org; opsawg-cha...@ietf.org 主题: [OPSAWG] WG adoption call for draft-wu-model-driven-management-virtualization-07 Hi WG, This email starts a 2 weeks working group adoption call for draft-wu-model-driven-management-virtualization-07. https://datatracker.ietf.org/doc/draft-wu-model-driven-management-virtualiza tion/ This document provides a framework that describes and discusses an architecture for service and network management automation that takes advantage of YANG modeling technologies. If you support adopting this document please say so, and please give an indication of why you think it is important. Also please say if you will be willing to review and help the draft. If you do not support adopting this document as a starting point for work on this topic, please say why. This poll will run until Nov 11. Thanks, Tianran and Joe _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
