IETF Logo Mail Archive

[Idr] draft-ietf-idr-bgp-model

"Wanghaibo (Rainsword)" <rainsword.wang@huawei.com> Thu, 15 August 2019 12:32 UTC

Return-Path: <rainsword.wang@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 044ED120046; Thu, 15 Aug 2019 05:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.093
X-Spam-Level:
X-Spam-Status: No, score=-3.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 VfT2iB6s9j8N; Thu, 15 Aug 2019 05:32:16 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D10DE120043; Thu, 15 Aug 2019 05:32:15 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 88A425CEA87230CD3B85; Thu, 15 Aug 2019 13:32:13 +0100 (IST)
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 15 Aug 2019 13:32:13 +0100
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 15 Aug 2019 13:32:13 +0100
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Thu, 15 Aug 2019 13:32:12 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Thu, 15 Aug 2019 20:32:02 +0800
From: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
To: "draft-ietf-idr-bgp-model@ietf.org" <draft-ietf-idr-bgp-model@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-ietf-idr-bgp-model
Thread-Index: AdVTYqP7HEGobTyKRLSJ6VQT3MRf2g==
Date: Thu, 15 Aug 2019 12:32:01 +0000
Message-ID: <1E61161D6E31D849BEA887261DB609348C8F2E20@nkgeml514-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.185]
Content-Type: multipart/alternative; boundary="_000_1E61161D6E31D849BEA887261DB609348C8F2E20nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TkxJm8RHJ7jm-bfPcO7L-qDavH4>
Subject: [Idr] draft-ietf-idr-bgp-model
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 12:32:18 -0000

Hi authors,

I have some question about the bgp model.

In current model, the bgp module will augment to routing,
     /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol:
And the routing will schema mount to network-instance.

In this model, how to realize the multiple bgp public instance, like that

bgp instance 1 as-number 100
  neighbor 2.2.2.2
address-family vpn-ipv4
  vrf vpn1
neighbor 11.1.1.1
  address-family ipv4

bgp instance 2 as-number 200
  neighbor 3.3.3.3
address-family vpn-ipv4
  vrf vpn2
neighbor 12.1.1.1
  address-family ipv4

Bgp doesn't like ospf or isis, the vrf's bgp will associate to public bgp's special address family.
I'm not find how to describe the associate in current model

Best regards,
Haibo

v2.23.0 | Report a Bug | By Email