Re: [sidr] bgpsec-spec S. 4.2 comments
"Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov> Wed, 02 May 2012 15:43 UTC
Return-Path: <kotikalapudi.sriram@nist.gov>
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 09CE521F85B6 for <sidr@ietfa.amsl.com>; Wed, 2 May 2012 08:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level:
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038, 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 9GzUe6BFxzI6 for <sidr@ietfa.amsl.com>; Wed, 2 May 2012 08:43:15 -0700 (PDT)
Received: from wsget1.nist.gov (wsget1.nist.gov [129.6.13.150]) by ietfa.amsl.com (Postfix) with ESMTP id 17F1221F85AE for <sidr@ietf.org>; Wed, 2 May 2012 08:43:14 -0700 (PDT)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 2 May 2012 11:43:08 -0400
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Wed, 2 May 2012 11:42:48 -0400
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Date: Wed, 02 May 2012 11:43:11 -0400
Thread-Topic: [sidr] bgpsec-spec S. 4.2 comments
Thread-Index: Ac0odRsrcoeHB3mOQ+e9bOwx5Ui5gwAAFKBw
Message-ID: <D7A0423E5E193F40BE6E94126930C4930B98F8632E@MBCLUSTER.xchange.nist.gov>
References: <D7A0423E5E193F40BE6E94126930C4930B98F86215@MBCLUSTER.xchange.nist.gov> <01068404-27B5-42B6-B1BF-9F1CABA8B3AA@ericsson.com>
In-Reply-To: <01068404-27B5-42B6-B1BF-9F1CABA8B3AA@ericsson.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"
MIME-Version: 1.0
Cc: "John Scudder (jgs@juniper.net)" <jgs@juniper.net>, "sidr wg list (sidr@ietf.org)" <sidr@ietf.org>
Subject: Re: [sidr] bgpsec-spec S. 4.2 comments
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, 02 May 2012 15:43:17 -0000
>that's also flawed. >You should be able to sign anything that you can. > >Suppose you receive it from an ibgp peer that sourced it but didn't sign it. > >-- >Jakob Heitz. > What a BGPSEC router does when "originating" a new BGPSEC update is covered in Section 4.1. You are right -- the router can receive a prefix route (without an AS path) from an ibgp peer who sourced it, and the method of signing that (or any prefix being originated) is in Section 4.1. The discussion here (and John's comment) is related to text in Section 4.2, where we discuss what a BGPSEC router does when "propagating" a route advertisement. "Propagating" connotes here that the update (or route) was received from an eBGP peer. Sriram
- [sidr] bgpsec-spec S. 4.2 comments Sriram, Kotikalapudi
- Re: [sidr] bgpsec-spec S. 4.2 comments Jakob Heitz
- Re: [sidr] bgpsec-spec S. 4.2 comments Sriram, Kotikalapudi
- Re: [sidr] bgpsec-spec S. 4.2 comments Randy Bush