Subject: [IPsec] FW: New Version Notification for draft-ietf-lwig-minimal-esp-00.txt

From: Daniel Migault <[email-masked]>
Date: Mon, 8 Apr 2019 00:25:52 +0000

Hi, 

Please find our draft on minimal ESP that has been accepted as WG document. We would appreciate the review from ipsecme WG. Our goal is to provide a version ready for WG last call for the Montreal meeting. 

PS: Note that the minimal implementation does  not change ESP. 

Yours, 
Daniel

-----Original Message-----
From: [email-masked] <[email-masked]> 
Sent: Sunday, April 07, 2019 4:11 PM
To: Tobias Guggemos <[email-masked]>; Daniel Migault <[email-masked]>
Subject: New Version Notification for draft-ietf-lwig-minimal-esp-00.txt

A new version of I-D, draft-ietf-lwig-minimal-esp-00.txt
has been successfully submitted by Daniel Migault and posted to the IETF repository.

Name:		draft-ietf-lwig-minimal-esp
Revision:	00
Title:		Minimal ESP
Document date:	2019-04-02
Group:		lwig
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-ietf-lwig-minimal-esp-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-lwig-minimal-esp/
Htmlized:       https://tools.ietf.org/html/draft-ietf-lwig-minimal-esp-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-lwig-minimal-esp

Abstract:
   This document describes a minimal implementation of the IP
   Encapsulation Security Payload (ESP) defined in RFC 4303.  Its
   purpose is to enable implementation of ESP with a minimal set of
   options to remain compatible with ESP as described in RFC 4303.  A
   minimal version of ESP is not intended to become a replacement of the
   RFC 4303 ESP, but instead to enable a limited implementation to
   interoperate with implementations of RFC 4303 ESP.

   This document describes what is required from RFC 4303 ESP as well as
   various ways to optimize compliance with RFC 4303 ESP.

   This document does not update or modify RFC 4303, but provides a
   compact description of how to implement the minimal version of the
   protocol.  If this document and RFC 4303 conflicts then RFC 4303 is
   the authoritative description.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat