IETF Logo Mail Archive

Re: [Dcrouting] A comment on draft-keyupate-idr-bgp-spf

"Acee Lindem (acee)" <acee@cisco.com> Tue, 02 January 2018 17:29 UTC

Return-Path: <acee@cisco.com>
X-Original-To: dcrouting@ietfa.amsl.com
Delivered-To: dcrouting@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 620E1128C0A; Tue, 2 Jan 2018 09:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RE5nJXmzBZrE; Tue, 2 Jan 2018 09:29:10 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73425124E15; Tue, 2 Jan 2018 09:29:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7257; q=dns/txt; s=iport; t=1514914150; x=1516123750; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=0yg8GD1xJi2/HEQ5PRrc/BYBMvynh3KQMjpocBOvZ7A=; b=SfE+xgVUQGNmi5E+y+5jf6ZlSuIU5AnhSaxvoZyxcplVnehrU+pTy/nE alnI8AuAj6Ky/PdZAdCB79CKE028w1O7n20vkFxv6PPFt4Dh+fMKEzUnl tBXdARRKFIrYNqduFpeOlK+DX1CgRfjM3IhIMCZeIckpyXRi7zIIRGbIR 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DeAgD0v0ta/4gNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYJKdIFaJweEAJk+ggGJCIhRh2YKhTsCGoQWQhUBAQEBAQEBAQFrKIUjAQEBAQMjVhACAQgOAwMBAg0bAwICAh8RFAkIAQEEAQ0FiUpMAxWyB4InhzkNgnABAQEBAQEBAQEBAQEBAQEBAQEBAQEdhAyCEoZtgmtFgg6Cd4JlBZlhiS49ApA1hH6CF4YWi1CNYoh0AhEZAYE7ATUjgU9vFT2CKYRXeId8gRYBAQE
X-IronPort-AV: E=Sophos;i="5.45,498,1508803200"; d="scan'208,217";a="338436139"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2018 17:29:09 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w02HT8Fu013281 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Jan 2018 17:29:09 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 2 Jan 2018 12:29:08 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Tue, 2 Jan 2018 12:29:08 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, Xuxiaohu <xuxiaohu@huawei.com>, "dcrouting@ietf.org" <dcrouting@ietf.org>
CC: "lsvr@ietf.org" <lsvr@ietf.org>
Thread-Topic: [Dcrouting] A comment on draft-keyupate-idr-bgp-spf
Thread-Index: AdN6/qalrWTMjyrZR1yUr/rOo79ZxwAW0IKAAiVQMgA=
Date: Tue, 02 Jan 2018 17:29:08 +0000
Message-ID: <D6712B2D.E8033%acee@cisco.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE304A7141@NKGEML515-MBS.china.huawei.com> <CAMMESsw65Ock+AYPCmJWT49da-o6eF=X=_d=T8RoSEACU76Mrw@mail.gmail.com>
In-Reply-To: <CAMMESsw65Ock+AYPCmJWT49da-o6eF=X=_d=T8RoSEACU76Mrw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_D6712B2DE8033aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/pH5yUgsB-n2IC76NqFjk-j8j01w>
Subject: Re: [Dcrouting] A comment on draft-keyupate-idr-bgp-spf
X-BeenThere: dcrouting@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Routing in the Data Center: discussions about problems, requirements and potential solutions." <dcrouting.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrouting>, <mailto:dcrouting-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrouting/>
List-Post: <mailto:dcrouting@ietf.org>
List-Help: <mailto:dcrouting-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrouting>, <mailto:dcrouting-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 17:29:12 -0000

Used as an underlay, BGP SPF just works. What needs to be defined are the rules when the same prefix is advertised in both address families.
Thanks,
Acee

From: Dcrouting <dcrouting-bounces@ietf.org<mailto:dcrouting-bounces@ietf.org>> on behalf of Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>>
Date: Friday, December 22, 2017 at 9:20 AM
To: Xiaohu Xu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>, "dcrouting@ietf.org<mailto:dcrouting@ietf.org>" <dcrouting@ietf.org<mailto:dcrouting@ietf.org>>
Cc: "lsvr@ietf.org<mailto:lsvr@ietf.org>" <lsvr@ietf.org<mailto:lsvr@ietf.org>>
Subject: Re: [Dcrouting] A comment on draft-keyupate-idr-bgp-spf

On December 22, 2017 at 3:27:24 AM, Xuxiaohu (xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>) wrote:

Xiaohu:

Hi!

I wonder whether it's worthwhile to consider the coexistence of the traditional BGP-DV protocol and the BGP-SPF protocol on a given node. If so...

Yes, I think so.

That (coexistence with/separation from traditional BGP) is one of the pieces that I expect to see in a forthcoming proposed charter for lsvr — please subscribe to that list (cc’d here) and contribute your comments and ideas there. :-)

Thanks!!

Alvaro.

v2.23.0 | Report a Bug | By Email