Re: [Cfrg] Help with the use of contexts

Watson Ladd <watsonbladd@gmail.com> Sun, 29 January 2017 22:33 UTC

Return-Path: <watsonbladd@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA8C1296B9 for <cfrg@ietfa.amsl.com>; Sun, 29 Jan 2017 14:33:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 ArEUh8pbzMun for <cfrg@ietfa.amsl.com>; Sun, 29 Jan 2017 14:33:41 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 5D44B1296B8 for <cfrg@irtf.org>; Sun, 29 Jan 2017 14:33:41 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id c85so190426766wmi.1 for <cfrg@irtf.org>; Sun, 29 Jan 2017 14:33:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=3yj+y5EGNtLesPjlwT+csFXYjP5K1txSQse8i13ATLE=; b=UiYuQV0+kM2WO9o1dtxhl5bmpTNWpkd1JwZ8gTKLzxk1pgOvsWH2D1rp09RQovrusT +6uxdAv3iJY2BT4b8uX4QRijV7M0zZpf+XTUKiUPk4SwpEDkLmlsubpMtcxhcZhMHyRe ojSNI6vlOLRu5Z6A80on9LiYcS0nqz61D3zO7XrQv7J8lU47jnAkk3d/5FNFuxcXlJap +u4adHCZ7V/7eh5ayH9EgAUvqOeGJ+d0bYS3ay9Xw2IufVEd1cGKqruvoRyM68nC0quz kLN1ZeMK3aq78opwCfgccm7EXzfdAggepA3JBQGFXk4sG5Vd5beslwbVjBy+RvhffKle eXBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=3yj+y5EGNtLesPjlwT+csFXYjP5K1txSQse8i13ATLE=; b=AQBk4vlCDtlylFFoqgkURTMuCO1a4oTkdMvlFr6WKV8+CkwcXyAMrhyA73+eHySSud GI9aeetfdSqWho0SkOdLC+Jcdv1FMV7xmT61HtNiBm12LG0Ew0iB9/UBdDa6B9zq1X/f HIjAB0XnYhW0Wrk8VHO75+h/TTPfFfuJ25JsgYwfNVmprayhfJ9bKhBPBnrEIqPnIuhc MPuKUQ2WZyD8h/ZWeD3/dJxhp2OgKyxnY5DF7WwTLqkEFSoiD8RS904QHXAXe0NVsXKf LEZUU5SGFJRDLnVteVAp9K/ylebGfbhWDY424XEfTK3L0eQ1Xms9jpODVP2LXTfTLbVG mg4A==
X-Gm-Message-State: AIkVDXLxPvUpxzv65mXE1fd+0wkthks13YhMms53cAnGGaE/cKGQZO15+9GWCkrse4wOISp7gblo1VnLwP8vSA==
X-Received: by 10.28.188.9 with SMTP id m9mr10959791wmf.79.1485729219783; Sun, 29 Jan 2017 14:33:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.164.130 with HTTP; Sun, 29 Jan 2017 14:33:39 -0800 (PST)
In-Reply-To: <708C8E8E-37AE-4B8F-9843-B0F8CDB29229@gmail.com>
References: <20170116200948.6535.qmail@cr.yp.to> <5eeb3d4d-1fc0-35ba-6f47-87fa0d808edc@cs.tcd.ie> <AA42E783-43FC-4C9B-A387-623B5B18B4FB@gmail.com> <708C8E8E-37AE-4B8F-9843-B0F8CDB29229@gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Sun, 29 Jan 2017 14:33:39 -0800
Message-ID: <CACsn0cm22h8_61CEZjKYyHfnd7vvnC39ZMjhusjWcZKu_Z0zhw@mail.gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/i-DgDsJ9-YDcumA1BR_p9n_1lk4>
Cc: "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] Help with the use of contexts
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jan 2017 22:33:43 -0000

On Tue, Jan 24, 2017 at 11:02 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:
>
>>
>>> On 17 Jan 2017, at 13:48, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>>>
>>>
>>> However, I really do wish that CFRG specs would not offer
>>> both choices - that will simply lead to repeating this
>>> discussion each time an IETF protocol wants to use the CFRG
>>> spec. And of course, different decisions will be made over
>>> time,
>>
>> Not over time. In the next few months the IESG is going to get documents about EdDSA signatures from TLS, IPsecME and curdle for signatures in TLS, IKE, and PKIX respectively.  If the decision is not the same in all of them, I think (hope) that the IESG would ask why.
>
> So now that RFC 8032 is out and does include both choices, what is our advice to TLS, IPsecME and Curdle?  Contexts or no?
>
> Yoav
>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> https://www.irtf.org/mailman/listinfo/cfrg

No contexts. Why did we ever include them?

-- 
"Man is born free, but everywhere he is in chains".
--Rousseau.