[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[TLS] RE: [IANA #12633] General Request for Assignments (TLS parameters)
Pasi,
Here's the updated version of the draft. I've addressed those few
comments that were mentioned on the list.
Regarding Informational vs. PS status - I strongly believe that since
we're adding suites that are not vendor-specific, it should be on the
standards track - because of its generic applicability (whenever for
whatever reason one cannot use encryption).
Thanks,
Uri
-----Original Message-----
From: Pasi.Eronen@xxxxxxxxx [mailto:Pasi.Eronen@xxxxxxxxx]
Sent: Wednesday, September 27, 2006 12:04 AM
To: Blumenthal, Uri; ekr@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [IANA #12633] General Request for Assignments (TLS
parameters)
Uri,
The mail can be found from the archive:
http://www1.ietf.org/mail-archive/web/tls/current/msg00754.html
Best regards,
Pasi
> -----Original Message-----
> From: ext Blumenthal, Uri [mailto:uri.blumenthal@xxxxxxxxx]
> Sent: 27 September, 2006 00:43
> To: Eronen Pasi (Nokia-NRC/Helsinki); ekr@xxxxxxxxxxxxxxxxxxxx
> Subject: RE: [IANA #12633] General Request for Assignments
> (TLS parameters)
>
> Gentlemen,
>
> The Last Call is over, correct? :-)
>
> Pasi, you sent me a few nits - but I cannot find that email. :-(
> Could you please re-send them to me, so I can apply the edits?
>
> Thank you!
>
> Regards,
> Uri
>
> -----Original Message-----
> From: Pasi.Eronen@xxxxxxxxx [mailto:Pasi.Eronen@xxxxxxxxx]
> Sent: Tuesday, September 19, 2006 5:59 AM
> To: Blumenthal, Uri; ekr@xxxxxxxxxxxxxxxxxxxx
> Cc: jari.arkko@xxxxxxxxx
> Subject: RE: [IANA #12633] General Request for Assignments (TLS
> parameters)
>
> Uri,
>
> The document is advancing, but there're still several steps
> to go until it's approved:
>
> - Working Group last call ends (on Friday).
> - Authors prepare new I-D version to handle WGLC comments, and
> discuss with WG chairs that it really reflects WG consensus.
> - Document shepherd (one of the WG chairs) prepares a "document
> write-up" and sends it do AD (probably Russ Housley; I don't
> know why IANA thought it's Jari).
> - AD reads the document and provides comments.
> - (Optionally) AD asks authors to prepare a new I-D version to
> handle the comments (alternatively, the comments can be
> considered at the same time as IETF last call comments).
> - AD starts IETF last call, lasting two weeks. During this time,
> the document gets reviewed by SecDir, GEN-ART, and others.
> - Depending on the comments, AD may ask the authors to prepare
> a new I-D version to handle them.
> - Document goes to IESG evaluation, which usually takes about
> two weeks.
> - Depending on the comments, AD may ask the authors to prepare
> yet another new I-D version.
> - IESG declares the document approved.
>
> Only at this point the document has some official status (until
> this, it's just a random "work in progress"), and it gets sent
> to IANA who assign the numbers.
>
> (And yes, this does take some time. TLS-PSK took 2.5 years from
> first individual internet-draft to RFC.)
>
> Best regards,
> Pasi
>
> > -----Original Message-----
> > From: ext Blumenthal, Uri [mailto:uri.blumenthal@xxxxxxxxx]
> > Sent: 19 September, 2006 04:15
> > To: Eronen Pasi (Nokia-NRC/Helsinki); Eric Rescorla
> > Cc: Jari Arkko
> > Subject: FW: [IANA #12633] General Request for Assignments
> > (TLS parameters)
> >
> >
> > Folks,
> >
> > Could you please tell me whether the draft is in the Last
> Call yet? I
> > thought that after presenting the protocol suite(s) it was
> > agreed by the
> > WG, WG chairpeople and the audience that this document will
> advance on
> > the standards track (and there were comments like "we
> > should've done it
> > the first time")...
> >
> > Yours in confusion,
> > Uri
> >
> > -----Original Message-----
> > From: Michelle Cotton via RT [mailto:iana-prot-param@xxxxxxxxx]
> > Sent: Monday, September 18, 2006 7:13 PM
> > To: Blumenthal, Uri
> > Subject: [IANA #12633] General Request for Assignments (TLS
> > parameters)
> >
> > Dear Uri,
> >
> > This registration procedures for the parameters you
> > are requesting is Standards Action. Please see:
> > http://www.iana.org/assignments/tls-parameters as well as RFC4346
> >
> > We see that you mention an Internet-Draft. After your
> > I-D is approved for publication as an RFC, the IANA will
> > register the parameter you are requesting.
> >
> > Copied on this message is Jari Arkko who is the Shepherding
> > AD for this
> > document according to the tracker should you have questions
> about the
> > status
> > of this draft.
> >
> > We are administratively closing this request without
> > prejudice at this time.
> >
> > Please let us know if you have any questions. If you
> respond to this
> > ticket
> > it will re-open.
> >
> > Thank you,
> >
> >
> > Michelle Cotton
> > Internet Assigned Numbers Authority (IANA)
> >
> > On Thu Aug 03 09:21:57 2006, uri.blumenthal@xxxxxxxxx wrote:
> > > Contact Name :
> > > Uri Blumenthal
> > >
> > > Contact Email :
> > > uri.blumenthal@xxxxxxxxx
> > >
> > > Type of Assignment :
> > > Assign numbers for new cipher suites approved by TLS
> Working Group.
> > >
> > > Registry :
> > > TLS Cipher Suite Registry (RFC 4346)
> > >
> > > Description :
> > > New draft approved by TLS WG defines new cipher suites.
> They need to
> > > be registered.
> > >
> > > People are breathing down my neck, so if I could ask you to
> > accelerate
> > > this one please? Thank you!
> > >
> > > Additional Info :
> > > draft-ietf-tls-psk-null-00.txt
> > >
> > > We propose to allocate from 0x00,0x5D-5F
> > >
> >
>
TLS Working Group U. Blumenthal
Internet Draft P. Goel
Expires: March 2007 Intel Corporation
September 27, 2006
Pre-Shared Key Cipher Suites with NULL Encryption for
Transport Layer Security (TLS)
draft-ietf-tls-psk-null-01.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that
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
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
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
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 27, 2007.
Abstract
This document specifies authentication-only cipher suites for the
Pre-Shared Key based Transport Layer Security (TLS) protocol to
support null encryption. These cipher suites are useful for countries
and places with cryptography-related restrictions.
Blumenthal & Goel Expires March 27, 2007 [Page 1]
Internet-Draft PSK NULL-encryption Cipher Suites for TLS September
2006
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Table of Contents
1. Introduction...................................................2
2. Cipher Usage...................................................2
3. Security Considerations........................................3
4. IANA Considerations............................................3
5. Acknowledgments................................................3
6. References.....................................................4
6.1. Normative References......................................4
Author's Addresses................................................4
Intellectual Property Statement...................................4
Disclaimer of Validity............................................5
Copyright Statement...............................................5
Acknowledgment....................................................5
1. Introduction
The RFC for Pre-Shared Key based TLS [TLS-PSK] specifies cipher
suites for supporting TLS using pre-shared symmetric keys. However
all the cipher suites defined in [TLS-PSK] require encryption. There
is a need for cipher suites that support no encryption. This is
required for implementations to meet import restrictions in some
countries. Even though no encryption is used, these cipher suites
support authentication of the client and server to each other, and
message integrity. This document augments [TLS-PSK] by adding three
more cipher suites (PSK, DHE, RSA) with authentication and integrity
only - no encryption.
2. Cipher Usage
The new cipher suites proposed here is very similar to cipher suites
defined in [TLS-PSK], except that they define null encryption.
The cipher suites defined here use the following options for key
exchange and hash part of the protocol:
Blumenthal & Goel Expires March 27, 2007 [Page 2]
Internet-Draft PSK NULL-encryption Cipher Suites for TLS September
2006
CipherSuite Key Exchange Cipher Hash
TLS_PSK_WITH_NULL_SHA PSK NULL SHA
TLS_DHE_PSK_WITH_NULL_SHA DHE_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-
PSK]. For the meaning of the terms DHE and RSA please refer to
section 7.4.2 in [TLS].
3. Security Considerations
As with all schemes involving shared keys, special care should be
taken to protect the shared values and to limit their exposure over
time. As this document augments [TLS-PSK], everything stated in its
Security Consideration section applies here. In addition, as cipher
suites defined here do not support confidentiality - care should be
taken not to send confidential information (such as passwords) over
TLS-PSK connection with no encryption.
4. IANA Considerations
This document defines three new cipher suites, whose values are to be
assigned from the TLS Cipher Suite registry defined in [TLS].
CipherSuite TLS_PSK_WITH_NULL_SHA = { 0x00, 0xTBD1 };
CipherSuite TLS_DHE_PSK_WITH_NULL_SHA = { 0x00, 0xTBD2 };
CipherSuite TLS_RSA_PSK_WITH_NULL_SHA = { 0x00, 0xTBD3 };
5. Acknowledgments
The cipher suites defined in this document are an augmentation to and
based on [TLS-PSK].
Blumenthal & Goel Expires March 27, 2007 [Page 3]
Internet-Draft PSK NULL-encryption Cipher Suites for TLS September
2006
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[TLS] Dierks, T. and Rescorla, E., "The TLS Protocol Version
1.1", RFC 4346, April 2006.
[TLS-PSK] Eronen, P., Tschofenig, H., "Pre-Shared Key CipherSuites
for Transport Layer Security (TLS)", RFC 4279, December
2005.
Author's Addresses
Uri Blumenthal
Intel Corporation
1515 State Route 10,
PY2-1 10-4
Parsippany, NJ 07054
USA
Email: Uri.Blumenthal@xxxxxxxxx
Purushottam Goel
Intel Corporation
2111 N.E. 25 Ave.
JF3-414
Hillsboro, OR 97124
USA
Email: Purushottam.Goel@xxxxxxxxx
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
Blumenthal & Goel Expires March 27, 2007 [Page 4]
Internet-Draft PSK NULL-encryption Cipher Suites for TLS September
2006
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
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
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@xxxxxxxxx
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Blumenthal & Goel Expires March 27, 2007 [Page 5]
_______________________________________________
TLS mailing list
TLS@xxxxxxxxxxxxxx
https://www1.ietf.org/mailman/listinfo/tls