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

["Wanghaibo (Rainsword)" <[e-mail]>]

Hi Jeff,
 
 Thanks for your reply. 

 I have read this example. But it doesn't solve my doubts. 
 If I have two public bgp instance like this:
    "ietf-routing:routing": {
       "router-id": "192.0.2.1",
       "control-plane-protocols": {
         "control-plane-protocol": [
           {
             "type": "ietf-routing:bgp",
             "name": "bgp0",
             "description": 
               "Bgp for CustomerA.",
             "bgp": {
			 "neighbors":{
			  "neighbor":[
			    {
				 "remote-address":"192.0.2.1",
                   "peer-as":"64497"
	               "afi-safis":{
                     "afi-safi":[
                       "afi-safi-name":"bt:l3vpn-ipv4-unicast"
                      ]
                    }
			    }	
			   ]
		      }
              }
           }
		 ]
         "control-plane-protocol": [
           {
             "type": "ietf-routing:bgp",
             "name": "bgp1",
             "description":
               "Static routing is used for the internal network.",
             "bgp": {
			 "neighbors":{
			  "neighbor":[
			    {
				 "remote-address":"192.0.3.1",
                   "peer-as":"64497"
	               "afi-safis":{
                     "afi-safi":[
                       "afi-safi-name":"bt:l2vpn-evpn"
                      ]
                    }
			    }	
			   ]
		      }
              } 
            }
         ]
       },
   
 And I have two vrf instance like :
    "ietf-network-instance:network-instances": {
      "network-instance": [
        {
          "name": "vrf-old",
           ...
        }
       ]
      }
    "ietf-network-instance:network-instances": {
      "network-instance": [
        {
          "name": "vrf-new",
           ...
        }
       ]
      }

  I want to specify the vrf-old use bgp0 to advertise routes using l3vpn-ipv4-unicast, and use bgp1 for vrf-new to advertise routes using l2vpn-evpn with type5.
  So how can I do this ?

Regards,
Haibo

-----Original Message-----
From: Jeffrey Haas [mailto:[e-mail]] 
Sent: Tuesday, August 27, 2019 4:39 AM
To: Wanghaibo (Rainsword) <[e-mail]>
Cc: [e-mail]; [e-mail]
Subject: Re: [Idr] draft-ietf-idr-bgp-model

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