[Cfrg] RFC 8645 on Re-keying Mechanisms for Symmetric Keys

rfc-editor@rfc-editor.org Thu, 29 August 2019 17:14 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C7D120891; Thu, 29 Aug 2019 10:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YRH5JLPtDxxA; Thu, 29 Aug 2019 10:14:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C179120A16; Thu, 29 Aug 2019 10:14:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4656DB80CF0; Thu, 29 Aug 2019 10:13:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, cfrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190829171357.4656DB80CF0@rfc-editor.org>
Date: Thu, 29 Aug 2019 10:13:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/0Gef0CSGcnvknJBepSbMM8VAQmo>
Subject: [Cfrg] RFC 8645 on Re-keying Mechanisms for Symmetric Keys
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2019 17:14:21 -0000

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

        
        RFC 8645

        Title:      Re-keying Mechanisms for Symmetric Keys 
        Author:     S. Smyshlyaev, Ed.
        Status:     Informational
        Stream:     IRTF
        Date:       August 2019
        Mailbox:    svs@cryptopro.ru
        Pages:      69
        Characters: 141580
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-cfrg-re-keying-17.txt

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

        DOI:        10.17487/RFC8645

A certain maximum amount of data can be safely encrypted when
encryption is performed under a single key.  This amount is called
the "key lifetime".  This specification describes a variety of
methods for increasing the lifetime of symmetric keys.  It provides
two types of re-keying mechanisms based on hash functions and block
ciphers that can be used with modes of operations such as CTR, GCM,
CBC, CFB, and OMAC.

This document is a product of the Crypto Forum Research Group (CFRG)
in the IRTF.

This document is a product of the Crypto Forum Research Group of the IRTF.


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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
  https://www.irtf.org/mailman/listinfo/irtf-announce

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