IETF Logo Mail Archive

Re: [lisp] LISP Overlay Model

Sharon Barkai <Sharon@Contextream.com> Tue, 25 August 2015 14:48 UTC

Return-Path: <Sharon@Contextream.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7EB1AD05D for <lisp@ietfa.amsl.com>; Tue, 25 Aug 2015 07:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 doHr21Y0EWT6 for <lisp@ietfa.amsl.com>; Tue, 25 Aug 2015 07:48:01 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0619.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::619]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B49C1B2CE1 for <lisp@ietf.org>; Tue, 25 Aug 2015 07:48:00 -0700 (PDT)
Received: from DB4PR06MB0909.eurprd06.prod.outlook.com (10.161.250.141) by DB4PR06MB0912.eurprd06.prod.outlook.com (10.161.250.144) with Microsoft SMTP Server (TLS) id 15.1.243.23; Tue, 25 Aug 2015 14:47:42 +0000
Received: from DB4PR06MB0909.eurprd06.prod.outlook.com ([10.161.250.141]) by DB4PR06MB0909.eurprd06.prod.outlook.com ([10.161.250.141]) with mapi id 15.01.0243.020; Tue, 25 Aug 2015 14:47:42 +0000
From: Sharon Barkai <Sharon@Contextream.com>
To: Fabio Maino <fmaino@cisco.com>
Thread-Topic: [lisp] LISP Overlay Model
Thread-Index: AQHQ0u+Ixv5XRsfTYkqbfVvUGylZXp4cg6IAgABVjICAAArw3g==
Date: Tue, 25 Aug 2015 14:47:42 +0000
Message-ID: <9DFAF652-FD9F-45A2-9FC6-22072D13AF49@Contextream.com>
References: <89CA974F-ADB1-444E-BF65-7C2B8C572AA6@gigix.net> <2819C9B6-4BD7-438A-BEF7-6AAB85AD136F@gigix.net>, <55DC76E1.3040109@cisco.com>
In-Reply-To: <55DC76E1.3040109@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Sharon@Contextream.com;
x-originating-ip: [2601:647:4300:d1e2:411d:51:d27c:fde0]
x-microsoft-exchange-diagnostics: 1; DB4PR06MB0912; 5:bI7YhNyWLB5fWFBukgleGbknez4QEn4Cr1hynCQcRkYfeVqMsYxUBs26DMv794aSWAGShX4T2+QCBVz+XB5t05LLbKtuZa0hGvzkcKsHInX6qYHGFRb7oMAXWGKvauLPVydLhzC+G4mSMe9sq4IORw==; 24:0h8+bMUw5uUHQzc54+bN5uecB+0e7WNXe1LrCNLn1RCChSmvAoxjUERW5qiiZDgRbnjUVlnbstCePC56IjcrvRTBXAuDjXMcaWbKCglb9Qg=; 20:KAKl4HWzvaYVpUYmzpvV53zG4IFmO4iSJORJ2iqlUKOkJxJ/DkUUCX9z+O++MCXshYyJpsRTBTgtmQ2EeV7koA==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB0912;
x-microsoft-antispam-prvs: <DB4PR06MB091243C1391A60C150B6711AD8610@DB4PR06MB0912.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(8121501046)(5005006)(3002001); SRVR:DB4PR06MB0912; BCL:0; PCL:0; RULEID:; SRVR:DB4PR06MB0912;
x-forefront-prvs: 06793E740F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(53754006)(199003)(189002)(377454003)(479174004)(77156002)(5002640100001)(110136002)(19580405001)(2950100001)(81156007)(101416001)(36756003)(77096005)(62966003)(4001540100001)(5001860100001)(80792005)(2900100001)(33656002)(19580395003)(82746002)(189998001)(97736004)(5001830100001)(68736005)(92566002)(40100003)(83716003)(2656002)(122556002)(106356001)(10400500002)(46102003)(5007970100001)(105586002)(106116001)(5004730100002)(5001960100002)(64706001)(102836002)(54356999)(76176999)(50986999)(86362001)(15975445007)(87936001)(7059030)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR06MB0912; H:DB4PR06MB0909.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: Contextream.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Contextream.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Aug 2015 14:47:42.4098 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 31ea6a41-1b19-4e44-95ed-6c61c89a1582
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB0912
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/qNc7v210f5RhvH7HAtgxvWfMH98>
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] LISP Overlay Model
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Aug 2015 14:48:03 -0000

Support.

--szb

> On Aug 25, 2015, at 7:08 AM, Fabio Maino <fmaino@cisco.com> wrote:
> 
> As an author, I certainly support inclusion of VXLAN-GPE (and its counterpart LISP-GPE) and I'll continue to contribute to that work.
> 
> Given the wide availability of VXLAN in many HW and SW platforms, it may make sense to include VXLAN as well, especially for the NVO3 use cases. Note that with VXLAN-GPE, support for VXLAN will come almost implicitly.
> 
> 
> Fabio
> 
> 
>> On 8/25/15 2:02 AM, Luigi Iannone wrote:
>> Hi All,
>> 
>> Thanks from the reply so far.
>> 
>> What I gather is that there is interest in extending the LISP overlay model to support other data-planes.
>> 
>> What remain unclear is what those data-planes should be.
>> Note that it is impossible to cover all existing data-planes.
>> 
>> Would be helpful if the group gives a clearer direction by suggesting a set encaps to add support for.
>> (this include as well the willingness to directly contribute to the work)
>> 
>> ciao
>> 
>> L.
>> 
>> 
>>> On 10 Aug 2015, at 00:05, Luigi Iannone <ggx@gigix.net> wrote:
>>> 
>>> Hi,
>>> 
>>> LISP provides a rather complete and powerful control-plane, where
>>> by means of LCAF, possibly any existing namespace can be mapped
>>> on each other.
>>> However, the data-plane is not as flexible. The current specifications
>>> allow only IPv4 over IPv6 and vice versa.
>>> 
>>> In order to create what Sharon Barakai defined “map assisted overlays”
>>> more work is needed.
>>> 
>>> In this context the WG should also decide whether just an extended/enhanced
>>> data-plane is sufficient/needed. Or should the scope be slightly larger and
>>> allow as well to support multiple headers type?
>>> Such header are not necessarily defined by the LISP WG
>>> (e.g.  VXLAN-GPE, GENEVE, GUE, etc.)
>>> 
>>> Would the WG be interested in working in extending the LISP overlay model
>>> in order to provide data-plane support for what the control plane already allows?
>>> And what should be the scope?
>>> 
>>> Joel & Luigi
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email