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

Lei Wang <leiw0920@outlook.com> Thu, 04 January 2018 07:11 UTC

Return-Path: <leiw0920@outlook.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 9C3DC12895E for <netslices@ietfa.amsl.com>; Wed, 3 Jan 2018 23:11:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.759
X-Spam-Level:
X-Spam-Status: No, score=-1.759 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 S8LCe_QytIkE for <netslices@ietfa.amsl.com>; Wed, 3 Jan 2018 23:11:47 -0800 (PST)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-oln040092003082.outbound.protection.outlook.com [40.92.3.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 575AD128959 for <NetSlices@ietf.org>; Wed, 3 Jan 2018 23:11:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XFxtI43A93goa1eQX1kqgALoJxvV8XlJMWjLwldnruk=; b=XpA6Ui2JelvdOsn7lXLMei1DvbSxpSzezu1UcqxBefdrxmEy0kdsuWNkPkAmRjB/rHPty2Q69mbHWfGKck7pHum2vhNl2aFjwZ4io6qn6jX4v7vCoYkUjE1R3pusjoISSprC16m0UFaWO/JNYpoq3/ze7tKA5rN2CHCnBLP1f586HliqYzRzC3lKMGqDiiwEzMMxqOhBf7WwEglR3cvbo72oiOR6NIbFyWyMTfBkADkuuT7LPCX+06Yxoe8qqalh+NZTepDgEtLhC6HmWUJosT2gS0EJ6aDX0DSRMx676TdmDfWPjC3IBb8psKoVhLF5f5+FUIKJXlggttWDnmHx5w==
Received: from BL2NAM02FT020.eop-nam02.prod.protection.outlook.com (10.152.76.59) by BL2NAM02HT151.eop-nam02.prod.protection.outlook.com (10.152.77.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.345.12; Thu, 4 Jan 2018 07:11:45 +0000
Received: from DM5PR0501MB3688.namprd05.prod.outlook.com (10.152.76.58) by BL2NAM02FT020.mail.protection.outlook.com (10.152.77.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.345.12 via Frontend Transport; Thu, 4 Jan 2018 07:11:45 +0000
Received: from DM5PR0501MB3688.namprd05.prod.outlook.com ([fe80::5021:1c5b:f83f:8d09]) by DM5PR0501MB3688.namprd05.prod.outlook.com ([fe80::5021:1c5b:f83f:8d09%13]) with mapi id 15.20.0386.005; Thu, 4 Jan 2018 07:11:45 +0000
From: Lei Wang <leiw0920@outlook.com>
To: "qiangli (D)" <qiangli3@huawei.com>, NetSlices <NetSlices@ietf.org>
Thread-Topic: Re: [Netslices] Open Issue I: SouthBound/Mapping Interface
Thread-Index: AdNz7BaJGrRkEFbTREOfWwbxCLzW+g==
Date: Thu, 04 Jan 2018 07:11:45 +0000
Message-ID: <DM5PR0501MB3688237A8CB683F3B8E4C09CC01F0@DM5PR0501MB3688.namprd05.prod.outlook.com>
References: <06C389826B926F48A557D5DB5A54C4ED2A5DEDA1@dggemi509-mbs.china.huawei.com>, <VI1PR07MB084846CB3A16AE9691C1C3E09B0C0@VI1PR07MB0848.eurprd07.prod.outlook.com>, <06C389826B926F48A557D5DB5A54C4ED2A5DFC7D@dggemi509-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:6AC322BD6657113FE91A98CBE363C279BD5B780D4E351B07598640EB404AF962; UpperCasedChecksum:123C0BE856DC0A196C33F6FF2E17096BFEF36B6DAC15436574D73C6FED952145; SizeAsReceived:7199; Count:45
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [mbG85k0JEcxhOYmi02/Bl296d0dLHEie]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BL2NAM02HT151; 6:gYXBUYHEkmHNRBY8K18h+Uu6q2FCmdv7K/HvR1HaomxN6pHPutBfeXdjJWJsBXunlX++2yrNp57cVCBvp762GAg+aGp40KVT84q5qhtaJXe6zhMDac9YM/4BWI3ucG3Iw/c9TCAhaDoxH/KuvFYmweg/gaU5L2D2SCnVI5dYn7iQy7lvTQcTEx2LsCQq/9dvogl7R8wqn+E8GFpFLvhklcnI9SIJ6PtB0e1cGP2UXPKhsXKqGmvqHGHhe6x9s1Xa0Uy+A2Z+Pbj9J+I/gFDdWamlHQ7BPxA5Br9nIxG2PJ7rShDaS3XRkfekFjRsUCIBp8m8L9t8ZEpZbNW7fPZ3SQwkKFiqqko0bojbmpLdXJ4=; 5:wLBUnqmTMBDpRImEO3/5NHSwGZmMfV4rL4aUu1RjAoGS84UqbN+4KMxSYpM5dZuwdiP4KmtyesBX2rwdIMYhyKNHM6Bdq4IMTx93/PyRv2deair0OtlkbQi9OvtEfmjHziVOa+E+36EWXVet8Eff0G9x7xgOYp8Xap7GkRdXZfY=; 24:QxeVQSvd1DI0PUAdY/omvPNnxEPXs4DrTp6sHZJN+Olo0cd3Xs4noWvggkV3PEx1ljRH9Mwc7gP+LDkMxkWFNeIVEx8hysWg0chK1lyxslQ=; 7:kzyAr4AWyPjqq5gm4UyWXhTGpWKPRRhRO5C3iGzwnbp6hkYZoKWTgmeQs5GuXUNZoVZkyYMD9TOlBPF8imMJdHzpHBLDe2ZGrbC9d1f20uWmzMM6CNVZJLQhX+sxko4hPJ3UNRMlrff/G/EguEf3Zw0KrDogPuouqHA26x9cS+mwN2tinR5Rk0Xzq61ccOK8bW2UJb4AAxDBxc+Mvlu/g5B5UFFMk72KowmtXI4oydjTG184DOJOa95bKuk2ibc8
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045); SRVR:BL2NAM02HT151;
x-ms-traffictypediagnostic: BL2NAM02HT151:
x-ms-office365-filtering-correlation-id: 6d091ba9-3f06-4da8-82b9-08d553426960
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:BL2NAM02HT151; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BL2NAM02HT151;
x-forefront-prvs: 054231DC40
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BL2NAM02HT151; H:DM5PR0501MB3688.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR0501MB3688237A8CB683F3B8E4C09CC01F0DM5PR0501MB3688_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6d091ba9-3f06-4da8-82b9-08d553426960
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2018 07:11:45.8047 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2NAM02HT151
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/5A6qp5Mzw5JdBntX1MBh5NnGF7I>
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: Thu, 04 Jan 2018 07:11:49 -0000

Hi Cristina,

I agree with the Option 1. Maybe it is not the proper time to do  SBI standardization work in COMS now, not matter in terms of opportunity or technology.

About the Option 3,  do you mean we can discuss different situations of SBI according to respenctive technologies in information model that can be delivered to multi-domains ( e.g. ACTN, Detnet...) ? Or what you want to say is the classification of technology domains?


Kind Regards

Lei Wang


________________________________
leiw0920@outlook.com

From: qiangli (D)<mailto:qiangli3@huawei.com>
Date: 2017-12-21 17:02
To: Flinck, Hannu (Nokia - FI/Espoo)<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>; 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