IETF Logo Mail Archive

Re: [Cfrg] Help with the use of contexts

Yoav Nir <ynir.ietf@gmail.com> Sun, 29 January 2017 23:24 UTC

Return-Path: <ynir.ietf@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 1CE211296FC for <cfrg@ietfa.amsl.com>; Sun, 29 Jan 2017 15:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=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 SSct4KbxxpPf for <cfrg@ietfa.amsl.com>; Sun, 29 Jan 2017 15:24:11 -0800 (PST)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 2F7DC129759 for <cfrg@irtf.org>; Sun, 29 Jan 2017 15:24:11 -0800 (PST)
Received: by mail-wm0-x22d.google.com with SMTP id 196so2192170wmm.1 for <cfrg@irtf.org>; Sun, 29 Jan 2017 15:24:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=g/7Qalpa7Qxv7eD6U8qFvqeghyl8bY4FpobWOlfGMik=; b=Y1W80StV6QSDhvSKOiL6Y2iBSorcKqTMpVBHH0TxInfeTkBwxQoG/QFt3trar4IIqV UyL89RHHsN86146erKTICNcCRqzJ8/j4zveXSPUnQWZYtiGwG/7b0MY60aAe4DkkxdTZ k/XyMjpAclv+8c4yTBNEGI5SBc/WSCzcn+5+fqHOJG9RwAiQjgf3ZSfzAmhCWjzYaxyD tFZZzMQjTmqtb7fWzJe6SSIAVesy62KfSXsCxJYrAsHV84cwVzFN2jJ8oGPNV/z3FvyE lJp0hkqxxk0XZ5XWMGzDCrWyXU9hvN3PblxS2fqUtTM7ptoAGUD+6r+M2S+Bh69o16Qe /ohw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=g/7Qalpa7Qxv7eD6U8qFvqeghyl8bY4FpobWOlfGMik=; b=Ec3bEialkFd4Mt5jKC36muYdnrRUBisFdKA9iHkWltRNbyrqNoFKMlPk53f6fuuaOG 2EwhwMp0z/Epu6/k5X8txkStO3khbMmm/M6qRJnRr82I4zQ4JOCpfuUpOGX15sLkshjz He09+UVQjNEwpdtHWqvNDpdZZKhUx0MBEGLg/Aj1FaGJHMzq8mGLE+FPTaS8BR+y37HO vi+k5nBET3axk5lKSmfkEK6Q1ZMf4V8egfxzdvcoLDg120JAy0yCTqNwp84umvSzx9Mu 4n+y6pJnZdYlEwFNUKW1Y6eBa8dX3YAa854qQutpy7yYxd2ce4WeFf8V+BIrok5uXGEn 449g==
X-Gm-Message-State: AIkVDXJ9wUBHPwfnzbRdc3wdqXeDZkrZCwVr4XGAOpV46KfXHVHWMjJLH9nMHXViVrHOWw==
X-Received: by 10.28.103.3 with SMTP id b3mr10754607wmc.99.1485732249698; Sun, 29 Jan 2017 15:24:09 -0800 (PST)
Received: from [192.168.1.14] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id o70sm19873999wrc.20.2017.01.29.15.24.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jan 2017 15:24:08 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <DA141A39-05C2-4B87-92FA-AE8C5421E104@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0F5A10DD-469A-4F49-83F4-38DE8AD4E258"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Mon, 30 Jan 2017 01:24:06 +0200
In-Reply-To: <CACsn0cm22h8_61CEZjKYyHfnd7vvnC39ZMjhusjWcZKu_Z0zhw@mail.gmail.com>
To: Watson Ladd <watsonbladd@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> <CACsn0cm22h8_61CEZjKYyHfnd7vvnC39ZMjhusjWcZKu_Z0zhw@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/LPq30NQPbqT2yvj-xGaJsve5kfI>
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 23:24:13 -0000

> On 30 Jan 2017, at 0:33, Watson Ladd <watsonbladd@gmail.com> wrote:
> 
> 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?

Seemed like a good idea at the time. The thread begins here:

https://mailarchive.ietf.org/arch/msg/cfrg/GOPQ6lgJcfrXboexQmgNk_ZIZW8 <https://mailarchive.ietf.org/arch/msg/cfrg/GOPQ6lgJcfrXboexQmgNk_ZIZW8>

Regardless, ISTM that almost nobody is advocating for using contexts now for Ed448 in any of the above applications, or for using Ed25519ctx in there. 

Yoav

v2.30.2 | Report a Bug | By Email | System Status