IETF Logo Mail Archive

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

Brian Weis <bew@cisco.com> Thu, 07 April 2011 00:43 UTC

Return-Path: <bew@cisco.com>
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8BAD3A698B for <sidr@core3.amsl.com>; Wed, 6 Apr 2011 17:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level:
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pFneKJRDPQke for <sidr@core3.amsl.com>; Wed, 6 Apr 2011 17:43:07 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 299243A6847 for <sidr@ietf.org>; Wed, 6 Apr 2011 17:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bew@cisco.com; l=919; q=dns/txt; s=iport; t=1302137091; x=1303346691; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=OV64wUKBVa4Z+dgpD8XYU+Umgq4jXTLTdDV4Lgyfy2A=; b=QV5APz59PvvZ/GbtxQq1XqGl68cijgx8vis+vndVTsLLeyd7QutaUPDD /8d5aqXsQHV/TkrKkRF3o4ySguSoFhx9j9MtiyjDqoRooMLZpqDPQ/+y4 p9sInp/Y0sGYn38tP88nPIe3IIDC97Z3EOKpKq1Tmk6jRSIvEuRQ/gdPH w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPgHnU2rRDoI/2dsb2JhbACmAXeIeZ4nnHKFbASFTodv
X-IronPort-AV: E=Sophos;i="4.63,313,1299456000"; d="scan'208";a="290897524"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 07 Apr 2011 00:44:51 +0000
Received: from stealth-10-32-244-214.cisco.com (stealth-10-32-244-214.cisco.com [10.32.244.214]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p370ipkX022623; Thu, 7 Apr 2011 00:44:51 GMT
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Brian Weis <bew@cisco.com>
In-Reply-To: <m21v1i9ha8.wl%randy@psg.com>
Date: Wed, 06 Apr 2011 17:44:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF88D659-1BE5-4DD2-AB24-7A113360DF37@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>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1082)
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.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 07 Apr 2011 00:43:08 -0000

On Apr 4, 2011, at 8:18 AM, Randy Bush wrote:

>> some folks (not me) suggest that ipsec is the way to go here... (bgp I
>> mean) I think one point to keep in mind is that tcp-ao has exactly
>> zero implementations... while SSH implementations abound.
> 
> turns out that
> 
>  o yfv may have ssh client and server, but they do not have the library
>    in a form usable by arbitrary apps, e.g. bgp
> 
>  o no ao impls on unix, slowlaris, linuxes, ...
> 
> so i would really love to hear from the security folk if we can do
> something like hmac-md5 as the mandatory to implement.

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.

Brian

v2.23.0 | Report a Bug | By Email