Re: [sidr] I-D Action: draft-ietf-sidr-rtr-keying-05.txt

Randy Bush <randy@psg.com> Tue, 20 May 2014 13:49 UTC

Return-Path: <randy@psg.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 04B621A0460 for <sidr@ietfa.amsl.com>; Tue, 20 May 2014 06:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 oZm9BijfOzry for <sidr@ietfa.amsl.com>; Tue, 20 May 2014 06:49:30 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97C311A06F9 for <sidr@ietf.org>; Tue, 20 May 2014 06:49:30 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WmkQ4-00070V-Ka; Tue, 20 May 2014 13:49:29 +0000
Date: Tue, 20 May 2014 16:49:27 +0300
Message-ID: <m2d2f8ef14.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Sean Turner <TurnerS@ieca.com>
In-Reply-To: <C2542AFC-2EB9-46F8-B371-533C4E20BC6B@ieca.com>
References: <20140429141007.21954.23015.idtracker@ietfa.amsl.com> <99F6C803-C724-430F-AF95-461CBE778C05@ieca.com> <CF86D3BA.1A323%wesley.george@twcable.com> <25567F3D-6C59-48D2-B99F-A88F402D3058@ieca.com> <CF97BB69.1B86D%wesley.george@twcable.com> <m28uq5zlzo.wl%randy@psg.com> <C2542AFC-2EB9-46F8-B371-533C4E20BC6B@ieca.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/O2FJ73wKTZjBdNbnUJNzgLps4-8
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-rtr-keying-05.txt
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: Tue, 20 May 2014 13:49:32 -0000

>>> Though I’m not sure that there is a huge distinction between disabling
>>> BGPSec and taking the router offline since disabling BGPSec would trigger
>>> neighbor session resets for capability renegotiation unless we’ve
>>> specified otherwise in the protocol docs (doesn’t look like it in my quick
>>> skim), and most likely force an entirely ungraceful set of updates as the
>>> neighbors re-send their announcements with AS_PATH instead of BGPSEC_PATH.
>> 
>> likely significantly shorter than whatever time it takes to revoke, get
>> new cert, install, and then go through the bgp reset.  though you will
>> eventually do that anyway.
>> 
> I’m going to throw in a new version and ask for WGLC.

wfm

randy