Re: [sidr] draft-ietf-sidr-bgpsec-threats-02: Path shortening & lengthening

Stephen Kent <kent@bbn.com> Tue, 10 April 2012 02:23 UTC

Return-Path: <kent@bbn.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 CC5BD11E8074 for <sidr@ietfa.amsl.com>; Mon, 9 Apr 2012 19:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.54
X-Spam-Level:
X-Spam-Status: No, score=-106.54 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 dqVbiqMzGaLw for <sidr@ietfa.amsl.com>; Mon, 9 Apr 2012 19:23:07 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 312E021F8752 for <sidr@ietf.org>; Mon, 9 Apr 2012 19:23:07 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:46358 helo=[172.31.27.154]) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1SHQj9-0009cX-8a; Mon, 09 Apr 2012 22:22:40 -0400
Mime-Version: 1.0
Message-Id: <p06240807cba945654510@[172.31.27.154]>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21391B3EBFDFD9@EUSAACMS0701.eamcs.ericsson.se >
References: <64B29EFD-5C6E-4D0C-8E4F-92A2B5A86279@castlepoint.net> <p06240803cb99d283e548@[10.108.69.44]> <8D2985D4-07C3-42EE-A694-DAF24D34F84A@castlepoint.net> <7309FCBCAE981B43ABBE69B31C8D21391B3EBFDFD9@EUSAACMS0701.eamcs.ericsson.se >
Date: Mon, 9 Apr 2012 22:12:56 -0400
To: Jakob Heitz <jakob.heitz@ericsson.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: multipart/alternative; boundary="============_-878097901==_ma============"
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] draft-ietf-sidr-bgpsec-threats-02: Path shortening & lengthening
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, 10 Apr 2012 02:23:07 -0000

At 9:46 AM -0400 3/29/12, Jakob Heitz wrote:
>Let's just require that BGPSEC capable routers
>also support 4 byte AS. Then we don't need to worry
>about AS4_PTH.
>
>--
>Jakob Heitz.

This is already a requirement. See the BGPSEC protocol spec, page 4:

  By indicating support for receiving BGPSEC update messages, a BGP 
speaker is, in particular, indicating that the following are true:

    o  The BGP speaker understands the BGPSEC_Path_Signatures 
attribute (see Section 3).

    o  The BGP speaker supports 4-byte AS numbers (see RFC 4893).