draft-ietf-cat-ftpdsaauth-02.txt   draft-ietf-cat-ftpdsaauth-03.txt 
CAT Working Group Russell Housley (SPYRUS) CAT Working Group Russell Housley (SPYRUS)
<draft-ietf-cat-ftpdsaauth-02.txt> William A. Nace (NSA) <draft-ietf-cat-ftpdsaauth-03.txt> William A. Nace (NSA)
Updates: RFC 959 Peter Yee (SPYRUS) Updates: RFC 959 Peter Yee (SPYRUS)
Internet-Draft Expire in six months Internet-Draft Expire in six months
February 1998 December 1999
FTP Authentication Using DSA FTP Authentication Using DSA
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its areas, all provisions of Section 10 of RFC2026.
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are Draft documents valid for a maximum of six months Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ''work in progress.'' material or to cite them other than as "work in progress."
To learn the current status of any Internet-Draft, please check the The list of current Internet-Drafts can be accessed at
"1id-abstRacts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/ietf/1id-abstracts.txt
Directories on ds.internic.net (US East Coast), nic.nordu.net
Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Distribution of this memo is unlimited. Please send comments to the The list of Internet-Draft Shadow Directories can be accessed at
<cat-ietf@mit.edu> mailing list. http://www.ietf.org/shadow.html.
Distribution of this memo is unlimited. Please send comments to
yee@spyrus.com.
Abstract Abstract
This document defines a method to secure file transfers using the FTP This document defines a method to secure file transfers using the FTP
specification RFC 959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985) specification RFC 959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985)
and RFC 2228 "FTP Security Extensions" (October 1997) [1]. This and RFC 2228 "FTP Security Extensions" (October 1997) [1]. This
method will use the extensions proposed in the "FTP Security method will use the extensions proposed in the "FTP Security
Extensions" along with a public/private digital signature. Extensions" along with a public/private digital signature.
1 Introduction 1 Introduction
skipping to change at page 4, line 9 skipping to change at page 4, line 14
authentication. Each exchange employs various fields and tokens, authentication. Each exchange employs various fields and tokens,
some of which are optional. In addition, each token has several some of which are optional. In addition, each token has several
subfields that are optional. A conformant subset of the fields and subfields that are optional. A conformant subset of the fields and
subfields for use with FTP have been selected. Therefore, the subfields for use with FTP have been selected. Therefore, the
exchanges below do not show the FIPS PUB 196 notation indicating exchanges below do not show the FIPS PUB 196 notation indicating
optional fields, while only the mandatory subfields are allowed. The optional fields, while only the mandatory subfields are allowed. The
tokens are ASN.1 encoded per Appendix A of FIPS PUB 196, and each tokens are ASN.1 encoded per Appendix A of FIPS PUB 196, and each
token is named to indicate the direction in which it flows (i.e., token is named to indicate the direction in which it flows (i.e.,
TokenBA flows from Party B to Party A). In Figure 1, the client TokenBA flows from Party B to Party A). In Figure 1, the client
binds the last transmission (token identifier, certificate, and binds the last transmission (token identifier, certificate, and
token) together as an ASN.1 sequence. token) together as an ASN.1 SEQUENCE.
The exchanges detailed below presume a knowledge of FIPS PUB 196 and The exchanges detailed below presume a knowledge of FIPS PUB 196 and
the FTP Security Extensions. The client is Party A, while the server the FTP Security Extensions. The client is Party A, while the server
is Party B. The notation for concatenation is " || ". The pseudo- is Party B. The notation for concatenation is " || ". The pseudo-
function Sequence is used to indicate that its parameters are to be function Sequence is used to indicate that its parameters are to be
joined as an ASN.1 SEQUENCE. Verification of signed data, and in joined as an ASN.1 SEQUENCE. Verification of signed data, and in
particular certification path verification is implicitly assumed, but particular certification path verification is implicitly assumed, but
is not shown. is not shown.
--------------------------------------------------------------------- ---------------------------------------------------------------------
skipping to change at page 8, line 9 skipping to change at page 8, line 9
[3] - Secure Hash Standard. FIPS Pub 180-1. April 17, 1995. [3] - Secure Hash Standard. FIPS Pub 180-1. April 17, 1995.
[4] - Standard for Entity Authentication Using Public Key [4] - Standard for Entity Authentication Using Public Key
Cryptography. FIPS Pub 196. February 18, 1997. Cryptography. FIPS Pub 196. February 18, 1997.
7.0 Author's Address 7.0 Author's Address
Russell Housley Russell Housley
SPYRUS SPYRUS
PO Box 1198 381 Elden Street
Herndon, VA 20172 Suite 1120
Herndon, VA 20170
USA USA
Phone: +1 703 435-7344
Email: housley@spyrus.com Email: housley@spyrus.com
DIRNSA DIRNSA
Attn: X22 (W. Nace) Attn: X22 (W. Nace)
9800 Savage Road 9800 Savage Road
Fort Meade, MD 20755-6000 Fort Meade, MD 20755-6000
USA USA
Phone: +1 410 859-4464
Email: WANace@missi.ncsc.mil Email: WANace@missi.ncsc.mil
Peter Yee Peter Yee
SPYRUS SPYRUS
2460 N. First Street 5303 Betsy Rose Drive
Suite 100 Santa Clara, CA 95054
San Jose, CA 95131-1023
USA USA
Phone: +1 408 432-8180
Email: yee@spyrus.com Email: yee@spyrus.com
 End of changes. 14 change blocks. 
27 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/