Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis
Yaron Sheffer <yaronf.ietf@gmail.com> Sun, 20 November 2016 14:09 UTC
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8631294DF for <tls@ietfa.amsl.com>; Sun, 20 Nov 2016 06:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yWRdAL8VP18I for <tls@ietfa.amsl.com>; Sun, 20 Nov 2016 06:09:42 -0800 (PST)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29C581294EA for <tls@ietf.org>; Sun, 20 Nov 2016 06:09:42 -0800 (PST)
Received: by mail-pg0-x229.google.com with SMTP id f188so120528825pgc.3 for <tls@ietf.org>; Sun, 20 Nov 2016 06:09:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=5fdnOQatqfrExa1245or7IQzt+ZnNSp+9nI8ulSvVEY=; b=ZlkYTe09hHegBDG5orhhrYSC1+OOmwb0wrg9fTZuT0TCqk3gErN5bgUG8RIfOnuDDt yZxoZNJe4U0iH1RZHEvXtrXImhZ3ziy7kvYTdmZoudtL5Bvp/9qm3Xl5+XGD7xxkKtTG 7KaV1H3A7NQi7Jc/If7hassvOJC8uC42+JgfEnsodcQlfYVC6L6dffll2PNUurmgrcOI XDvDXI/jkeb7upCgqLmNJmPexVivCHf0Q5kTZAgrFsdo96HmMy9PABLSPC7V3jVVdDhZ +CaGvIHh8HgPMyRduiVA7Yrt81FttfV/79zawIdtqRZfFq96XZg5uDFdVkfhbesX38C2 F8sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=5fdnOQatqfrExa1245or7IQzt+ZnNSp+9nI8ulSvVEY=; b=b8U5Dshanqm9D3lsqZD40JGXwOduzniFD8A9ConPhGPMoFe5oyBMwUqu6kOHX181x3 wUv3IxHB5uKisVOKsZ5m+nz9hqB5qVJ5J1IGQNo9akbDyh10RWvQUUEYrw8R8pYCgwKh SND3qRUnXnbsHCzk2hemgzPAdGf1mruQ2UqxUqHj1fBMnvHanCJgVbMZ5zLA4q+buv45 w09BpQHqk+UOGqpF9/lfoYGt+Vw1Kwju+V9koHTtX4tYwKxJqmiH9cthaoZG28TXSazL Si5OdU9swYD2UD6LcAC+TcV/ha9mmGVf84VKyC50EmkdpoiTKT+TzkDOnZ97HhiD8Qhp 57+g==
X-Gm-Message-State: AKaTC02scE07TX6YTnUI9Dumuw0zF7jffF07TlyQDcTu8hAlT6k33zFp+f//84dwiWWNaA==
X-Received: by 10.99.48.68 with SMTP id w65mr21063593pgw.68.1479650981480; Sun, 20 Nov 2016 06:09:41 -0800 (PST)
Received: from [192.168.0.53] ([116.84.50.12]) by smtp.gmail.com with ESMTPSA id v1sm12732921pgv.33.2016.11.20.06.09.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Nov 2016 06:09:40 -0800 (PST)
To: "Salz, Rich" <rsalz@akamai.com>, Sean Turner <sean@sn3rd.com>, "<tls@ietf.org>" <tls@ietf.org>
References: <62B88142-2DBE-439F-AD4A-309053925794@sn3rd.com> <7462904085cc4a94914298af81157031@usma1ex-dag1mb1.msg.corp.akamai.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <7de8f9da-8ab1-cfc2-00ad-9c91c7694174@gmail.com>
Date: Sun, 20 Nov 2016 23:09:37 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <7462904085cc4a94914298af81157031@usma1ex-dag1mb1.msg.corp.akamai.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/pkfg46AH3zPV9YHNIRHrVdkJTec>
Subject: Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 20 Nov 2016 14:09:43 -0000
Hi Rich, I am confused by your response. For those who missed CURDLE, could you please briefly explain why we don't need signature context in non-TLS areas. And even if this is the case, the current thread is about TLS! So why are we now saying that contexts are not needed even for TLS? Thanks, Yaron On 20/11/16 13:21, Salz, Rich wrote: > In CURDLE this week, we had consensus (to be confirmed on the list, of course) that > Signature contexts were created in the TLS arena, we all thought we needed them in other areas, and we don't, therefore all CURDLE documents for those other areas will specify a zero-length context. > > FWIW. > > I agree with Yoav's message, for the reasons he states. > > -- > Senior Architect, Akamai Technologies > Member, OpenSSL Dev Team > IM: richsalz@jabber.at Twitter: RichSalz > > >> -----Original Message----- >> From: Sean Turner [mailto:sean@sn3rd.com] >> Sent: Friday, November 18, 2016 6:56 PM >> To: <tls@ietf.org> >> Subject: [TLS] WGLC for draft-ietf-tls-rfc4492bis >> >> All, >> >> This is a working group last call for the “4492bis to Standards Track" draft >> available @ http://datatracker.ietf.org/doc/draft-ietf-tls-rfc4492bis/. Please >> review the document and send your comments to the list by 9 December >> 2016. >> >> Note that we are particularly interesting in the issue Yoav raises in the >> following message: >> https://mailarchive.ietf.org/arch/msg/tls/8Ec7jQqLr_3FrvQfuclllfozKZk >> >> Thanks, >> J&S >> _______________________________________________ >> TLS mailing list >> TLS@ietf.org >> https://www.ietf.org/mailman/listinfo/tls > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
- [TLS] WGLC for draft-ietf-tls-rfc4492bis Sean Turner
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Yaron Sheffer
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Salz, Rich
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Yaron Sheffer
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Salz, Rich
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Yaron Sheffer
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis John Mattsson
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis John Mattsson
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Yoav Nir
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Yoav Nir
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Ilari Liusvaara
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Yaron Sheffer
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Sean Turner
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Sean Turner
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Martin Thomson
- Re: [TLS] WGLC for draft-ietf-tls-rfc4492bis Ilari Liusvaara