Re: [Netslices] Open Issue I: SouthBound/Mapping Interface

"Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com> Fri, 22 December 2017 14:02 UTC

Return-Path: <hannu.flinck@nokia-bell-labs.com>
X-Original-To: netslices@ietfa.amsl.com
Delivered-To: netslices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEEB712E8A9 for <netslices@ietfa.amsl.com>; Fri, 22 Dec 2017 06:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 nNJFSd71_49i for <netslices@ietfa.amsl.com>; Fri, 22 Dec 2017 06:02:49 -0800 (PST)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50114.outbound.protection.outlook.com [40.107.5.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 095F212D865 for <NetSlices@ietf.org>; Fri, 22 Dec 2017 06:02:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=J/IHxK/G2WZ+EPYtoP8sGbOVbzX0dHjbpw+WrkH30+Y=; b=PEHX92OeI2k3PuDKao4zf6xooBuJxA1ZG1NIRrd8lTzrbtbD5CX1pO4MYQtnGCQw62reQwwcKCmfLYPwDnkT6YBpz4hCjEOil2v34b3/Mh6P1+UJRQCkl0lwrbkrPZnd+eO47SWyWSB0qPh8C91pbvd39C5kKQwCMMdguzr8zks=
Received: from HE1PR07MB0842.eurprd07.prod.outlook.com (10.162.24.156) by HE1PR07MB0842.eurprd07.prod.outlook.com (10.162.24.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.345.10; Fri, 22 Dec 2017 14:02:46 +0000
Received: from HE1PR07MB0842.eurprd07.prod.outlook.com ([fe80::39b6:81e1:87f:6084]) by HE1PR07MB0842.eurprd07.prod.outlook.com ([fe80::39b6:81e1:87f:6084%14]) with mapi id 15.20.0345.013; Fri, 22 Dec 2017 14:02:46 +0000
From: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
To: "qiangli (D)" <qiangli3@huawei.com>, "NetSlices@ietf.org" <NetSlices@ietf.org>
Thread-Topic: [Netslices] Open Issue I: SouthBound/Mapping Interface
Thread-Index: AdNz7BaJGrRkEFbTREOfWwbxCLzW+gFshmWwACcM2QAACbDbgAAxOAMAAAGJO2A=
Date: Fri, 22 Dec 2017 14:02:46 +0000
Message-ID: <HE1PR07MB0842290EB5B00C953C7267349B020@HE1PR07MB0842.eurprd07.prod.outlook.com>
References: <06C389826B926F48A557D5DB5A54C4ED2A5DEDA1@dggemi509-mbs.china.huawei.com> <VI1PR07MB084846CB3A16AE9691C1C3E09B0C0@VI1PR07MB0848.eurprd07.prod.outlook.com> <06C389826B926F48A557D5DB5A54C4ED2A5DFC7D@dggemi509-mbs.china.huawei.com> <HE1PR07MB0842A5BCA7AD2B3BF7BA739E9B0D0@HE1PR07MB0842.eurprd07.prod.outlook.com> <06C389826B926F48A557D5DB5A54C4ED2A5E048B@dggemi509-mbs.china.huawei.com>
In-Reply-To: <06C389826B926F48A557D5DB5A54C4ED2A5E048B@dggemi509-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hannu.flinck@nokia-bell-labs.com;
x-originating-ip: [131.228.32.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR07MB0842; 6:Fp38QP+NaC0/1V9YFduBFe021LIFli/4GUOUlKzO4b/W47nrANrQVVSHbXIDEBljKxO56g67Q64X9dLDHhjsUuXKFuinxlWBtJ+HI1fgOayfSUI7Mx7BVH+JXzgopjfNoqYUKvggR/JSAFWtWNdHfUpIgElnehxgcjfRc2iGKdMNpqM3Yyro5qDmICwdsfKOQDuKDzZmGsQb9M9PtWgilbZnljKkXQUS953G5PWatUY8AKilTbdatqjIfOaH4QQ2V6gZYm6KpBlffJBy5RF5Hi0s4nGhQgNRZiK8UVqpj18Wzj8IL5TXYWqchuP3LxWrTTDkWC3eWIFGvopUYGoc1gFS8yLC932gIdmvfEwDkkw=; 5:0gUKwMajaiTxpB1g0emRf7H3ddTUPbnSP4/ztl7btKaIDvLqEVk4pRG9TdX/M6D3vFMO22Bh8oow7o8JvfpOh1o5QnqsdIgh1iKWqqtRVlQ7hkYdvkXH1QPrgys2PTbfgb5KacIcKqcVzpjJ6PbxsZ3y3IwSxSqC6DEsHHxZ0cU=; 24:5yFksG41bjOpbTJWHahcWZQ6X4/q6y/iDVA9tZdqwsHKbO5ncgrijIJ+bkoClepDfrjauFEAYkAUMP9R3eUS7MpZUVL08NRT2tZn7pdKqhg=; 7:Cneq5xGO8/M8YQIdQNK1ocBGw/9JHJVX168PWjc/rDUmzRI9LHwvqgRuieP9EcP/FKeRJPMp+Iv6SLMNX2/RADIDGhEwWkZJrBu43ARt/b6QOEzoncCv3jdGJwl2rQu7x64tdmXILYZIhS5yFCXqeOu1l16xEjrVXKMDIxftXGnUkmaE43VN8Hq8oukjCHcIbggqpHSDYdXZghwy6xkDXB4aAZpI0ZelsmhxynAI44FNJYExyE5lKjyARKh+uRnh
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: d325eb24-2291-480c-dc10-08d54944adb6
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5600026)(4604075)(3008031)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603307); SRVR:HE1PR07MB0842;
x-ms-traffictypediagnostic: HE1PR07MB0842:
x-microsoft-antispam-prvs: <HE1PR07MB08428DFFFD3CC84C30B551059B020@HE1PR07MB0842.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(50582790962513)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(3231023)(11241501184)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041268)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:HE1PR07MB0842; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:HE1PR07MB0842;
x-forefront-prvs: 05299D545B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(346002)(39860400002)(39380400002)(396003)(57704003)(199004)(189003)(53754006)(6436002)(54896002)(2950100002)(33656002)(55016002)(53936002)(3280700002)(6306002)(99286004)(3660700001)(236005)(25786009)(229853002)(76176011)(2906002)(9686003)(102836004)(7696005)(81166006)(53546011)(6506007)(97736004)(93886005)(66066001)(345774005)(2900100001)(81156014)(3846002)(74316002)(6116002)(790700001)(5660300001)(8936002)(8676002)(478600001)(14454004)(86362001)(105586002)(7736002)(106356001)(110136005)(68736007)(6246003)(316002)(5250100002)(2501003)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB0842; H:HE1PR07MB0842.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB0842290EB5B00C953C7267349B020HE1PR07MB0842eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d325eb24-2291-480c-dc10-08d54944adb6
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Dec 2017 14:02:46.2589 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB0842
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/YI79rCCQBl0DruKY2XW9UByBL7k>
Subject: Re: [Netslices] Open Issue I: SouthBound/Mapping Interface
X-BeenThere: netslices@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is intended for discussion and review of network slicing at IETF." <netslices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netslices>, <mailto:netslices-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netslices/>
List-Post: <mailto:netslices@ietf.org>
List-Help: <mailto:netslices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netslices>, <mailto:netslices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Dec 2017 14:02:54 -0000

