IETF Logo Mail Archive

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

"Marc Portoles Comeras (mportole)" <mportole@cisco.com> Tue, 24 March 2020 17:31 UTC

Return-Path: <mportole@cisco.com>
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 A248B3A0D03 for <lisp@ietfa.amsl.com>; Tue, 24 Mar 2020 10:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.6
X-Spam-Level:
X-Spam-Status: No, score=-14.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=NChBj5K9; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=WgTB74WL
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 L_CsA58cMqPB for <lisp@ietfa.amsl.com>; Tue, 24 Mar 2020 10:31:03 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 667323A0CDD for <lisp@ietf.org>; Tue, 24 Mar 2020 10:31:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1574; q=dns/txt; s=iport; t=1585071063; x=1586280663; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=AcguuiG6FcCdakMcKjEP0zlOCCtq/tVkvw0b1Rvrp/0=; b=NChBj5K9LkrpkKzGXVJGWVI47IJgzBO5OgelOstEuRTSGqnZBfEkd7Ab M2sS3fsxeUE//ugNkZnFtiS8inaDytw7VAeKXuXt+ciACMuDUpEwLNlt5 lDaJKTYtU8tfNiT77AOJRmkmgBp/wgFwLugWttsPltbdIAdAIM7meYCRE w=;
IronPort-PHdr: 9a23:NJYXbB1Xj0vnjuq2smDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQDFX8NuLtayESF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFBgBBQ3pe/4QNJK1mHAEBAQEBBwEBEQEEBAEBgXuBVFAFgUQgBAsqCoQOg0UDinOCOiWJbI4yglIDVAoBAQEMAQEtAgQBAYREAheCECQ4EwIDAQELAQEFAQEBAgEFBG2FVgyFYwEBAQECARIREQwBATcBBAsCAQgYAgImAgICHxEVEAIEDgUigwSCTAMOIAGjCwKBOYhidYEygn8BAQWCRYJsDQuCDAmBDiqMEh0aP4FBgREnDBSCTT6CG4VBMoIskHefHUQKgjySS4Q9HZtemleQLQIEAgQFAg4BAQWBaSKBWHAVZQGCQVAYDY4dERKDUIpVdIEpjRMBgQ8BAQ
X-IronPort-AV: E=Sophos;i="5.72,301,1580774400"; d="scan'208";a="452582059"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Mar 2020 17:31:02 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 02OHV2KN020863 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Mar 2020 17:31:02 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 24 Mar 2020 12:31:02 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 24 Mar 2020 13:31:01 -0400
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 24 Mar 2020 12:31:00 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=l0PddOVUBlSZu0UBYJvZphcVcM6PoKprU1x5F6kFA4lkw/yG0IgJn4Cm2TR8/8g2Zyq8N9C+96BxaMjmaPHYPtFvWlQOCX0FU3a4eX9p/4zepsfKwSdSJGayI9vifBG8KZSTMSOS9RPzYCRNaaG+vZcsOmBYSvGjMii+extkwT6hBrGEmsZy759qpNMB8yZfNOY2QoPQgsG2vaubuo5pAT5wotMlgEHba3GEdklEV/c+uxo3DQ/4maUSQ4bmf9rIA4MtKxITpUs+7CjwZfPzAmAftkbnS/51HBXTch2jGZMWnMJwh+s4Zo5X9xZfqfgClxsoqo5rCuT4Ne80R8oCfg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AcguuiG6FcCdakMcKjEP0zlOCCtq/tVkvw0b1Rvrp/0=; b=G37xDzKjG2k84uJeCj6LhIqSzeuvzpNAVT1E8PODBURfYSZL7uxRiNsaOquL+ysnAGMlxwHLDwpxviQ7UzObA14GOU7sNHgWoYJ8+85RHT+eDh+hvB+d4GXGDfDqBEBJfQ9SFlgE0MZZWUvssF8c0yOLoRo3fF2FZiRWnXanPKWUUP4bzBctkcfGBfhvlmGvPWuqnymJNRuEP/HixJgvPXekZNbdgJhpdqErLsrNHB86AJjXYrplydKHITA+4d1k5D7t72qBiv/9RjWBwDTTGPiXcBKy4evAP4x3MXp9b/IrdJOc1iQLxpQ2LSd1wMSGlm68PRYjTUmv4KGTfTkyqg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AcguuiG6FcCdakMcKjEP0zlOCCtq/tVkvw0b1Rvrp/0=; b=WgTB74WL+4TUjK1ERPPQO8PTAqC/JdK3IRbJSwFF8m+vOwdA9CS2tfHe4fiiG3tFoCQ+WIwkgH5fEoZZjiAe79DpB/ZgdOgSKicUpfS6xsK3m5tRycqVZTeLg0K/fM3OVqqHD9WjYTX9pCA3SitKQ/koGe0Fa3CT0NN4b59iO/M=
Received: from BYAPR11MB2661.namprd11.prod.outlook.com (2603:10b6:a02:c5::20) by BYAPR11MB3398.namprd11.prod.outlook.com (2603:10b6:a03:19::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.22; Tue, 24 Mar 2020 17:31:00 +0000
Received: from BYAPR11MB2661.namprd11.prod.outlook.com ([fe80::e495:5580:5b80:92fa]) by BYAPR11MB2661.namprd11.prod.outlook.com ([fe80::e495:5580:5b80:92fa%6]) with mapi id 15.20.2835.021; Tue, 24 Mar 2020 17:30:59 +0000
From: "Marc Portoles Comeras (mportole)" <mportole@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>
CC: Albert Cabellos <albert.cabellos@gmail.com>, "lisp@ietf.org list" <lisp@ietf.org>
Thread-Topic: [lisp] Wireguard and LISP [Was: Virtual meeting]
Thread-Index: AQHWAQu8bFduMrlC/Uypn+oU1M/QtahWtamA///7/ICAASQagP//tseA
Date: Tue, 24 Mar 2020 17:30:59 +0000
Message-ID: <8A1B78BF-7677-4D8B-9D9B-0741BD037F46@cisco.com>
References: <95B658E8-B629-4E44-AB99-E9E406D11FF1@cisco.com> <39E32C9F-28FF-44B4-BE28-255199CEC968@gmail.com>
In-Reply-To: <39E32C9F-28FF-44B4-BE28-255199CEC968@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mportole@cisco.com;
x-originating-ip: [76.102.45.110]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d8eb9973-c621-466b-6256-08d7d0191e70
x-ms-traffictypediagnostic: BYAPR11MB3398:
x-microsoft-antispam-prvs: <BYAPR11MB339870DA3A76B852B97CA5E9D2F10@BYAPR11MB3398.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 03524FBD26
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(366004)(396003)(39860400002)(136003)(6916009)(53546011)(66946007)(71200400001)(54906003)(36756003)(6506007)(2906002)(33656002)(6486002)(316002)(81166006)(8936002)(66446008)(6512007)(4326008)(26005)(86362001)(2616005)(186003)(66556008)(64756008)(66476007)(478600001)(5660300002)(8676002)(76116006)(81156014); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3398; H:BYAPR11MB2661.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /rloDMkmiwy7YOHcBRgP/Wdab7YXYUespznII1zXIhGEHdNf7SOx6GhK20iSH+rGF7a6MFJg8t194W1Gbmd+lRwdqKXgpghvCtDiMY+d7ELVLrHLI+396Vc1gTjSQafWrod6cTsbIOhNDBMaeAHffuFJsHs+yEIc5lqvBZoFCgdNwVca06Zts1QkWhkENU3/tV+4Tnxn42+3G8l3j7OAU+b89TXsvwbLFlCaCuSM7BJY4az+zrjL4IdGps9LpT8x4yx3amwqBlEtyLP5ozVUU5vmBSoi0Ixf2IYmei2dm2crRTVKeH3zWAxxfg5itmvlYj28RKAY5KrII51D7bn08FevTRlx0/4swYXhojG+OGRWU0uq+VEgc7fDQnmstnHH7NcN0+afBAX377+VnHGUCl/2hk5teK3e042jEPJDT1ii8WZCIy5oQLzJcI000sFN
x-ms-exchange-antispam-messagedata: M3+yvoDzlP317kLAnaEG1EylYWIE3tAgwiwU5a7KGt7xd9DWC2VcBlPWvrswthiq8rcNuVR4jvJdeE3y412+0JGQZmSPDVplvcHNohkAqxJo2b0YjNyR/9KhiEefteLme3glx/4CIefiLWMELXRLjg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <DAF8C5F03C5CF94881C74220B036A173@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d8eb9973-c621-466b-6256-08d7d0191e70
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Mar 2020 17:30:59.8236 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ggl9UT7q3rPW6akhXfLibmopSclwXRQpY1tN07SCECNR4vNjdZEbs4GBi/WpBySRo3MQ8KKAfhCxJveADyafcQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3398
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/NBOZH4xYOhYXaBCMS-cokZSk-lw>
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 17:31:07 -0000

> Well since Wireguard can support multiple encapsulations, it could add support for LISP encapsulation fairly easy. And then they get segmentation with it and it can map its style of VPNs to draft-ietf-lisp-vpn.

Do you mean using lisp encapsulation as part of the encrypted payload? Or as an alternative to the wireguard header?
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


On 3/24/20, 7:53 AM, "Dino Farinacci" <farinacci@gmail.com> wrote:

Marc,

> On Mar 23, 2020, at 9:27 PM, Marc Portoles Comeras (mportole) <mportole@cisco.com> wrote:
> 
> Have you given any thought to supporting segmentation when using wireguard encapsulation in the  dataplane? Could the Receiver field in the wireguard header be used for that and linked somehow to LISP IIDs?

Well since Wireguard can support multiple encapsulations, it could add support for LISP encapsulation fairly easy. And then they get segmentation with it and it can map its style of VPNs to draft-ietf-lisp-vpn. 

Dino

v2.23.0 | Report a Bug | By Email