RFC 2949 on CAST-128 64 bit Output Feedback

RFC Editor <rfc-ed@ISI.EDU> Fri, 13 October 2000 00:43 UTC

Message-Id: <200010122337.QAA09831@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2949 on CAST-128 64 bit Output Feedback
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 12 Oct 2000 16:37:02 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2949

        Title:	    Telnet Encryption: CAST-128 64 bit Output Feedback
        Author(s):  J. Altman
        Status:     Standards Track 
	Date:       September 2000
        Mailbox:    jaltman@columbia.edu
        Pages:      5
        Characters: 9240
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-altman-telnet-enc-cast128-ofb-00.txt

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


This document specifies how to use the CAST-128 encryption algorithm
in output feedback mode with the telnet encryption option.  Two key
sizes are defined: 40 bit and 128 bit.

This is now a Proposed Standard Protocol.

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
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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/rfc2949.txt"><ftp://ftp.isi.edu/in-notes/rfc2949.txt>

RFC 2949 on CAST-128 64 bit Output Feedback RFC Editor