IETF Logo Mail Archive

Re: [dnsext] draft-hoffman-dnssec-ecdsa-04

Miek Gieben <miek@miek.nl> Thu, 12 April 2012 13:45 UTC

Return-Path: <miekg@atoom.net>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5CE921F8593 for <dnsext@ietfa.amsl.com>; Thu, 12 Apr 2012 06:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qe9DAbFNcJOz for <dnsext@ietfa.amsl.com>; Thu, 12 Apr 2012 06:45:08 -0700 (PDT)
Received: from elektron.atoom.net (cl-201.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:c8::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9CB21F853F for <dnsext@ietf.org>; Thu, 12 Apr 2012 06:45:08 -0700 (PDT)
Received: by elektron.atoom.net (Postfix, from userid 1000) id 619C4402CD; Thu, 12 Apr 2012 15:45:02 +0200 (CEST)
Date: Thu, 12 Apr 2012 15:45:02 +0200
From: Miek Gieben <miek@miek.nl>
To: dnsext WG <dnsext@ietf.org>
Message-ID: <20120412134502.GA1173@miek.nl>
Mail-Followup-To: dnsext WG <dnsext@ietf.org>
References: <20120412071421.GA19834@miek.nl> <201204121117.q3CBHIi5033363@givry.fdupont.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5"
Content-Disposition: inline
In-Reply-To: <201204121117.q3CBHIi5033363@givry.fdupont.fr>
User-Agent: Vim/Mutt/Linux
X-Home: http://www.miek.nl
Subject: Re: [dnsext] draft-hoffman-dnssec-ecdsa-04
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Apr 2012 13:45:08 -0000

[ Quoting <Francis.Dupont@fdupont.fr> in "Re: [dnsext] draft-hoffman-dnssec-e..." ]
> => in fact they can get leading zeros so not the length you expect.
> IMHO the critical thing is (quoting the I-D):
>    For P-256, each integer MUST be encoded as 32 octets; for
>    P-384, each integer MUST each be encoded as 48 octets.

I'm still an ECC noob (and I expect other people reading this might also lack
some crypto skills), but are those integers *always* 32 or 48 octets? I.e there
is never a need for padding?

Regards,
    Miek Gieben

v2.23.0 | Report a Bug | By Email