IETF Logo Mail Archive

Re: [sidr] Conflict between rtr-keying, bgpsec-pki-profile, and RFC 6487

Sean Turner <TurnerS@ieca.com> Mon, 12 May 2014 22:54 UTC

Return-Path: <TurnerS@ieca.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280A51A07A7 for <sidr@ietfa.amsl.com>; Mon, 12 May 2014 15:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
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 3OSbhvNBvyKn for <sidr@ietfa.amsl.com>; Mon, 12 May 2014 15:54:13 -0700 (PDT)
Received: from gateway04.websitewelcome.com (gateway04.websitewelcome.com [64.5.50.5]) by ietfa.amsl.com (Postfix) with ESMTP id B62BE1A078C for <sidr@ietf.org>; Mon, 12 May 2014 15:54:13 -0700 (PDT)
Received: by gateway04.websitewelcome.com (Postfix, from userid 5007) id 7149B47E90576; Mon, 12 May 2014 17:54:07 -0500 (CDT)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway04.websitewelcome.com (Postfix) with ESMTP id DB76047E90274 for <sidr@ietf.org>; Mon, 12 May 2014 17:54:06 -0500 (CDT)
Received: from [96.231.225.192] (port=50638 helo=[192.168.1.4]) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <TurnerS@ieca.com>) id 1Wjz6k-00041Q-5M; Mon, 12 May 2014 17:54:06 -0500
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Sean Turner <TurnerS@ieca.com>
In-Reply-To: <m2wqdq3gtd.wl%randy@psg.com>
Date: Mon, 12 May 2014 18:54:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E43F204-1FD6-4D92-AE6A-F0B6EDA93FFC@ieca.com>
References: <20140221233023.4ABC9170A4@thrintun.hactrn.net> <530B7657.10806@bbn.com> <965AC70C-983A-4C9F-B555-4C5A7AAD3F91@ieca.com> <20140404171253.E2CF21721C@thrintun.hactrn.net> <C228CA80-2486-42ED-82A1-1F4BE3C21C4B@apnic.net> <DAB01E95-83AA-4F1B-B486-25D3A6F1BA04@ieca.com> <m2wqdq3gtd.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1874)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 96.231.225.192
X-Exim-ID: 1Wjz6k-00041Q-5M
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([192.168.1.4]) [96.231.225.192]:50638
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/116Mz6ughLNp8fEnO0gJ1rmw9Pk
Cc: sidr@ietf.org
Subject: Re: [sidr] Conflict between rtr-keying, bgpsec-pki-profile, and RFC 6487
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
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, 12 May 2014 22:54:15 -0000

On May 12, 2014, at 16:03, Randy Bush <randy@psg.com> wrote:

>> Would it make sense to have the name that goes in the router
>> certificate then be something like “ROUTER-#-32_bit_BGP_Identifier”
>> where the # gets incremented everytime there’s a new key?  For those
>> that love hard coded lengths this might be an issue if the # grows,
>> but is that the only drawback?
> 
> if you have to go down that path, and i am unsure of it, then use a
> fixed length router# and wrap.

I could live with that make it like 000 an wrap 999.  If you have to rekey that often ….

> and keep in mind that bgp_id is unique only within an AS.

yep that’s true.

spt

v2.23.0 | Report a Bug | By Email