Re: [Netslices] Initial Draft Agenda for COMS BoF
Qin Wu <bill.wu@huawei.com> Fri, 16 March 2018 20:20 UTC
Return-Path: <bill.wu@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 00AB6124BAC for <netslices@ietfa.amsl.com>; Fri, 16 Mar 2018 13:20:57 -0700 (PDT)
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 rZPHJAzfn9H5 for <netslices@ietfa.amsl.com>; Fri, 16 Mar 2018 13:20:55 -0700 (PDT)
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 EE96E124C27 for <NetSlices@ietf.org>; Fri, 16 Mar 2018 13:20:54 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id B71CFE583D242; Fri, 16 Mar 2018 20:20:51 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Mar 2018 20:20:53 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Sat, 17 Mar 2018 04:20:47 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Jari Arkko <jari.arkko@piuha.net>
CC: Benoit Claise <bclaise@cisco.com>, Adrian Farrel <adrian@olddog.co.uk>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, NetSlices <NetSlices@ietf.org>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [Netslices] Initial Draft Agenda for COMS BoF
Thread-Index: AdO9YfmVVJ8jzG+dSYqbOPY9hUinTA==
Date: Fri, 16 Mar 2018 20:20:46 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AD88C3F@nkgeml513-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.55.171]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/pka4ir9QqB_BDI_rPzluBzcc9Jo>
Subject: Re: [Netslices] Initial Draft Agenda for COMS BoF
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, 16 Mar 2018 20:20:57 -0000
Yes, top down and bottom up can not be separated. We have a draft to investigate top down and bottom up interact with each other for agile service creation, delivery and maintenance. https://tools.ietf.org/html/draft-wu-model-driven-management-virtualization-00 -Qin -----邮件原件----- 发件人: Netslices [mailto:netslices-bounces@ietf.org] 代表 Jari Arkko 发送时间: 2018年3月15日 3:51 收件人: Alex Galis <a.galis@ucl.ac.uk> 抄送: Benoit Claise <bclaise@cisco.com>; Adrian Farrel <adrian@olddog.co.uk>; Jeff Tantsura <jefftant.ietf@gmail.com>; Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>; NetSlices <NetSlices@ietf.org> 主题: Re: [Netslices] Initial Draft Agenda for COMS BoF FWIW, my personal opinion is that there critical issue is demonstrating we can actually connect the top-down and bottom-up in some way. Sometimes it is useful just as a thought exercise to consider what would be the smallest possible thing we could do and how that relates to existing pieces. E.g., "we will extend a data model from WG X in this manner". Or "we make a new construct that can be mapped to something in WG Y". Does someone have an idea what the possible answer might be? Once we know an answer (or some), we can then extend to bigger things and see how far we want to go. Jari _______________________________________________ Netslices mailing list Netslices@ietf.org https://www.ietf.org/mailman/listinfo/netslices