Re: [Actn] 答复: FW: New Version Notification for draft-ceccarelli-actn-framework-06.txt

Hi Haomian,

Sorry for a very late response to your comment. Just got back to work. 

Please see inline for my comment.

Thanks.
Young

-----Original Message-----
From: ACTN [mailto:actn-bounces@ietf.org] On Behalf Of Zhenghaomian
Sent: Sunday, December 28, 2014 7:09 PM
To: Daniele Ceccarelli; actn@ietf.org
Subject: [Actn] 答复: FW: New Version Notification for draft-ceccarelli-actn-framework-06.txt

Hi Daniele and all,

Merry Christmas and happy new year!

I have not got a chance to review 05 and it is great you update 06 which allowed me to get involved again:) Please find my comments below:

- In section 3.2 and some other places, there are still MDSC mis-spelled as MSDC (totally 11 matches found), maybe a global replacement is helpful; besides one 'controllers' is written as 'controllersr' in the first paragraph of section 3.2, 'collocated' should be 'co-located';

YOUNG>> Good catch, will correct. 

- In Fig. 5, 6 and 7 (section 4.2), there are two DC4 without DC5, one of them need to be changed;  for the PNC at righthand side, 'Transport Network C' is preferred with a CAPITAL 'N';

YOUNG>> OK. 

- In section 4.2.2, VNF was discussed, however the terminology is too similar as NFV (also discussed in 4.2.3) which is well-known and may therefore result in unnecessary misunderstanding. Furthermore, what is the relationship between VNF and Application?

YOUNG>> Yes, it is VNF from NFV. As customer applications might need both network connectivity and certain VNFs (e.g., security verification, etc.) this applicability associates VN request with VNFs. 

- In section 5.1 CMI requirement, I didn't see the need for interaction between CNC and MDSC for item 4 and 5, VN Topology Abstraction Model. My understanding such model is something inside MDSC, with which the abstracted topology could be provided to different customers. If this is true and we want to include some internal requirement in this section, there may also be some additional requirement, such as TED mgmt.

YOUNG>> Here 4, 5 do not mean internal model. 4,5 are meant to provide customer VNs, not the network-wide ones. 

- In section 5.1 CMI requirement, item 7 and 8 has a strict requirement on real-time performance, therefore I think synchronization mechanism is an important piece of work on CMI. Do we need to mention such requirement? Or we have already had such description?

YOUNG>> Yes, we have forgot to put a synchronization requirement. But we put in Section 5.2 (MPI) under item 10 from a network side. 

- In section 5.2 MPI requirement, for item 2, I suggest also include 'other types' to make it consistent with item 2 of section 5.1;

YOUNG>> Ok. 

- In section 5.2 MPI requirement, besides creation and update of LSP, the resource query (from MDSC to PNC) and removal of LSP are missed, both of which should be extensible from PCEP/YANG. I think we can mention these in this section.

YOUNG>> We have in Section 5.1 on life cycle management of VNs (item 8). We may need this in Section 5.2 as well. 

Thank you very much.

Best wishes,
Haomian

-----邮件原件-----
发件人: Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com]
发送时间: 2014年12月24日 3:19
收件人: actn@ietf.org
主题: [Actn] FW: New Version Notification for draft-ceccarelli-actn-framework-06.txt

Hi all,

We have updated the ACTN framework (v.6): http://datatracker.ietf.org/doc/draft-ceccarelli-actn-framework/.
If you don't feel like reading the whole 47 pages from the beginning  think you might be interested in the new sections from 4.2 on and 5.

Major updates include the interface requirements in Section 5.1 (CMI) and 5.2 (MPI) and Section 4.2 (We have added one more Application figure for a ACTN, See section 4.2.3).
Peter’s comments on the IDINIT have also been addressed.

Many thanks and Merry Christmas
Daniele and the authors

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
Sent: martedì 23 dicembre 2014 17:11
To: Daniele Ceccarelli; Luyuan Fang; Young Lee; Daniel King; Luyuan Fang; Daniele Ceccarelli; Daniel King; Young Lee; Diego R. Lopez; Diego Lopez; Sergio Belotti; Sergio Belotti
Subject: New Version Notification for draft-ceccarelli-actn-framework-06.txt

A new version of I-D, draft-ceccarelli-actn-framework-06.txt
has been successfully submitted by Young Lee and posted to the IETF repository.

Name:           draft-ceccarelli-actn-framework
Revision:       06
Title:          Framework for Abstraction and Control of Transport Networks
Document date:  2014-12-23
Group:          Individual Submission
Pages:          47
URL:            http://www.ietf.org/internet-drafts/draft-ceccarelli-actn-framework-06.txt
Status:         https://datatracker.ietf.org/doc/draft-ceccarelli-actn-framework/
Htmlized:       http://tools.ietf.org/html/draft-ceccarelli-actn-framework-06
Diff:           http://www.ietf.org/rfcdiff?url2=draft-ceccarelli-actn-framework-06

Abstract:
   This draft provides a framework for abstraction and control of
   transport networks.

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.

The IETF Secretariat

_______________________________________________
ACTN mailing list
ACTN@ietf.org
https://www.ietf.org/mailman/listinfo/actn