[Netslices] 答复: some considerations for the next steps towards IETF101.
"Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com> Tue, 02 January 2018 01:26 UTC
Return-Path: <liguangpeng@huawei.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 40E92124D85 for <netslices@ietfa.amsl.com>; Mon, 1 Jan 2018 17:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.231
X-Spam-Level:
X-Spam-Status: No, score=-4.231 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 VpT1tk6tAV7g for <netslices@ietfa.amsl.com>; Mon, 1 Jan 2018 17:26:26 -0800 (PST)
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 A76C31242EA for <NetSlices@ietf.org>; Mon, 1 Jan 2018 17:26:26 -0800 (PST)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 4A15DCCABB466 for <NetSlices@ietf.org>; Tue, 2 Jan 2018 01:26:23 +0000 (GMT)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 2 Jan 2018 01:26:23 +0000
Received: from DGGEMM513-MBS.china.huawei.com ([169.254.4.39]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0361.001; Tue, 2 Jan 2018 09:26:19 +0800
From: "Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com>
To: Alex Galis <a.galis@ucl.ac.uk>, Network Slices <NetSlices@ietf.org>
Thread-Topic: [Netslices] some considerations for the next steps towards IETF101.
Thread-Index: AQHTe/MOOL1s+b69akyWrmpqI1QN3aNf11KA
Date: Tue, 02 Jan 2018 01:26:19 +0000
Message-ID: <6F4E6B0C717D4641A2B79BC1740D8CF4A7A8CA76@dggemm513-mbs.china.huawei.com>
References: <3205575B-3E70-401C-AB92-7B7FDCED69D9@ucl.ac.uk>
In-Reply-To: <3205575B-3E70-401C-AB92-7B7FDCED69D9@ucl.ac.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.157.47]
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/netslices/p44HpF238jYBolyPmk_AX2WNoAA>
Subject: [Netslices] 答复: some considerations for the next steps towards IETF101.
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: Tue, 02 Jan 2018 01:26:29 -0000
Hi Alex I am glad to join the weekly Wednesday WebCall. Could you include me in the discussing? Best Regards Guangpeng Li > -----邮件原件----- > 发件人: Netslices [mailto:netslices-bounces@ietf.org] 代表 Alex Galis > 发送时间: 2017年12月23日 21:36 > 收件人: Network Slices <NetSlices@ietf.org> > 主题: Re: [Netslices] some considerations for the next steps towards IETF101. > > Hi All > > Please find enclosed some additional considerations for the next steps towards > IETF101. > > The two presentations at the last IETF100 have highlighted the following new > needed work: > > 1. Jari Arkko, Jeff Tantsura et all - Presentation: "Considerations on Network > Virtualization and Slicing" > (https://datatracker.ietf.org/meeting/100/materials/slides-100-rtgwg-sessa-dr > aft-arkko-arch-virtualization/). Proposed new work: > > • 1.1 Data models > > • 1.2 Managing heterogeneous technologies, e.g., across SDN and > traditionally built networks, or manage both general-purpose and very > technology-specific virtualization parameters (e.g., VPNs + 5G radio) > > • 1.3 New underlying VPN or API capabilities — e.g., ability to specify > "statistical" rather than hard performance parameters > > • 1.4 Cross-domain management and VPNs > > • 1.5 Some terminology and conceptual alignment across industry would also > be useful, e.g., to know what words to use in SLAs. > > > 2. Liang Geng et all network slicing proponents - Presentation: "4 drafts from > the netslicing proponents" > (https://datatracker.ietf.org/meeting/100/materials/slides-100-opsawg-ietf10 > 0-netslicing-slides/). Proposed new work: > > • 2.1 Review and feedback from the group and Update and consolidate drafts > > • 2.2 Align terminologies among related drafts > > • 2.3 (Common Operation and Management on network Slicing ) COMS-centric > working items > > • 2.3.1 Service delivery and network configuration model design > (NBI/SBI of NS manager) > > • 2.3.2 Interfaces and data model for Network slicing OAM > interfaces and data models > > o Life-cycle management, fault detections, monitoring and etc. > > o Information exchange between multiple NS domain agents > > • 2.3.3 Management capability exposure to NST > > > > 3. Additional feedback from Benoit: he recommended for the next steps to > better clarify the positioning of COMS work in relation to the following 4 > dimensions: > > • 3.1 Better account of the 4 key elements used in COMS: connectivity, > compute, storage resources + network & service functions > > • 3.2 Better description of the functional blocks and heir positions used in > COMS > > • 3.3 FCAPS coverage > > • 3.4 Coverage of the management of the dataplane > > > > Taking into account all the above and in line with what was already discussed by > Cristina/ Hannu/ Xavier/ Diego / Pedro / Kiran I trust that there is sufficient > interest to progress on existing/new drafts for IETF101 and also as support for > COMS BoF as follows: > > Progress on existing COMS-centric drafts: > > I. consolidated management slicing architecture (i.e. issues 1.5, 2.2 > and 3.2) objective based on existing drafts: > https://tools.ietf.org/html/draft-geng-netslices-architecture-02 and > draft-geng-coms-problem-statement-01 ) > > II. consolidation of COMS Information model (issues 1.1 and 3.1) > based on existing draft > https://www.ietf.org/internet-drafts/draft-qiang-coms-netslicing-information- > model-01.txt) > > III. consolidation of subnet interconnections and slice compositions > based on > https://tools.ietf.org/id/draft-defoy-coms-subnet-interconnection-01.tx > > IV. Refinements of slice management requirements based on > draft-netslices-usecases-02 > > V. Refinements & consolidation of FCAP coverage – issue 3.3 - based > on draft-flinck-slicing-management-00 > > > > Starting some new COMS-centric drafts: > > > VI. Service model mapping to an instance of a slice and its > management – issue 2.3.1 > > VII. Management capability exposure - issue 2.3.3 (i.e. this can be > combined with (V) > > VIII. Cross domain management of slices -issue 1.4 > > IX. Mapping COMS Information model to ACTN – issues 1.2, 3.4 > > > > Please note that “New underlying VPN or API capabilities” (issue 1.3 ) and how > various existing IETF pieces fit together (service models... traffic engineering... > detnetworking... ACTN…, VPN.++…) would be better addressed by RTG. > > > > The NetSlicing proponents will start discussing and progressing the above work > plan in weekly Wednesday at 13:00 London time WebCall starting with 10th > January 2015. Please send an email if you are interested in joining our > Netslicing proponents efforts. > > Thank you in advance > > > > May I take this opportunity to thank you for your support and work at IETF and > to wish you all Best Seasonal Greetings, a Happy 2018 Year and relaxing and > enjoyable vacation time. > > > > Best Regards > > Alex > > > > > > > > > > > > > > > _______________________________________________ > Netslices mailing list > Netslices@ietf.org > https://www.ietf.org/mailman/listinfo/netslices
- Re: [Netslices] some considerations for the next … Alex Galis
- [Netslices] 答复: some considerations for the next … Liguangpeng (Roc, Network Technology Laboratory)