[TLS] New version of draft-ietf-tls-rsa-aes-gcm and draft-ietf-tls-ecc-new-mac
"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Tue, 15 April 2008 21:37 UTC
Return-Path: <tls-bounces@ietf.org>
X-Original-To: tls-archive@ietf.org
Delivered-To: ietfarch-tls-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E149F3A68B1; Tue, 15 Apr 2008 14:37:03 -0700 (PDT)
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A61CD3A69DC for <tls@core3.amsl.com>; Tue, 15 Apr 2008 14:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.208
X-Spam-Level:
X-Spam-Status: No, score=-6.208 tagged_above=-999 required=5 tests=[AWL=0.391, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfNvxmBjOKFT for <tls@core3.amsl.com>; Tue, 15 Apr 2008 14:37:01 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id CA8F43A68B1 for <tls@ietf.org>; Tue, 15 Apr 2008 14:37:01 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 15 Apr 2008 14:37:36 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m3FLbaiV012217 for <tls@ietf.org>; Tue, 15 Apr 2008 14:37:36 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3FLbZvw013526 for <tls@ietf.org>; Tue, 15 Apr 2008 21:37:36 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Apr 2008 14:37:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 15 Apr 2008 14:38:25 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE505A0218F@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New version of draft-ietf-tls-rsa-aes-gcm and draft-ietf-tls-ecc-new-mac
Thread-Index: AcifQQlKif7nykJkSV6RmCc9KDW3IA==
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: tls@ietf.org
X-OriginalArrivalTime: 15 Apr 2008 21:37:35.0862 (UTC) FILETIME=[EB8C4160:01C89F40]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=862; t=1208295456; x=1209159456; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jsalowey@cisco.com; z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci sco.com> |Subject:=20New=20version=20of=20draft-ietf-tls-rsa-aes-gcm =20and=20draft-ietf-tls-ecc-new-mac |Sender:=20; bh=x5vusNn7nlm4g6KeYBXiwBiDrdgvPvxiQaZ8jlYjcIM=; b=UUkj0isZ+xQDdjxOuAuvw8diheslGRPx6dtKh501HyHEriND1kCUY5HGZl k4SK9SCfguJ4uXMP40l0YoYgiGnmrSva/FKyXioBpJjEUSHQjV39yJHipwJm 4XU2qhogAXu3Lx8Q5B9BEjYkMUF8AkmhhY8RWtRHHNdoI1jIswSYg=;
Authentication-Results: sj-dkim-1; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Subject: [TLS] New version of draft-ietf-tls-rsa-aes-gcm and draft-ietf-tls-ecc-new-mac
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tls-bounces@ietf.org
Errors-To: tls-bounces@ietf.org
I posted draft-ietf-tls-rsa-aes-gcm-03 last night, I think it address the issues raised in WG last call. Here is a summary of resolutions and changes: + Added text to mandate use of bad_record_mac alert in case of AES-GCM failure (Issue 91) + Removed references to DTLS - Cipher suites will be discussed in DTLS update + Editorial changes - cleaned up introduction - align terminology with TLS 1.2 - fixed up references Eric also posted a revision to draft-ietf-tls-ecc-new-mac, here are the major changes I know of (Eric can send an update if there are others): + Document now points to draft-ietf-tls-rsa-aes-gcm for AES GCM details and security considerations + ECDH-RSA and ECDHE-RSA cipher suites added (Issue 93) Please take a final look at the documents before they go on to AD evaluations. Thanks, Joe _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
- [TLS] New version of draft-ietf-tls-rsa-aes-gcm a… Joseph Salowey (jsalowey)