Ok. Think I what you might be after. Probably what you want is to have a set of reference or example mappings for few representative technologies? Such as


-          A slice over the WAN/transport network for a given technology,

-          A slice over VNF infrastructure (SFCs and nvo3),

-          A slice that is a concatenation of the two across different domains (this we know is missing).

Is this what you would like to see? If so, it sounds to me reasonable and motivating work and would be  useful to identify possible gaps and needed additions.

Best regards
Hannu

From: qiangli (D) [mailto:qiangli3@huawei.com]
Sent: Friday, December 22, 2017 3:09 PM
To: Flinck, Hannu (Nokia - FI/Espoo) <hannu.flinck@nokia-bell-labs.com>; NetSlices@ietf.org
Subject: RE: [Netslices] Open Issue I: SouthBound/Mapping Interface

Hi Hannu,

You're right. Still that question, If there does not exist a uniform mapping interface between COMS and various implementation technologies, I am afraid we are unable to analyze all possibilities.  That's why I suggested option 3 even I'm also not sure whether we can find out an appropriate classification method.

Best regards,

Cristina QIANG

From: Flinck, Hannu (Nokia - FI/Espoo) [mailto:hannu.flinck@nokia-bell-labs.com]
Sent: Thursday, December 21, 2017 9:43 PM
To: qiangli (D) <qiangli3@huawei.com<mailto:qiangli3@huawei.com>>; NetSlices@ietf.org<mailto:NetSlices@ietf.org>
Subject: RE: [Netslices] Open Issue I: SouthBound/Mapping Interface

