Re: [sidr] Keys and algorithms for Updates - feasibility analysis? (was Re: RPKI and private keys)

Christopher Morrow <morrowc.lists@gmail.com> Fri, 11 May 2012 20:20 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 B931321F873A for <sidr@ietfa.amsl.com>; Fri, 11 May 2012 13:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.574
X-Spam-Level:
X-Spam-Status: No, score=-103.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 T5zfBJ0kcKrn for <sidr@ietfa.amsl.com>; Fri, 11 May 2012 13:20:19 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3353821F8716 for <sidr@ietf.org>; Fri, 11 May 2012 13:20:19 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so4452044obb.31 for <sidr@ietf.org>; Fri, 11 May 2012 13:20:18 -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; bh=kkSsjv7vn+AnINarAdISAag3B3uNvy7wSO9jiojebbw=; b=sJu/QvVOZEkodKSVnnawGA8KBS0dy8vd7olLQRPWlNlXQOh7UYaoBQwT5emcFGGNDw nYsq4CKTBKTQGhw5xrFJaIcgPgmzK5FddqV04iU876A1wPksQP2Che+yCAM2/GTBEcPy 90t31WG95iVA0Lr0MX6+Poniad5JL/ojTaYIBfEB2bAApr+za54ycqLlhIe/jwgR8ZLL m+U986CXVuEJrti/tDbzDludn8XnorHl48XlmAVD3TuaKwdTftLgOMnCN4KNuyzm+9DJ POaZcLPO5tzIDiay6sBk/HOEZSvzhvACcWSedekSPLZWqDQ2drhglTB/t6et91eujWAO NARQ==
MIME-Version: 1.0
Received: by 10.182.31.11 with SMTP id w11mr13509839obh.64.1336767618859; Fri, 11 May 2012 13:20:18 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.166.71 with HTTP; Fri, 11 May 2012 13:20:18 -0700 (PDT)
In-Reply-To: <CAH1iCio4_PaLFACs_cDZRV9c3iYhn93XqCrQrR5PD48bpyM3BA@mail.gmail.com>
References: <CAH1iCiruThFzpef5u9NVt+3AokGnuFhq-GrbqEOkkKnVhav4zQ@mail.gmail.com> <CAL9jLab2XT-4NWr8KyHKOiQMTWqE5cTavmEr4Uw+S4zhrA=YLA@mail.gmail.com> <CAH1iCiq3so54pE9XBM5Bp13xaERbmShipmCg=ckEySiDsh5ZPQ@mail.gmail.com> <D7A0423E5E193F40BE6E94126930C4930B990A66A8@MBCLUSTER.xchange.nist.gov> <CAH1iCirMKm1TbtBzWSKy=vHGLdYHvbtnXcwO1G9aG00n3DXmyw@mail.gmail.com> <D7A0423E5E193F40BE6E94126930C4930B990A6710@MBCLUSTER.xchange.nist.gov> <D7A0423E5E193F40BE6E94126930C4930B990A6716@MBCLUSTER.xchange.nist.gov> <CABFLmSTVmEUMYZmXNkbhSac0_jb0o-2nPG2_58Si0SGmF0podA@mail.gmail.com> <D7A0423E5E193F40BE6E94126930C4930B985DEF48@MBCLUSTER.xchange.nist.gov> <24B20D14B2CD29478C8D5D6E9CBB29F60F70871E@Hermes.columbia.ads.sparta.com> <CAH1iCio4_PaLFACs_cDZRV9c3iYhn93XqCrQrR5PD48bpyM3BA@mail.gmail.com>
Date: Fri, 11 May 2012 16:20:18 -0400
X-Google-Sender-Auth: 5LMQPsjmYkPYBStp2kqcfFJ9ARQ
Message-ID: <CAL9jLab0aSJBpQTtbNLq_qLbxwhXj7Y3-_aqZVeMPoTB5C8DTA@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"
Cc: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>, "Murphy, Sandra" <Sandra.Murphy@sparta.com>, "sidr wg list (sidr@ietf.org)" <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: Fri, 11 May 2012 20:20:19 -0000

On Fri, May 11, 2012 at 3:44 PM, Brian Dickson
<brian.peter.dickson@gmail.com> wrote:
> It has been proposed that a roadmap timeframe of 5-7 years is acceptable, in
> order that vendors provide hardware-based implementations. No justification
> for this has been offered, beyond "well, it is common sense".

I believe the timeframes take into account common larger-network
depreciation rates for equipment.
  core -> agg -> fastedge -> hinter-lands-edge -> gone

takes ~4-7 years... or so network folk had said (this came out in the
RAWS WG as well, in 2006)

-chris