[saag] FW: TLS WG Report

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Thu, 26 March 2009 20:13 UTC

Return-Path: <jsalowey@cisco.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id F0CDC3A69F7 for <saag@core3.amsl.com>; Thu, 26 Mar 2009 13:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.186
X-Spam-Status: No, score=-6.186 tagged_above=-999 required=5 tests=[AWL=0.413, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id AKEh-WYsQ-h2 for <saag@core3.amsl.com>; Thu, 26 Mar 2009 13:13:04 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com []) by core3.amsl.com (Postfix) with ESMTP id F15EA3A695C for <saag@ietf.org>; Thu, 26 Mar 2009 13:12:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,428,1233532800"; d="scan'208";a="147255911"
Received: from sj-dkim-3.cisco.com ([]) by sj-iport-3.cisco.com with ESMTP; 26 Mar 2009 20:13:48 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com []) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n2QKDm4U021915 for <saag@ietf.org>; Thu, 26 Mar 2009 13:13:48 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com []) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n2QKDmK8013988 for <saag@ietf.org>; Thu, 26 Mar 2009 20:13:48 GMT
Received: from xmb-sjc-225.amer.cisco.com ([]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Mar 2009 13:13:47 -0700
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
Date: Thu, 26 Mar 2009 13:13:46 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE507B333C4@xmb-sjc-225.amer.cisco.com>
Thread-Topic: TLS WG Report
Thread-Index: AcmuTaEFlhJN4i5eRNKxKKosohhfFwAAa4Pw
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: <saag@ietf.org>
X-OriginalArrivalTime: 26 Mar 2009 20:13:48.0040 (UTC) FILETIME=[5F3F4080:01C9AE4F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=855; t=1238098428; x=1238962428; c=relaxed/simple; s=sjdkim3002; 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:=20FW=3A=20TLS=20WG=20Report |Sender:=20; bh=9Z1Tb7naovP4TwT2FdvESUiIhYFn3Yt16L3zQzcWBkg=; b=O0leq4lV/p+pmnzhg12fhYOPr0z2JtBGtqmrDdFVWO6EueeOkxnOlsPOa4 b9uOyhPI5X8quLFYu1pi9fEJie8UAz/QKJNvIfvOAsX5XEsDAnf9AkuuJcWh g7tp+WgHsS;
Authentication-Results: sj-dkim-3; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Subject: [saag] FW: TLS WG Report
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 20:13:05 -0000

The TLS WG met at 9 AM on Thu March 26

We have three documents in various stages of being almost finished:

TLS Exporters: finished WGLC. Only editorial comments. Needs a new draft
and then can go to the IESG.
TLS Extensions: needs a new straightforward revision and then WGLC.
DTLS 1.2: ready for WGLC

We had a presentation from Stefan Santesson about a protocol for caching
server information on the client to reduce handshake size (this is a
modification of the old Fast Track concept). The WG decided to take on
this work.

We also had a presentation from Michael Williams about DTLS MOBI-D, an
application mobility solution for DTLS. There was some enthusiasm for
this work, but we recognize that it is substantial work and impacts
areas outside of TLS. The Chairs will work with the ADs to work out how
best to proceed.