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

Jeffrey Haas <jhaas@pfrc.org> Mon, 26 August 2019 20:36 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 5152E120838; Mon, 26 Aug 2019 13:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hRNSkoK3msxR; Mon, 26 Aug 2019 13:36:26 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 527E112004D; Mon, 26 Aug 2019 13:36:26 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 946831E2F6; Mon, 26 Aug 2019 16:38:50 -0400 (EDT)
Date: Mon, 26 Aug 2019 16:38:50 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
Cc: "draft-ietf-idr-bgp-model@ietf.org" <draft-ietf-idr-bgp-model@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <20190826203850.GH24671@pfrc.org>
References: <1E61161D6E31D849BEA887261DB609348C8F2E20@nkgeml514-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1E61161D6E31D849BEA887261DB609348C8F2E20@nkgeml514-mbx.china.huawei.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7SUlaFmoti5eg9Msvhriv3tNFMg>
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: Mon, 26 Aug 2019 20:36:28 -0000

On Thu, Aug 15, 2019 at 12:32:01PM +0000, Wanghaibo (Rainsword) wrote:
> 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

The bgp model uses NMDA:
  augment "/rt:routing/rt:control-plane-protocols/"
        + "rt:control-plane-protocol" {

You may find this example from RFC 8349 helpful:

https://tools.ietf.org/html/rfc8349

: Appendix D.  Data Tree Example
: [...]
: 
: 
:      "ietf-routing:routing": {
:        "router-id": "192.0.2.1",
:        "control-plane-protocols": {
:          "control-plane-protocol": [
:            {
:              "type": "ietf-routing:static",
:              "name": "st0",
:              "description":
:                "Static routing is used for the internal network.",
:  

The definition of control plane protocols permits multi-instancing via name:

:        container control-plane-protocols {
:          description
:            "Support for control-plane protocol instances.";
:          list control-plane-protocol {
:            key "type name";
:            description

-- Jeff