Re: [sidr] comments needed (Re: I-D Action: draft-ietf-sidr-rtr-keying-14.txt)

Sandra Murphy <sandy@tislabs.com> Fri, 08 December 2017 21:04 UTC

Return-Path: <sandy@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 60BB31272E1; Fri, 8 Dec 2017 13:04:48 -0800 (PST)
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, SPF_PASS=-0.001] autolearn=ham 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 5wc4t3GrezPx; Fri, 8 Dec 2017 13:04:47 -0800 (PST)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E01A9128D40; Fri, 8 Dec 2017 13:04:46 -0800 (PST)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 43C5128B003B; Fri, 8 Dec 2017 16:04:46 -0500 (EST)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 3C3361F8036; Fri, 8 Dec 2017 16:04:46 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <5990F5D0-B532-482E-BA4F-D20908F6B862@tislabs.com>
Date: Fri, 8 Dec 2017 16:04:45 -0500
Cc: Sandra Murphy <sandy@tislabs.com>, sidr chairs <sidr-chairs@ietf.org>, draft-ietf-sidr-rtr-keying@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0681C485-6A67-4B54-BD36-7695B0D74644@tislabs.com>
References: <150851896075.15465.7110696373396971840@ietfa.amsl.com> <68DEA77B-EB7C-4345-A60E-A134E5CAC2F7@sn3rd.com> <79137BEA-5FD8-4E08-8C49-215146A352F2@tislabs.com> <48765D76-8B14-492B-B444-9F895A920D89@tislabs.com> <260B2F04-6A90-464C-A6B1-7518AD68F7E6@tislabs.com> <5990F5D0-B532-482E-BA4F-D20908F6B862@tislabs.com>
To: sidr list <sidr@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/LHFlMbD2LLbhb_oGh0d8ls6frak>
Subject: Re: [sidr] comments needed (Re: I-D Action: draft-ietf-sidr-rtr-keying-14.txt)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 08 Dec 2017 21:04:48 -0000

Another thought about one point in my long list of comments.


> On Nov 14, 2017, at 9:07 PM, Sandra Murphy <sandy@tislabs.com> wrote:
> 
> 
> 4.  “corresponds” again - there’s no mention of a router verifying that the router cert it receives has an AS that is configured on the router.  There are lots of other checks and double checks - why not this one?  

Is it possible for a router to be configured with an AS before it actually brings up a BGP/BGPsec session to a neighbor?  (my guess: yes.  but IANAOp)

If the router does not know its AS configuration unless it has already started a BGP session, then the check of the AS in a received cert would have to be done while BGP was active but BGPsec was not yet activated.

Is there a way for a router to receive a cert and check the AS after it has been configured with an AS, but before the session with the neighbor actually starts?

If the BGP session must be up before the configured AS is known, and the desire was to check a received cert for a configured AS, then a session could not start with BGPsec from the very beginning.

So.

Q1: Is the sequence

(1) configure AS (2) check AS in received cert (3) start BGPsec session 

possible?

Q2: If the sequence needs to be

(1) configure AS (2) start BGP (3) check AS in received cert (4) start BGPsec

is that acceptable?

Q3: If the second sequence is necessary, then is that bad enough, sufficient reason, to abandon the idea of checking the AS in the cert?

—Sandy