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

Linda Dunbar <linda.dunbar@futurewei.com> Thu, 15 August 2019 23:40 UTC

Return-Path: <linda.dunbar@futurewei.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 68BE01200F3; Thu, 15 Aug 2019 16:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 4AyOMkdMrO3J; Thu, 15 Aug 2019 16:40:49 -0700 (PDT)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680098.outbound.protection.outlook.com [40.107.68.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B53C21200E9; Thu, 15 Aug 2019 16:40:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IJfcriPy6Y01dPKLhOLDi+3eeLIkB2Mpkc7s4kUpzzqPTCRNPYjUlQpNLX/wnUClo+GPyS2PCQAxscysyN+NFw4RpPNP9M9NhBn0giFCsJxfxMdq2GsqAPIEvDUrnh+rrB4MFZXaPpVBicCb7O4J2lyaUcFtDzqehhlXErS2Qrt5959Ii75qairbz5D/86WGVB5KFEmB47pHFDp+BseQuWtzMcfqhecq5c5VD5QxxRMWS9vqjrHjIi56HEDP4Yybo5xv3AuKesnGxP3CwJ/7YcfKd9tOVzYxyk5rnqKkuZi9rXvjoRsPFDk841wBNPN9Vexz34iZevpnUQSGbyL40w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wxVeXl2wLpKBa95JncrHnEA6kfEHsVs8tGejf+eNwC0=; b=ZPkEkQOdavA1xlniyFGj4kAnLk4AmqU8RNenujBHJxl29okzqYGp4opsuJB/aa3/Zo7GNwdjb/Ks85VjFAsVhjkZkbt57LX47tuIMYQ+c9hWjQnoia/X2Qh3lz0yaEzOhjevvZ1JXAkzTh0xzQKO1B6i4UzWr9BHDNLgMzrGTw0XOED0VQIiY4fDPsz7LeU2gCS0/+jboF7GKyR1nZa+F4qRAXIhta05oW7sQGdf5FmX5t8kyhkfcFsZ5Mxy4MJuzNWhX9RJSvl597nMs8orTkXT53aStwg/SH19oSc4mdteIi4Bbm18kkZW8RcDnueZsg+F8D21e1hifVnYSVSfIw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wxVeXl2wLpKBa95JncrHnEA6kfEHsVs8tGejf+eNwC0=; b=Jl0TSlaIGR68bI/7BuMPTr9tjcgx6EercfPZLrcZE1NVlAAFUm4NGkvQG2dYFfyVGFtN2hgffTgPQophFVn2OyCBiv+fM2GATaspyMB6xIPoTxGsat49Roy6x6NkZ6PhTAU+OFjtvyiNJtSdOj75FLgFplHj5rkrOHB7IaNW27k=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.238.139) by MN2PR13MB2735.namprd13.prod.outlook.com (20.178.252.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.14; Thu, 15 Aug 2019 23:40:46 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::51ed:57ae:d3a7:e4bd]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::51ed:57ae:d3a7:e4bd%7]) with mapi id 15.20.2178.016; Thu, 15 Aug 2019 23:40:46 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>, "draft-ietf-idr-bgp-model@ietf.org" <draft-ietf-idr-bgp-model@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] draft-ietf-idr-bgp-model
Thread-Index: AdVTYqP7HEGobTyKRLSJ6VQT3MRf2gAYBovQ
Date: Thu, 15 Aug 2019 23:40:46 +0000
Message-ID: <MN2PR13MB3582C3C7ACB93D4E610B068C85AC0@MN2PR13MB3582.namprd13.prod.outlook.com>
References: <1E61161D6E31D849BEA887261DB609348C8F2E20@nkgeml514-mbx.china.huawei.com>
In-Reply-To: <1E61161D6E31D849BEA887261DB609348C8F2E20@nkgeml514-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 92b68504-94f4-4b71-2b07-08d721d9ff03
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB2735;
x-ms-traffictypediagnostic: MN2PR13MB2735:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR13MB273530FAE02A5B21C652A9D285AC0@MN2PR13MB2735.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6108;
x-forefront-prvs: 01304918F3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(396003)(376002)(136003)(39840400004)(366004)(189003)(199004)(44832011)(478600001)(76116006)(99286004)(53546011)(33656002)(476003)(53936002)(11346002)(446003)(76176011)(8936002)(110136005)(102836004)(6246003)(6506007)(7696005)(186003)(316002)(486006)(2501003)(26005)(14454004)(2906002)(66446008)(8676002)(6436002)(25786009)(229853002)(81166006)(66556008)(86362001)(4326008)(7736002)(55016002)(66476007)(66066001)(9686003)(52536014)(54896002)(64756008)(790700001)(66946007)(5660300002)(3846002)(6116002)(256004)(6306002)(71200400001)(81156014)(71190400001)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB2735; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 4/REeyyosNJX0koEh96MKWpF3lwgrdou8ypdRW7rKbom2k/ySXjT9RdHy5oFSrz+kkGctHfMCDT1ucFOKTWWDK4ygzWuI45LzBtFhG0yAGwtPSmRCH+owarJfqSxEXzi5XkMOX4Ugob+Kvw0rRgWjVqiiw8Tbv9Iohk8V561BYF/KlfBvV1BpPpGPg2YzpWUUjk2LHqBbR+sT6ZIWw992G7lxWrQBndTS+9qg8pRpu4+YBTQqzNZUZFio43JWbY5vFelPq14O8PSozVCgBvzVJ6qyShZ2Zg3bF8xayPDyHSSeRKsWK+hNB3G9oZg94+NQFoUkBbn8/sBfrZlunBJAHJtkJ5h4JR80olvojWb6lVRC6oSO+wbOqnkRphKUuo1XQUkz+88l1Wvw3nDQ0CLzaZUle1hFCTF2kHaM7PKmVc=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3582C3C7ACB93D4E610B068C85AC0MN2PR13MB3582namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 92b68504-94f4-4b71-2b07-08d721d9ff03
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Aug 2019 23:40:46.4992 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: h1rPoobkpAgVPmRWCMo1QZxjRdzumMAmm4tXWDmZ+WdhN+l4AnYzuY1y7UOQ+U0af9fCEDLfl/H0ZF+fwMJXTw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2735
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jZnlkvRgfEl0mFduiF2jG1aoUO8>
Subject: Re: [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 23:40:52 -0000

Disclaimer:  I am not the author for this draft.

The document does say:
Additional modules or submodules to handle other aspects of BGP configuration,
including policy, VRFs, VPNs, and additional address families are also expected

Does it mean that VRF VPN1 for AS 100 and VRF VPN2 for AS200 can't yet be specified until the respective YANG Model document is specified?

I would think the following can be used to "realize the multiple BGP public instances" (missing the VPN part) as you requested?

<global>
   <as>100</as>
     <neighbor>
       <remote-address>2.2.2.2</remote-address>
       <afi-safis>
         <afi-safi>
           <afi-safi-name
            xmlns:bt="urn:ietf:params:xml:ns:yang:ietf-bgp-types">bt:l3vpn-ipv4-unicast
           </afi-safi-name>
        </afi-safi>
       </afi-safis>
    <neighbor>


  <as>200</as>
     <neighbor>
       <remote-address>3.3.3.3</remote-address>
       <afi-safis>
         <afi-safi>
           <afi-safi-name
            xmlns:bt="urn:ietf:params:xml:ns:yang:ietf-bgp-types">bt:l3vpn-ipv4-unicast
           </afi-safi-name>
        </afi-safi>
       </afi-safis>
    <neighbor>

</global>

Linda Dunbar


From: Idr <idr-bounces@ietf.org>; On Behalf Of Wanghaibo (Rainsword)
Sent: Thursday, August 15, 2019 7:32 AM
To: draft-ietf-idr-bgp-model@ietf.org
Cc: idr@ietf.org
Subject: [Idr] draft-ietf-idr-bgp-model

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