Hello Cristina

I am not sure I understand the option 3 sufficiently. What would be the use of the classification? Should we identify classes of technologies that can be served by same/similar mapping based on the classification?

Best regards
Hannu

From: Netslices [mailto:netslices-bounces@ietf.org] On Behalf Of qiangli (D)
Sent: Thursday, December 21, 2017 11:02 AM
To: Flinck, Hannu (Nokia - FI/Espoo) <hannu.flinck@nokia-bell-labs.com<mailto:hannu.flinck@nokia-bell-labs.com>>; NetSlices@ietf.org<mailto:NetSlices@ietf.org>
Subject: Re: [Netslices] Open Issue I: SouthBound/Mapping Interface

Hi Hannu and  others,


Thank you for your comments. As you and Diego mentioned, the standardization of southbound interface is a sensitive matter, we'd better avoid infringing other WGs/RGs.

To solve this issue, maybe we should figure out "Is it possible to have a uniform/standard mapping interface to adapt to a variety of implementation technologies?" first. If Pedro is right, such uniform interface does exist, then it's not a big deal to standardize it IMHO. Otherwise, I think we may need to consider which option listed below will be better:

Option 1: No standardization work on southbound interface, at least before IETF 101
Option 2: Separately analyze all specific technologies as you have done -- ACTN [un-checked], NFV [checked], then how about SFC, VPN...?
Option 3: Classify technologies (e.g., providing connectivity, provide VNF....) , then discuss for each classification.

I personally prefer 1 or 3, what's your opinion?

Best regards,

Cristina QIANG

From: Flinck, Hannu (Nokia - FI/Espoo) [mailto:hannu.flinck@nokia-bell-labs.com]
Sent: Wednesday, December 20, 2017 10:33 PM
To: qiangli (D) <qiangli3@huawei.com<mailto:qiangli3@huawei.com>>; NetSlices@ietf.org<mailto:NetSlices@ietf.org>
Subject: RE: [Netslices] Open Issue I: SouthBound/Mapping Interface

Hello Cristina and others,

I would suggest that  COMS/ATCN interface mapping would be developed in the TEAS WG since that is an IETF WG, is also alluding to slicing topics, has related specifications and the expertise of the transport networks.

However, NFVO related work is currently within NVFRG where the slicing work is a minor subset of much larger territory of what the RG is discussing.  Therefore, it would be better to do such focused work in COMS when and if it becomes an IETF WG.


Best regards
Hannu

From: Netslices [mailto:netslices-bounces@ietf.org] On Behalf Of qiangli (D)
Sent: Wednesday, December 13, 2017 10:41 AM
To: NetSlices@ietf.org<mailto:NetSlices@ietf.org>
Subject: [Netslices] Open Issue I: SouthBound/Mapping Interface

Hi All,

This email is want to collect your opinion on the following issue:

Do we need to standardize the Southbound/Mapping interface of a network slice aware system in COMS? Or do you think this work should be carried out in existing WGs/RGs? (e.g., mapping interface between COMS and ACTN, mapping interface between COMS and NFVO)

Best regards,

Cristina QIANG