RFC 2947 on DES3 64 bit Cipher Feedback

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

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08724; Thu, 12 Oct 2000 20:23:22 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA07865 for ietf-123-outbound.10@ietf.org; Thu, 12 Oct 2000 20:15:01 -0400 (EDT)
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 TAA07502 for <all-ietf@loki.ietf.org>; Thu, 12 Oct 2000 19:33:18 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA07867 for <all-ietf@ietf.org>; Thu, 12 Oct 2000 19:33:15 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA09225; Thu, 12 Oct 2000 16:33:14 -0700 (PDT)
Message-Id: <200010122333.QAA09225@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2947 on DES3 64 bit Cipher Feedback
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 12 Oct 2000 16:33:14 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2947

        Title:	    Telnet Encryption: DES3 64 bit Cipher Feedback
        Author(s):  J. Altman
        Status:     Standards Track 
	Date:       September 2000
        Mailbox:    jaltman@columbia.edu
        Pages:      6
        Characters: 11064
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-altman-telnet-enc-des3-cfb-01.txt

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


This document specifies how to use the Triple-DES (data encryption
standard) encryption algorithm in cipher feedback mode with the telnet
encryption option.

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/rfc2947.txt"><ftp://ftp.isi.edu/in-notes/rfc2947.txt>