Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?

Stephen Kent <kent@bbn.com> Mon, 11 April 2011 22:30 UTC

Return-Path: <kent@bbn.com>
X-Original-To: sidr@ietfc.amsl.com
Delivered-To: sidr@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A86DAE06C1 for <sidr@ietfc.amsl.com>; Mon, 11 Apr 2011 15:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level:
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13O-8DdK+onx for <sidr@ietfc.amsl.com>; Mon, 11 Apr 2011 15:30:47 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfc.amsl.com (Postfix) with ESMTP id DBC46E06C0 for <sidr@ietf.org>; Mon, 11 Apr 2011 15:30:43 -0700 (PDT)
Received: from dhcp89-089-127.bbn.com ([128.89.89.127]:49171 helo=[128.89.89.213]) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Q9NAK-000FkW-HW; Mon, 11 Apr 2011 15:52:52 -0400
Mime-Version: 1.0
Message-Id: <p06240810c9c90b883458@[128.89.89.213]>
In-Reply-To: <8BE1C346-6214-4343-9E46-BFA8D96E4B6C@cisco.com>
References: <AANLkTimq3hcdK7-f_Pa9sWJJOTzF_GBLcYu36sB3WszN@mail.gmail.com> <AANLkTikfn_ZRQNQx0QLV7fJa8DDeqMa=yRqWUH4krMHD@mail.gmail.com> <AANLkTinV88U3cF6z51eNtPeF-xKG1aWVgALd06CPq4kE@mail.gmail.com> <m2d3l6cj2l.wl%randy@psg.com> <289DB32D-D175-49DE-AA82-100407F64C23@juniper.net> <Pine.WNT.4.64.1104012156360.4612@mw-PC> <20110401210506.GA3082@juniper.net> <Pine.WNT.4.64.1104021120430.4612@mw-PC> <20110404083237.GA1860@juniper.net> <FFD0D281-AA3C-4CF2-8AF2-E1A2FE0A53A0@tcb.net> <20110404125015.GA3277@juniper.net> <BANLkTi=eZ=pQ2gJfiPBfeb4frH8Tncempw@mail.gmail.com> <m21v1i9ha8.wl%randy@psg.com> <BF88D659-1BE5-4DD2-AB24-7A113360DF37@cisco.com> <m2tyea7urr.wl%randy@psg.com> <8BE1C346-6214-4343-9E46-BFA8D96E4B6C@cisco.com>
Date: Mon, 11 Apr 2011 15:49:46 -0400
To: Brian Weis <bew@cisco.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?
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: Mon, 11 Apr 2011 22:30:48 -0000

At 9:30 PM -0700 4/6/11, Brian Weis wrote:
>On Apr 6, 2011, at 5:46 PM, Randy Bush wrote:
>
>>>  Getting a new application (such as the rtr protocol) specifying
>>>  hmac-md5 mandatory to implement through a Secdir review and then the
>>>  Security ADs just won't happen. The only exception I can think of is
>>>  if there were no possible alternatives, and that's obviously not the
>>>  case here.
>>
>>  with AO not implemented on any servers, routers not having ssh
>>  libraries, and this being a server to router protocol, what are the
>>  alternatives?
>>
>>  randy
>
>I'm surprised IPsec hasn't been mentioned in this thread ... was it 
>previously discussed and rejected? Correct me if I'm wrong, but I 
>believe it's common for BGP routers to support IPsec and servers 
>definitely support IPsec. On the router side, one or two IPsec 
>sessions to servers should not be a burden. I'm less sure of the 
>server IPsec scaling properties, but I would expect a LINUX or BSD 
>kernel to have the scaling issues as were discussed earlier in this 
>thread regarding SSH but I'm no expert here.
>
>Brian

A few years ago we were told by vendors that many router 
implementations of IPsec were available only to traffic passing 
through a router, not to the
control plane terminating in a router.  Unless that has changed, IPsec is
not a good candidate here.

Steve