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

Hannes Gredler <hannes@juniper.net> Mon, 04 April 2011 08:31 UTC

Return-Path: <hannes@juniper.net>
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 1B1EE3A6935 for <sidr@core3.amsl.com>; Mon, 4 Apr 2011 01:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 yLlxw7XaYyW6 for <sidr@core3.amsl.com>; Mon, 4 Apr 2011 01:31:37 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by core3.amsl.com (Postfix) with ESMTP id 5794F3A6940 for <sidr@ietf.org>; Mon, 4 Apr 2011 01:31:35 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKTZmCTfMIcU1a5HlpZ/PzrTfhDnZ/xAl7@postini.com; Mon, 04 Apr 2011 01:33:19 PDT
Received: from hannes-755.juniper.net (172.30.152.52) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server id 8.2.254.0; Mon, 4 Apr 2011 01:31:00 -0700
Received: by hannes-755.juniper.net (Postfix, from userid 1000) id 4477825AE1; Mon, 4 Apr 2011 10:32:38 +0200 (CEST)
Date: Mon, 04 Apr 2011 10:32:38 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Matthias Waehlisch <waehlisch@ieee.org>
Message-ID: <20110404083237.GA1860@juniper.net>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.WNT.4.64.1104021120430.4612@mw-PC>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: John Scudder <jgs@juniper.net>, Christopher Morrow <christopher.morrow@gmail.com>, 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: Mon, 04 Apr 2011 08:31:38 -0000

On Sat, Apr 02, 2011 at 11:22:18AM +0200, Matthias Waehlisch wrote:
| Hi Hannes,
| 
| On Fri, 1 Apr 2011, Hannes Gredler wrote:
| 
| > so i'd be much more in favour of TCP-AO or even TCP-MD5 (did i mention 
| > that i am no security guy ;-)), since those are the standard tools to 
| > protect message integrity of the BGP session itself - its already 
| > onboard and does not cause much userspace / userspace transport 
| > weirdness since both for linux and BSD its implemented in the kernel.
| > 
|   could you give a reference to both, Linux and BSD, TCP-AO 
| implementations?

to my knowledge there are none up to date, however it has to be done at
some point as TCP-MD5 for securing the base BGP session seems to
be too weak as well.

so my question is: "why do we need to solve the same problem
(= protecting message integrity) 2 times in different ways" ?

/hannes