IETF Logo Mail Archive

Re: [lisp] Wireguard and LISP [Was: Virtual meeting]

Jordi Paillissé Vilanova <jordip@ac.upc.edu> Tue, 24 March 2020 19:03 UTC

Return-Path: <jordip@ac.upc.edu>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D233A1276 for <lisp@ietfa.amsl.com>; Tue, 24 Mar 2020 12:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 oxBcKD8FshBh for <lisp@ietfa.amsl.com>; Tue, 24 Mar 2020 12:03:40 -0700 (PDT)
Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id 35A233A126A for <lisp@ietf.org>; Tue, 24 Mar 2020 12:03:39 -0700 (PDT)
Received: from correu-1.ac.upc.es (correu-1.ac.upc.es [147.83.30.91]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id 02OJ3Zv2014862; Tue, 24 Mar 2020 20:03:35 +0100
Received: from [192.168.86.52] (75-59-236-132.lightspeed.sntcca.sbcglobal.net [75.59.236.132]) by correu-1.ac.upc.es (Postfix) with ESMTPSA id E93BD1DD; Tue, 24 Mar 2020 20:03:28 +0100 (CET)
To: Dino Farinacci <farinacci@gmail.com>, "Marc Portoles Comeras (mportole)" <mportole@cisco.com>
Cc: "lisp@ietf.org list" <lisp@ietf.org>
References: <95B658E8-B629-4E44-AB99-E9E406D11FF1@cisco.com> <39E32C9F-28FF-44B4-BE28-255199CEC968@gmail.com> <8A1B78BF-7677-4D8B-9D9B-0741BD037F46@cisco.com> <6E6DACF7-0FBB-48E6-B432-3413646EC3D6@gmail.com>
From: Jordi Paillissé Vilanova <jordip@ac.upc.edu>
Message-ID: <bcf659e8-c380-2d3c-d27b-46b41381c82c@ac.upc.edu>
Date: Tue, 24 Mar 2020 12:03:25 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <6E6DACF7-0FBB-48E6-B432-3413646EC3D6@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/5-mhL_easBP7PvshTbLBwMXe4Vw>
Subject: Re: [lisp] Wireguard and LISP [Was: Virtual meeting]
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Mar 2020 19:04:01 -0000

Hi Dino, Marc,

Yes, we considered adding an IID. However, since this means changing the 
WG kernel code, we discarded this option in favor of a user-space 
solution. I agree that it would be a nice addition though :)

 From an implementation perspective I don't think it's straightforward 
to do LISP in WG encapsulation without substantial processing overhead. 
Right now we're programming the WG interface, but if we want LISP in WG 
we probably need handling packets in user space also.

Thanks,

Jordi

El 24/3/20 a les 10:32, Dino Farinacci ha escrit:
>> Do you mean using lisp encapsulation as part of the encrypted payload? Or as an alternative to the wireguard header?
> The former.
>
>> The wireguard whitepaper seems to establish the dataplane header very specifically, but since it seems to assume that the payload is an ip packet, a lisp packet could work there.
>>
>> Thanks,
>> Marc
> Right.
>
> Dino
>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email