Re: [secdir] secdir review of draft-cakulev-mikey-ibake-02

"Dan Harkins" <dharkins@lounge.org> Wed, 22 September 2010 22:51 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 783BA3A6809; Wed, 22 Sep 2010 15:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.572
X-Spam-Level:
X-Spam-Status: No, score=-5.572 tagged_above=-999 required=5 tests=[AWL=0.693, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TM3mFpr5iDuA; Wed, 22 Sep 2010 15:51:12 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by core3.amsl.com (Postfix) with ESMTP id 7DE2B3A6812; Wed, 22 Sep 2010 15:51:10 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 60A461E00BA; Wed, 22 Sep 2010 15:51:38 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Wed, 22 Sep 2010 15:51:38 -0700 (PDT)
Message-ID: <2854ac8e63b1bad22adfd01498af694f.squirrel@www.trepanning.net>
In-Reply-To: <002801cb5a38$5db4f5c0$191ee140$@net>
References: <002801cb5a38$5db4f5c0$191ee140$@net>
Date: Wed, 22 Sep 2010 15:51:38 -0700 (PDT)
From: "Dan Harkins" <dharkins@lounge.org>
To: "Glen Zorn" <gwz@net-zen.net>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: violeta.cakulev@alcatel-lucent.com, 'Tim Polk' <william.polk@nist.gov>, ganesh.sundaram@alcatel-lucent.com, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] secdir review of draft-cakulev-mikey-ibake-02
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 22:51:13 -0000

  Hello,

On Wed, September 22, 2010 2:27 am, Glen Zorn wrote:
[snip]
> Section 4.1
>
> .         The first sentence of paragraph 4 contains rather confusing
> notation.  It says "The Initiator next chooses a random x and computes xP
> (i.e. adds P to itself x times), where P is a point on elliptic curve E
> known to all users."  The notation "xP" is a conventional one for
> expressing
> the multiplication of P by x, which is not the same as the addition of P
> to
> itself x times.  If the latter interpretation is actually, I think that a
> better notation should be chosen.

  Actually multiplication of P by x is "the addition of P to itself x-1
times" since adding P to itself 1 time would be P + P = 2P.

  Regarding the notation, it would be nice if there was some convention
on how to should show ECC operations in an I-D or RFC. Should it be
multiplicative notation or additive notation? Should points on the curve
be upper-case and scalars are lower-case, or vice versa? How do you
represent the elliptic curve identity element? RFC 5931 uses additive
notation, uses upper-case for points and lower-case for scalars and calls
it the "point at infinity", respectively, while David McGrew's fundamental
ECC draft uses multiplicative notation, uses lower-case for points and
upper-case for scalars and defines it as "e", respectively.

  This draft is proposing "xP" while the additive notation used in
RFC 5931 is "x*P". So this is yet another notation for the same old thing.

  A diktat from the IESG or the Security Area ADs would be helpful.

  regards,

  Dan.