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

Hannes Gredler <hannes@juniper.net> Mon, 04 April 2011 12:48 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 BFB583A69EA for <sidr@core3.amsl.com>; Mon, 4 Apr 2011 05:48:42 -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 0xmPlftOqdBJ for <sidr@core3.amsl.com>; Mon, 4 Apr 2011 05:48:42 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id 0DD733A67D1 for <sidr@ietf.org>; Mon, 4 Apr 2011 05:48:41 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTZm+j2KBhT5Byqqik0Hcf8FygZZ0wFOK@postini.com; Mon, 04 Apr 2011 05:50:24 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 05:48:35 -0700
Received: by hannes-755.juniper.net (Postfix, from userid 1000) id 76FEA2E49B; Mon, 4 Apr 2011 14:50:16 +0200 (CEST)
Date: Mon, 04 Apr 2011 14:50:16 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Danny McPherson <danny@tcb.net>
Message-ID: <20110404125015.GA3277@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> <20110404083237.GA1860@juniper.net> <FFD0D281-AA3C-4CF2-8AF2-E1A2FE0A53A0@tcb.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <FFD0D281-AA3C-4CF2-8AF2-E1A2FE0A53A0@tcb.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
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: Mon, 04 Apr 2011 12:48:42 -0000

On Mon, Apr 04, 2011 at 08:22:42AM -0400, Danny McPherson wrote:
| 
| On Apr 4, 2011, at 4:32 AM, Hannes Gredler wrote:
| 
| > 
| > so my question is: "why do we need to solve the same problem
| > (= protecting message integrity) 2 times in different ways" ?
| 
| This new machinery simply introduces object-level integrity functions 
| in the application (i.e., BGP), it does nothing to ameliorate attacks 
| at lower layers - all those substrate attack vectors (e.g., transport 
| connection resets, injection or replay attacks) still exist and 
| require controls as well -- else things might break in even uglier ways 
| at higher layers.

still that does not answer my question: why do we need to solve the problem
of transport integrity twice (or to play devils advocate:
shall we encapsulate BGP into SSH up until something better than MD5
is available ;-))

/hannes