RFC 8682 on TinyMT32 Pseudorandom Number Generator (PRNG)
rfc-editor@rfc-editor.org Tue, 14 January 2020 23:39 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 E21DB120C23; Tue, 14 Jan 2020 15:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 M9hRC6yLNWGk; Tue, 14 Jan 2020 15:39:11 -0800 (PST)
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 B99D7120C07; Tue, 14 Jan 2020 15:39:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AC6B8F4074E; Tue, 14 Jan 2020 15:39:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8682 on TinyMT32 Pseudorandom Number Generator (PRNG)
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, tsvwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200114233904.AC6B8F4074E@rfc-editor.org>
Date: Tue, 14 Jan 2020 15:39:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-0disNItGX8j3uPEstZxx12sLtI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 14 Jan 2020 23:39:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8682
Title: TinyMT32 Pseudorandom Number Generator (PRNG)
Author: M. Saito,
M. Matsumoto,
V. Roca, Ed.,
E. Baccelli
Status: Standards Track
Stream: IETF
Date: January 2020
Mailbox: saito@math.sci.hiroshima-u.ac.jp,
m-mat@math.sci.hiroshima-u.ac.jp,
vincent.roca@inria.fr,
emmanuel.baccelli@inria.fr
Pages: 12
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-tinymt32-06.txt
URL: https://www.rfc-editor.org/info/rfc8682
DOI: 10.17487/RFC8682
This document describes the TinyMT32 Pseudorandom Number Generator
(PRNG), which produces 32-bit pseudorandom unsigned integers and aims
at having a simple-to-use and deterministic solution. This PRNG is a
small-sized variant of the Mersenne Twister (MT) PRNG. The main
advantage of TinyMT32 over MT is the use of a small internal state,
compatible with most target platforms that include embedded devices,
while keeping reasonably good randomness that represents a
significant improvement compared to the Park-Miller Linear
Congruential PRNG. However, neither the TinyMT nor MT PRNG is meant
to be used for cryptographic applications.
This document is a product of the Transport Area Working Group 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 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