[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipsec
Subject:    Re: [IPsec] Last Call: <draft-ietf-lwig-minimal-esp-06.txt> (Minimal ESP) to Informational RFC
From:       Erik Kline <ek.ietf () gmail ! com>
Date:       2021-08-15 0:28:57
Message-ID: CAMGpriVU4fO59kwMUZRWHqWTuYcHpBD0Cj1xjFb9kbH2cd+DVg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


[+ipsec]

On Thu, Aug 12, 2021 at 2:50 PM The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from the Light-Weight Implementation
> Guidance
> WG (lwig) to consider the following document: - 'Minimal ESP'
>   <draft-ietf-lwig-minimal-esp-06.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2021-08-26. Exceptionally, comments
> may
> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning
> of the Subject line to allow automated sorting.
>
> 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.  Instead, a minimal implementation is expected to be
>    optimized for constrained environment while remaining interoperable
>    with implementations of RFC 4303 ESP.  Some constraints include
>    limiting the number of flash writes, handling frequent wakeup / sleep
>    states, limiting wakeup time, or reducing the use of random
>    generation.
>
>    This document does not update or modify RFC 4303, but provides a
>    compact description of how to implement the minimal version of the
>    protocol.  RFC 4303 remains the authoritative description.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-lwig-minimal-esp/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
>

[Attachment #5 (text/html)]

<div dir="ltr">[+ipsec]</div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Aug 12, 2021 at 2:50 PM The IESG &lt;<a \
href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> The IESG has \
received a request from the Light-Weight Implementation Guidance<br> WG (lwig) to \
consider the following document: - &#39;Minimal ESP&#39;<br>  \
&lt;draft-ietf-lwig-minimal-esp-06.txt&gt; as Informational RFC<br> <br>
The IESG plans to make a decision in the next few weeks, and solicits final<br>
comments on this action. Please send substantive comments to the<br>
<a href="mailto:last-call@ietf.org" target="_blank">last-call@ietf.org</a> mailing \
lists by 2021-08-26. Exceptionally, comments may<br> be sent to <a \
href="mailto:iesg@ietf.org" target="_blank">iesg@ietf.org</a> instead. In either \
case, please retain the beginning<br> of the Subject line to allow automated \
sorting.<br> <br>
Abstract<br>
<br>
<br>
     This document describes a minimal implementation of the IP<br>
     Encapsulation Security Payload (ESP) defined in RFC 4303.   Its<br>
     purpose is to enable implementation of ESP with a minimal set of<br>
     options to remain compatible with ESP as described in RFC 4303.   A<br>
     minimal version of ESP is not intended to become a replacement of the<br>
     RFC 4303 ESP.   Instead, a minimal implementation is expected to be<br>
     optimized for constrained environment while remaining interoperable<br>
     with implementations of RFC 4303 ESP.   Some constraints include<br>
     limiting the number of flash writes, handling frequent wakeup / sleep<br>
     states, limiting wakeup time, or reducing the use of random<br>
     generation.<br>
<br>
     This document does not update or modify RFC 4303, but provides a<br>
     compact description of how to implement the minimal version of the<br>
     protocol.   RFC 4303 remains the authoritative description.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href="https://datatracker.ietf.org/doc/draft-ietf-lwig-minimal-esp/" \
rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-lwig-minimal-esp/</a><br>
 <br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div>



_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec


[prev in list] [next in list] [prev in thread] [next in thread]