Re: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03

Italo Busi <Italo.Busi@huawei.com> Mon, 17 January 2022 16:56 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3130C3A1453 for <ccamp@ietfa.amsl.com>; Mon, 17 Jan 2022 08:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 kGjNcHbo8Gma for <ccamp@ietfa.amsl.com>; Mon, 17 Jan 2022 08:56:25 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25FAA3A1454 for <ccamp@ietf.org>; Mon, 17 Jan 2022 08:56:25 -0800 (PST)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Jcydn4rMSz6GD5h; Tue, 18 Jan 2022 00:53:17 +0800 (CST)
Received: from fraeml715-chm.china.huawei.com (10.206.15.34) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 17 Jan 2022 17:56:20 +0100
Received: from fraeml715-chm.china.huawei.com ([10.206.15.34]) by fraeml715-chm.china.huawei.com ([10.206.15.34]) with mapi id 15.01.2308.021; Mon, 17 Jan 2022 17:56:20 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: 'Daniele Ceccarelli' <daniele.ceccarelli@ericsson.com>, Aihua Guo <aihuaguo.ietf@gmail.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
CC: Igor Bryskin <i_bryskin@yahoo.com>, Fatai Zhang <zhangfatai=40huawei.com@dmarc.ietf.org>, CCAMP <ccamp@ietf.org>
Thread-Topic: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03
Thread-Index: AQHYC5ChGlba59NIWEieKwDt1Bk9uqxnbh5Q
Date: Mon, 17 Jan 2022 16:56:20 +0000
Message-ID: <8cb8ea3a00794fb6a3ba6e608b19f150@huawei.com>
References: <57454ea9d22240cbad4dd7c29b75f89a@huawei.com> <04c001d808a1$d5b22b50$811681f0$@olddog.co.uk> <b53138302d4a4045a33ebff2360b341f@huawei.com> <2004075666.607918.1642149263418@mail.yahoo.com> <AM8PR07MB829500AFC4EAC646B45A1391F0549@AM8PR07MB8295.eurprd07.prod.outlook.com> <062401d80967$bd0766d0$37163470$@olddog.co.uk> <CAFS+G6RvMYfbamQd5RU0hPzwakF+LOZHy0nvMMVircfGUJMjUQ@mail.gmail.com> <AM8PR07MB8295AF656228994AC8DC4A7FF0579@AM8PR07MB8295.eurprd07.prod.outlook.com>
In-Reply-To: <AM8PR07MB8295AF656228994AC8DC4A7FF0579@AM8PR07MB8295.eurprd07.prod.outlook.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.24.104]
Content-Type: multipart/alternative; boundary="_000_8cb8ea3a00794fb6a3ba6e608b19f150huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/NLKRtYWpqRQdlnkAcSVaEXs0dBA>
Subject: Re: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 16:56:31 -0000

This is also my understanding.

Igor is right that from a data plane perspective all the “ingredients” to realize an OTN slice are defined.

Section 3 of the draft describes the framework for OTN slicing and identifies few gaps in the YANG data models. No gaps are identified in the data plane.

Section 4 of the draft proposes new YANG data models to address the gaps identified in section 3.

Italo

From: Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com]
Sent: lunedì 17 gennaio 2022 11:54
To: Aihua Guo <aihuaguo.ietf@gmail.com>; adrian@olddog.co.uk
Cc: Igor Bryskin <i_bryskin@yahoo.com>; Fatai Zhang <zhangfatai=40huawei.com@dmarc.ietf.org>; CCAMP <ccamp@ietf.org>
Subject: Re: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03

Hi Aihua,

The distinction between realization and intention makes sense. I believe that from the realization point of view they are identical (control plane excluded) but from an intent point of view there is a difference.

Cheers,
Daniele

From: Aihua Guo <aihuaguo.ietf@gmail.com<mailto:aihuaguo.ietf@gmail.com>>
Sent: den 14 januari 2022 23:20
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>
Cc: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com<mailto:daniele.ceccarelli@ericsson.com>>; Igor Bryskin <i_bryskin@yahoo.com<mailto:i_bryskin@yahoo.com>>; Fatai Zhang <zhangfatai=40huawei.com@dmarc.ietf.org<mailto:zhangfatai=40huawei.com@dmarc.ietf.org>>; CCAMP <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03

Hi Adrian, Daniele and Igor,

IMHO an OTN slice, like an IETF network slice, is used to represent an intent from a (internal or external) customer's view. This intent includes a combination of resource requirements which can be expressed by connectivities or topologies, along with the common and OTN technology-specific SLOs. Customers usually do not care how an OTN slice is realized at the control plane and/or data plane, and VPN is one of the possible realizations.

To summarize, an L1VPN with QoS parameters can be considered as a possible realization of an OTN slice.

Also, if I understand it correctly, L1VPN is implemented using the control plane per rfc4878 and is not targeted as an NBI model.

Thanks,
Aihua

On Fri, Jan 14, 2022 at 11:57 AM Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>> wrote:
I think there is a difference between a L3/L2 VPN and a L1VPN that is to do with the nature of connectivity in the underlying network. A packet VPN is expressed as a set of edge points and the edge connectivity capacities, but not the edge-to-edge capacities. A L1VPN (at least for some L1 technologies – but not all?) has to be expressed in terms of edge-to-edge capacities because you cannot do “on-demand” traffic routing within the network – the flow markings are at a macro level.

From that perspective, I’d agree that L1VPN is close to L1 slicing. It would be good to hear the authors spell out the differences that they obviously have in mind.

But, not only did Daniele ask his question in TEAS, he also go an answer 😊. There are service models in which a network slice may look like a “VPN with QoS” – those are the enhanced VPN cases. But there are also service models where the edge-to-edge flows are spelled out in more detail than in a VPN.

Ciao,
Adrian

From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com<mailto:daniele.ceccarelli@ericsson.com>>
Sent: 14 January 2022 16:14
To: Igor Bryskin <i_bryskin@yahoo.com<mailto:i_bryskin@yahoo.com>>; zhangfatai=40huawei.com@dmarc.ietf.org<mailto:40huawei.com@dmarc.ietf.org>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'CCAMP' <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: RE: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03

Indeed a very good question…which is similar to the more generic question of what is the difference between a LxVPN with QoS (e.g a L3VPN bound to a TE tunnel) and a slice which I tried to ask in TEAS (but that’s a different story).
Let’s focus on the difference between L1VPN and OTN slice here.

BR
Daniele

From: CCAMP <ccamp-bounces@ietf.org<mailto:ccamp-bounces@ietf.org>> On Behalf Of Igor Bryskin
Sent: den 14 januari 2022 09:34
To: zhangfatai=40huawei.com@dmarc.ietf.org<mailto:zhangfatai=40huawei.com@dmarc.ietf.org>; Fatai Zhang <zhangfatai=40huawei.com@dmarc.ietf.org<mailto:zhangfatai=40huawei.com@dmarc.ietf.org>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Fatai Zhang' <zhangfatai=40huawei.com@dmarc.ietf.org<mailto:zhangfatai=40huawei.com@dmarc.ietf.org>>; 'CCAMP' <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] 答复: WG adoption poll on draft-zheng-ccamp-yang-otn-slicing-03

Hi Fatai,

I like that you and Adrian like my style, but I did ask questions before the last IETF. The basic one is this:
When I explain my wife what IETF network slice is, I say: Remember, we have this thing called IP VPN?  Network slice is roughly IP VPN with QOS parameters.

Considering that L1VPN cannot be without QOS, my question to the authors what is the difference between L1VPN and OTN slice?

Cheers,
Igor
Sent from Yahoo Mail on Android<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-3b3081161b9d5ba0&q=1&e=df107fd9-1747-4e23-801b-18984b9b6289&u=https%3A%2F%2Fgo.onelink.me%2F107872968%3Fpid%3DInProduct%26c%3DGlobal_Internal_YGrowth_AndroidEmailSig__AndroidUsers%26af_wl%3Dym%26af_sub1%3DInternal%26af_sub2%3DGlobal_YGrowth%26af_sub3%3DEmailSignature>

On Fri, Jan 14, 2022 at 2:00 AM, Fatai Zhang
<zhangfatai=40huawei.com@dmarc.ietf.org<mailto:zhangfatai=40huawei.com@dmarc.ietf.org>> wrote:
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org<mailto:CCAMP@ietf.org>
https://www.ietf.org/mailman/listinfo/ccamp
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org<mailto:CCAMP@ietf.org>
https://www.ietf.org/mailman/listinfo/ccamp