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

[Jeffrey Haas <[e-mail]>]

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