3 namespace "urn:opendaylight:params:xml:ns:yang:bgp-rib";
6 import bgp-message { prefix bgp-msg; revision-date 2020-01-20; }
7 import bgp-multiprotocol { prefix bgp-mp; revision-date 2018-03-29; }
8 import ietf-inet-types { prefix inet; revision-date 2013-07-15; }
10 organization "Cisco Systems, Inc.";
11 contact "Robert Varga <rovarga@cisco.com>";
14 "This module contains the concept of a Routing Information Base,
15 as defined by RFC4271.
17 Copyright (c)2013 Cisco Systems, Inc. All rights reserved.
19 This program and the accompanying materials are made available
20 under the terms of the Eclipse Public License v1.0 which
21 accompanies this distribution, and is available at
22 http://www.eclipse.org/legal/epl-v10.html";
24 revision "2018-03-29" {
25 description "Add support for add-path for all afi/safi.";
28 revision "2017-12-07" {
29 description "Add support for add-path in base BGP NLRI.";
32 revision "2013-09-25" {
42 typedef application-rib-id {
48 "An abstract peer identifier. The protocol part identifies
49 the type of the peer. One well-known protocol is define, which
50 has the following format: bgp://1.2.3.4, where 1.2.3.4 is the
51 peer's BGP Identifier in IPv4 dotted-quad format.";
65 uses bgp-msg:path-id-grouping;
68 "The sole function of this leaf
69 to act as the key in the list.
70 Its format does not form the
71 API contract of this model.";
74 uses bgp-msg:path-attributes;
79 uses bgp-mp:bgp-table-type;
82 container attributes {
95 list application-rib {
99 type application-rib-id;
124 list supported-tables {
126 uses bgp-mp:bgp-add-path-table-type;
128 container adj-rib-in {
129 description "Routes as we have received them from the peer.";
131 augment tables/attributes {
134 description "Presence indicates that all routes in this table
135 are to be treated as having LLGR_STALE community
141 container effective-rib-in {
142 description "Routes as processed by inbound policy.";
145 container adj-rib-out {