IETF Logo Mail Archive

Re: [saag] A case against algorithm agility (long)

S Moonesamy <sm+ietf@elandsys.com> Mon, 05 May 2014 14:57 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC071A00A5 for <saag@ietfa.amsl.com>; Mon, 5 May 2014 07:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 yq94y8T9t8iC for <saag@ietfa.amsl.com>; Mon, 5 May 2014 07:57:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA3B1A0366 for <saag@ietf.org>; Mon, 5 May 2014 07:57:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.134.8]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s45EufP6009680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 May 2014 07:56:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1399301814; bh=DgxXoWB2iBu32Op+uqnXCpYxKElMduqkGZ7rpCJ7+FA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=N39AaEcCWqt6SVGMEipN1sb8n9SB64CUsdNTrRmr1iE7NhYkqlZn1ArAvwFQYT3uS TNdMm033ALbopUoeCCGs8IJPeCb6/fsyLEW5IcMk6bhJhiYiOpr1ptfQEmnX8oBBwf p4EIUL4I8VB12gjcBV6VRmJjyKhH+c+gmoeIrfHk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1399301814; i=@elandsys.com; bh=DgxXoWB2iBu32Op+uqnXCpYxKElMduqkGZ7rpCJ7+FA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sa6G6rTH/Sw1ZN0i1KreZAXzxva150WylAgIg+N532JpnDuSG5Se3+H3rthqWL4d/ xOtu2+8XMIjb9V3egOwQKe1fHFupTyIGJOBgXzaCj+igV8X1W48Qk1Gz4OatHVDxt0 G9EO33Q78hTzKR8NLDfkNjoTZIgounGtrH88Ie7o=
Message-Id: <6.2.5.6.2.20140505064813.0cbc65e8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 05 May 2014 07:41:24 -0700
To: Yoav Nir <ynir.ietf@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <9CF4CFC1-736F-4D4A-843E-1C6D96598443@gmail.com>
References: <53650F27.6040607@iang.org> <5366F7E2.7000605@brainhub.org> <6.2.5.6.2.20140505020707.0bd48c48@resistor.net> <9CF4CFC1-736F-4D4A-843E-1C6D96598443@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/saag/kd4HybZuZ0M78etU-KWcaA0E4GM
Cc: saag@ietf.org
Subject: Re: [saag] A case against algorithm agility (long)
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 05 May 2014 14:57:10 -0000

Hi Yoav,
At 03:29 05-05-2014, Yoav Nir wrote:
>You didn't say which countries, but if your IPsec/TLS/SSH/SMIME is 
>carrying personal information in Russia, it is required to use 
>GOST.  In Japan you can use Camelia, but I don't know if that would 
>fulfil the legal requirements in Europe.

I did not mention the name countries or the technology as my comments 
were probably off-topic. :-)

Camellia is in the recommended list for Japan since 2013.

>That's the beauty of algorithm agility. The same implementation of 
>these protocols can be used with all of these different algorithms.

I am not disagreeing with what you wrote.  It is worthwhile to 
consider whether there are any valid arguments against algorithm agility.

>So I think Andrey meant national standards as well as IETF, IEEE, or 
>ISO standards.

Yes.

Regards,
S. Moonesamy

v2.8.7 | Report a Bug | By Email