Re: [sidr] Keys and algorithms for Updates - feasibility analysis? (was Re: RPKI and private keys)
Christopher Morrow <morrowc.lists@gmail.com> Mon, 07 May 2012 20:29 UTC
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7C621F867E for <sidr@ietfa.amsl.com>; Mon, 7 May 2012 13:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.582
X-Spam-Level:
X-Spam-Status: No, score=-103.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 5dplLM4yPTPI for <sidr@ietfa.amsl.com>; Mon, 7 May 2012 13:29:17 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id 775F921F8659 for <sidr@ietf.org>; Mon, 7 May 2012 13:29:17 -0700 (PDT)
Received: by qabj40 with SMTP id j40so3563720qab.15 for <sidr@ietf.org>; Mon, 07 May 2012 13:29:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gOQ2PtApbtWP0qaKWeEE7Tlu+FcFrQVmd4hbSzuUVaI=; b=Fu5ObXxrFmJgdrIEgmToPnf+nJNdXISy4ChA3pn92g8dIYAUXgWUllPeQ37VqjPEXK oEQtd2p39C00Z4+7jxNtwaRUORS5hGPBRTEjGMUklgQ8Yh0sc2IgnK4ChHT8mQoAhyN1 ksnMVsFZQwXzO12anWTw9msN7vuri1mi8jLhpvbvvVgQQ0XVmQbpZ3AWn+9hSCpK7pMF W5DgyLL4olbPsVuF3Uef4P3eSOdeazE96QZmHYTqvlD0BvPjsVb4iIIjjUGjomiuO3RC B+BIaTCOh8Mgh25qnE46YrHsEBQZFOcLimAkbzGlkDAZjGR2ttrkiWBBWsSDZMyT9+wS CaUA==
MIME-Version: 1.0
Received: by 10.60.4.1 with SMTP id g1mr23327497oeg.55.1336422556763; Mon, 07 May 2012 13:29:16 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.155.39 with HTTP; Mon, 7 May 2012 13:29:16 -0700 (PDT)
In-Reply-To: <CAH1iCiruThFzpef5u9NVt+3AokGnuFhq-GrbqEOkkKnVhav4zQ@mail.gmail.com>
References: <CAH1iCiruThFzpef5u9NVt+3AokGnuFhq-GrbqEOkkKnVhav4zQ@mail.gmail.com>
Date: Mon, 07 May 2012 16:29:16 -0400
X-Google-Sender-Auth: u0QNM2BWmu9Si51dVdU1733XZS4
Message-ID: <CAL9jLab2XT-4NWr8KyHKOiQMTWqE5cTavmEr4Uw+S4zhrA=YLA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Keys and algorithms for Updates - feasibility analysis? (was Re: RPKI and private keys)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 20:29:18 -0000
I'm probably confused, or the example has been simplified.. but On Mon, May 7, 2012 at 2:58 PM, Brian Dickson <brian.peter.dickson@gmail.com> wrote: > Scenario 2: > perform basic pseudo-signature once, repeat for routing table of 400,000 in > size. > pseudo-signature operation: > use N distinct pseudo-random number generators (PNRG), seeded > separately with state preservation (N=8 corresponds to 256 bits of entropy) > call random() from each preserved state to generate a 32-bit random > number, concatenate the N x 32 bit values how do I check 3 as-hops away that whatever is attached to the update means that the update was signed? you seem to be saying: "sign with some random bytes that you make up on the fly". -chris
- [sidr] Keys and algorithms for Updates - feasibil… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Christopher Morrow
- Re: [sidr] Keys and algorithms for Updates - feas… Christopher Morrow
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Sriram, Kotikalapudi
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Ross.Anderson@cl.cam.ac.uk
- Re: [sidr] Keys and algorithms for Updates - feas… Sriram, Kotikalapudi
- Re: [sidr] Keys and algorithms for Updates - feas… Murphy, Sandra
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Christopher Morrow
- Re: [sidr] Keys and algorithms for Updates - feas… Murphy, Sandra
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Christopher Morrow
- Re: [sidr] Keys and algorithms for Updates - feas… Brian Dickson
- Re: [sidr] Keys and algorithms for Updates - feas… Christopher Morrow
- Re: [sidr] Keys and algorithms for Updates - feas… Ross.Anderson@cl.cam.ac.uk
- Re: [sidr] Keys and algorithms for Updates - feas… Christopher Morrow
- Re: [sidr] Keys and algorithms for Updates - feas… Montgomery, Douglas
- Re: [sidr] sidrKeys and algorithms for Updates - … Wes Hardaker