IETF Logo Mail Archive

Re: [sidr] Route Leak fix: V free routing

Brian Dickson <brian.peter.dickson@gmail.com> Tue, 22 November 2011 17:17 UTC

Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 811E321F8C57 for <sidr@ietfa.amsl.com>; Tue, 22 Nov 2011 09:17:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.498
X-Spam-Level:
X-Spam-Status: No, score=-3.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1ptPLyM0P4Y for <sidr@ietfa.amsl.com>; Tue, 22 Nov 2011 09:17:08 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id A764121F8C54 for <sidr@ietf.org>; Tue, 22 Nov 2011 09:17:07 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so77424bkb.31 for <sidr@ietf.org>; Tue, 22 Nov 2011 09:17:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3s8pRbZMlWK4zk78Thp32L+0+Hz0HCW7v7uiH/aHyaU=; b=j0SAGII6y3moSslqoG5tgbBjA0XFFOea24aibRSz3hTOGrXLR7z+oSZ/OqO38805+W G5ljClhX33X/hEiVuIr9iKP/5I41yeuIGiwUBxHObHSTRyq0ppTVEFhdFny8xiKaXZHd i8+ED9cocH4zATEsMArvQQwIrLQZYXdkO9Hzc=
MIME-Version: 1.0
Received: by 10.204.154.25 with SMTP id m25mr19730268bkw.140.1321982226775; Tue, 22 Nov 2011 09:17:06 -0800 (PST)
Received: by 10.223.143.8 with HTTP; Tue, 22 Nov 2011 09:17:06 -0800 (PST)
In-Reply-To: <DEA0EFCF-F9A4-4184-A3DB-B80F56B95503@ericsson.com>
References: <F45661E8FBC74F4EB7E1E0386B562A7502B85C80@ftrdmel0.rd.francetelecom.fr> <CAEFE521.704A0%dougm@nist.gov> <m2aa7onudn.wl%randy@psg.com> <CAH1iCipJPGHLzLsUnAK1r0+KY-sEvVQNZjNUbb_=FnL1hyRorQ@mail.gmail.com> <DEA0EFCF-F9A4-4184-A3DB-B80F56B95503@ericsson.com>
Date: Tue, 22 Nov 2011 12:17:06 -0500
Message-ID: <CAH1iCiofjU_Mgx+3e9HtDytK28XKZgfS37RsYPT=CbNz1Hb+kQ@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Route Leak fix: V free routing
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: Tue, 22 Nov 2011 17:17:08 -0000

On Tue, Nov 22, 2011 at 12:11 PM, Jakob Heitz <jakob.heitz@ericsson.com> wrote:
> That's like making the British drive on the right: you can not incrementally deploy.

I don't understand your comment - can you be more specific and precise?

What can you not deploy incrementally?

BGPsec? An end-to-end BGPsec secured path?

Or are you talking about adding this to the spec - clearly this would
be incompatible
with BGPsec implementations that didn't have it.

If the latter, note: the deployed set is currently the null set, so
your argument is moot.

Brian

v2.23.0 | Report a Bug | By Email