Re: [Netslices] Data-plane work in DMM WG with slicing concept

Satoru Matsushima <satoru.matsushima@gmail.com> Thu, 09 February 2017 10:33 UTC

Return-Path: <satoru.matsushima@gmail.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 C9EFE12996F for <netslices@ietfa.amsl.com>; Thu, 9 Feb 2017 02:33:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 U8dngwS3su0O for <netslices@ietfa.amsl.com>; Thu, 9 Feb 2017 02:33:55 -0800 (PST)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B254129565 for <netslices@ietf.org>; Thu, 9 Feb 2017 02:33:55 -0800 (PST)
Received: by mail-pg0-x230.google.com with SMTP id v184so57024121pgv.3 for <netslices@ietf.org>; Thu, 09 Feb 2017 02:33:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=BG15Z5hoz1MPmP90Wu19j3/3i3AuLLJZ3u7TSztH+0g=; b=vaeayis22+PrOaeEe/+v4uYUi3xX7kdte8OnJfMtPG6Lft6bftNpRz85wG+2byisuo hha8UKkLaD5xP6UydW9ClPRQZjfhgjbDzkAoHq8rL+7TUndwdEvX/a6ySy4/O3yX4zrF h4Griyp8pp8McBXt9s5tNvdan1hF9p8auK2eMnPvjrRkqsHukjn4+EY2wQMi1XARw1n7 eniQFO7T32KxBVYh4lK6hWZ6TR/OcpHtJ9AnX+4fbi+csoy1ODPaTO5M4RF1X+LD2Y/V qjtHPA9Zj8pXQAZpE9iofp47/IQOhdU2+y5qo4Af/JHCPTtDy+J6/2vJDLi17HBZIqDb s2PA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=BG15Z5hoz1MPmP90Wu19j3/3i3AuLLJZ3u7TSztH+0g=; b=Q66RkHPFPLq0WO3eO5sbXvXt2Io5W8XGUUEkCUkLk5eV4nxJ0Pm+/YnQ3mIQpPsYax cfE8tpuTINexiPBTu7m0xjRHgojOhM5c1s14dV1g4zsQrNV2ce6aRz43HUccMSXtOIoH wOv0RZQX+tb1M0OHgEKFbsRMGg1w82TvEkEzQ947Gdu/SMlbXHvYZRSXWdajW8WHmo9h dp7n7uHX3ctIaW2Ve2eChe6ai+zT7EzO8McxSZrrWpUt9fe8DHAeqa/0KaM2I7LKbCfw 943r8stRaQPdfywCqt7doV3iilpV6rWv744B0VsjGBUSoUw9TSwqti3y6Ow2C9uF3Si5 qylQ==
X-Gm-Message-State: AMke39kCZDkDMiv+SNo/X3ETobvzoq2MI6YP35qiQoXowFxQJ8RLH6X6XoNOqkjrtB2fYA==
X-Received: by 10.98.212.23 with SMTP id a23mr2954429pfh.18.1486636433690; Thu, 09 Feb 2017 02:33:53 -0800 (PST)
Received: from [10.207.114.125] ([202.45.12.164]) by smtp.gmail.com with ESMTPSA id e25sm27767358pfk.3.2017.02.09.02.33.52 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 09 Feb 2017 02:33:53 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset="utf-8"
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <76CD132C3ADEF848BD84D028D243C9279357B4CB@NKGEML515-MBX.china.huawei.com>
Date: Thu, 09 Feb 2017 19:33:51 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <F510ED2D-D849-4C32-91DA-430265C2BF72@gmail.com>
References: <503A1908-2068-47A2-B8E0-5D7E3BF88444@gmail.com> <76CD132C3ADEF848BD84D028D243C9279357B4CB@NKGEML515-MBX.china.huawei.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/p8J921GPa6wg9UDc31IJp---ifw>
Cc: "netslices@ietf.org" <netslices@ietf.org>
Subject: Re: [Netslices] Data-plane work in DMM WG with slicing concept
X-BeenThere: netslices@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Feb 2017 10:33:57 -0000

Hi Jie,

> 
> Thanks for introducing the network slicing related work in DMM. 
> 
> While I don't have much expertise in DMM, my rough understanding is the separation of data plane and control plane in mobile network may have some requirement on network slicing, and for E2E network slicing it may be needed to jointly consider the slicing in mobile network and transport network. It would be great if you could help to describe the slicing requirements from DMM perspective. 
> 


Thanks, but sorry just terse introduction for that DMM work.

Yes you’re right.

The DMM work named Forwarding Policy Configuration (FPC) is a neutral interface from specific mobility management systems, like 3GPP GTP or IETF (P)MIP for example, that to manage data-plane configurations. One of original motivations of DMM is to provide optimal data-path for mobile applications. Each application may see different path as its optimal path so that FPC need to be able to provide that.

Let me explain a little bit about it. FPC is designed to support that an infrastructure operator provides its network as data-plane for multiple mobile operators as tenants who are able to virtually construct multiple Domain (slices) to meet requirements of their applications. The entities of mobility management in a Domain are abstracted as FPC-topology model on the FPC agent which configure data-plane nodes in the infrastructure. That configurations are based on the constructed model and the session states of which mobile control-plane or applications generated with its policies.

For sure that, the virtually constructed model of Domains should be bound to appropriate infrastructure resources, like links, bandwidth and queueing schedule priorities, etc,. Let me think for that with YANG model, I suppose that resources would also be abstracted as a slice topology using i2rs based schemas, ACTN for example, and be instantiated statically or dynamically on demand basis. Then the constructed FPC model can be able to bind that slice instance as its data-plane. In that FPC model if some specific mobile data-plane entities which require NFV infrastructure to be instantiated on it, the data-plane model should also be able to include NFVI as its part of resources as well.

Hope it helps you to understand DMM FPC work, and I’m happy if we can discuss on this perspective.

Best regards,
--satoru



> Best regards,
> Jie
> 
>> -----Original Message-----
>> From: Netslices [mailto:netslices-bounces@ietf.org] On Behalf Of Satoru
>> Matsushima
>> Sent: Tuesday, February 07, 2017 2:02 PM
>> To: netslices@ietf.org
>> Subject: [Netslices] Data-plane work in DMM WG with slicing concept
>> 
>> All,
>> 
>> IETF DMM (Distributed Mobility Management) working group has been
>> chartered to make separation of data-plane from mobile control-plane, which
>> defines data-plane obstruction models with network slicing concept.
>> 
>> Through the discussion on the Netslices list, I’ve noticed what the draft calls
>> “Domain” would almost close to “Network Slicing”.
>> 
>> Data-plane model of FPC provides information and data model by YANG for
>> mobile network which IMO would be helpful to figure slicing model out.
>> 
>> FPC-topology tree is one for that. FPC-policy would be requirements to the slice.
>> 
>> 
>> https://datatracker.ietf.org/doc/draft-ietf-dmm-fpc-cpdp/
>> 
>> 
>> Protocol for Forwarding Policy Configuration (FPC) in DMM
>>             draft-ietf-dmm-fpc-cpdp-05.txt
>> 
>> 
>> Abstract
>> 
>> 
>>   This document describes the solution of data-plane separation from
>>   control-plane which enables a flexible mobility management system
>>   using agent and client functions.  To configure data-plane nodes and
>>   functions, the data-plane is abstracted by an agent interface to the
>>   client.  The data-plane abstraction model is extensible in order to
>>   support many different type of mobility management systems and data-
>>   plane functions.
>> 
>> Best regards,
>> --satoru
>> _______________________________________________
>> Netslices mailing list
>> Netslices@ietf.org
>> https://www.ietf.org/mailman/listinfo/netslices