Re: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt

Hi Fatai,

Yes, this is clear. Thanks for catching this. Will correct this in the next opportunity for the revision. 

Best regards,
Young

-----Original Message-----
From: Fatai Zhang 
Sent: Thursday, October 26, 2017 2:19 AM
To: Leeyoung <leeyoung@huawei.com>; Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com>; Lou Berger <lberger@labn.net>; TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
Subject: 答复: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt

Hi Young,

I think you repeat some text, should it be as follows?

NEW: 

>     The capability of a CNC beyond its CMI role is outside the scope of
>     ACTN and may be implemented in different ways. For example, the CNC
>     may in fact be a controller or part of a controller in the customer's domain , or the CNC
>     functionality could also be implemented as part of a provisioning
>     portal. 

Thanks

Fatai

-----邮件原件-----
发件人: Teas [mailto:teas-bounces@ietf.org] 代表 Leeyoung
发送时间: 2017年10月25日 22:14
收件人: Scharf, Michael (Nokia - DE/Stuttgart); Lou Berger; TEAS WG
抄送: TEAS WG Chairs
主题: Re: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt

Hi,

Combining CNC description suggested by Lou and Michael (to be added in Section 3.2) can be:

NEW: 

>     The capability of a CNC beyond its CMI role is outside the scope of
>     ACTN and may be implemented in different ways.  For example, the CNC
>     may in fact be a controller in the customer's domain , or the CNC
>     functionality could also be implemented as part of a provisioning
>     portal. For example, the CNC may in fact be a controller or part of a controller in the customer's domain.

Let us know if this is good to go. 

Thanks.
Young

-----Original Message-----
From: Leeyoung
Sent: Wednesday, October 25, 2017 8:26 AM
To: 'Scharf, Michael (Nokia - DE/Stuttgart)' <michael.scharf@nokia.com>; Lou Berger <lberger@labn.net>; TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
Subject: RE: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt

Hi Michael and Lou,

I agree that the suggested description of CNC would help. I  would leave the CNC name as is  with the reason Michael quoted from Section 5.5. 

Thanks,
Young

-----Original Message-----
From: Scharf, Michael (Nokia - DE/Stuttgart) [mailto:michael.scharf@nokia.com]
Sent: Wednesday, October 25, 2017 8:17 AM
To: Lou Berger <lberger@labn.net>; Leeyoung <leeyoung@huawei.com>; TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
Subject: RE: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt

Your proposed wording would help.

BTW, according to section 5.5, the "CNC" may also be embedded inside a PNC. This "controller-in-controller" embedding could perhaps also be mentioned earlier in the document, e.g., as part of your proposed text. It could be something like: "For example, the CNC may in fact be a controller or part of a controller in the customer's domain".

Anyway, I was just wondering if terminology other than the generic "controller" could perhaps better distinguish the different functionality. I won't insist on any change.

Michael

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Lou Berger
> Sent: Wednesday, October 25, 2017 2:57 PM
> To: Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com>; 
> Leeyoung <leeyoung@huawei.com>; TEAS WG <teas@ietf.org>
> Cc: TEAS WG Chairs <teas-chairs@ietf.org>
> Subject: Re: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt
> 
> Michael,
> 
> What about adding some text (that you propose ;-) to section 3.2 to 
> clarify this point and leaving the CNC name as is.  Perhaps something like:
> 
>     The capability of a CNC beyond its CMI role is outside the scope of
>     ACTN and may be implemented in different ways.  For example, the CNC
>     may in fact be a controller in the customer's domain , or the CNC
>     functionality could also be implemented as part of a provisioning
>     portal.
> 
> Lou
> 
> 
> On 10/25/2017 08:03 AM, Scharf, Michael (Nokia - DE/Stuttgart) wrote:
> > Since the terminology for "PNC" got changed recently, wouldn't it 
> > make
> sense to review the term "CNC" as well?
> >
> > Due to topology abstraction, the entity that implements the CNC
> functionality may not have much "control" over the network. And, as an 
> example, the CNC functionality could also be implemented as part of a portal.
> In such cases the term "controller" may perhaps not be a widely used 
> in industry.
> >
> > For what it is worth, an alternative expansion would be "Customer
> Network Commissioning". Other terms may exist as well.
> >
> > Just as a thought - this would be editorial only
> >
> > Michael
> >
> >
> >> -----Original Message-----
> >> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Leeyoung
> >> Sent: Monday, October 23, 2017 6:42 PM
> >> To: TEAS WG <teas@ietf.org>
> >> Cc: TEAS WG Chairs <teas-chairs@ietf.org>
> >> Subject: Re: [Teas] I-D Action: 
> >> draft-ietf-teas-actn-framework-10.txt
> >>
> >> Hi,
> >>
> >> With -10, we have addressed all comments that we have received and 
> >> believe that the document is complete and ready for WG last call.
> >> The companion drafts (i.e., ACTN  requirements and Info Model)  are 
> >> already completely aligned with the Framework Draft (This version).
> >> Obviously some other documents will need to be updated to bring 
> >> them in synch especially with minor changes in the terminology, but 
> >> we do not think that those changes are in anyway gating the 
> >> progress of this draft through WG LC and RFC publication.
> >>
> >> We'd appreciate your comment on this version 10 which was published 
> >> last week.
> >>
> >> Thanks & Best regards,
> >> Young (on behalf of co-authors and contributors)
> >>
> >>
> >> -----Original Message-----
> >> From: Leeyoung
> >> Sent: Wednesday, October 18, 2017 4:37 PM
> >> To: TEAS WG <teas@ietf.org>
> >> Subject: RE: [Teas] I-D Action: 
> >> draft-ietf-teas-actn-framework-10.txt
> >>
> >> Hi,
> >>
> >> This update was the result of offline discussions with the chairs.
> >> The only change is Section 5.5 where VN recursion with network 
> >> layers was added per Chairs' request.
> >>
> >> Hope this is the last change (until the next one) :)
> >>
> >> Thanks & Best regards,
> >> Young (on behalf of co-authors and contributors).
> >>
> >> -----Original Message-----
> >> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of internet- 
> >> drafts@ietf.org
> >> Sent: Wednesday, October 18, 2017 4:31 PM
> >> To: i-d-announce@ietf.org
> >> Cc: teas@ietf.org
> >> Subject: [Teas] I-D Action: draft-ietf-teas-actn-framework-10.txt
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >> This draft is a work item of the Traffic Engineering Architecture 
> >> and Signaling WG of the IETF.
> >>
> >>         Title           : Framework for Abstraction and Control of Traffic
> Engineered
> >> Networks
> >>         Authors         : Daniele Ceccarelli
> >>                           Young Lee
> >> 	Filename        : draft-ietf-teas-actn-framework-10.txt
> >> 	Pages           : 37
> >> 	Date            : 2017-10-18
> >>
> >> Abstract:
> >>    Traffic Engineered networks have a variety of mechanisms to
> >>    facilitate the separation of the data plane and control plane. They
> >>    also have a range of management and provisioning protocols to
> >>    configure and activate network resources.  These mechanisms
> >>    represent key technologies for enabling flexible and dynamic
> >>    networking.
> >>
> >>    Abstraction of network resources is a technique that can be applied
> >>    to a single network domain or across multiple domains to create a
> >>    single virtualized network that is under the control of a network
> >>    operator or the customer of the operator that actually owns
> >>    the network resources.
> >>
> >>    This document provides a framework for Abstraction and Control of
> >>    Traffic Engineered Networks (ACTN).
> >>
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-teas-actn-framework/
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-ietf-teas-actn-framework-10
> >> https://datatracker.ietf.org/doc/html/draft-ietf-teas-actn-framewor
> >> k-
> >> 10
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-actn-framework-10
> >>
> >>
> >> 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/
> >>
> >> _______________________________________________
> >> Teas mailing list
> >> Teas@ietf.org
> >> https://www.ietf.org/mailman/listinfo/teas
> >>
> >> _______________________________________________
> >> Teas mailing list
> >> Teas@ietf.org
> >> https://www.ietf.org/mailman/listinfo/teas
> >
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas