IETF Logo Mail Archive

Re: [sidr] BGPSEC proposal to drop AS_PATH [was: Fwd: request for agenda items for interim meeting 6 Jun]

Jakob Heitz <jakob.heitz@ericsson.com> Wed, 30 May 2012 00:47 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 ACA2821F8687; Tue, 29 May 2012 17:47:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFslkLacnUxU; Tue, 29 May 2012 17:47:44 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1454921F867B; Tue, 29 May 2012 17:47:39 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q4U0lcsn028834 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 May 2012 19:47:38 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.31]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 29 May 2012 20:47:37 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Randy Bush <randy@psg.com>
Date: Tue, 29 May 2012 20:47:36 -0400
Thread-Topic: [sidr] BGPSEC proposal to drop AS_PATH [was: Fwd: request for agenda items for interim meeting 6 Jun]
Thread-Index: Ac09+0eISep1YF9nT8a9bfJn5+bX0AAAiVEw
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BFA66011@EUSAACMS0701.eamcs.ericsson.se>
References: <5BA9D6DE-BE0E-4922-9E09-7B85BD6F9342@juniper.net> <CE876529-6CDB-44ED-9184-CA73DFD2D048@juniper.net> <C37AE148-0873-4D9A-B1B2-1959A427435D@bgp.nu> <7309FCBCAE981B43ABBE69B31C8D213921BFA65FD8@EUSAACMS0701.eamcs.ericsson.se> <m2sjeise8s.wl%randy@psg.com>
In-Reply-To: <m2sjeise8s.wl%randy@psg.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: idr wg <idr@ietf.org>, sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] BGPSEC proposal to drop AS_PATH [was: Fwd: request for agenda items for interim meeting 6 Jun]
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: Wed, 30 May 2012 00:47:44 -0000

On Tuesday, May 29, 2012 5:29 PM, Randy Bush <mailto:randy@psg.com> wrote:

>> AS_PATH is used to specify the path that the payload takes.
> 
> really?  i thought it was a routing loop detection mechanism.
> it's been a while since folk wrote research papers describing
> schemes for routing by AS.
> 
> i would phrase it as
> 
> AS_PATH specifies the ASs through which the routing announcement has
> passed.
> 
>> Signed_AS_PATH is to verify the path that the update message takes.
> 
> and then this works really nicely.
> 
>> There is no reason they can not be different.
> 
> and here i thought that detecting that they differ, as an attack, is
> the core goal of as-path validation.

I thought it was to prevent an AS from
announcing an update that it was not authorised  to.

An entirely different thing.

> 
> randy

-- 
Jakob Heitz.

v2.23.0 | Report a Bug | By Email