RFC 2994 on MISTY1

RFC Editor <rfc-ed@ISI.EDU> Wed, 22 November 2000 00:58 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05962; Tue, 21 Nov 2000 19:58:28 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA00907 for ietf-123-outbound.10@ietf.org; Tue, 21 Nov 2000 19:55:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA00874 for <all-ietf@loki.ietf.org>; Tue, 21 Nov 2000 19:50:51 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04986 for <all-ietf@ietf.org>; Tue, 21 Nov 2000 19:50:50 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA20918; Tue, 21 Nov 2000 16:50:48 -0800 (PST)
Message-Id: <200011220050.QAA20918@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2994 on MISTY1
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 21 Nov 2000 16:50:48 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2994

        Title:	    A Description of the MISTY1 Encryption Algorithm
        Author(s):  H. Ohta, M. Matsui
        Status:     Informational
	Date:       November 2000
        Mailbox:    hidenori@iss.isl.melco.co.jp,
                    matsui@iss.isl.melco.co.jp 
        Pages:      10
        Characters: 17803
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ohta-misty1desc-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2994.txt


This document describes a secret-key cryptosystem MISTY1, which is
block cipher with a 128-bit key, a 64-bit block and a variable number
of rounds.  It documents the algorithm description including key
scheduling part and data randomizing part.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2994.txt"><ftp://ftp.isi.edu/in-notes/rfc2994.txt>