Re: [Lwip] Milestones changed for lwig WG

["Tobias Guggemos" <[e-mail]>]

Hey,

we just published a new version of the Minimal-ESP document.

We’re looking forward for any comments on the document!

Regards

Tobias

 

A new version of I-D, draft-mglt-lwig-minimal-esp-06.txt

has been successfully submitted by Tobias Guggemos and posted to the IETF repository.

 

Name:                 draft-mglt-lwig-minimal-esp

Revision:             06

Title:                    Minimal ESP

Document date:              2018-06-21

Group:                 Individual Submission

Pages:                  12

URL:             <https://www.ietf.org/internet-drafts/draft-mglt-lwig-minimal-esp-06.txt> https://www.ietf.org/internet-drafts/draft-mglt-lwig-minimal-esp-06.txt

Status:          <https://datatracker.ietf.org/doc/draft-mglt-lwig-minimal-esp/> https://datatracker.ietf.org/doc/draft-mglt-lwig-minimal-esp/

Htmlized:        <https://tools.ietf.org/html/draft-mglt-lwig-minimal-esp-06> https://tools.ietf.org/html/draft-mglt-lwig-minimal-esp-06

Htmlized:        <https://datatracker.ietf.org/doc/html/draft-mglt-lwig-minimal-esp> https://datatracker.ietf.org/doc/html/draft-mglt-lwig-minimal-esp

Diff:            <https://www.ietf.org/rfcdiff?url2=draft-mglt-lwig-minimal-esp-06> https://www.ietf.org/rfcdiff?url2=draft-mglt-lwig-minimal-esp-06

 

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

 

 

Von: [e-mail] [mailto:[e-mail]] Im Auftrag von Daniel Migault
Gesendet: Dienstag, 19. Juni 2018 22:33
An: [e-mail]
Cc: Tobias Guggemos <[e-mail]>
Betreff: Fwd: [Lwip] Milestones changed for lwig WG

 

Hi, 

 

We are updating the draft, and expect to submit it by the end of the week. Before we proceed I would like to check if you expect us to submit it as draft-mglt-lwig-minial-esp or as a WG document draft-ietf-lwig-minimal-esp ?

 

Yours, 

Daniel

 

---------- Forwarded message ----------
From: IETF Secretariat < <mailto:[e-mail]> [e-mail]>
Date: Wed, Mar 28, 2018 at 11:34 PM
Subject: [Lwip] Milestones changed for lwig WG
To:  <mailto:[e-mail]> [e-mail]


Changed milestone "Submit the minimal ESP guidance document to the IESG for
publication as an Informational RFC", set due date to November 2018 from
March 2018.

Changed milestone "Submit the CoAP implementation document to the IESG for
publication as an Informational RFC", set due date to November 2018 from
March 2017.

Changed milestone "Submit the TCP over constrained networks guidance document
to the IESG for publication as an Informational RFC", set due date to
November 2018 from November 2017.

URL:  <https://datatracker.ietf.org/wg/lwig/about/> https://datatracker.ietf.org/wg/lwig/about/

_______________________________________________
Lwip mailing list
 <mailto:[e-mail]> [e-mail]
 <https://www.ietf.org/mailman/listinfo/lwip> https://www.ietf.org/mailman/listinfo/lwip