RFC 9333 on Minimal IP Encapsulating Security Payload (ESP)
rfc-editor@rfc-editor.org Fri, 13 January 2023 23:01 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA79C16FE4E; Fri, 13 Jan 2023 15:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPKzEL8DqlXU; Fri, 13 Jan 2023 15:01:16 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F8CBC16FE50; Fri, 13 Jan 2023 15:01:16 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6A7294C292; Fri, 13 Jan 2023 15:01:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9333 on Minimal IP Encapsulating Security Payload (ESP)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lwip@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230113230116.6A7294C292@rfcpa.amsl.com>
Date: Fri, 13 Jan 2023 15:01:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/I0ofVGDk5v3kktqqQUo_3svd04E>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jan 2023 23:01:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9333
Title: Minimal IP Encapsulating Security Payload (ESP)
Author: D. Migault,
T. Guggemos
Status: Informational
Stream: IETF
Date: January 2023
Mailbox: daniel.migault@ericsson.com,
guggemos@mnm-team.org
Pages: 13
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lwig-minimal-esp-12.txt
URL: https://www.rfc-editor.org/info/rfc9333
DOI: 10.17487/RFC9333
This document describes the minimal properties that an IP
Encapsulating Security Payload (ESP) implementation needs to meet to
remain interoperable with the standard ESP as defined in RFC 4303.
Such a minimal version of ESP is not intended to become a replacement
of ESP in RFC 4303. Instead, a minimal implementation is expected to
be optimized for constrained environments while remaining
interoperable with implementations of ESP. In addition, this document
provides some considerations for implementing minimal ESP in a
constrained environment, such as limiting the number of flash writes,
handling frequent wakeup and sleep states, limiting wakeup time, and
reducing the use of random generation.
This document does not update or modify RFC 4303. It provides a
compact description of how to implement the minimal version of that
protocol. RFC 4303 remains the authoritative description.
This document is a product of the Light-Weight Implementation Guidance Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC