Subject: Re: [OPSAWG] draft-ietf-opsawg-l3sm-l3nm

From: Qin Wu <[email-masked]>
Date: Thu, 7 Nov 2019 13:40:48 +0000

2.Allow several BGP sessions under the same Network Access.
To support several Routing Protocols sessions under the same Network Access we have changed the Key to have an ID to allow several protocols under the same Network Access:

           |     |        +--rw routing-protocol* [id]

           |     |           +--rw id                  string

           |     |           +--rw type?               identityref

           |     |           +--rw routing-profiles* [id]

           |     |           |  +--rw id      -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id

           |     |           |  +--rw type?   ie-type

           |     |           +--rw ospf {rtg-ospf}?

           |     |           |  +--rw address-family*   address-family

           |     |           |  +--rw area-address      yang:dotted-quad

           |     |           |  +--rw metric?           uint16

           |     |           |  +--rw mtu?              uint16

           |     |           |  +--rw security

           |     |           |  |  +--rw auth-key?   string

           |     |           |  +--rw sham-links {rtg-ospf-sham-link}?

           |     |           |     +--rw sham-link* [target-site]

           |     |           |        +--rw target-site    svc-id

           |     |           |        +--rw metric?        uint16

           |     |           +--rw bgp {rtg-bgp}?

           |     |           |  +--rw autonomous-system    uint32

           |     |           |  +--rw address-family*      address-family

           |     |           |  +--rw neighbor?            inet:ip-address

           |     |           |  +--rw multihop?            uint8

           |     |           |  +--rw security

           |     |           |     +--rw auth-key?   string

           |     |           +--rw static

           |     |           |  +--rw cascaded-lan-prefixes

           |     |           |     +--rw ipv4-lan-prefixes* [lan next-hop] {ipv4}?

           |     |           |     |  +--rw lan         inet:ipv4-prefix

           |     |           |     |  +--rw lan-tag?    string

           |     |           |     |  +--rw next-hop    inet:ipv4-address

           |     |           |     +--rw ipv6-lan-prefixes* [lan next-hop] {ipv6}?

           |     |           |        +--rw lan         inet:ipv6-prefix

           |     |           |        +--rw lan-tag?    string

           |     |           |        +--rw next-hop    inet:ipv6-address

           |     |           +--rw rip {rtg-rip}?

           |     |           |  +--rw address-family*   address-family

           |     |           +--rw vrrp {rtg-vrrp}?

           |     |              +--rw address-family*   address-family

[Qin]: I think type under routing-protocol should add a new identity for routing-profiles category
identity routing-profile {
  base routing-protocol-type;
  description
  "Identity for routing profile type.";
}