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

Jakob Heitz <jakob.heitz@ericsson.com> Tue, 22 November 2011 18:02 UTC

Return-Path: <jakob.heitz@ericsson.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 249BF1F0C38 for <sidr@ietfa.amsl.com>; Tue, 22 Nov 2011 10:02:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.417
X-Spam-Level:
X-Spam-Status: No, score=-6.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 IapWAWlphmg9 for <sidr@ietfa.amsl.com>; Tue, 22 Nov 2011 10:02:20 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 94CAF1F0C35 for <sidr@ietf.org>; Tue, 22 Nov 2011 10:02:20 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAMI2F44015079; Tue, 22 Nov 2011 12:02:18 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 22 Nov 2011 13:02:13 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Tue, 22 Nov 2011 13:02:11 -0500
Thread-Topic: [sidr] Route Leak fix: V free routing
Thread-Index: AcypOpAtWrRtDwSwS0i9By2Py4lHfQABRmrg
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21391A47045B49@EUSAACMS0701.eamcs.ericsson.se>
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> <CAH1iCiofjU_Mgx+3e9HtDytK28XKZgfS37RsYPT=CbNz1Hb+kQ@mail.gmail.com>
In-Reply-To: <CAH1iCiofjU_Mgx+3e9HtDytK28XKZgfS37RsYPT=CbNz1Hb+kQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 18:02:21 -0000

I stand corrected. Good idea.

If I understand it right, the presence of a BGPSEC signature
AND the absence of a provenance signature signals that
the prefix has left the set of AS's that are contracted
to provide it reachability.

--
Jakob Heitz.

> -----Original Message-----
> From: Brian Dickson [mailto:brian.peter.dickson@gmail.com]
> Sent: Tuesday, November 22, 2011 9:17 AM
> To: Jakob Heitz
> Cc: sidr wg list
> Subject: Re: [sidr] Route Leak fix: V free routing
> 
> 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