Thanks Chongfeng for useful comments, please see my reply inline below.
发件人: Chongfeng Xie [mailto:[email protected]]
发送时间: 2019年6月29日 21:40
收件人: Qin Wu <[email protected]>; Tianran Zhou <[email protected]>; opsawg
<[email protected]>
主题: 回复: Re: [OPSAWG] I-D Action:
draft-wu-model-driven-management-virtualization-04.txt
Hi,
Firstly, I support the progression of this draft, which gives a architecture of
how to make multiple models work together to meet service provioning
automatically. In addition, I have the following comments,
1) As one type of model in the framework, network resource model should be
given a definition or illustration in section 2.1.2. Personally, I think more
focus should be given to the framework itself, the series of models can be
taken as examples.
[Qin]:Good suggestion, the purpose of this draft is to investigate and discuss
how different level model are put together to define the service, realize the
service and provide the service assurance, one important component is network
resource model, that’s why introduce it in this framework. You are right, to
add clarity, I will add definition for it in the next version.
2) In section 3.1,there is the following text "The IETF has developed a
number of service level, network level and device level modules. Different
service level modules may rely on the same set of network level or device level
modules. Service level modules usually follow top down approach and are mostly
customer-facing models providing a common model construct for higher level
network services, which can be further mapped to network technology-specific
models at lower layer.“”
It seems that this talk about the backgound of this architecture, if so, it
is better to move it to the first section 1 of this draft.
[Qin]: I am not sure I make the scope clear. The logic in the introduction
section of this draft is first describe why model is important, and then
describe what the problem is for these developed models, last clarify the goal
of this draft, I will see how to tweak section 3.1 and consolidate some of
confusing text into section 1. Thanks for your advice.
Chongfeng
________________________________
发件人： Qin Wu<mailto:[email protected]>
发送时间： 2019-06-24 14:43
收件人： Tianran Zhou<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
主题： Re: [OPSAWG] I-D Action:
draft-wu-model-driven-management-virtualization-04.txt
-----邮件原件-----
发件人: Tianran Zhou
发送时间: 2019年6月24日 10:35
收件人: Qin Wu <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
主题: RE: I-D Action: draft-wu-model-driven-management-virtualization-04.txt
> -----Original Message-----
> From: Qin Wu
> Sent: Friday, June 21, 2019 11:47 AM
> To: Tianran Zhou <[email protected]<mailto:[email protected]>>;
> [email protected]<mailto:[email protected]>
> Subject: RE: I-D Action:
> draft-wu-model-driven-management-virtualization-04.txt
>
> Hi, Tianran:
> -----邮件原件-----
> 发件人: Tianran Zhou
> 发送时间: 2019年6月21日 11:11
> 收件人: Qin Wu <[email protected]<mailto:[email protected]>>;
> [email protected]<mailto:[email protected]>
> 主题: RE: I-D Action:
> draft-wu-model-driven-management-virtualization-04.txt
>
> Hi Qin and the authors,
>
> I think this is a valuable work as a comprehensive thinking on the
> model driven work in IETF.
> I am very interested on the architecture, the classification, the
> mapping methodology, etc.
>
> Some points may be useful:
> 1. When I am looking at the " Figure 1: An overview of IETF YANG
> Modules", I think it's better not to list the specific models in "Network
> Service Models".
> Or you can use for example. Otherwise people may think those are the
> only considered service models in IETF.
> [Qin]: Fair point, I intend to use them as example modules and will
> make this clear in the figure 1, e.g., add "etc" for each category of models.
>
>
> 2. While I think it's really good to investigate "all" the current
> models in IETF, you may not need to list them in the main content. You
> can keep the classification, the introduction to each category, the
> inter-connectivity description. But I suggest to move the
> "document:introduction" to the appendix. As you mentioned, the
> document identifies a comprehensive list of modules to exemplify the
> proposed approach, but the document does not claim to be exhaustive. The list
> may keep exploding and make the document not stable.
>
> [Qin]: The rationale behind is first list what model does IETF have on
> the table and then discuss how these models are put together, move
> model introductions to appendix may make people feel disconnected, in
> my personal view. Yes, we have statement to say we are not intending
> to enumerate all IETF defined YANG models. We can add a few text in
> each section title to say the models listed here are just examples.
> One example such section title could
> be:
> "2.1.1. Network Service Models: Definition and Samples".
> Does this address your concern?
Hi Qin,
I am OK with this modification. This makes the draft more clear.
Maybe, a better way is to state only your perspective and conclusion in the
main content. The examples, from my perspective, are support material. I am
afraid they will affect people to focus on your points, especially when you
give each one model an abstract.
But this is trivial compared to your work have done in the draft. :-)
Cheers,
Tianran
[Qin]: Thanks, Tianran, point taken.
> More comments will come later.
>
> Cheers,
> Tianran
> > -----Original Message-----
> > From: OPSAWG [mailto:[email protected]] On Behalf Of Qin Wu
> > Sent: Friday, June 21, 2019 10:38 AM
> > To: [email protected]<mailto:[email protected]>
> > Subject: Re: [OPSAWG] I-D Action:
> > draft-wu-model-driven-management-virtualization-04.txt
> >
> > Hi, Folks:
> > We have submitted an v-04 of
> > draft-wu-model-driven-management-virtualization based on feedback on
> > the ML and last IETF meeting discussion
> > https://datatracker.ietf.org/doc/html/draft-wu-model-driven-manageme
> > nt
> > -v
> > irtualization-04
> > And would like to solicit more feedback on this draft.
> >
> > The goal of this draft is to discuss how top down top down built
> > model (e.g., customer-facing data models) interact with bottom up
> > built model (network resource-facing data models) in the context of
> > service delivery and assurance.
> >
> > The document identifies a comprehensive list of modules to exemplify
> > the proposed approach, but the document does not claim to be exhaustive.
> >
> > Further Comments, suggestions, input are welcome.
> >
> > -Qin (on behalf of coauthors)
> > -----邮件原件-----
> > 发件人: I-D-Announce [mailto:[email protected]] 代表
> > [email protected]<mailto:[email protected]>
> > 发送时间: 2019年6月19日 20:14
> > 收件人: [email protected]<mailto:[email protected]>
> > 主题: I-D Action:
> draft-wu-model-driven-management-virtualization-04.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> > Title : A Framework for Automating Service and Network
> > Management with YANG
> > Authors : Qin Wu
> > Mohamed Boucadair
> > Young Lee
> > Filename :
> > draft-wu-model-driven-management-virtualization-04.txt
> > Pages : 37
> > Date : 2019-06-19
> >
> > Abstract:
> > Model-driven service and network management provides a programmatic
> > and standard-based approach for representing (virtual) services or
> > networks and configuration to the network device that are used to
> > build and deliver the service. Models can be used at various phases
> > of service and network management life cycle such as service
> > instantiation, service provisionning, optimization, monitoring, and
> > diagnostic. Also, models can be designed to automate network
> > management and provide closed-loop control for the sake of adaptive
> > and deterministic service creation, delivery, and maintenance.
> >
> > This document provides a framework that describes and discusses an
> > architecture for service and network management automation with YANG
> > modeling technologies. An applicability of YANG data models to
> > automation of virtualized network service is also investigated.
> >
> > The document aims to exemplify an approach to illustrate the journey
> > from technology-agnostic services to technology-specific actions.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-wu-model-driven-management-vi
> > rt
> > ua
> > lization/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-wu-model-driven-management-virtual
> > iz
> > at
> > ion-04
> > https://datatracker.ietf.org/doc/html/draft-wu-model-driven-manageme
> > nt
> > -v
> > irtualization-04
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-wu-model-driven-management-v
> > ir
> > tu
> > alization-04
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at
> tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > [email protected]<mailto:[email protected]>
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > _______________________________________________
> > OPSAWG mailing list
> > [email protected]<mailto:[email protected]>
> > https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
