Re: [Teas] Network slicing framework : Issue #7: Workflow

"Ogaki, Kenichi" <ke-oogaki@kddi.com> Thu, 30 September 2021 10:33 UTC

Return-Path: <ke-oogaki@kddi.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 E1E7A3A0A90 for <teas@ietfa.amsl.com>; Thu, 30 Sep 2021 03:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=o365kddi.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 sdhN0lixXtQg for <teas@ietfa.amsl.com>; Thu, 30 Sep 2021 03:33:00 -0700 (PDT)
Received: from kddi.com (athena5.kddi.com [27.90.165.210]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 997723A0A9D for <teas@ietf.org>; Thu, 30 Sep 2021 03:33:00 -0700 (PDT)
Received: from kddi.com ([127.0.0.1]) by LTMC3101.kddi.com (mc MTA5 1.4) with ESMTP id 521093019325765000.14426 for <teas@ietf.org> ; Thu, 30 Sep 2021 19:32:57 +0900
Received: from kddi.com ([10.206.2.120]) by LTMC3101.kddi.com (mc MTA4 1.4) with ESMTP id 421093019325686200.14403 for <teas@ietf.org> ; Thu, 30 Sep 2021 19:32:56 +0900
Received: from LTKC3133.kddi.com ([10.206.20.239]) by LTKC3123.kddi.com (mc MTA6 1.4) with ESMTP id 621093019325229400.28979 ; Thu, 30 Sep 2021 19:32:52 +0900
Received: from LTKC3133.kddi.com (localhost.localdomain [127.0.0.1]) by LTKC3133.kddi.com with ESMTP id 18UAWpfi025529; Thu, 30 Sep 2021 19:32:52 +0900
Received: from LTKC3133.kddi.com.mid_3000618 (localhost.localdomain [127.0.0.1]) by LTKC3133.kddi.com with ESMTP id 18UAMo3x022264; Thu, 30 Sep 2021 19:22:51 +0900
X-SA-MID: 3000618
Received: from LTKC3144.kddi.com ([10.206.20.232]) by LTKC3124.kddi.com (mc MTA 1.4) with ESMTP id 121093019225047700.00329 ; Thu, 30 Sep 2021 19:22:50 +0900
Received: from LTKC3144.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 5BBB113C0053; Thu, 30 Sep 2021 19:22:50 +0900 (JST)
Received: from kddi.com (LTMC3101 [10.206.2.41]) by LTKC3144.kddi.com (Postfix) with ESMTP id 496F213C0043; Thu, 30 Sep 2021 19:22:50 +0900 (JST)
Received: from JPN01-TY1-obe.outbound.protection.outlook.com ([104.47.93.57/tls]) by LTMC3101.kddi.com (mc MTA 1.4) with ESMTP id 121093019224996300.19782 ; Thu, 30 Sep 2021 19:22:49 +0900
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZymQ8HJySTd58+DqzXQtRL2A3HfPA2t0jrwKFckKlIUWspM9sk+6GKiszTFvxuOy5QDTcAasXDUoflx1X/67ckqIdHPnXl5Egi8OJZz8QZvPCUu5TNRpQ6yaOW1wTZWJ1SIINYqr5kjWuHLgJDfFYAyrNf4+eUUhsh9750VCRfCQD/CgylAWm3HPjEQxaT6ICSVoCKdVhYkVJZV4ISwoojhOzTDG7uyvcYTfFPiru2U7t7VEhnAittDFzz42aA+0Q8OxdI5RGdprDWeLpRQRLhr99F1luxAg4cqXHIRYV7Tl8cWUQbcQPLhmGp2sHWpGjDBcWSsYhuQEi3RsgkofNQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=JRL+Q3oBQv3E/5671/eWSEpH46c2Pv2naOyTSK+n0v4=; b=H5Vuytr9PUIjb0ZvLcIEI45zYFlbQktzR9b12gU4mfC9KBX4PcyS6cDZQOwn8sOLAvaiGHc2bbe5oozWhnz/jnFKVzOZULICn1WmSzk++6SKnOXXbAlhCmxe9uCsGfeZa32drPq8r99RVakriMGRDIi3vtGPqLWcJNtQ0WxNoFdwmOWYRLyUCn2Iq179WuOfb03FoSBGG3XPFXE9INutC4jZj+vzZUFlZRi6v9QwqFq4JkeNCgYL9Bw02IUP7htOtgb+AUkPDCIT+xQVoji+rc8UWIzX8NWLoRcpQR6m4WlLoIMrPCjcWhc1lJik616fg9EdVHRtouekMGsgYVbvtw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=kddi.com; dmarc=pass action=none header.from=kddi.com; dkim=pass header.d=kddi.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=o365kddi.onmicrosoft.com; s=selector2-o365kddi-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JRL+Q3oBQv3E/5671/eWSEpH46c2Pv2naOyTSK+n0v4=; b=eKPRgXg66pVXDzscOn+wLlBEib+QH6te/gJz+swCOrX+9Db/4Rmg5WAhpfAOqAJDUWOxEVheoq5t/hjknDCb6d3NBShLLPWW3Nf6DXfp67GNsfckI9x7SrqB/baTd6MATF86G2AX+lnD8WC8/0WjcnXLLyUGOQjhTDiAOF0pPgo=
Received: from OSAPR01MB3554.jpnprd01.prod.outlook.com (2603:1096:604:32::10) by OSBPR01MB5271.jpnprd01.prod.outlook.com (2603:1096:604:40::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4566.15; Thu, 30 Sep 2021 10:22:48 +0000
Received: from OSAPR01MB3554.jpnprd01.prod.outlook.com ([fe80::48a3:a318:863:2730]) by OSAPR01MB3554.jpnprd01.prod.outlook.com ([fe80::48a3:a318:863:2730%5]) with mapi id 15.20.4566.015; Thu, 30 Sep 2021 10:22:48 +0000
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] Network slicing framework : Issue #7: Workflow
Thread-Index: Adezy3Z20CHuNJR/TCK6n8h4jyhklABfCbLAACNBDfAAAPO9UAACo+QQ
Date: Thu, 30 Sep 2021 10:22:48 +0000
Message-ID: <OSAPR01MB3554D03AFF7BAA1F9597893990AA9@OSAPR01MB3554.jpnprd01.prod.outlook.com>
References: <055201d7b3cd$0b577eb0$22067c10$@olddog.co.uk> <6733_1632930272_615489E0_6733_151_7_787AE7BB302AE849A7480A190F8B93303540F420@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <OSAPR01MB35548BCBDDE80A9DC5ACAF1190AA9@OSAPR01MB3554.jpnprd01.prod.outlook.com> <7016_1632993050_61557F1A_7016_25_4_787AE7BB302AE849A7480A190F8B93303540FCED@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <7016_1632993050_61557F1A_7016_25_4_787AE7BB302AE849A7480A190F8B93303540FCED@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: orange.com; dkim=none (message not signed) header.d=none;orange.com; dmarc=none action=none header.from=kddi.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: da301e48-645a-46da-6343-08d983fc4072
x-ms-traffictypediagnostic: OSBPR01MB5271:
x-microsoft-antispam-prvs: <OSBPR01MB5271B232C7D45D8DFCBCFD5590AA9@OSBPR01MB5271.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FtrVxABo8WApb5ZEHXWLaUFMctkklTwNnBAVykSzwBeLM0W7VfkMwfY4z3SnU4uv5gjVCr/5e65bbIchzfs7HjPRICoT56R0M6JfTNLJoTWTRMAJxzg+WCSWZB2JW2BAth10owDzMHsJYU35Areuspx6YQ3SK4D6tFCeJ8keU4WbBz1YR9zmd7fKl6KcdMrcMqx6w8DEQagGlVABBOd37oPCUFbqX5CEKZKM+bMu0r1YYptFJc6E1CprToYNHTo01Ho20by80e4RXDrp+Zucrj7lmRcZuklM4tQ/CLp3YZYfa4VSOnxz5B4DjW6Sh+J4ba1Kjb6Bur8mC8uuZbxYjvhJ/dp8SXXTiZlQUJs8IdI72jUGOX/k4QRteA2yxL6KgLEaoJ+pkV1RJzs5BAuj+7sJrWsbHTyfyXxeq81kiPXYecIihZfTTpCmGTFwr/M5CQG5VK7mvczipYY454eApgaApinbnehGtvPeQ59Trpes3TWSPLoPEffTf6U0qG1p2QzTn7UiTFc6NgkO5uBf/X9muKgP4mLTw2XpoW73h+ivsKZV08/Sd1XleYdPTNUN3GVvED/W4xarI+GNBvB0LgcH2C1DaJeidT2fclczBB3bkuBMAeoI+GGdDssXVaqescfD/w76NovNlW4Khu0GobQXV6NoqSX2b8ACjbm6TPx8hhr6LmPpe538KeqYmJ/8T4yucbZJe4rWjYp6ew6tsFEwVGjnyPQ0LcxT2LXUAKrqd8qrytHeEbc0iLTewkcnxJlxbvb1ofu+Gfks+u/gp/RpofkYdysPWOh9wlLq0w/zBbCYW0Xqa0oCJ47ZsCDoAgyXo8cmLvuKoY4aegZufQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:OSAPR01MB3554.jpnprd01.prod.outlook.com; PTR:; CAT:NONE; SFS:(366004)(9686003)(6506007)(53546011)(5660300002)(52536014)(966005)(8936002)(55016002)(85182001)(8676002)(316002)(110136005)(83380400001)(7696005)(508600001)(71200400001)(2906002)(86362001)(76116006)(186003)(122000001)(38070700005)(66446008)(64756008)(66556008)(66476007)(26005)(38100700002)(33656002)(66946007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: I7n6coWQbeHoUnfVnlqEUoQnMQuXGmxs1A86cnJ9C0f3C8SPUi9wGT3oO8uwOQufHgL0Ss3n1Pj0EQZriNdbkjHFSJPqXjH5G1hzEa0fcPpZzXDTgLq4XfEZitbrxpNMsp264n8+ajdwYWgG8wvSZu9dtl3aTgoU50r2ADHX4DFDyZHRi8WPvOW5P2XZEDq8+3yzbpEHcv+6ad3Vo/xPv8eHONo5eOvNE/1kHrkauJ0T03xgDWpRAkd2B4ccR02kkdl1NBCbKUrYlrOMgC2EocSGPGr2ndS9kDb1842YwYJ2j/BYrOKwTiQbplE3zLgnE2NLdjgotyPy4OPcl4FYgd53+hTbByFfnj4eqbo/VFsW8DZ5l6G/5Jv3t7+nrCpRtLdD246rOvvaF6cjWTycd7JiDxjm0JI0SfMF/gzBubktucFFXmXDiZyFvAS6iAjs4c3WP/KtiLW0RRX6JGgmvJIHSjb2BJIP92Gg4QS2EvwcpREjQ2c7LzJOuNVsiRSEDvMBDSn48AskQMwf+XzQo8kYQF64U1PHtb9wRLeyBrt2578KbePI4sQVFpIkCdosmCpNy5hCD0rG6imdT7dBF5diXdlm9E/mq8WmSx5Kjc9mGFFi/K0R3u8Ycqu/uE7X9e44o0pyivj5uzTjlFynttphZ+ojfP/sTPDKk+NPUJOT+YzgiYwwBNgJvs4CgEQNRNXd6m+w61BQHZ3mgxg9B4toQto84l1fqaQKboJlXZ3w4TnrXtik7sCVOiN4IkjyqDxSg4nBQzh/Yanh2e78AEGS+AoaXbxWKsNvbXJLh4FqgxL6vYkFohYG1dZxq6xudGExPMujAw5W9AbkeZA9gGPks/tKNpluAovX5/TTkimjA/aML8a8IY+UmRMMhiwS1xOGfDm1EHYPY7+wh30RRnohTX98VvMjpeUmmYjd6nUxbS/418y4bhJSTQOASLDJKLkCdvpDnl4M3d/oLFtxB6hFtMKu/bRzJFajn0+gz/C0wEfcXC+XV7eESFBqleB9RGcjsOp2a/x7BLpBHOWOTCLf7YhHHqvLW7WgfURf21OTQSQ0IRwwUuf7FEzEiD+QsbirU+5sOmh+Zva84fdBGC3hhTpba6z4UuQ0DMhBwQytzKXn1XhyI/FGJzeGCXLmmVCi5ILqooPGNzslkKW/A1bwlNE2nZTtOtPm2NYFHDSbngGodx0Vewo5CwoqDmZSInbTxoS7mPTw/BwNOaerOjngjgb1bddK7JS9FyyU0eog9S5FwKK46lU6eXbC1BIvrvByvIh+jejTTBqtT0HjtJ7eWaZDW+R8lfDdYZioFbQ=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: kddi.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: OSAPR01MB3554.jpnprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: da301e48-645a-46da-6343-08d983fc4072
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Sep 2021 10:22:48.4991 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 040b5c43-0c27-49b3-b8e6-cdec886abcee
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: VFHwRHXrgD69k1TfKrQR3L/ujRyldRRin+HzLg12gwoKvLXCOJnattk19afrjzv7katKl3Au+SIFgjZI5yqgew==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSBPR01MB5271
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/XXtR79MHlf4OlEcbLNuWq7RinnY>
Subject: Re: [Teas] Network slicing framework : Issue #7: Workflow
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 30 Sep 2021 10:33:06 -0000

Hi Med,

In the other SDOs, the reservation step may be introduced after a successful feasibility check.
Clause 7.3.3. of ETSI NFV IFA 013 V4.2.1 is easy to understand.
https://www.etsi.org/deliver/etsi_gs/nfv-ifa/001_099/013/04.02.01_60/gs_nfv-ifa013v040201p.pdf

When we assume TE technology, the reservation, LSP setup, is almost same as the creation, but the reservation may be necessary for SFC case.

Thanks,
Kenichi

-----Original Message-----
From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com> 
Sent: Thursday, September 30, 2021 6:11 PM
To: 大垣 健一 <ke-oogaki@kddi.com>; adrian@olddog.co.uk; teas@ietf.org
Subject: RE: [Teas] Network slicing framework : Issue #7: Workflow

Hi Kenichi, 

I agree this makes sense even if I think that this can be handled by the protocol used to place a request (confirmed commit in netconf, for example). 

A successful feasibility check does not guarantee that a subsequent request will be accepted unless some resource preservations are made, though. 

Cheers,
Med

> -----Message d'origine-----
> De : Teas <teas-bounces@ietf.org> De la part de Ogaki, Kenichi Envoyé 
> : jeudi 30 septembre 2021 10:39 À : BOUCADAIR Mohamed INNOV/NET 
> <mohamed.boucadair@orange.com>; adrian@olddog.co.uk; teas@ietf.org 
> Objet : Re: [Teas] Network slicing framework : Issue #7: Workflow
> 
> Hi Adrian and Med,
> 
> As I wrote below before, a feasibility check request step may be 
> introduced before the creation request.
> A feasibility check has a broad sense, but we can limit the scope to 
> the available resource check to create a slice.
> This may be not used by an end user(consumer), but a Customer higher 
> level operations system* may require to avoid the creation failure or 
> suspended state.
> It corresponds to VN compute of Sec. 4.3.1 of actn-vn-yang model.
> 
> https://mailarchive.ietf.org/arch/msg/teas/WZKp2PHrPqH5J5_km8Mz8P2pSVU
> /
> 
> *Figure 1 in draft-ietf-teas-ietf-network-slices-04
> 
> Thanks,
> Kenichi
> 
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of 
> mohamed.boucadair@orange.com
> Sent: Thursday, September 30, 2021 12:45 AM
> To: adrian@olddog.co.uk; teas@ietf.org
> Subject: Re: [Teas] Network slicing framework : Issue #7: Workflow
> 
> Hi Adrian,
> 
> > For that reason, I think it would be wrong to document a workflow.
> > (This is a change to my original opinion!)
> >
> > Maybe add a sentence to explain that the order that the 
> > architectural networks are constructed is open for operational choice.
> 
> Seems reasonable. Internals to the NSC should be kep as such 
> (especially, the second and third bullets of your list).
> 
> Another approach would be to focus only on the visible external 
> behavior,
> e.g.,:
> 
> - The network exposes its (slice) capabilities
> - The customer requests a slice
> - The NSC maps the requests to the capabilities while applies provider 
> policies (if any) and then creates the resource partition
> - The NSC reports back to the customer as a function of the previous 
> step
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Teas <teas-bounces@ietf.org> De la part de Adrian Farrel Envoyé :
> > lundi 27 septembre 2021 20:25 À : teas@ietf.org Objet : [Teas] 
> > Network slicing framework : Issue #7: Workflow
> >
> > Dependent slightly on the resolution of issue #6 (architecture and 
> > terminology), we could document a workflow.
> >
> > For example,:
> > - customer requests a slice
> > - NSC maps slice to a slice group
> > - NSC maps slice group to a resource partition
> > - NSC allocates resources to the resource partition
> >
> > But it seems to me that these steps could happen in pretty much any 
> > order depending to operational preferences and possibly the 
> > technology of the network.
> >
> > For that reason, I think it would be wrong to document a workflow.
> > (This is a change to my original opinion!)
> >
> > Maybe add a sentence to explain that the order that the 
> > architectural networks are constructed is open for operational choice.
> >
> > Cheers,
> > Adrian
> >
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> 
> ______________________________________________________________________
> ____ _______________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
> exploites ou copies sans autorisation. Si vous avez recu ce message 
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi 
> que les pieces jointes. Les messages electroniques etant susceptibles 
> d'alteration, Orange decline toute responsabilite si ce message a ete 
> altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or 
> privileged information that may be protected by law; they should not 
> be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.