RE: [TLS] NIST TLS recomendations (IV generation)
"Blumenthal, Uri" <uri.blumenthal@intel.com> Tue, 21 November 2006 18:05 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmZze-0004h5-Np; Tue, 21 Nov 2006 13:05:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmZzd-0004eX-1p for tls@lists.ietf.org; Tue, 21 Nov 2006 13:05:13 -0500
Received: from mga03.intel.com ([143.182.124.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmZza-0005xo-PH for tls@lists.ietf.org; Tue, 21 Nov 2006 13:05:13 -0500
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by mga03.intel.com with ESMTP; 21 Nov 2006 10:05:08 -0800
Received: from fmsmsx334.amr.corp.intel.com ([132.233.42.1]) by azsmga001.ch.intel.com with ESMTP; 21 Nov 2006 10:05:07 -0800
X-ExtLoop1: 1
X-IronPort-AV: i="4.09,444,1157353200"; d="scan'208"; a="148948669:sNHT21248843"
Received: from hdsmsx412.amr.corp.intel.com ([10.127.2.72]) by fmsmsx334.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Nov 2006 10:05:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [TLS] NIST TLS recomendations (IV generation)
Date: Tue, 21 Nov 2006 13:04:55 -0500
Message-ID: <279DDDAFA85EC74C9300A0598E704056FE6A49@hdsmsx412.amr.corp.intel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [TLS] NIST TLS recomendations (IV generation)
thread-index: AccNlH5r81ZMndAnRPKnF49KA+kVjQAAr81w
From: "Blumenthal, Uri" <uri.blumenthal@intel.com>
To: Bodo Moeller <bmoeller@acm.org>
X-OriginalArrivalTime: 21 Nov 2006 18:05:06.0311 (UTC) FILETIME=[9322E970:01C70D97]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: tls@lists.ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org
>Being unpredictable makes the IVs unique except with >negligible probability (unless you've used CBC on too >long a data stream), so there's no need for an explicit >uniqueness requirement. It's that small probability that bothers me. But I guess it is small enough to ignore for practical purposes of real-world commercial applications. >If we write "MUST be unique", this might evoke the perception >that implementations using randomly generated IVs are expected >to check whether these actually are unique, which usually is >totally impractical, and totally unnecessary. Agree. >So "SHOULD be chosen at random, and MUST be unpredictable" >looks exactly right to me. OK. _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls
- RE: [TLS] NIST TLS recomendations (IV generation) Blumenthal, Uri
- RE: [TLS] NIST TLS recomendations (IV generation) Pasi.Eronen
- RE: [TLS] NIST TLS recomendations (IV generation) Blumenthal, Uri
- Re: [TLS] NIST TLS recomendations (IV generation) Bodo Moeller
- RE: [TLS] NIST TLS recomendations (IV generation) Blumenthal, Uri
- Re: [TLS] NIST TLS recomendations (IV generation) Ray Perlner
- Re: [TLS] NIST TLS recomendations (IV generation) Eric Rescorla
- Re: [TLS] NIST TLS recomendations (IV generation) Ray Perlner