%% You should probably cite draft-mglt-ipsecme-ikev2-diet-esp-extension instead of this I-D. @techreport{mglt-6lo-diet-esp-context-ikev2-extension-02, number = {draft-mglt-6lo-diet-esp-context-ikev2-extension-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-mglt-6lo-diet-esp-context-ikev2-extension/02/}, author = {Daniel Migault}, title = {{Diet-ESP Context IKEv2 Extension}}, pagetotal = 13, year = 2015, month = feb, day = 16, abstract = {Diet-ESP has been designed for IoT to limit the IPsec ESP overhead in each IPsec packet. Diet-ESP is based on the standard IPsec ESP, and needs that peers agree on a Diet-ESP Context that defines how standard ESP packets can be compressed before being sent over the wire. Standard IPsec ESP can be agreed between peers using IKEv2. However, current IKEv2 does not make possible to negotiate a Diet-ESP Context, and thus to negotiate a Diet-ESP communication. This draft defines an extension for IKEv2 so peers can agree the Diet-ESP Context, and thus negotiate a Diet-ESP association.}, }