draft-ietf-tls-psk-null-02.txt   draft-ietf-tls-psk-null-03.txt 
TLS Working Group U. Blumenthal TLS Working Group U. Blumenthal
Internet Draft P. Goel Internet Draft P. Goel
Expires: April 2007 Intel Corporation Expires: April 2007 Intel Corporation
October 3, 2006 October 20, 2006
Pre-Shared Key Cipher Suites with NULL Encryption for Pre-Shared Key Cipher Suites with NULL Encryption for
Transport Layer Security (TLS) Transport Layer Security (TLS)
draft-ietf-tls-psk-null-02.txt draft-ietf-tls-psk-null-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 3, 2007. This Internet-Draft will expire on April 20, 2007.
Abstract Abstract
This document specifies authentication-only cipher suites for the This document specifies authentication-only cipher suites (with no
Pre-Shared Key based Transport Layer Security (TLS) protocol to encryption) for the Pre-Shared Key based Transport Layer Security
support null encryption. These cipher suites are useful for countries (TLS) protocol. These cipher suites are useful when authentication
and places with cryptography-related restrictions. and integrity protection is desired, but confidentiality is not
needed or not permitted.
Internet-Draft PSK NULL-encryption Cipher Suites for TLS October Internet-Draft PSK NULL-encryption Cipher Suites for TLS October
2006 2006
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. Cipher Usage...................................................2 2. Cipher Usage...................................................2
3. Security Considerations........................................3 3. Security Considerations........................................3
4. IANA Considerations............................................3 4. IANA Considerations............................................3
5. Acknowledgments................................................3 5. Acknowledgments................................................3
6. References.....................................................4 6. References.....................................................4
6.1. Normative References......................................4 6.1. Normative References......................................4
Author's Addresses................................................4 Author's Addresses................................................4
Intellectual Property Statement...................................4 Intellectual Property Statement...................................5
Disclaimer of Validity............................................5 Disclaimer of Validity............................................5
Copyright Statement...............................................5 Copyright Statement...............................................5
Acknowledgment....................................................5 Acknowledgment....................................................4
1. Introduction 1. Introduction
The RFC for Pre-Shared Key based TLS [TLS-PSK] specifies cipher The RFC for Pre-Shared Key based TLS [TLS-PSK] specifies cipher
suites for supporting TLS using pre-shared symmetric keys. However suites for supporting TLS using pre-shared symmetric keys. However
all the cipher suites defined in [TLS-PSK] require encryption. There all the cipher suites defined in [TLS-PSK] require encryption.
is a need for cipher suites that support no encryption. This is However there are cases when only authentication and integrity
required for implementations to meet import restrictions in some protection is required, and confidentiality is not needed. There are
countries. Even though no encryption is used, these cipher suites also cases when confidentiality is not permitted - e.g. for
support authentication of the client and server to each other, and implementations that must meet import restrictions in some countries.
message integrity. This document augments [TLS-PSK] by adding three Even though no encryption is used, these cipher suites support
more cipher suites (PSK, DHE_PSK, RSA_PSK) with authentication and authentication of the client and server to each other, and message
integrity only - no encryption. integrity. This document augments [TLS-PSK] by adding three more
cipher suites (PSK, DHE_PSK, RSA_PSK) with authentication and
integrity only - no encryption. The reader is expected to become
familiar with [TLS-PSK] standard prior to studying this document.
2. Cipher Usage 2. Cipher Usage
The new cipher suites proposed here is very similar to cipher suites The three new cipher suites proposed here match the three cipher
defined in [TLS-PSK], except that they define null encryption. suites defined in [TLS-PSK], except that we define suites with null
encryption.
The cipher suites defined here use the following options for key
exchange and hash part of the protocol:
Internet-Draft PSK NULL-encryption Cipher Suites for TLS October Internet-Draft PSK NULL-encryption Cipher Suites for TLS October
2006 2006
The cipher suites defined here use the following options for key
exchange and hash part of the protocol:
CipherSuite Key Exchange Cipher Hash CipherSuite Key Exchange Cipher Hash
TLS_PSK_WITH_NULL_SHA PSK NULL SHA TLS_PSK_WITH_NULL_SHA PSK NULL SHA
TLS_DHE_PSK_WITH_NULL_SHA DHE_PSK NULL SHA TLS_DHE_PSK_WITH_NULL_SHA DHE_PSK NULL SHA
TLS_RSA_PSK_WITH_NULL_SHA RSA_PSK NULL SHA TLS_RSA_PSK_WITH_NULL_SHA RSA_PSK NULL SHA
For the meaning of the terms PSK please refer to section 1 in [TLS- For the meaning of the terms PSK please refer to section 1 in [TLS-
PSK]. For the meaning of the terms DHE and RSA please refer to PSK]. For the meaning of the terms DHE, RSA and SHA please refer to
section 7.4.2 in [TLS]. sections A.5 and Appendix B in [TLS].
3. Security Considerations 3. Security Considerations
As with all schemes involving shared keys, special care should be As with all schemes involving shared keys, special care should be
taken to protect the shared values and to limit their exposure over taken to protect the shared values and to limit their exposure over
time. As this document augments [TLS-PSK], everything stated in its time. As this document augments [TLS-PSK], everything stated in its
Security Consideration section applies here. In addition, as cipher Security Consideration section applies here. In addition, as cipher
suites defined here do not support confidentiality - care should be suites defined here do not support confidentiality - care should be
taken not to send sensitive information (such as passwords) over taken not to send sensitive information (such as passwords) over
connection protected with one of the cipher suites defined in this connection protected with one of the cipher suites defined in this
skipping to change at page 4, line 42 skipping to change at page 4, line 42
Purushottam Goel Purushottam Goel
Intel Corporation Intel Corporation
2111 N.E. 25 Ave. 2111 N.E. 25 Ave.
JF3-414 JF3-414
Hillsboro, OR 97124 Hillsboro, OR 97124
USA USA
Email: Purushottam.Goel@intel.com Email: Purushottam.Goel@intel.com
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Internet-Draft PSK NULL-encryption Cipher Suites for TLS October
2006
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
Internet-Draft PSK NULL-encryption Cipher Suites for TLS October
2006
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
skipping to change at page 5, line 42 skipping to change at line 218
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 13 change blocks. 
28 lines changed or deleted 37 lines changed or added

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