> 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" <farina...@gmail.com> wrote: Marc, > On Mar 23, 2020, at 9:27 PM, Marc Portoles Comeras (mportole) > <mport...@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 _______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
