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

"qiangli (D)" <qiangli3@huawei.com> Mon, 18 December 2017 07:19 UTC

Return-Path: <qiangli3@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 07EF31276AF for <netslices@ietfa.amsl.com>; Sun, 17 Dec 2017 23:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 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] 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 lOOb2zXKIE4J for <netslices@ietfa.amsl.com>; Sun, 17 Dec 2017 23:19:31 -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 3BBA5126CC4 for <NetSlices@ietf.org>; Sun, 17 Dec 2017 23:19:31 -0800 (PST)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 2A866C1F94FE8; Mon, 18 Dec 2017 07:19:28 +0000 (GMT)
Received: from DGGEMI406-HUB.china.huawei.com (10.3.17.144) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 18 Dec 2017 07:19:28 +0000
Received: from DGGEMI509-MBS.china.huawei.com ([169.254.2.152]) by dggemi406-hub.china.huawei.com ([10.3.17.144]) with mapi id 14.03.0361.001; Mon, 18 Dec 2017 15:19:22 +0800
From: "qiangli (D)" <qiangli3@huawei.com>
To: "Diego R. Lopez" <diego.r.lopez@telefonica.com>, Pedro Martinez-Julia <pedro@nict.go.jp>
CC: "NetSlices@ietf.org" <NetSlices@ietf.org>
Thread-Topic: [Netslices] Open Issue I: SouthBound/Mapping Interface
Thread-Index: AQHTc+9mutS2BrP4sEuZpL0PfF5PfqNAdCwAgAhD3JA=
Date: Mon, 18 Dec 2017 07:19:21 +0000
Message-ID: <06C389826B926F48A557D5DB5A54C4ED2A5DF3D3@dggemi509-mbs.china.huawei.com>
References: <06C389826B926F48A557D5DB5A54C4ED2A5DEDA1@dggemi509-mbs.china.huawei.com> <20171213085009.GH9512@spectre> <EA75F46E-B62D-471A-9D3A-7E350A1991A1@telefonica.com>
In-Reply-To: <EA75F46E-B62D-471A-9D3A-7E350A1991A1@telefonica.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.163.138]
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/szpt1T9PxokPgIzm--MX3PUt5j4>
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: Mon, 18 Dec 2017 07:19:33 -0000

Technically speaking, is it possible to have a uniform/standard mapping interface to adapt to a variety of implementation technologies? 

Best regards,

Cristina QIANG

-----Original Message-----
From: Diego R. Lopez [mailto:diego.r.lopez@telefonica.com] 
Sent: Wednesday, December 13, 2017 5:02 PM
To: Pedro Martinez-Julia <pedro@nict.go.jp>; qiangli (D) <qiangli3@huawei.com>
Cc: NetSlices@ietf.org
Subject: Re: [Netslices] Open Issue I: SouthBound/Mapping Interface

Hmm... I disagree. I'd prefer to go for mapping specs or profiling (or even direct endorsement) whenever possible. Let's avoid to invent another one-and-only standard.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------
On 13/12/2017, 09:50, "Netslices on behalf of Pedro Martinez-Julia" <netslices-bounces@ietf.org on behalf of pedro@nict.go.jp> wrote:

    Dear Li,

    We need to do it in COMS to avoid decentralization and ensure coherence
    among solutions. Otherwise, we would get different interface standards
    and it will be more difficult for the network slicing to be homogeneous
    and thus less usefulness.

    Regards,
    Pedro

    On Wed, Dec 13, 2017 at 08:40:56AM +0000, qiangli (D) wrote:
    > 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
    >

    > _______________________________________________
    > Netslices mailing list
    > Netslices@ietf.org
    > https://www.ietf.org/mailman/listinfo/netslices


    --
    Pedro Martinez-Julia
    Network Science and Convergence Device Technology Laboratory
    Network System Research Institute
    National Institute of Information and Communications Technology (NICT)
    4-2-1, Nukui-Kitamachi, Koganei, Tokyo 184-8795, Japan
    Email: pedro@nict.go.jp
    ---------------------------------------------------------
    *** Entia non sunt multiplicanda praeter necessitatem ***

    _______________________________________________
    Netslices mailing list
    Netslices@ietf.org
    https://www.ietf.org/mailman/listinfo/netslices



________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição