Re: [Teas] Martin Vigoureux's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)

Leeyoung <leeyoung@huawei.com> Sun, 27 May 2018 09:26 UTC

Return-Path: <leeyoung@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 881F712D962; Sun, 27 May 2018 02:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NiyaDnzqEhju; Sun, 27 May 2018 02:26:49 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D1F212D955; Sun, 27 May 2018 02:26:49 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A36DC1FF164A6; Sun, 27 May 2018 10:26:42 +0100 (IST)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.382.0; Sun, 27 May 2018 10:26:43 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.141]) by SJCEML701-CHM.china.huawei.com ([169.254.3.168]) with mapi id 14.03.0382.000; Sun, 27 May 2018 02:26:38 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'The IESG' <iesg@ietf.org>
CC: "draft-ietf-teas-actn-framework@ietf.org" <draft-ietf-teas-actn-framework@ietf.org>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "vbeeram@juniper.net" <vbeeram@juniper.net>
Thread-Topic: [Teas] Martin Vigoureux's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)
Thread-Index: AQHT8z0s2Zo2rVJeCUKt9Ti2hECWjKQ/JOsAgAAr+YCAABpIgIAAS9SAgAC68ACAABqCAIACxVJQ
Date: Sun, 27 May 2018 09:26:36 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D0057A8@sjceml521-mbx.china.huawei.com>
References: <152715220506.30129.5178063481055865022.idtracker@ietfa.amsl.com> <074a01d3f34b$08369d10$18a3d730$@olddog.co.uk> <616b6d2f-d7b9-10e5-7414-5d961cd14389@nokia.com> <VI1PR07MB316736406F74CBAF550D735AF06A0@VI1PR07MB3167.eurprd07.prod.outlook.com> <37a75335-6136-4805-e349-5c96c338db26@nokia.com> <VI1PR07MB3167DE560D7D498E40BA865FF0690@VI1PR07MB3167.eurprd07.prod.outlook.com> <60682ba9-aae6-186f-8c9e-5f8f157cea90@nokia.com>
In-Reply-To: <60682ba9-aae6-186f-8c9e-5f8f157cea90@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.81.155]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/80wRjqXM2r8ghgDI1NAoY_7x2Ec>
Subject: Re: [Teas] Martin Vigoureux's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 May 2018 09:26:52 -0000

Hi Martin,

On your one outstanding question, you are correct. In Figure 2, the NO and SP are merged. 

With this, are there any other issues still pending? Please let us know. 

Thanks.
Young

-----Original Message-----
From: Martin Vigoureux [mailto:martin.vigoureux@nokia.com] 
Sent: Friday, May 25, 2018 3:03 AM
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>;; adrian@olddog.co.uk; 'The IESG' <iesg@ietf.org>;
Cc: draft-ietf-teas-actn-framework@ietf.org; teas-chairs@ietf.org; teas@ietf.org; vbeeram@juniper.net
Subject: Re: [Teas] Martin Vigoureux's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)

Thank you Daniele.

I had one outstanding question:

Fig. 1 shows the Customer in relation with the Service Provider but Fig. 
2 shows a boundary between Customer and Network Operator. Are the NO and SP merged in Fig. 2?

Thx
-m

Le 2018-05-25 à 8:28, Daniele Ceccarelli a écrit :
> Hi Martin,
> 
> cleaning up a bit
> [snip]
> 
>>> [DC] We’re referring to the documents that describe the ACTN MPI and 
>>> CMI interfaces. (which is basically a set of YANG models like e.g. 
>>> the TE-Topology, TE-tunnel, etc). Basically the idea is: “I’m not 
>>> telling you here what you have to implement to be compliant with and 
>>> ACTN MPI, but it you can implement and ACTN MPI on top of one of the 
>>> boxes listed above, such box can be put into the ACTN controllers 
>>> hierarchy and that works just fine”.
>> ok ...
>> So you're saying that what an implementation would have to comply 
>> with is out of the scope of this document. Why not be explicit about that?
>>
> [>DC] Exactly. Yes, worth saying it.
> 
>> What about my comment on NBI?
> [>DC] missed it sorry. Since it occurs just once we can extend it.
> 
> [snip]
>>>
>>> 4.1. MDSC Hierarchy
>>>
>>> Can there be more than two levels in the MDSC hierarchy? In other 
>>> words, can an MDSC-L for an MDSC-H be itself an MDSC-H for an MDSC-L?
>>> As a side note, since I made the mistake while writing this, you 
>>> have two occurrences of MSDC (instead of MDSC) in the doc .
> [>DC] will fix it too.
>>>
>>> [DC] exactly, yes.
>> Wouldn't it be worth saying it?
> [>DC] Ok. What about this addition in section 4.1:
> 
> OLD
> The hierarchy of MDSCs can be seen in Figure 4.
> 
> NEW
> The hierarchy of MDSC can be recursive, where an MDSC-H is in turn an MDSC-L to an higher level MDSC-H. An example of hierarchy can be seen in Figure 4.
> 
> 
> 
>>>
>>> Cheers
>>>
>>> Daniele