Re: [TLS] New Revision of draft-ietf-tls-applayerprotoneg posted

Sean Turner <TurnerS@ieca.com> Fri, 31 January 2014 15:25 UTC

Return-Path: <TurnerS@ieca.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 164BB1A058D for <tls@ietfa.amsl.com>; Fri, 31 Jan 2014 07:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.167
X-Spam-Level:
X-Spam-Status: No, score=-0.167 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3f8LZHoWhDdG for <tls@ietfa.amsl.com>; Fri, 31 Jan 2014 07:25:13 -0800 (PST)
Received: from gateway07.websitewelcome.com (gateway07.websitewelcome.com [69.56.170.18]) by ietfa.amsl.com (Postfix) with ESMTP id A87641A057F for <tls@ietf.org>; Fri, 31 Jan 2014 07:25:13 -0800 (PST)
Received: by gateway07.websitewelcome.com (Postfix, from userid 5007) id 18E938A654337; Fri, 31 Jan 2014 09:25:10 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway07.websitewelcome.com (Postfix) with ESMTP id EB9D98A65428F for <tls@ietf.org>; Fri, 31 Jan 2014 09:25:09 -0600 (CST)
Received: from [209.23.210.2] (port=60069 helo=[192.168.100.229]) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <TurnerS@ieca.com>) id 1W9Fxt-0006Ms-FW for tls@ietf.org; Fri, 31 Jan 2014 09:25:09 -0600
From: Sean Turner <TurnerS@ieca.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7CA45647-DA89-4554-B18D-E9891C0EF914"; protocol="application/pkcs7-signature"; micalg="sha1"
Message-Id: <8C1E329B-B6BF-4457-9A4F-5FE70E4A691E@ieca.com>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Date: Fri, 31 Jan 2014 10:25:06 -0500
References: <2AA4F2B7B0341A4CA4DAB10D4EDA0D7C2328AB80@xmb-aln-x02.cisco.com>
To: tls@ietf.org
In-Reply-To: <2AA4F2B7B0341A4CA4DAB10D4EDA0D7C2328AB80@xmb-aln-x02.cisco.com>
X-Mailer: Apple Mail (2.1827)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 209.23.210.2
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([192.168.100.229]) [209.23.210.2]:60069
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 2
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Subject: Re: [TLS] New Revision of draft-ietf-tls-applayerprotoneg posted
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
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>
X-List-Received-Date: Fri, 31 Jan 2014 15:25:15 -0000

Just so no one will be surprised I plan to place this document on the IESG telechat for next week. I do plan to add a comment based on Paul’s comment on the shepherd write-up.

spt

On Jan 24, 2014, at 14:30, Stephan Friedl (sfriedl) <sfriedl@cisco.com> wrote:

> We have just posted a new revision of draft-ietf-tls-applayerprotoneg.
> 
> This revision addresses comments received during the IETF LC, notably comments from Alyssa Rowan and Yoav Nir and others concerning enriching the Security Considerations section to call out that the protocol selected is transmitted in the clear and to encourage protocol designers and implementers to take this into consideration for scenarios where protocol leakage could lead to leaking personally identifiable information.
> 
> Thanks,
> 
> Stephan
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls