3 namespace "urn:opendaylight:params:xml:ns:yang:bgp-rib";
6 import bgp-message { prefix bgp-msg; revision-date 2013-09-19; }
7 import bgp-multiprotocol { prefix bgp-mp; revision-date 2013-09-19; }
8 import ietf-inet-types { prefix inet; revision-date 2010-09-24; }
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 "2013-09-25" {
34 typedef application-rib-id {
40 "An abstract peer identifier. The protocol part identifies
41 the type of the peer. One well-known protocol is define, which
42 has the following format: bgp://1.2.3.4, where 1.2.3.4 is the
43 peer's BGP Identifier in IPv4 dotted-quad format.";
56 uses bgp-msg:path-attributes;
61 uses bgp-mp:bgp-table-type;
64 container attributes {
77 list application-rib {
81 type application-rib-id;
106 list supported-tables {
108 uses bgp-mp:bgp-table-type;
110 container adj-rib-in {
111 description "Routes as we have received them from the peer.";
114 container effective-rib-in {
115 description "Routes as processed by inbound policy.";
118 container adj-rib-out {