Re: [sidr] EE cert to RTR

Michael Baer <baerm@tislabs.com> Wed, 25 January 2017 18:47 UTC

Return-Path: <baerm@tislabs.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 D8D4D129AD4 for <sidr@ietfa.amsl.com>; Wed, 25 Jan 2017 10:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 HvdHm6rlMFzz for <sidr@ietfa.amsl.com>; Wed, 25 Jan 2017 10:47:09 -0800 (PST)
Received: from mail.mikesoffice.com (v6.mikesoffice.com [IPv6:2001:470:1f05:274::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9196129ADF for <sidr@ietf.org>; Wed, 25 Jan 2017 10:47:09 -0800 (PST)
Received: from localhost (unknown [IPv6:2001:470:1f05:274:3e97:eff:feba:52f]) by mail.mikesoffice.com (Postfix) with ESMTPSA id 38CA939005A; Wed, 25 Jan 2017 10:47:09 -0800 (PST)
From: Michael Baer <baerm@tislabs.com>
To: Randy Bush <randy@psg.com>
References: <191c277b0ab244bdb6e8c6c2223e7233@XCH-ALN-014.cisco.com> <31d3cc54874344d38e0a085301420c19@XCH-ALN-014.cisco.com> <m2y3y5gm01.wl-randy@psg.com>
X-Face: "*g#dUT3; 8M9AE5dLk\\b4G\cNCQkRb.g/2QwEXQKf.:<GckOP:; wBMTb7\%Y"JI=R<M6g?6}tR)6Z7rp5X*24G\bkb!
Date: Wed, 25 Jan 2017 10:47:09 -0800
In-Reply-To: <m2y3y5gm01.wl-randy@psg.com> (Randy Bush's message of "Sat, 21 Jan 2017 11:55:26 +0900")
Message-ID: <87inp3vuxe.fsf@tislabs.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/FVimyPLPGrctY1YCYA1lNsRvCZo>
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] EE cert to RTR
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 25 Jan 2017 18:47:11 -0000

>>>>> On Sat, 21 Jan 2017 11:55:26 +0900, Randy Bush <randy@psg.com>; said:

    >> https://tools.ietf.org/html/draft-ietf-sidr-rpki-rtr-rfc6810-bis-08
    RB> dragon research labs software supports it.  drl relying party cacheware
    RB> fully supports 6810-bis.  and the drl CA gooey has the router cert
    RB> functions you need to create the router certs.

    RB> and i presume the two test bgpsec implementations have some way of
    RB> generating router certs which you can then use with any relying party
    RB> cacheware which supports 6810-bis.

And the presumption is correct.  Both the BGPsec for Bird and the
BGP-Srx implementations can generate key pairs and I believe both
implementations (although I can only speak about the BGPsec on BIRD
implementation authoritatively) have support for the RPKI-RTR protocol
for delivering public keys to the router.

-Mike

-- 
Michael Baer
baerm@tislabs.com