Subject: [IPsec] RFC 8221 on Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)

From: [email-masked]
Date: Tue, 17 Oct 2017 16:27:45 -0700 (PDT)

A new Request for Comments is now available in online RFC libraries.

        RFC 8221

        Title:      Cryptographic Algorithm Implementation Requirements 
                    and Usage Guidance for Encapsulating Security 
                    Payload (ESP) and Authentication Header (AH) 
        Author:     P. Wouters,
                    D. Migault,
                    J. Mattsson,
                    Y. Nir,
                    T. Kivinen
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2017
        Mailbox:    [email-masked], 
                    [email-masked], 
                    [email-masked],
                    [email-masked], 
                    [email-masked]
        Pages:      15
        Characters: 33610
        Obsoletes:  RFC 7321

        I-D Tag:    draft-ietf-ipsecme-rfc7321bis-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8221

        DOI:        10.17487/RFC8221

This document replaces RFC 7321, "Cryptographic Algorithm Implementation        
Requirements and Usage Guidance for Encapsulating Security Payload              
(ESP) and Authentication Header (AH)".  The goal of this document is
to enable ESP and AH to benefit from cryptography that is up to date
while making IPsec interoperable.

This document is a product of the IP Security Maintenance and Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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 [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC