Re: [Ideas] [lisp] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt
Lin Han <Lin.Han@huawei.com> Thu, 29 September 2016 17:49 UTC
Return-Path: <Lin.Han@huawei.com>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id A9C3312B123;
Thu, 29 Sep 2016 10:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level:
X-Spam-Status: No, score=-6.537 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, RP_MATCHES_RCVD=-2.316, 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 g39cZ5h0L_bM; Thu, 29 Sep 2016 10:49:24 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id BCBEB12B0FA;
Thu, 29 Sep 2016 10:49:23 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com)
([172.18.7.190])
by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id CXD42789; Thu, 29 Sep 2016 17:49:21 +0000 (GMT)
Received: from DFWEML702-CAH.china.huawei.com (10.193.5.176) by
lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server
(TLS) id 14.3.235.1; Thu, 29 Sep 2016 18:49:20 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by
dfweml702-cah.china.huawei.com ([10.193.5.176]) with mapi id 14.03.0235.001;
Thu, 29 Sep 2016 10:49:10 -0700
From: Lin Han <Lin.Han@huawei.com>
To: Padmadevi Pillay Esnault <padma@huawei.com>, Dino Farinacci
<farinacci@gmail.com>, Richard Li <renwei.li@huawei.com>
Thread-Topic: [Ideas] [lisp] Mapping System Requirements and
draft-padma-ideas-problem-statement-00.txt
Thread-Index: AdIZzOP8v2BaiL1kTEal3ROYmzzdQAARGsOAAAyKg6AADWMFMA==
Date: Thu, 29 Sep 2016 17:49:09 +0000
Message-ID: <1D30AF33624CDD4A99E8C395069A2A162AFA9F91@dfweml501-mbb>
References: <F061CEB6876F904F8EA6D6B92877731C39C37147@dfweml501-mbb>
<DD6845A6-3B73-4C0F-9D52-1804C1DEAA56@gmail.com>
<EC7A99B9A59C1B4695037EEB5036666B90DC5E@SJCEML701-CHM.china.huawei.com>
In-Reply-To: <EC7A99B9A59C1B4695037EEB5036666B90DC5E@SJCEML701-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.213.64.181]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
refid=str=0001.0A020201.57ED5421.0345, ss=1, re=0.000, recu=0.000, reip=0.000,
cl=1, cld=1, fgs=0, ip=0.0.0.0,
so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 21593b2ea99517b86651e5381f2c8864
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/d32SycLTlCoFA8OkY2i0c2PLpqU>
Cc: "ideas@ietf.org" <ideas@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>,
Padmadevi Pillay Esnault <padma@huawei.com>
Subject: Re: [Ideas] [lisp] Mapping System Requirements and
draft-padma-ideas-problem-statement-00.txt
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussions relating to the development, clarification,
and implementation of control-plane infrastructures and
functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>,
<mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>,
<mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 17:49:27 -0000
Hi, Padma This sounds interesting, are you saying that the mapping system will finally support the interworking between different Loc/id protocols, such as LISP and HIP and others? Also, could you elaborate the "common control plane". This impressed me it will be a super-controller, isn't it? Thanks Lin -----Original Message----- From: Ideas [mailto:ideas-bounces@ietf.org] On Behalf Of Padmadevi Pillay Esnault Sent: Wednesday, September 28, 2016 4:51 PM To: Dino Farinacci; Richard Li Cc: ideas@ietf.org; lisp@ietf.org; Padmadevi Pillay Esnault Subject: Re: [Ideas] [lisp] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt Hi Richard Thank you for your comment. The ideas problem statement is introducing a new Network Mapping Systems (NMS) in order to have an efficient interoperable solution between ID based protocols. The LISP mapping system's main functionality is to provide the mapping of ID/LOC in LISP. However, the NMS goal is to have a common control plane for multiple data-planes rather than one mapping system or scheme per protocol. We also are building the NMS to cater for a wide variety of fixed and mobility cases including IoT, IP mobility and mobility over heterogeneous access networks. The Network mapping systems may also have different scopes (local, regional or global) and be private or public as well. The expectations is that the NMS will be a powerful extensible infrastructure usable by all and not restricted to specific use cases. Padma -----Original Message----- From: Ideas [mailto:ideas-bounces@ietf.org] On Behalf Of Dino Farinacci Sent: Wednesday, September 28, 2016 3:21 PM To: Richard Li Cc: ideas@ietf.org; lisp@ietf.org Subject: Re: [Ideas] [lisp] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt > Since some efforts have been made, at least partially, in LISP, why do we still want to work on it? Appreciated if you could explain it a little bit. LISP is a solution. The draft is a requirements document. We need to generate requirements to decide if the LISP solution meets them. It might sound backwards, but that is how it works out chronologically. Dino _______________________________________________ Ideas mailing list Ideas@ietf.org https://www.ietf.org/mailman/listinfo/ideas _______________________________________________ Ideas mailing list Ideas@ietf.org https://www.ietf.org/mailman/listinfo/ideas
- [Ideas] Mapping System Requirements and draft-pad… Dino Farinacci
- Re: [Ideas] Mapping System Requirements and draft… Dino Farinacci
- Re: [Ideas] [nvo3] Mapping System Requirements an… Black, David
- Re: [Ideas] [nvo3] Mapping System Requirements an… Michael Menth
- Re: [Ideas] [nvo3] Mapping System Requirements an… Dino Farinacci
- Re: [Ideas] [nvo3] Mapping System Requirements an… Padma Pillay-Esnault
- Re: [Ideas] [nvo3] Mapping System Requirements an… Dino Farinacci
- Re: [Ideas] Mapping System Requirements and draft… Lin Han
- Re: [Ideas] Mapping System Requirements and draft… Dino Farinacci
- Re: [Ideas] [lisp] Mapping System Requirements an… Richard Li
- Re: [Ideas] [lisp] Mapping System Requirements an… Dino Farinacci
- Re: [Ideas] [lisp] Mapping System Requirements an… Padmadevi Pillay Esnault
- Re: [Ideas] Mapping System Requirements and draft… Lin Han
- Re: [Ideas] [lisp] Mapping System Requirements an… Lin Han
- Re: [Ideas] [lisp] Mapping System Requirements an… Dino Farinacci
- Re: [Ideas] [5gangip] Mapping System Requirements… Padmadevi Pillay Esnault
- Re: [Ideas] [5gangip] Mapping System Requirements… Tom Herbert
- Re: [Ideas] Mapping System Requirements and draft… Robert Raszuk
- Re: [Ideas] Mapping System Requirements and draft… Dino Farinacci
- Re: [Ideas] [lisp] Mapping System Requirements an… Michael Menth
- Re: [Ideas] Mapping System Requirements and draft… Michael Menth
- Re: [Ideas] Mapping System Requirements and draft… Dino Farinacci
- Re: [Ideas] [lisp] Mapping System Requirements an… Dino Farinacci
- Re: [Ideas] [lisp] Mapping System Requirements an… Sharon
- Re: [Ideas] [5gangip] Mapping System Requirements… Padmadevi Pillay Esnault