>> >> 2) the layout does not fit well with draft-farinacci-lisp-crypto-00. Are >> there any plans to solve this? Should this at least be mentioned somewhere? > > > Both this draft and lisp-crypto are proposals to extend the LISP encap with > new features. I don't think they need to refer each other at this point. > > I just note that by adding multiprotocol support, one could add a shim header > that provides encryption services to the LISP payload.
When I selected the location of the K bits, I knew the P-bit was predefined in the gpe draft, so I didn't use that location. There are no flag bits left if GPE and lisp-crypto are accepted as working group items. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
