draft-shaikh-idr-bgp-model-01.txt   draft-shaikh-idr-bgp-model-02.txt 
Interdomain Routing A. Shaikh Interdomain Routing A. Shaikh, Ed.
Internet-Draft Google Internet-Draft Google
Intended status: Informational K. D'Souza Intended status: Informational R. Shakir, Ed.
Expires: September 10, 2015 AT&T Expires: December 16, 2015 BT
K. Patel, Ed.
Cisco
S. Hares, Ed.
Huawei
K. D'Souza
AT&T
D. Bansal D. Bansal
Microsoft Microsoft
R. Shakir A. Clemm
BT A. Zhdankin
March 9, 2015 Cisco
M. Jethanandani
Ciena
X. Liu
Ericsson
June 14, 2015
BGP Model for Service Provider Networks BGP Model for Service Provider Networks
draft-shaikh-idr-bgp-model-01 draft-shaikh-idr-bgp-model-02
Abstract Abstract
This document defines a YANG data model for configuring and managing This document defines a YANG data model for configuring and managing
BGP, including protocol, policy, and operational aspects based on BGP, including protocol, policy, and operational aspects based on
carrier and content provider operational requirements. data center, carrier and content provider operational requirements.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 10, 2015. This Internet-Draft will expire on December 16, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
This document describes a YANG [RFC6020] data model for BGP [RFC4271] YANG [RFC6020] is a data modeling language that was introduced to
protocol and policy configuration, as well as defining key define the contents of a conceptual data store that allows networked
operational state data. The model is intended to be vendor-neutral, devices to be managed using NETCONF [RFC6241]. YANG is proving
in order to allow operators to manage BGP configuration in relevant beyond its initial confines, as bindings to other interfaces
heterogeneous environments with routers supplied by multiple vendors. (e.g. ReST) and encodings other than XML (e.g. JSON) are being
The model is also intended to be readily mapped to existing defined. Furthermore, YANG data models can be used as the basis of
implementations, however, to facilitate support from as large a set implementation for a number of interfaces, such as CLIs and
of routing hardware and software vendors as possible. programmatic APIs.
This document describes a YANG data model for the BGP [RFC4271]
protocol, including various protocol extensions, policy
configuration, as well as defining key operational state data. The
model is intended to be vendor-neutral, in order to allow operators
to manage BGP configuration in heterogeneous environments with
routers supplied by multiple vendors. The model is also intended to
be readily mapped to existing implementations to facilitate support
from as large a set of routing hardware and software vendors as
possible.
1.1. Goals and approach 1.1. Goals and approach
This model does not (in the current iteration) aim to be feature The model covers the base BGP features that are deployed across major
complete (i.e., cover all possible features of a BGP implementation). implementations and the common BGP configurations in use across a
Rather its development is driven by examination of BGP configurations number of operator network deployments. In particular, this model
in use across a number of operator network deployments. attempts to cover BGP features defined in [RFC4271], [RFC1997],
[RFC4456], [RFC4760], [RFC3065], [RFC2439], [RFC4724], and [RFC6811].
The focus area of the first version of the model is on base BGP Along with configuration of base BGP features, this model also
protocol configuration and policy configuration with "hooks" to add addresses policy configuration, by providing "hooks" for applying
support for additional address families, as well as operational data policies, and also defining BGP-specific policy features. The BGP
to enable a common model for reading BGP-related state from devices. policy features are intended to be used with the general routing
policy model defined in [I-D.shaikh-rtgwg-policy-model]. The model
also supports operational state data to enable a common model for
reading BGP-related state from a BGP speaker.
The focus of the the BGP model described in this document is on For the base BGP features, the focus of the model described in this
providing the base configuration and operational state information document is on providing configuration and operational state
relating to: information relating to:
o The global BGP instance, and neighbors whose configuration is o The global BGP instance, and neighbors whose configuration is
specified individually, or templated with the use of peer-groups. specified individually, or templated with the use of peer-groups.
o The address families that are supported by peers, and the global o The address families that are supported by peers, and the global
configuration which relates to them. configuration which relates to them.
o The policies that relate to a neighbor - controlling the import o The policy configuration "hooks" and BGP-specific policy features
and export of NLRI. that relate to a neighbor - controlling the import and export of
NLRIs.
Configuration items that are deemed to be widely available in As mentioned earlier, any configuration items that are deemed to be
existing major BGP implementations are included in the model. Those widely available in existing major BGP implementations are included
configuration items that are only available from a single in the model. Additional, more esoteric, configuration items that
implementation are omitted from the model with the expectation they are not commonly used, or only available from a single
will be available in companion modules that augment the current implementation, are omitted from the model with an expectation that
they will be available in companion modules that augment the current
model. This allows clarity in identifying data that is part of the model. This allows clarity in identifying data that is part of the
vendor-neutral model. vendor-neutral base model.
Where possible, naming in the model follows conventions used in Where possible, naming in the model follows conventions used in
available standards documents, and otherwise tries to be self- available standards documents, and otherwise tries to be self-
explanatory with sufficient descriptions of the intended behavior. explanatory with sufficient descriptions of the intended behavior.
Similarly, configuration data value constraints and default values, Similarly, configuration data value constraints and default values,
where used, are based on recommendations in current standards where used, are based on recommendations in current standards
documentation. Since implementations vary widely in this respect, documentation. Since implementations vary widely in this respect,
this version of the model specifies only a limited set of defaults this version of the model specifies only a limited set of defaults
and ranges with the expectation of being more prescriptive in future and ranges with the expectation of being more prescriptive in future
versions based on actual operator use. versions based on actual operator use.
2. Model overview 2. Model overview
The BGP model is defined across several YANG modules but at a high The BGP model is defined across several YANG modules but at a high
level is organized into four elements: level is organized into Six elements:
o base protocol configuration -- configuration affecting BGP o base protocol configuration -- configuration affecting BGP
protocol-related operations, defined at various levels of protocol-related operations, defined at various levels of
hierarchy. hierarchy.
o multiprotocol configuration -- configuration affecting individual o multiprotocol configuration -- configuration affecting individual
address-families within BGP [RFC4760]. address-families within BGP [RFC4760].
o policy configuration -- configuration defining the policies that o neighbor configuration -- configuration affecting an individual
act on routes sent (received) to (from) peers or other routing neighbor within BGP.
protocols.
o neighbor multiprotocol configuration -- configuration affecting
individual address-families for a neighbor within BGP.
o policy configuration -- hooks for application of the policies
defined in [I-D.shaikh-rtgwg-policy-model] that act on routes sent
(received) to (from) peers or other routing protocols and BGP-
specific policy features.
o operational state -- variables used for monitoring, management, o operational state -- variables used for monitoring, management,
etc. of BGP operations. etc. of BGP operations.
These modules also make use of the standard Internet types, such as These modules also make use of standard Internet types, such as IP
IP addresses, autonomous system numbers, etc., defined in RFC 6991 addresses and prefixes, autonomous system numbers, etc., defined in
[RFC6991]. RFC 6991 [RFC6991].
Throughout the model, the approach described in Throughout the model, the approach described in
[I-D.openconfig-netmod-opstate] is used to represent configuration [I-D.openconfig-netmod-opstate] is used to represent configuration
(intended state), operational and derived state data. That is to (intended state), operational and derived state data. That is to
say, that each container holds a "config" and "state" sub-container - say, that each container holds a "config" and "state" sub-container -
with the config container being used for configurable parameters, and with the config container being used for configurable parameters, and
the state container container holding representing both the the state container container holding representing both the
operational state of configurable leaves, and derived counters and operational state of configurable leaves, and derived counters and
statistical information. statistical information.
skipping to change at page 4, line 18 skipping to change at page 4, line 52
+--rw neighbors +--rw neighbors
| +--rw neighbor* [neighbor-address] | +--rw neighbor* [neighbor-address]
| +-- (neighbor-configuration-options) | +-- (neighbor-configuration-options)
+--rw peer-groups +--rw peer-groups
+--rw peer-group* [peer-group-name] +--rw peer-group* [peer-group-name]
+-- (neighbor-configuration-options) +-- (neighbor-configuration-options)
Users may specify configuration at a higher level and have it apply Users may specify configuration at a higher level and have it apply
to all lower-level items, or provide overriding configuration at a to all lower-level items, or provide overriding configuration at a
lower level of the hierarchy. Overriding configuration items are lower level of the hierarchy. Overriding configuration items are
optional with per-neighbor configuration being the most specific or optional, with neighbor specific configuration being the most
lowest level, followed by peer-group, and finally global. Global specific or lowest level, followed by peer-group, and finally global.
configuration options reflect a subset of the per-peer-group or per- Global configuration options reflect a subset of the peer-group or
neighbor configuration options which are relevant to the entire BGP neighbor specific configuration options which are relevant to the
instance. entire BGP instance.
The model makes the simplifying assumption that most of the The model makes the simplifying assumption that most of the
configuration items are available at all levels of the hierarchy. configuration items are available at all levels of the hierarchy.
That is, very little configuration is specific to a particular level That is, very little configuration is specific to a particular level
in the hierarchy, other than obvious items such as "group- name" only in the hierarchy, other than obvious items such as "group-name" only
being available for the peer group-level config. A notable exception being available for the peer group-level config. A notable exception
is for sub-address family configuration where some items are only is for sub-address family configuration where some items are only
applicable for a given AFI-SAFI combination. applicable for a given AFI-SAFI combination.
In order to allow common configuration to be applied to a set of In order to allow common configuration to be applied to a set of
neighbors, all neighbor configuration options are available within a neighbors, all neighbor configuration options are available within a
peer-group. A neighbor is associated to a particular peer-group peer-group. A neighbor is associated to a particular peer-group
through the use of a peer-group leaf (which provides a reference to a through the use of a peer-group leaf (which provides a reference to a
configured item in the peer-group list). configured item in the peer-group list).
Address-family configuration is made available in multiple points Address-family configuration is made available in multiple points
within the model - primarily within the global container, where within the model - primarily within the global container, where
instance-wide configuration can be set (for example, the BGP bestpath instance-wide configuration can be set (for example, global protocol
route selection options, or global policies relating to the address- parameters, the BGP best path route selection options, or global
family); and on a per-neighbor or per-peer-group basis, where policies relating to the address-family); and on a per-neighbor or
address-families can be enabled or disabled, and policy associated per-peer-group basis, where address-families can be enabled or
with the parent entity applied. Within the afi-safi container, disabled, and policy associated with the parent entity applied.
generic configuration that applies to all address-families (e.g., Within the afi-safi container, generic configuration that applies to
whether the AFI-SAFI is enabled) is presented at the top-level, with all address-families (e.g., whether the AFI-SAFI is enabled) is
address-family specific containers made available for options presented at the top-level, with address-family specific containers
relating to only that AFI-SAFI. Within the current revision of the made available for options relating to only that AFI-SAFI. Within
model a generic set of address-families, and common configuration and the current revision of the model a generic set of address-families,
state options included - further work is expected to add additional and common configuration and state options are included - further
parameters to this area of the model. work is expected to add additional parameters to this area of the
model.
The following address-families are currently supported by the model: The following address-families are currently supported by the model:
| +--rw afi-safi +--rw bgp!
| | +--rw afi-safi* [afi-safi-name] +--rw global
| | +--rw afi-safi-name identityref +--rw afi-safis
| | +--rw route-selection-options +--rw afi-safi* [afi-safi-name]
| | +--rw use-multiple-paths! +--rw afi-safi-name -> ../config/afi-safi-name
| | +--rw apply-policy |
| | +--rw ipv4-unicast! +--rw ipv4-unicast
| | +--rw ipv6-unicast! | ...
| | +--rw ipv4-labelled-unicast! +--rw ipv6-unicast
| | +--rw ipv6-labelled-unicast! | ...
| | +--rw l3vpn-ipv4-unicast! +--rw ipv4-labelled-unicast
| | +--rw l3vpn-ipv6-unicast! | ...
| | +--rw l3vpn-ipv4-multicast! +--rw ipv6-labelled-unicast
| | +--rw l3vpn-ipv6-multicast! | ...
| | +--rw l2vpn-vpls! +--rw l3vpn-ipv4-unicast
| | +--rw l2vpn-evpn! | ...
+--rw l3vpn-ipv6-unicast
| ...
+--rw l3vpn-ipv4-multicast
| ...
+--rw l3vpn-ipv6-multicast
| ...
+--rw l2vpn-vpls
| ...
+--rw l2vpn-evpn
| ...
2.2. Policy configuration overview 2.2. Policy configuration overview
The BGP policy configuration model references the generic YANG The BGP policy configuration model references the generic YANG
routing policy model described in [I-D.shaikh-rtgwg-policy-model]. routing policy model described in [I-D.shaikh-rtgwg-policy-model],
This model represents a condition-action policy framework. This which represents a condition-action policy framework for routing.
model adds BGP-specific conditions (e.g., matching on the community This model adds BGP-specific conditions (e.g., matching on the
attribute), and actions (e.g., setting local preference) to the community attribute), and actions (e.g., setting local preference) to
generic policy framework. the generic policy framework.
Policies that are defined in the routing-policy model are then Policies that are defined in the routing-policy model are referenced
referenced in multiple places within the model: in multiple places within the model:
o Within the global instance, where a policy applies to all address- o within the global instance, where a policy applies to all address-
families for all peers. families for all peers.
o On a global AFI-SAFI basis, where policies apply to all peers for o on a global AFI-SAFI basis, where policies apply to all peers for
a particular address-family. a particular address-family.
o On a per-peer-group or per-neighbor basis - where the policy o on a per-peer-group or per-neighbor basis - where the policy
applies to all address-families for the particular parent entity. applies to all address-families for the particular parent entity.
o On a per-afi-safi basis within a neighbor or peer-group context, o on a per-afi-safi basis within a neighbor or peer-group context,
where the policy is specific to the AFI-SAFI. where the policy is specific to the AFI-SAFI for a a specific
neighbor or group.
+--rw bgp +--rw bgp
+--rw global +--rw global
| +--rw afi-safi | +--rw afi-safi
| | +--rw afi-safi* [afi-safi-name] | | +--rw afi-safi* [afi-safi-name]
| | +--rw apply-policy | | +--rw apply-policy
| +--rw apply-policy | +--rw apply-policy
+--rw neighbors +--rw neighbors
| +--rw neighbor* [neighbor-address] | +--rw neighbor* [neighbor-address]
| +--rw afi-safi | +--rw afi-safi
skipping to change at page 6, line 29 skipping to change at page 7, line 33
+--rw afi-safi +--rw afi-safi
| +--rw afi-safi* [afi-safi-name] | +--rw afi-safi* [afi-safi-name]
| +--rw apply-policy | +--rw apply-policy
+--rw apply-policy +--rw apply-policy
2.3. Operational data overview 2.3. Operational data overview
The BGP operational model contains a set of parameters which relate The BGP operational model contains a set of parameters which relate
to the operational state of the various elements of the BGP router. to the operational state of the various elements of the BGP router.
As noted in Section 2 - the approach described in As noted in Section 2 - the approach described in
[I-D.openconfig-netmod-opstate] is utilised for the inclusion of [I-D.openconfig-netmod-opstate] is utilized for the inclusion of
operational and statistical data. To this end, the "_state" operational and statistical data. To this end, the "_state"
groupings (those that contain derived operational parameters) are groupings (those that contain derived operational parameters) are
contained within the BGP operational model - and included within the contained within the BGP operational model - and included within the
relevant "state" containers throughout the core BGP model. In some relevant "state" containers throughout the core BGP model. In some
cases, operational information may be relevant to one instance of a cases, operational information may be relevant to one instance of a
common grouping, but not another - for example, the number of common grouping, but not another - for example, the number of
received, advertised and installed prefixes is relevant on a per- received, advertised, and installed prefixes is relevant on a per-
neighbor-basis, but is not required (or meaningful) when within the neighbor-basis, but is not required (or meaningful) in the peer-group
peer-group context. To enable state to be added to particular context. To enable state to be added to particular contexts, the
contexts, the tree is augmented through the base BGP module to add tree is augmented through the base BGP module to add these variables,
these variables, without requiring separate groupings. without requiring separate groupings.
3. Security Considerations 3. Security Considerations
BGP configuration has a significant impact on network operations, and BGP configuration has a significant impact on network operations, and
as such any related protocol or model carries potential security as such any related protocol or model carries potential security
risks. risks.
YANG data models are generally designed to be used with the NETCONF YANG data models are generally designed to be used with the NETCONF
protocol over an SSH transport. This provides an authenticated and protocol over an SSH transport. This provides an authenticated and
secure channel over which to transfer BGP configuration and secure channel over which to transfer BGP configuration and
skipping to change at page 7, line 14 skipping to change at page 8, line 19
encoding (e.g., JSON over HTTPS) would require similar mechanisms for encoding (e.g., JSON over HTTPS) would require similar mechanisms for
authenticating and securing access to configuration data. authenticating and securing access to configuration data.
Most of the data elements in the configuration model could be Most of the data elements in the configuration model could be
considered sensitive from a security standpoint. Unauthorized access considered sensitive from a security standpoint. Unauthorized access
or invalid data could cause major disruption. or invalid data could cause major disruption.
4. IANA Considerations 4. IANA Considerations
This YANG data model and the component modules currently use a This YANG data model and the component modules currently use a
temporary ad-hoc namespace. If and when it is placed on redirected temporary ad-hoc namespace. If and when it is redirected for the
for the standards track, an appropriate namespace URI will be standards track, an appropriate namespace URI will be registered in
registered in the IETF XML Registry" [RFC3688]. The BGP YANG modules the IETF XML Registry" [RFC3688]. The BGP YANG modules will be
will be registered in the "YANG Module Names" registry [RFC6020]. registered in the "YANG Module Names" registry [RFC6020].
5. YANG modules 5. YANG modules
The modules comprising the BGP configuration and operational model The modules comprising the BGP configuration and operational model
are described by the YANG modules in the sections below. The base are described by the YANG modules in the sections below. The base
module imports the other modules to create the overall model. module imports the other modules to create the overall model.
5.1. BGP base items 5.1. BGP base items
<CODE BEGINS> file bgp.yang <CODE BEGINS> file bgp.yang
skipping to change at page 8, line 21 skipping to change at page 9, line 25
submodules to handle other aspects of BGP configuration, submodules to handle other aspects of BGP configuration,
including policy, VRFs, VPNs, and additional address families including policy, VRFs, VPNs, and additional address families
are also expected. are also expected.
This model supports the following BGP configuration level This model supports the following BGP configuration level
hierarchy: hierarchy:
BGP BGP
| |
+-> [ global BGP configuration ] +-> [ global BGP configuration ]
+-> AFI / SAFI global
+-> peer group +-> peer group
+-> [ peer group config ] +-> [ peer group config ]
+-> AFI / SAFI [ per-AFI overrides ] +-> AFI / SAFI [ per-AFI overrides ]
+-> neighbor +-> neighbor
+-> [ neighbor config ] +-> [ neighbor config ]
+-> [ optional pointer to peer-group ] +-> [ optional pointer to peer-group ]
+-> AFI / SAFI [ per-AFI overrides ]"; +-> AFI / SAFI [ per-AFI overrides ]";
revision "2014-03-05" { revision "2015-05-15" {
description description
""; "";
reference "TBD"; reference "TBD";
} }
grouping bgp-global_config { grouping bgp-global_config {
description description
"Global configuration options for the BGP router."; "Global configuration options for the BGP router.";
leaf as { leaf as {
skipping to change at page 9, line 34 skipping to change at page 10, line 40
BGP (iBGP)."; BGP (iBGP).";
} }
} }
grouping bgp-confederation_config { grouping bgp-confederation_config {
description description
"Configuration options specifying parameters when the local "Configuration options specifying parameters when the local
router is within an autonomous system which is part of a BGP router is within an autonomous system which is part of a BGP
confederation."; confederation.";
leaf enabled {
type boolean;
description
"When this leaf is set to true it indicates that
the local-AS is part of a BGP confederation";
}
leaf identifier { leaf identifier {
type inet:as-number; type inet:as-number;
description description
"Confederation identifier for the autonomous system."; "Confederation identifier for the autonomous system.";
} }
leaf-list member-as { leaf-list member-as {
type inet:as-number; type inet:as-number;
description description
"Remote autonomous systems that are to be treated "Remote autonomous systems that are to be treated
as part of the local confederation."; as part of the local confederation.";
} }
} }
grouping bgp-neighbor_config { grouping bgp-neighbor_config {
description description
skipping to change at page 10, line 7 skipping to change at page 11, line 18
as part of the local confederation."; as part of the local confederation.";
} }
} }
grouping bgp-neighbor_config { grouping bgp-neighbor_config {
description description
"Neighbor level configuration items."; "Neighbor level configuration items.";
leaf peer-as { leaf peer-as {
type inet:as-number; type inet:as-number;
mandatory "true";
description description
"AS number of the peer."; "AS number of the peer.";
} }
leaf local-as {
type inet:as-number;
description
"The local autonomous system number that is to be used
when establishing sessions with the remote peer or peer
group, if this differs from the global BGP router
autonomous system number.";
}
leaf peer-type { leaf peer-type {
type bgp-types:peer-type; type bgp-types:peer-type;
description description
"Explicitly designate the peer or peer group as internal "Explicitly designate the peer or peer group as internal
(iBGP) or external (eBGP)."; (iBGP) or external (eBGP).";
} }
leaf auth-password { leaf auth-password {
type string; type string;
description description
skipping to change at page 10, line 33 skipping to change at page 12, line 4
neighboring devices."; neighboring devices.";
} }
leaf remove-private-as { leaf remove-private-as {
// could also make this a container with a flag to enable // could also make this a container with a flag to enable
// remove-private and separate option. here, option implies // remove-private and separate option. here, option implies
// remove-private is enabled. // remove-private is enabled.
type bgp-types:remove-private-as-option; type bgp-types:remove-private-as-option;
description description
"Remove private AS numbers from updates sent to peers."; "Remove private AS numbers from updates sent to peers.";
} }
leaf route-flap-damping { leaf route-flap-damping {
type boolean; type boolean;
default false;
description description
"Enable route flap damping."; "Enable route flap damping.";
} }
leaf send-community { leaf send-community {
type bgp-types:community-type; type bgp-types:community-type;
default "NONE"; default "NONE";
description description
"Specify which types of community should be sent to the "Specify which types of community should be sent to the
neighbor or group. The default is to not send the neighbor or group. The default is to not send the
skipping to change at page 12, line 4 skipping to change at page 13, line 25
default 30; default 30;
description description
"Time interval in seconds between transmission of keepalive "Time interval in seconds between transmission of keepalive
messages to the neighbor. Typically set to 1/3 the messages to the neighbor. Typically set to 1/3 the
hold-time."; hold-time.";
} }
leaf minimum-advertisement-interval { leaf minimum-advertisement-interval {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
default 30; default 30;
description description
"Mininum time interval in seconds between transmission "Minimum time which must elapse between subsequent UPDATE
of BGP updates to neighbors"; messages relating to a common set of NLRI being transmitted
to a peer. This timer is referred to as
MinRouteAdvertisementIntervalTimer by RFC 4721 and serves to
reduce the number of UPDATE messages transmitted when a
particular set of NLRI exhibit instability.";
reference reference
"RFC 4271 - A Border Gateway Protocol 4, Sec 10"; "RFC 4271 - A Border Gateway Protocol 4, Sec 9.2.1.1";
}
leaf send-update-delay {
type decimal64 {
fraction-digits 2;
}
description
"Time interval between routes changing in the routing
table and corresponding updates sent to neighbors --
serves to batch updates";
} }
} }
grouping bgp-neighbor-transport_config { grouping bgp-neighbor-transport_config {
description description
"Configuration parameters relating to the transport protocol "Configuration parameters relating to the transport protocol
used by the BGP session to the peer"; used by the BGP session to the peer";
leaf tcp-mss { leaf tcp-mss {
type uint16; type uint16;
description description
"Sets the max segment size for BGP TCP sessions."; "Sets the max segment size for BGP TCP sessions.";
} }
leaf mtu-discovery { leaf mtu-discovery {
type boolean; type boolean;
default false;
description description
"Turns path mtu discovery for BGP TCP sessions on (true) "Turns path mtu discovery for BGP TCP sessions on (true)
or off (false)"; or off (false)";
} }
leaf passive-mode { leaf passive-mode {
type boolean; type boolean;
default false;
description description
"Wait for peers to issue requests to open a BGP session, "Wait for peers to issue requests to open a BGP session,
rather than initiating sessions from the local router."; rather than initiating sessions from the local router.";
} }
leaf local-address { leaf local-address {
type inet:ip-address; type union {
type inet:ip-address;
type string;
}
//TODO: the string should be converted to a leafref type
//to point to an interface when YANG 1.1 is available with
//leafrefs in union types.
description description
"Set the local IP (either IPv4 or IPv6) address to use "Set the local IP (either IPv4 or IPv6) address to use
for the session when sending BGP update messages."; for the session when sending BGP update messages. This
may be expressed as either an IP address or reference
to the name of an interface.";
} }
} }
grouping bgp-neighbor-error-handling_config { grouping bgp-neighbor-error-handling_config {
description description
"Configuration parameters relating to enhanced error handling "Configuration parameters relating to enhanced error handling
behaviours for BGP"; behaviours for BGP";
leaf treat-as-withdraw { leaf treat-as-withdraw {
type boolean; type boolean;
skipping to change at page 13, line 44 skipping to change at page 15, line 21
"Configure logging of peer state changes. Default is "Configure logging of peer state changes. Default is
to enable logging of peer state changes."; to enable logging of peer state changes.";
} }
} }
grouping bgp-neighbor-multihop_config { grouping bgp-neighbor-multihop_config {
description description
"Configuration parameters specifying the multihop behaviour for "Configuration parameters specifying the multihop behaviour for
BGP sessions to the peer"; BGP sessions to the peer";
leaf enabled {
type boolean;
default "false";
description
"When enabled the referenced group or neighbors are permitted
to be indirectly connected - including cases where the TTL
can be decremented between the BGP peers";
}
leaf multihop-ttl { leaf multihop-ttl {
type uint8; type uint8;
default 1;
description description
"Time-to-live for multihop BGP sessions. The default "Time-to-live value to use when packets are sent to the
value of 1 is for directly connected peers (i.e., referenced group or neighbors and ebgp-multihop is enabled";
multihop disabled";
} }
} }
grouping bgp-neighbor-route-reflector_config { grouping bgp-neighbor-route-reflector_config {
description description
"Configuration parameters determining whether the behaviour of "Configuration parameters determining whether the behaviour of
the local system when acting as a route-reflector"; the local system when acting as a route-reflector";
leaf route-reflector-cluster-id { leaf route-reflector-cluster-id {
type bgp-types:rr-cluster-id-type; type bgp-types:rr-cluster-id-type;
description description
skipping to change at page 14, line 35 skipping to change at page 16, line 18
"Configure the neighbor as a route reflector client."; "Configure the neighbor as a route reflector client.";
} }
} }
grouping bgp-neighbor-as-path-options_config { grouping bgp-neighbor-as-path-options_config {
description description
"Configuration parameters allowing manipulation of the AS_PATH "Configuration parameters allowing manipulation of the AS_PATH
attribute"; attribute";
leaf allow-own-as { leaf allow-own-as {
// rjs: this could be uint32, but ALU SROS treats as a type uint8;
// boolean. JUNOS, IOS & IOS XR treat as an integer default 0;
// specifying the number of occurrences.
type boolean;
default "false";
description description
"Specify whether routes for which the local router's AS "Specify the number of occurrences of the local BGP speaker's
appears in the path are rejected as looped."; AS that can occur within the AS_PATH before it is rejected.";
} }
leaf replace-peer-as { leaf replace-peer-as {
type boolean; type boolean;
default "false"; default "false";
description description
"Replace occurrences of the peer's AS in the AS_PATH "Replace occurrences of the peer's AS in the AS_PATH
with the local autonomous system number"; with the local autonomous system number";
} }
} }
skipping to change at page 15, line 4 skipping to change at page 16, line 33
} }
leaf replace-peer-as { leaf replace-peer-as {
type boolean; type boolean;
default "false"; default "false";
description description
"Replace occurrences of the peer's AS in the AS_PATH "Replace occurrences of the peer's AS in the AS_PATH
with the local autonomous system number"; with the local autonomous system number";
} }
} }
grouping bgp-neighbor-add-paths_config { grouping bgp-neighbor-add-paths_config {
description description
"Configuration parameters specfying whether the local system "Configuration parameters specfying whether the local system
will send or receive multiple paths using ADD_PATHS"; will send or receive multiple paths using ADD_PATHS";
leaf receive { leaf receive {
type empty; type boolean;
default false;
description description
"Enable ability to receive multiple path advertisements "Enable ability to receive multiple path advertisements
for an NLRI from the neighbor or group"; for an NLRI from the neighbor or group";
} }
leaf send-max { leaf send-max {
type uint8; type uint8;
description description
"The maximum number of paths to advertise to neighbors "The maximum number of paths to advertise to neighbors
for a single NLRI"; for a single NLRI";
skipping to change at page 15, line 41 skipping to change at page 17, line 25
type leafref { type leafref {
// we are at /bgp/neighbors/neighbor/ // we are at /bgp/neighbors/neighbor/
path "/bgp/peer-groups/peer-group/peer-group-name"; path "/bgp/peer-groups/peer-group/peer-group-name";
require-instance true; require-instance true;
} }
description description
"The peer-group with which this neighbor is associated"; "The peer-group with which this neighbor is associated";
} }
} }
grouping bgp-graceful-restart_config { grouping bgp-graceful-restart {
description description
"Configures BGP graceful restart, which is a negotiated "Configures BGP graceful restart, which is a negotiated
option that indicates that a BGP speaker is able to retain option that indicates that a BGP speaker is able to retain
forwarding state when a BGP session restarts"; forwarding state when a BGP session restarts";
reference "RFC 4724: Graceful Restart Mechanism for BGP"; reference "RFC 4724: Graceful Restart Mechanism for BGP";
container graceful-restart { container graceful-restart {
presence
"Presence of this item indicates that BGP graceful restart
is enabled.";
description description
"Parameters relating the graceful restart mechanism for BGP"; "Parameters relating the graceful restart mechanism for BGP";
container config { container config {
description description
"Configuration parameters relating to graceful-restart"; "Configuration parameters relating to graceful-restart";
uses bgp-neighbor-graceful-restart_config; uses bgp-neighbor-graceful-restart_config;
} }
container state { container state {
config false; config false;
description description
"State information associated with graceful-restart"; "State information associated with graceful-restart";
uses bgp-neighbor-graceful-restart_config; uses bgp-neighbor-graceful-restart_config;
} }
} }
} }
grouping bgp-neighbor-graceful-restart_config { grouping bgp-neighbor-graceful-restart_config {
description description
"Configuration parameters relating to BGP graceful restart."; "Configuration parameters relating to BGP graceful restart.";
leaf enabled {
type boolean;
description
"Enable or disable the graceful-restart capability.";
}
leaf restart-time { leaf restart-time {
type uint16 { type uint16 {
range 0..4096; range 0..4096;
} }
description description
"Estimated time in seconds for the BGP session to be "Estimated time (in seconds) for the local BGP speaker to
re-established after a restart. This is a 12-bit value restart a session. This value is advertise in the graceful
advertised by the router to peers. Per RFC 4724, the restart BGP capability. This is a 12-bit value, referred to
suggested default value is <= the hold-time value"; as Restart Time in RFC4724. Per RFC4724, the suggested
default value is <= the hold-time value.";
} }
leaf stale-routes-time { leaf stale-routes-time {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
description description
"Sets an upper bound on the time in seconds that stale "An upper-bound on the time thate stale routes will be
routes will be retained by the router after a session is retained by a router after a session is restarted. If an
restarted"; End-of-RIB (EOR) marker is received prior to this timer
expiring stale-routes will be flushed upon its receipt - if
no EOR is received, then when this timer expires stale paths
will be purged. This timer is referred to as the
Selection_Deferral_Timer in RFC4724";
}
leaf helper-only {
type boolean;
description
"Enable graceful-restart in helper mode only. When this
leaf is set, the local system does not retain forwarding
its own state during a restart, but supports procedures
for the receiving speaker, as defined in RFC4724.";
} }
} }
// ************************************************************ // ************************************************************
// * configuration context containers * // * configuration context containers *
// ************************************************************ // ************************************************************
grouping bgp-global-base { grouping bgp-global-base {
description description
"Global configuration parameters for the BGP router"; "Global configuration parameters for the BGP router";
skipping to change at page 17, line 19 skipping to change at page 19, line 19
uses bgp-global_config; uses bgp-global_config;
} }
container state { container state {
config false; config false;
description description
"State information relating to the global BGP router"; "State information relating to the global BGP router";
uses bgp-global_config; uses bgp-global_config;
uses bgp-op:bgp-global_state; uses bgp-op:bgp-global_state;
} }
uses bgp-mp:bgp-route-selection-options;
container default-route-distance { container default-route-distance {
description description
"Administrative distance (or preference) assigned to "Administrative distance (or preference) assigned to
routes received from different sources routes received from different sources
(external, internal, and local)."; (external, internal, and local).";
container config { container config {
description description
"Configuration parameters relating to the default route "Configuration parameters relating to the default route
distance"; distance";
skipping to change at page 17, line 40 skipping to change at page 19, line 42
} }
container state { container state {
config false; config false;
description description
"State information relating to the default route distance"; "State information relating to the default route distance";
uses bgp-default-route-distance_config; uses bgp-default-route-distance_config;
} }
} }
container confederation { container confederation {
presence
"Presence of this container indicates that the local AS is
part of a confederation";
description description
"Parameters indicating whether the local system acts as part "Parameters indicating whether the local system acts as part
of a BGP confederation"; of a BGP confederation";
container config { container config {
description description
"Configuration parameters relating to BGP confederations"; "Configuration parameters relating to BGP confederations";
uses bgp-confederation_config; uses bgp-confederation_config;
} }
container state { container state {
config false; config false;
description description
"State information relating to the BGP confederations"; "State information relating to the BGP confederations";
uses bgp-confederation_config; uses bgp-confederation_config;
} }
} }
uses bgp-mp:bgp-use-multiple-paths_config; uses bgp-mp:bgp-use-multiple-paths;
uses bgp-graceful-restart_config;
container afi-safi { uses bgp-graceful-restart;
container afi-safis {
description description
"Address family specific configuration"; "Address family specific configuration";
uses bgp-mp:bgp-global-afi-safi-list; uses bgp-mp:bgp-common-afi-safi-list;
} }
} }
grouping bgp-neighbors { grouping bgp-neighbors {
description description
"BGP neighbors configured on the local system"; "BGP neighbors configured on the local system";
list neighbor { list neighbor {
key "neighbor-address"; key "neighbor-address";
description description
"List of BGP neighbors configured on the local system, "List of BGP neighbors configured on the local system,
uniquely identified by peer IPv[46] address"; uniquely identified by peer IPv[46] address";
leaf neighbor-address { leaf neighbor-address {
type inet:ip-address; type leafref {
path "../config/neighbor-address";
}
description description
"Address of the BGP peer, either in IPv4 or IPv6"; "Reference to the address of the BGP neighbor used as
a key in the neighbor list";
} }
uses bgp-neighbor-group; uses bgp-neighbor-group;
} }
} }
grouping bgp-peer-group { grouping bgp-peer-group {
description description
"BGP peer-groups configured on the local system"; "BGP peer-groups configured on the local system";
list peer-group { list peer-group {
key "peer-group-name"; key "peer-group-name";
description description
skipping to change at page 18, line 51 skipping to change at page 21, line 5
grouping bgp-peer-group { grouping bgp-peer-group {
description description
"BGP peer-groups configured on the local system"; "BGP peer-groups configured on the local system";
list peer-group { list peer-group {
key "peer-group-name"; key "peer-group-name";
description description
"List of BGP peer-groups configured on the local system - "List of BGP peer-groups configured on the local system -
uniquely identified by peer-group name"; uniquely identified by peer-group name";
leaf peer-group-name { leaf peer-group-name {
type string; type leafref {
description path "../config/peer-group-name";
"";
} }
description
"Reference to the name of the BGP peer-group used as a
key in the peer-group list";
}
uses bgp-neighbor-group; uses bgp-neighbor-group;
} }
} }
grouping bgp-neighbor-group { grouping bgp-neighbor-group {
description description
"Parameters related to a BGP neighbor or group"; "Parameters related to a BGP neighbor or group";
container config { container config {
description description
skipping to change at page 22, line 32 skipping to change at page 24, line 37
uses bgp-neighbor-add-paths_config; uses bgp-neighbor-add-paths_config;
} }
container state { container state {
config false; config false;
description description
"State information associated with ADD_PATHS"; "State information associated with ADD_PATHS";
uses bgp-neighbor-add-paths_config; uses bgp-neighbor-add-paths_config;
} }
} }
container afi-safi { container afi-safis {
description description
"Per-address-family configuration parameters associated with "Per-address-family configuration parameters associated with
the neighbor or group"; the neighbor or group";
uses bgp-mp:bgp-global-afi-safi-list; uses bgp-mp:bgp-common-afi-safi-list;
} }
uses bgp-graceful-restart_config; uses bgp-graceful-restart;
uses rpol:apply-policy-group; uses rpol:apply-policy-group;
} }
grouping bgp-neighbor-neighbor-address_config {
description
"Configuration options relating to the BGP neighbor address";
leaf neighbor-address {
type inet:ip-address;
description
"Address of the BGP peer, either in IPv4 or IPv6";
}
}
grouping bgp-peer-group-peer-group-name_config {
description
"Configuration options relating to the BGP peer-group name";
leaf peer-group-name {
type string;
description
"Name of the BGP peer-group";
}
}
// add peer-group pointer only for the neighbor list // add peer-group pointer only for the neighbor list
augment /bgp/neighbors/neighbor/config { augment /bgp/neighbors/neighbor/config {
description description
"Augmentation to allow association of a neighbor with a "Augmentation to allow association of a neighbor with a
peer-group"; peer-group";
uses bgp-neighbor-peer-group_config; uses bgp-neighbor-peer-group_config;
} }
augment /bgp/neighbors/neighbor/state { augment /bgp/neighbors/neighbor/state {
description description
"Augmentation to reflect the association of a neighbor with a "Augmentation to reflect the association of a neighbor with a
peer-group"; peer-group";
uses bgp-neighbor-peer-group_config; uses bgp-neighbor-peer-group_config;
} }
augment /bgp/peer-groups/peer-group { augment /bgp/peer-groups/peer-group {
description description
"Augmentation to add multipath configuration to a peer-group"; "Augmentation to add multipath configuration to a peer-group";
uses bgp-mp:bgp-use-multiple-paths_config; uses bgp-mp:bgp-use-multiple-paths;
} }
augment /bgp/neighbors/neighbor { augment /bgp/neighbors/neighbor {
description description
"Augmentation to add the multipath configuration to a "Augmentation to add the multipath configuration to a
neighbor"; neighbor";
uses bgp-mp:bgp-use-multiple-paths-neighbor_config; uses bgp-mp:bgp-use-multiple-paths-neighbor;
}
augment /bgp/peer-groups/peer-group/afi-safis/afi-safi {
description
"Augmentation to add multipath configuration to a peer-group
on a per-AFI-SAFI basis";
uses bgp-mp:bgp-use-multiple-paths;
}
augment /bgp/neighbors/neighbor/afi-safis/afi-safi {
description
"Augmentation to add multipath configuration to a neighbor
on a per-AFI-SAFI basis";
uses bgp-mp:bgp-use-multiple-paths-neighbor;
}
augment /bgp/global/afi-safis/afi-safi {
description
"Augmentation to add global instance specific AFI-SAFI
configuration information";
uses bgp-mp:bgp-global-afi-safi;
uses bgp-mp:bgp-use-multiple-paths;
}
augment /bgp/peer-groups/peer-group/afi-safis/afi-safi {
description
"Augmentation that adds peer-group instance specific
AFI-SAFI configuration information";
uses bgp-mp:bgp-group-afi-safi;
}
augment /bgp/neighbors/neighbor/config {
description
"Augmentation adding the neighbor address to the
neighbor configuration container";
uses bgp-neighbor-neighbor-address_config;
}
augment /bgp/neighbors/neighbor/state {
description
"Augmentation adding the neighbor address to the
neighbor state container";
uses bgp-neighbor-neighbor-address_config;
}
augment /bgp/peer-groups/peer-group/config {
description
"Augmentation adding the peer-group name to the
peer-group configuration container";
uses bgp-peer-group-peer-group-name_config;
}
augment /bgp/peer-groups/peer-group/state {
description
"Augmentation adding the peer-group name to the
peer-group state container";
uses bgp-peer-group-peer-group-name_config;
} }
// ************************************************************ // ************************************************************
// * Augmentations to add state * // * Augmentations to add state *
// * (rjs: cleaner to have these in the base module to avoid * // * (rjs: cleaner to have these in the base module to avoid *
// needing to specify which module - e.g. augment of * // needing to specify which module - e.g. augment of *
// /bgp:bgp/bgp:neighbors/bgp:neighbor...) * // /bgp:bgp/bgp:neighbors/bgp:neighbor...) *
// ************************************************************ // ************************************************************
augment /bgp/neighbors/neighbor/state { augment /bgp/neighbors/neighbor/state {
description description
skipping to change at page 25, line 4 skipping to change at page 28, line 41
associated with a BGP neighbor"; associated with a BGP neighbor";
uses bgp-op:bgp-afi-safi-graceful-restart_state; uses bgp-op:bgp-afi-safi-graceful-restart_state;
} }
augment /bgp/peer-groups/peer-group/state { augment /bgp/peer-groups/peer-group/state {
description description
"Augmentation to add the operational state and counters "Augmentation to add the operational state and counters
relating to a BGP peer-group"; relating to a BGP peer-group";
uses bgp-op:bgp-peer-group_state; uses bgp-op:bgp-peer-group_state;
} }
augment /bgp/global/afi-safi/afi-safi/state {
augment /bgp/global/afi-safis/afi-safi/state {
description description
"Augmentation to add operational state and counters "Augmentation to add operational state and counters
on a per-AFI-SAFI basis to the global BGP router"; on a per-AFI-SAFI basis to the global BGP router";
uses bgp-op:bgp-global-afi-safi_state; uses bgp-op:bgp-global-afi-safi_state;
} }
augment /bgp/neighbors/neighbor/afi-safi/afi-safi/state { augment /bgp/neighbors/neighbor/afi-safis/afi-safi/state {
description description
"Augmentation to add per-AFI-SAFI operational state "Augmentation to add per-AFI-SAFI operational state
and counters to the BGP neighbor"; and counters to the BGP neighbor";
uses bgp-op:bgp-neighbor-afi-safi_state; uses bgp-op:bgp-neighbor-afi-safi_state;
} }
augment "/bgp/neighbors/neighbor/afi-safis/afi-safi/" +
"graceful-restart/state" {
description
"Augmentation to add per-AFI-SAFI operational state for BGP
graceful-restart";
uses bgp-op:bgp-neighbor-afi-safi-graceful-restart_state;
}
// ************************************************************ // ************************************************************
// * module structure containers * // * module structure containers *
// ************************************************************ // ************************************************************
container bgp { container bgp {
presence "Container for BGP protocol hierarchy"; presence "Container for BGP protocol hierarchy";
description description
"Top-level configuration and state for the BGP router"; "Top-level configuration and state for the BGP router";
container global { container global {
skipping to change at page 26, line 10 skipping to change at page 30, line 4
} }
} }
} }
<CODE ENDS> <CODE ENDS>
5.2. BGP base types 5.2. BGP base types
<CODE BEGINS> file bgp-types.yang <CODE BEGINS> file bgp-types.yang
module bgp-types { module bgp-types {
yang-version "1"; yang-version "1";
namespace "http://openconfig.net/yang/bgp-types"; namespace "http://openconfig.net/yang/bgp-types";
prefix "bgp-types"; prefix "bgp-types";
import ietf-inet-types { prefix inet; } import ietf-inet-types { prefix inet; }
import ietf-yang-types { prefix yang; }
// meta // meta
organization organization
"OpenConfig working group"; "OpenConfig working group";
contact contact
"OpenConfig working group "OpenConfig working group
netopenconfig@googlegroups.com"; netopenconfig@googlegroups.com";
description description
"This module contains general data definitions for use in BGP "This module contains general data definitions for use in BGP
policy. It can be imported by modules that make use of BGP policy. It can be imported by modules that make use of BGP
attributes"; attributes";
revision "2015-03-03" { revision "2015-05-15" {
description "Initial revision"; description "Initial revision";
reference "TBD"; reference "TBD";
} }
typedef peer-type {
type enumeration {
enum INTERNAL {
description "internal (iBGP) peer";
}
enum EXTERNAL {
description "external (eBGP) peer";
}
}
description
"labels a peer or peer group as explicitly internal or
external";
}
typedef remove-private-as-option {
type enumeration {
enum ALL {
description "remove all private ASes in the path";
}
enum REPLACE {
description "replace private ASes with local AS";
}
}
description
"set of options for configuring how private AS path numbers
are removed from advertisements";
}
typedef percentage {
type uint8 {
range "0..100";
}
description
"Integer indicating a percentage value";
}
typedef rr-cluster-id-type {
type union {
type uint32;
type inet:ipv4-address;
}
description
"union type for route reflector cluster ids:
option 1: 4-byte number
option 2: IP address";
}
typedef community-type {
type enumeration {
enum STANDARD {
description "send only standard communities";
}
enum EXTENDED {
description "send only extended communities";
}
enum BOTH {
description "send both standard and extended communities";
}
enum NONE {
description "do not send any community attribute";
}
}
description
"type describing variations of community attributes:
STANDARD: standard BGP community [rfc1997]
EXTENDED: extended BGP community [rfc4360]
BOTH: both standard and extended community";
}
identity bgp-capability { identity bgp-capability {
description "Base identity for a BGP capability"; description "Base identity for a BGP capability";
} }
identity MPBGP { identity MPBGP {
base "bgp-capability"; base "bgp-capability";
description description
"Multi-protocol extensions to BGP"; "Multi-protocol extensions to BGP";
reference "RFC2858"; reference "RFC2858";
} }
skipping to change at page 30, line 28 skipping to change at page 32, line 48
"BGP-signalled VPLS (AFI,SAFI = 25,65)"; "BGP-signalled VPLS (AFI,SAFI = 25,65)";
reference "RFC4761"; reference "RFC4761";
} }
identity l2vpn-evpn { identity l2vpn-evpn {
base afi-safi-type; base afi-safi-type;
description description
"BGP MPLS Based Ethernet VPN (AFI,SAFI = 25,70)"; "BGP MPLS Based Ethernet VPN (AFI,SAFI = 25,70)";
} }
identity bgp-well-known-std-community {
description
"Reserved communities within the standard community space
defined by RFC1997. These communities must fall within the
range 0x00000000 to 0xFFFFFFFF";
reference "RFC1997";
}
identity NO_EXPORT {
base bgp-well-known-std-community;
description
"Do not export NLRI received carrying this community outside
the bounds of this autonomous system, or this confederation if
the local autonomous system is a confederation member AS. This
community has a value of 0xFFFFFF01.";
reference "RFC1997";
}
identity NO_ADVERTISE {
base bgp-well-known-std-community;
description
"All NLRI received carrying this community must not be
advertised to other BGP peers. This community has a value of
0xFFFFFF02.";
reference "RFC1997";
}
identity NO_EXPORT_SUBCONFED {
base bgp-well-known-std-community;
description
"All NLRI received carrying this community must not be
advertised to external BGP peers - including over confederation
sub-AS boundaries. This community has a value of 0xFFFFFF03.";
reference "RFC1997";
}
identity NOPEER {
base bgp-well-known-std-community;
description
"An autonomous system receiving NLRI tagged with this community
is advised not to readvertise the NLRI to external bi-lateral
peer autonomous systems. An AS may also filter received NLRI
from bilateral peer sessions when they are tagged with this
community value";
reference "RFC3765";
}
identity INTERNET {
base bgp-well-known-std-community;
description
"A community used by some implementations with the value 0:0
which represents all possible community values.";
}
typedef bgp-session-direction { typedef bgp-session-direction {
type enumeration { type enumeration {
enum INBOUND { enum INBOUND {
description description
"Refers to all NLRI received from the BGP peer"; "Refers to all NLRI received from the BGP peer";
} }
enum OUTBOUND { enum OUTBOUND {
description description
"Refers to all NLRI advertised to the BGP peer"; "Refers to all NLRI advertised to the BGP peer";
} }
} }
description description
"Type to describe the direction of NLRI transmission"; "Type to describe the direction of NLRI transmission";
} }
}
<CODE ENDS>
5.3. BGP policy items
<CODE BEGINS> file bgp-policy.yang
module bgp-policy {
yang-version "1";
// namespace
namespace "http://openconfig.net/yang/bgp-policy";
prefix "bgp-pol";
// import some basic types
import ietf-inet-types { prefix inet; }
import routing-policy {prefix rpol; }
import policy-types {prefix pt; }
// meta
organization
"OpenConfig working group";
contact
"OpenConfig working group
netopenconfig@googlegroups.com";
description
"This module contains data definitions for BGP routing policy.
It augments the base routing-policy module with BGP-specific
options for conditions and actions.";
revision "2014-11-30" {
description
"Updated model to augment base routing-policy module";
reference "TBD";
}
// extension statements
// feature statements
// identity statements
// typedef statements
typedef bgp-as-path-prepend-repeat {
type uint8;
description
"Option for the BGP as-prepend policy action. Prepends the
local AS number repeated n times";
}
typedef bgp-well-known-community-type { typedef bgp-well-known-community-type {
type enumeration { type identityref {
enum INTERNET { base bgp-well-known-std-community;
description "entire Internet community (0x00000000)";
}
enum NO_EXPORT {
// value 0xFFFFFF01;
description "no export";
}
enum NO_ADVERTISE {
description "no advertise (0xFFFFFF02)";
}
enum NO_EXPORT_SUBCONFED {
description "no export subconfed, equivalent to
local AS (0xFFFFFF03)";
}
} }
description description
"Type definition for well-known IETF community attribute "Type definition for well-known IETF community attribute
values"; values";
reference "RFC 1997 - BGP Communities Attribute"; reference
"IANA Border Gateway Protocol (BGP) Well Known Communities";
} }
typedef bgp-std-community-type { typedef bgp-std-community-type {
// TODO: further refine restrictions and allowed patterns // TODO: further refine restrictions and allowed patterns
// 4-octet value: // 4-octet value:
// <as number> 2 octets // <as number> 2 octets
// <community value> 2 octets // <community value> 2 octets
type union { type union {
type uint32 { type uint32 {
// per RFC 1997, 0x00000000 - 0x0000FFFF and 0xFFFF0000 - // per RFC 1997, 0x00000000 - 0x0000FFFF and 0xFFFF0000 -
skipping to change at page 33, line 27 skipping to change at page 35, line 29
// take. // take.
type string; type string;
description description
"Type definition for communities specified as regular "Type definition for communities specified as regular
expression patterns"; expression patterns";
} }
typedef bgp-origin-attr-type { typedef bgp-origin-attr-type {
type enumeration { type enumeration {
enum IGP { enum IGP {
value 0;
description "Origin of the NLRI is internal"; description "Origin of the NLRI is internal";
} }
enum EGP { enum EGP {
value 1;
description "Origin of the NLRI is EGP"; description "Origin of the NLRI is EGP";
} }
enum INCOMPLETE { enum INCOMPLETE {
value 2;
description "Origin of the NLRI is neither IGP or EGP"; description "Origin of the NLRI is neither IGP or EGP";
} }
} }
description description
"Type definition for standard BGP origin attribute"; "Type definition for standard BGP origin attribute";
reference "RFC 4271 - A Border Gateway Protocol 4 (BGP-4), reference "RFC 4271 - A Border Gateway Protocol 4 (BGP-4),
Sec 4.3"; Sec 4.3";
} }
typedef peer-type {
type enumeration {
enum INTERNAL {
description "internal (iBGP) peer";
}
enum EXTERNAL {
description "external (eBGP) peer";
}
}
description
"labels a peer or peer group as explicitly internal or
external";
}
typedef remove-private-as-option {
type enumeration {
enum ALL {
description "remove all private ASes in the path";
}
enum REPLACE {
description "replace private ASes with local AS";
}
}
description
"set of options for configuring how private AS path numbers
are removed from advertisements";
}
typedef percentage {
type uint8 {
range "0..100";
}
description
"Integer indicating a percentage value";
}
typedef rr-cluster-id-type {
type union {
type uint32;
type inet:ipv4-address;
}
description
"union type for route reflector cluster ids:
option 1: 4-byte number
option 2: IP address";
}
typedef community-type {
type enumeration {
enum STANDARD {
description "send only standard communities";
}
enum EXTENDED {
description "send only extended communities";
}
enum BOTH {
description "send both standard and extended communities";
}
enum NONE {
description "do not send any community attribute";
}
}
description
"type describing variations of community attributes:
STANDARD: standard BGP community [rfc1997]
EXTENDED: extended BGP community [rfc4360]
BOTH: both standard and extended community";
}
}
<CODE ENDS>
5.3. BGP policy items
<CODE BEGINS> file bgp-policy.yang
module bgp-policy {
yang-version "1";
// namespace
namespace "http://openconfig.net/yang/bgp-policy";
prefix "bgp-pol";
// import some basic types
import ietf-inet-types { prefix inet; }
import routing-policy {prefix rpol; }
import policy-types { prefix pt; }
import bgp-types { prefix bgp-types; }
// meta
organization
"OpenConfig working group";
contact
"OpenConfig working group
netopenconfig@googlegroups.com";
description
"This module contains data definitions for BGP routing policy.
It augments the base routing-policy module with BGP-specific
options for conditions and actions.";
revision "2015-05-15" {
description
"Updated model to augment base routing-policy module";
reference "TBD";
}
// extension statements
// feature statements
// identity statements
// typedef statements
typedef bgp-as-path-prepend-repeat {
type uint8;
description
"Option for the BGP as-prepend policy action. Prepends the
local AS number repeated n times";
}
typedef bgp-set-community-option-type { typedef bgp-set-community-option-type {
type enumeration { type enumeration {
enum ADD { enum ADD {
description "add the specified communities to the existing description
community attribute"; "add the specified communities to the existing
community attribute";
} }
enum REMOVE { enum REMOVE {
description "remove the specified communities from the description
existing community attribute"; "remove the specified communities from the
existing community attribute";
} }
enum REPLACE { enum REPLACE {
description "replace the existing community attribute with description
the specified communities"; "replace the existing community attribute with
} the specified communities. If an empty set is
enum NULL { specified, this removes the community attribute
description "set the community attribute to empty / NULL"; from the route.";
} }
} }
description description
"Type definition for options when setting the community "Type definition for options when setting the community
attribute in a policy action"; attribute in a policy action";
} }
typedef bgp-next-hop-type { typedef bgp-next-hop-type {
type union { type union {
type inet:ip-address; type inet:ip-address;
type enumeration { type enumeration {
enum SELF { enum SELF {
description "special designation for local router's own description "special designation for local router's own
address, i.e., next-hop-self"; address, i.e., next-hop-self";
} }
skipping to change at page 34, line 29 skipping to change at page 39, line 17
typedef bgp-next-hop-type { typedef bgp-next-hop-type {
type union { type union {
type inet:ip-address; type inet:ip-address;
type enumeration { type enumeration {
enum SELF { enum SELF {
description "special designation for local router's own description "special designation for local router's own
address, i.e., next-hop-self"; address, i.e., next-hop-self";
} }
} }
} }
description "type definition for specifying next-hop in policy description
actions"; "type definition for specifying next-hop in policy actions";
} }
typedef bgp-set-med-type { typedef bgp-set-med-type {
type union { type union {
type uint32; type uint32;
type string {
pattern "^[+-][0-9]+";
}
type enumeration { type enumeration {
enum IGP { enum IGP {
description "set the MED value to the IGP cost toward the description "set the MED value to the IGP cost toward the
next hop for the route"; next hop for the route";
} }
} }
} }
description "type definition for specifying how the BGP MED can description
be set in BGP policy actions"; "Type definition for specifying how the BGP MED can
be set in BGP policy actions. The three choices are to set
the MED directly, increment/decrement using +/- notation,
and setting it to the IGP cost (predefined value).";
} }
// grouping statements // grouping statements
grouping bgp-match-conditions { grouping bgp-match-conditions {
description description
"Condition statement definitions for checking membership in a "Condition statement definitions for checking membership in a
defined set"; defined set";
container match-community-set { container match-community-set {
skipping to change at page 35, line 18 skipping to change at page 40, line 12
"The presence of this container indicates that the routes "The presence of this container indicates that the routes
should match the referenced community-set"; should match the referenced community-set";
description description
"Match a referenced community-set according to the logic "Match a referenced community-set according to the logic
defined in the match-set-options leaf"; defined in the match-set-options leaf";
leaf community-set { leaf community-set {
type leafref { type leafref {
path "/rpol:routing-policy/rpol:defined-sets/" + path "/rpol:routing-policy/rpol:defined-sets/" +
"bgp-pol:bgp-defined-sets/bgp-pol:community-set/" + "bgp-pol:bgp-defined-sets/bgp-pol:community-sets/" +
"bgp-pol:community-set-name"; "bgp-pol:community-set/bgp-pol:community-set-name";
require-instance true; require-instance true;
} }
description description
"References a defined community set"; "References a defined community set";
} }
uses rpol:match-set-options-group; uses rpol:match-set-options-group;
} }
container match-ext-community-set { container match-ext-community-set {
presence presence
"The presence of this container indicates that the routes "The presence of this container indicates that the routes
should match the referenced extended community set"; should match the referenced extended community set";
description description
"Match a referenced extended community-set according to the "Match a referenced extended community-set according to the
logic defined in the match-set-options leaf"; logic defined in the match-set-options leaf";
leaf ext-community-set { leaf ext-community-set {
type leafref { type leafref {
path "/rpol:routing-policy/rpol:defined-sets/" + path "/rpol:routing-policy/rpol:defined-sets/" +
"bgp-pol:bgp-defined-sets/bgp-pol:ext-community-set/" + "bgp-pol:bgp-defined-sets/bgp-pol:ext-community-sets/" +
"bgp-pol:ext-community-set/" +
"bgp-pol:ext-community-set-name"; "bgp-pol:ext-community-set-name";
require-instance true; require-instance true;
} }
description "References a defined extended community set"; description "References a defined extended community set";
} }
uses rpol:match-set-options-group; uses rpol:match-set-options-group;
} }
container match-as-path-set { container match-as-path-set {
presence presence
"The presence of this container indicates that the route "The presence of this container indicates that the route
should match the referenced as-path set"; should match the referenced as-path set";
description description
"Match a referenced as-path set according to the logic "Match a referenced as-path set according to the logic
defined in the match-set-options leaf"; defined in the match-set-options leaf";
leaf as-path-set { leaf as-path-set {
type leafref { type leafref {
path "/rpol:routing-policy/rpol:defined-sets/" + path "/rpol:routing-policy/rpol:defined-sets/" +
"bgp-pol:bgp-defined-sets/bgp-pol:as-path-set/" + "bgp-pol:bgp-defined-sets/bgp-pol:as-path-sets/" +
"bgp-pol:as-path-set-name"; "bgp-pol:as-path-set/bgp-pol:as-path-set-name";
require-instance true; require-instance true;
} }
description "References a defined AS path set"; description "References a defined AS path set";
} }
uses rpol:match-set-options-group; uses rpol:match-set-options-group;
} }
} }
grouping bgp-attribute-conditions { grouping bgp-attribute-conditions {
description description
skipping to change at page 36, line 36 skipping to change at page 41, line 31
attribute to a specified value"; attribute to a specified value";
leaf med-eq { leaf med-eq {
type uint32; type uint32;
description description
"Condition to check if the received MED value is equal to "Condition to check if the received MED value is equal to
the specified value"; the specified value";
} }
leaf origin-eq { leaf origin-eq {
type bgp-origin-attr-type; type bgp-types:bgp-origin-attr-type;
description description
"Condition to check if the route origin is equal to the "Condition to check if the route origin is equal to the
specified value"; specified value";
} }
leaf-list next-hop-in { leaf-list next-hop-in {
type inet:ip-address; type inet:ip-address;
description description
"List of next hop addresses to check for in the route "List of next hop addresses to check for in the route
update"; update";
skipping to change at page 38, line 4 skipping to change at page 42, line 43
enum EXTERNAL { enum EXTERNAL {
description "route type is external"; description "route type is external";
} }
} }
description description
"Condition to check the route type in the route update"; "Condition to check the route type in the route update";
} }
} }
// augment statements // augment statements
augment "/rpol:routing-policy/rpol:defined-sets" { augment "/rpol:routing-policy/rpol:defined-sets" {
description "adds BGP defined sets container to routing policy description "adds BGP defined sets container to routing policy
model"; model";
container bgp-defined-sets { container bgp-defined-sets {
description description
"BGP-related set definitions for policy match conditions"; "BGP-related set definitions for policy match conditions";
list community-set { container community-sets {
key community-set-name;
description description
"Definitions for community sets"; "Enclosing container for community sets";
leaf community-set-name { list community-set {
type string; key community-set-name;
mandatory true;
description description
"name / label of the community set -- this is used to "Definitions for community sets";
reference the set in match conditions";
}
leaf-list community-members { leaf community-set-name {
type union { type string;
type bgp-std-community-type; mandatory true;
type bgp-community-regexp-type; description
type bgp-well-known-community-type; "name / label of the community set -- this is used to
reference the set in match conditions";
} }
description
"members of the community set";
}
leaf-list community-member {
type union {
type bgp-types:bgp-std-community-type;
type bgp-types:bgp-community-regexp-type;
type bgp-types:bgp-well-known-community-type;
}
description
"members of the community set";
}
}
} }
list ext-community-set { container ext-community-sets {
key ext-community-set-name;
description description
"Definitions for extended community sets"; "Enclosing container for extended community sets";
leaf ext-community-set-name { list ext-community-set {
type string; key ext-community-set-name;
description description
"name / label of the extended community set -- this is "Definitions for extended community sets";
used to reference the set in match conditions";
}
leaf-list ext-community-members { leaf ext-community-set-name {
type union { type string;
type bgp-ext-community-type; description
// TODO: is regexp support needed for extended "name / label of the extended community set -- this is
// communities? used to reference the set in match conditions";
type bgp-community-regexp-type; }
leaf-list ext-community-member {
type union {
type bgp-types:bgp-ext-community-type;
// TODO: is regexp support needed for extended
// communities?
type bgp-types:bgp-community-regexp-type;
}
description
"members of the extended community set";
} }
description
"members of the extended community set";
} }
} }
list as-path-set { container as-path-sets {
key as-path-set-name;
description description
"Definitions for AS path sets"; "Enclosing container for AS path sets";
leaf as-path-set-name { list as-path-set {
type string; key as-path-set-name;
description description
"name of the AS path set -- this is used to reference the "Definitions for AS path sets";
the set in match conditions";
}
leaf-list as-path-set-members { leaf as-path-set-name {
// TODO: need to refine typedef for AS path expressions type string;
type string; description
description "name of the AS path set -- this is used to reference
"AS path expression -- list of ASes in the set"; the set in match conditions";
} }
leaf-list as-path-set-member {
// TODO: need to refine typedef for AS path expressions
type string;
description
"AS path expression -- list of ASes in the set";
}
}
} }
} }
} }
augment "/rpol:routing-policy/rpol:policy-definition/" + augment "/rpol:routing-policy/rpol:policy-definitions/" +
"rpol:statement/rpol:conditions" { "rpol:policy-definition/rpol:statements/rpol:statement/" +
"rpol:conditions" {
description "BGP policy conditions added to routing policy description "BGP policy conditions added to routing policy
module"; module";
container bgp-conditions { container bgp-conditions {
description "Policy conditions for matching description "Policy conditions for matching
BGP-specific defined sets or comparing BGP-specific BGP-specific defined sets or comparing BGP-specific
attributes"; attributes";
uses bgp-match-conditions; uses bgp-match-conditions;
uses bgp-attribute-conditions; uses bgp-attribute-conditions;
} }
} }
augment "/rpol:routing-policy/rpol:policy-definition/" + augment "/rpol:routing-policy/rpol:policy-definitions/" +
"rpol:statement/rpol:actions" { "rpol:policy-definition/rpol:statements/rpol:statement/" +
"rpol:actions" {
description "BGP policy actions added to routing policy description "BGP policy actions added to routing policy
module"; module";
container bgp-actions { container bgp-actions {
description description
"Definitions for policy action statements that "Definitions for policy action statements that
change BGP-specific attributes of the route"; change BGP-specific attributes of the route";
container set-as-path-prepend { container set-as-path-prepend {
presence "node is pesent in the config data to use the AS presence "node is present in the config data to use the AS
prepend action"; prepend action";
description description
"action to prepend local AS number to the AS-path a "action to prepend local AS number to the AS-path a
specified number of times"; specified number of times";
leaf repeat-n { leaf repeat-n {
type uint8; type uint8;
description "number of times to prepend the local AS description "number of times to prepend the local AS
number"; number";
} }
} }
container set-community { container set-community {
presence "node is present in the config data when presence "node is present in the config data when
set-community action is used"; set-community action is used";
description description
"action to set the community attributes of the route, along "action to set the community attributes of the route, along
with options to modify how the community is modified"; with options to modify how the community is modified";
leaf-list communities { choice set-community-method {
type union {
type bgp-std-community-type;
type bgp-well-known-community-type;
}
description description
"community values for the update"; "Option to set communities using an inline list or
} reference to an existing defined set.";
case inline {
leaf-list communities {
type union {
type bgp-types:bgp-std-community-type;
type bgp-types:bgp-well-known-community-type;
}
description
"Set the community values for the update inline with
a list.";
}
}
case reference {
leaf community-set-ref {
type leafref {
path "/rpol:routing-policy/rpol:defined-sets/" +
"bgp-pol:bgp-defined-sets/" +
"bgp-pol:community-sets/bgp-pol:community-set/" +
"bgp-pol:community-set-name";
require-instance true;
}
description
"References a defined community set by name";
}
}
}
leaf options { leaf options {
type bgp-set-community-option-type; type bgp-set-community-option-type;
description description
"options for modifying the community attribute with the "Options for modifying the community attribute with
specified values"; the specified values. These options apply to both
methods of setting the community attribute.";
} }
} }
container set-ext-community { container set-ext-community {
presence "node is present in the config data when presence "node is present in the config data when
set-community action is used"; set-community action is used";
description description
"action to set the extended community attributes of the "Action to set the extended community attributes of the
route, along with options to modify how the community is route, along with options to modify how the community is
modified"; modified";
leaf-list communities { choice set-ext-community-method {
type union {
type bgp-ext-community-type;
type bgp-well-known-community-type;
}
description description
"community values for the update"; "Option to set communities using an inline list or
} reference to an existing defined set.";
case inline {
leaf-list communities {
type union {
type bgp-types:bgp-ext-community-type;
type bgp-types:bgp-well-known-community-type;
}
description
"Set the community values for the update inline with
a list.";
}
}
case reference {
leaf ext-community-set-ref {
type leafref {
path "/rpol:routing-policy/rpol:defined-sets/" +
"bgp-pol:bgp-defined-sets/" +
"bgp-pol:ext-community-sets/" +
"bgp-pol:ext-community-set/" +
"bgp-pol:ext-community-set-name";
require-instance true;
}
description
"References a defined extended community set by
name";
}
}
}
leaf options { leaf options {
type bgp-set-community-option-type; type bgp-set-community-option-type;
description description
"options for modifying the community attribute with the "options for modifying the extended community
specified values"; attribute with the specified values. These options
apply to both methods of setting the community
attribute.";
} }
} }
leaf set-route-origin { leaf set-route-origin {
type bgp-origin-attr-type; type bgp-types:bgp-origin-attr-type;
description "set the origin attribute to the specified description "set the origin attribute to the specified
value"; value";
} }
leaf set-local-pref { leaf set-local-pref {
type uint32; type uint32;
description "set the local pref attribute on the route description "set the local pref attribute on the route
update"; update";
} }
skipping to change at page 42, line 50 skipping to change at page 49, line 7
"This module is part of a YANG model for BGP protocol "This module is part of a YANG model for BGP protocol
configuration, focusing on configuration of multiprotocol configuration, focusing on configuration of multiprotocol
BGP, in particular various relevant address families (AFI) and BGP, in particular various relevant address families (AFI) and
sub-address families (SAFI). sub-address families (SAFI).
Identities (rather than enumerated types) are used to identify Identities (rather than enumerated types) are used to identify
each AFI / SAFI type to make it easier for users to extend to each AFI / SAFI type to make it easier for users to extend to
pre-standard or custom AFI/SAFI types. This module is only pre-standard or custom AFI/SAFI types. This module is only
intended to capture the most"; intended to capture the most";
revision "2014-11-30" { revision "2015-05-15" {
description description
"Refactored multiprotocol module"; "Refactored multiprotocol module";
reference "TBD"; reference "TBD";
} }
grouping ipv4-unicast-group { grouping ipv4-unicast-group {
description description
"Group for IPv4 Unicast configuration options"; "Group for IPv4 Unicast configuration options";
container ipv4-unicast { container ipv4-unicast {
when "../afi-safi-name = 'bgp-mp:ipv4-unicast'" { when "../afi-safi-name = 'bgp-mp:ipv4-unicast'" {
description description
"Include this container for IPv4 Unicast specific "Include this container for IPv4 Unicast specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the IPv4 Unicast
AFI,SAFI is enabled for a neighbour or group";
description "IPv4 unicast configuration options"; description "IPv4 unicast configuration options";
// include common IPv[46] unicast options // include common IPv[46] unicast options
uses ipv4-ipv6-unicast-common; uses ipv4-ipv6-unicast-common;
// placeholder for IPv4 unicast specific configuration // placeholder for IPv4 unicast specific configuration
} }
} }
grouping ipv6-unicast-group { grouping ipv6-unicast-group {
description description
"Group for IPv6 Unicast configuration options"; "Group for IPv6 Unicast configuration options";
container ipv6-unicast { container ipv6-unicast {
when "../afi-safi-name = 'bgp-mp:ipv6-unicast'" { when "../afi-safi-name = 'bgp-mp:ipv6-unicast'" {
description description
"Include this container for IPv6 Unicast specific "Include this container for IPv6 Unicast specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the IPv6 Unicast
AFI,SAFI is enabled for a neighbour or group";
description "IPv6 unicast configuration options"; description "IPv6 unicast configuration options";
// include common IPv[46] unicast options // include common IPv[46] unicast options
uses ipv4-ipv6-unicast-common; uses ipv4-ipv6-unicast-common;
// placeholder for IPv6 unicast specific configuration // placeholder for IPv6 unicast specific configuration
// options // options
} }
} }
grouping ipv4-labelled-unicast-group { grouping ipv4-labelled-unicast-group {
description description
"Group for IPv4 Labelled Unicast configuration options"; "Group for IPv4 Labelled Unicast configuration options";
container ipv4-labelled-unicast { container ipv4-labelled-unicast {
when "../afi-safi-name = 'bgp-mp:ipv4-labelled-unicast'" { when "../afi-safi-name = 'bgp-mp:ipv4-labelled-unicast'" {
description description
skipping to change at page 44, line 20 skipping to change at page 50, line 19
description description
"Group for IPv4 Labelled Unicast configuration options"; "Group for IPv4 Labelled Unicast configuration options";
container ipv4-labelled-unicast { container ipv4-labelled-unicast {
when "../afi-safi-name = 'bgp-mp:ipv4-labelled-unicast'" { when "../afi-safi-name = 'bgp-mp:ipv4-labelled-unicast'" {
description description
"Include this container for IPv4 Labelled Unicast specific "Include this container for IPv4 Labelled Unicast specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the IPv4 Labelled
Unicast AFI,SAFI is enabled for a neighbour or group";
description "IPv4 Labelled Unicast configuration options"; description "IPv4 Labelled Unicast configuration options";
uses all-afi-safi-common; uses all-afi-safi-common;
// placeholder for IPv4 Labelled Unicast specific config // placeholder for IPv4 Labelled Unicast specific config
// options // options
} }
} }
grouping ipv6-labelled-unicast-group { grouping ipv6-labelled-unicast-group {
description description
"Group for IPv6 Labelled Unicast configuration options"; "Group for IPv6 Labelled Unicast configuration options";
container ipv6-labelled-unicast { container ipv6-labelled-unicast {
when "../afi-safi-name = 'bgp-mp:ipv6-labelled-unicast'" { when "../afi-safi-name = 'bgp-mp:ipv6-labelled-unicast'" {
description description
"Include this container for IPv6 Labelled Unicast specific "Include this container for IPv6 Labelled Unicast specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the IPv6 Labelled
Unicast AFI,SAFI is enabled for a neighbour or group";
description "IPv6 Labelled Unicast configuration options"; description "IPv6 Labelled Unicast configuration options";
uses all-afi-safi-common; uses all-afi-safi-common;
// placeholder for IPv6 Labelled Unicast specific config // placeholder for IPv6 Labelled Unicast specific config
// options. // options.
} }
} }
grouping l3vpn-ipv4-unicast-group { grouping l3vpn-ipv4-unicast-group {
description description
"Group for IPv4 Unicast L3VPN configuration options"; "Group for IPv4 Unicast L3VPN configuration options";
container l3vpn-ipv4-unicast { container l3vpn-ipv4-unicast {
skipping to change at page 45, line 20 skipping to change at page 51, line 10
description description
"Group for IPv4 Unicast L3VPN configuration options"; "Group for IPv4 Unicast L3VPN configuration options";
container l3vpn-ipv4-unicast { container l3vpn-ipv4-unicast {
when "../afi-safi-name = 'bgp-mp:l3vpn-ipv4-unicast'" { when "../afi-safi-name = 'bgp-mp:l3vpn-ipv4-unicast'" {
description description
"Include this container for IPv4 Unicast L3VPN specific "Include this container for IPv4 Unicast L3VPN specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that IPv4 Unicast L3VPN
AFI,SAFI is enabled for a neighbour or group";
description "Unicast IPv4 L3VPN configuration options"; description "Unicast IPv4 L3VPN configuration options";
// include common L3VPN configuration options // include common L3VPN configuration options
uses l3vpn-ipv4-ipv6-unicast-common; uses l3vpn-ipv4-ipv6-unicast-common;
// placeholder for IPv4 Unicast L3VPN specific config options. // placeholder for IPv4 Unicast L3VPN specific config options.
} }
} }
grouping l3vpn-ipv6-unicast-group { grouping l3vpn-ipv6-unicast-group {
description description
"Group for IPv6 Unicast L3VPN configuration options"; "Group for IPv6 Unicast L3VPN configuration options";
container l3vpn-ipv6-unicast { container l3vpn-ipv6-unicast {
when "../afi-safi-name = 'bgp-mp:l3vpn-ipv6-unicast'" { when "../afi-safi-name = 'bgp-mp:l3vpn-ipv6-unicast'" {
description description
"Include this container for unicast IPv6 L3VPN specific "Include this container for unicast IPv6 L3VPN specific
configuration"; configuration";
} }
presence "Presence of this container indicates that the IPv6
Unicast L3VPN AFI,SAFI is enabled";
description "Unicast IPv6 L3VPN configuration options"; description "Unicast IPv6 L3VPN configuration options";
// include common L3VPN configuration options // include common L3VPN configuration options
uses l3vpn-ipv4-ipv6-unicast-common; uses l3vpn-ipv4-ipv6-unicast-common;
// placeholder for IPv6 Unicast L3VPN specific configuration // placeholder for IPv6 Unicast L3VPN specific configuration
// options // options
} }
} }
grouping l3vpn-ipv4-multicast-group { grouping l3vpn-ipv4-multicast-group {
description description
"Group for IPv4 L3VPN multicast configuration options"; "Group for IPv4 L3VPN multicast configuration options";
container l3vpn-ipv4-multicast { container l3vpn-ipv4-multicast {
skipping to change at page 46, line 20 skipping to change at page 51, line 51
description description
"Group for IPv4 L3VPN multicast configuration options"; "Group for IPv4 L3VPN multicast configuration options";
container l3vpn-ipv4-multicast { container l3vpn-ipv4-multicast {
when "../afi-safi-name = 'bgp-mp:l3vpn-ipv4-multicast'" { when "../afi-safi-name = 'bgp-mp:l3vpn-ipv4-multicast'" {
description description
"Include this container for multicast IPv6 L3VPN specific "Include this container for multicast IPv6 L3VPN specific
configuration"; configuration";
} }
presence "Presence of this container indicates the
IPv4 L3VPN Unicast AFI-SAFI is enabled";
description "Multicast IPv4 L3VPN configuration options"; description "Multicast IPv4 L3VPN configuration options";
// include common L3VPN multicast options // include common L3VPN multicast options
uses l3vpn-ipv4-ipv6-multicast-common; uses l3vpn-ipv4-ipv6-multicast-common;
// placeholder for IPv4 Multicast L3VPN specific configuration // placeholder for IPv4 Multicast L3VPN specific configuration
// options // options
} }
} }
grouping l3vpn-ipv6-multicast-group { grouping l3vpn-ipv6-multicast-group {
description description
skipping to change at page 46, line 44 skipping to change at page 52, line 23
description description
"Group for IPv6 L3VPN multicast configuration options"; "Group for IPv6 L3VPN multicast configuration options";
container l3vpn-ipv6-multicast { container l3vpn-ipv6-multicast {
when "../afi-safi-name = 'bgp-mp:l3vpn-ipv6-multicast'" { when "../afi-safi-name = 'bgp-mp:l3vpn-ipv6-multicast'" {
description description
"Include this container for multicast IPv6 L3VPN specific "Include this container for multicast IPv6 L3VPN specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the IPv6 Multicast
L3VPN AFI,SAFI is enabled";
description "Multicast IPv6 L3VPN configuration options"; description "Multicast IPv6 L3VPN configuration options";
// include common L3VPN multicast options // include common L3VPN multicast options
uses l3vpn-ipv4-ipv6-multicast-common; uses l3vpn-ipv4-ipv6-multicast-common;
// placeholder for IPv6 Multicast L3VPN specific configuration // placeholder for IPv6 Multicast L3VPN specific configuration
// options // options
} }
} }
grouping l2vpn-vpls-group { grouping l2vpn-vpls-group {
description description
"Group for BGP-signalled VPLS configuration options"; "Group for BGP-signalled VPLS configuration options";
container l2vpn-vpls { container l2vpn-vpls {
skipping to change at page 47, line 20 skipping to change at page 52, line 44
description description
"Group for BGP-signalled VPLS configuration options"; "Group for BGP-signalled VPLS configuration options";
container l2vpn-vpls { container l2vpn-vpls {
when "../afi-safi-name = 'bgp-mp:l2vpn-vpls'" { when "../afi-safi-name = 'bgp-mp:l2vpn-vpls'" {
description description
"Include this container for BGP-signalled VPLS specific "Include this container for BGP-signalled VPLS specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the BGP-signalled
VPLS AFI,SAFI is enabled";
description "BGP-signalled VPLS configuration options"; description "BGP-signalled VPLS configuration options";
// include common L2VPN options // include common L2VPN options
uses l2vpn-common; uses l2vpn-common;
// placeholder for BGP-signalled VPLS specific configuration // placeholder for BGP-signalled VPLS specific configuration
// options // options
} }
} }
grouping l2vpn-evpn-group { grouping l2vpn-evpn-group {
description description
"Group for BGP EVPN configuration options"; "Group for BGP EVPN configuration options";
container l2vpn-evpn { container l2vpn-evpn {
when "../afi-safi-name = 'bgp-mp:l2vpn-evpn'" { when "../afi-safi-name = 'bgp-mp:l2vpn-evpn'" {
description description
"Include this container for BGP EVPN specific "Include this container for BGP EVPN specific
skipping to change at page 47, line 45 skipping to change at page 53, line 18
description description
"Group for BGP EVPN configuration options"; "Group for BGP EVPN configuration options";
container l2vpn-evpn { container l2vpn-evpn {
when "../afi-safi-name = 'bgp-mp:l2vpn-evpn'" { when "../afi-safi-name = 'bgp-mp:l2vpn-evpn'" {
description description
"Include this container for BGP EVPN specific "Include this container for BGP EVPN specific
configuration"; configuration";
} }
presence
"Presence of this container indicates that the BGP EVPN
AFI,SAFI is enabled";
description "BGP EVPN configuration options"; description "BGP EVPN configuration options";
// include common L2VPN options // include common L2VPN options
uses l2vpn-common; uses l2vpn-common;
// placeholder for BGP EVPN specific configuration options // placeholder for BGP EVPN specific configuration options
} }
} }
grouping bgp-route-selection-options_config { grouping bgp-route-selection-options_config {
skipping to change at page 49, line 4 skipping to change at page 54, line 20
the active path."; the active path.";
} }
leaf advertise-inactive-routes { leaf advertise-inactive-routes {
type boolean; type boolean;
default "false"; default "false";
description description
"Advertise inactive routes to external peers. The "Advertise inactive routes to external peers. The
default is to only advertise active routes."; default is to only advertise active routes.";
} }
leaf enable-aigp { leaf enable-aigp {
type empty; type boolean;
default false;
description description
"Flag to enable sending / receiving accumulated IGP "Flag to enable sending / receiving accumulated IGP
attribute in routing updates"; attribute in routing updates";
} }
leaf ignore-next-hop-igp-metric { leaf ignore-next-hop-igp-metric {
type boolean; type boolean;
default "false"; default "false";
description description
"Ignore the IGP metric to the next-hop when calculating "Ignore the IGP metric to the next-hop when calculating
skipping to change at page 50, line 16 skipping to change at page 55, line 35
leaf maximum-paths { leaf maximum-paths {
type uint32; type uint32;
default 1; default 1;
description description
"Maximum number of parallel paths to consider when using "Maximum number of parallel paths to consider when using
iBGP multipath. The default is to use a single path"; iBGP multipath. The default is to use a single path";
} }
} }
grouping bgp-use-multiple-paths_config { grouping bgp-use-multiple-paths {
description description
"Configuration parameters relating to multipath for BGP - both "Configuration parameters relating to multipath for BGP - both
iBGP and eBGP"; iBGP and eBGP";
container use-multiple-paths { container use-multiple-paths {
presence
"Presence of this container indicates that multipath is
enabled for eBGP and iBGP. Absence of the container
indicates that multipath is disabled";
description description
"Parameters related to the use of multiple paths for the "Parameters related to the use of multiple paths for the
same NLRI"; same NLRI";
container config {
description
"Configuration parameters relating to multipath";
uses bgp-use-multiple-paths_config;
}
container state {
description
"State parameters relating to multipath";
uses bgp-use-multiple-paths_config;
}
container ebgp { container ebgp {
description description
"Multipath parameters for eBGP"; "Multipath parameters for eBGP";
container config { container config {
description description
"Configuration parameters relating to eBGP multipath"; "Configuration parameters relating to eBGP multipath";
uses bgp-use-multiple-paths-ebgp_config; uses bgp-use-multiple-paths-ebgp_config;
} }
container state { container state {
config false; config false;
skipping to change at page 51, line 17 skipping to change at page 56, line 42
container state { container state {
config false; config false;
description description
"State information relating to iBGP multipath"; "State information relating to iBGP multipath";
uses bgp-use-multiple-paths-ibgp_config; uses bgp-use-multiple-paths-ibgp_config;
} }
} }
} }
} }
grouping bgp-use-multiple-paths-neighbor_config { grouping bgp-use-multiple-paths-neighbor {
description description
"Per-neighbor configuration for multipath for BGP"; "Per-neighbor configuration for multipath for BGP";
container use-multiple-paths { container use-multiple-paths {
presence
"Presence of this container indicates that multiple paths
from this neighbor should be installed into the RIB. Absence
of this container results in the multipath configuration
being inherited from the peer-group if it exists.";
description description
"Parameters related to the use of multiple-paths for the same "Parameters related to the use of multiple-paths for the same
NLRI when they are received only from this neighbor"; NLRI when they are received only from this neighbor";
container config {
description
"Configuration parameters relating to multipath";
uses bgp-use-multiple-paths_config;
}
container state {
description
"State parameters relating to multipath";
uses bgp-use-multiple-paths_config;
}
container ebgp { container ebgp {
description description
"Multipath configuration for eBGP"; "Multipath configuration for eBGP";
container config { container config {
description description
"Configuration parameters relating to eBGP multipath"; "Configuration parameters relating to eBGP multipath";
uses bgp-use-multiple-paths-ebgp-as-options_config; uses bgp-use-multiple-paths-ebgp-as-options_config;
} }
container state { container state {
config false; config false;
description description
"State information relating to eBGP multipath"; "State information relating to eBGP multipath";
uses bgp-use-multiple-paths-ebgp-as-options_config; uses bgp-use-multiple-paths-ebgp-as-options_config;
} }
} }
} }
} }
grouping bgp-use-multiple-paths_config {
description
"Generic configuration options relating to use of multiple
paths for a referenced AFI-SAFI, group or neighbor";
leaf enabled {
type boolean;
default false;
description
"Whether the use of multiple paths for the same NLRI is
enabled for the neighbor. This value is overridden by
any more specific configuration value.";
}
}
grouping bgp-afi-safi-graceful-restart_config {
description
"BGP graceful restart parameters that apply on a per-AFI-SAFI
basis";
leaf enabled {
type boolean;
default false;
description
"This leaf indicates whether graceful-restart is enabled for
this AFI-SAFI";
}
}
grouping bgp-afi-safi_config { grouping bgp-afi-safi_config {
description description
"Configuration parameters used for all BGP AFI-SAFIs"; "Configuration parameters used for all BGP AFI-SAFIs";
leaf afi-safi-name {
type identityref {
base bgp-types:afi-safi-type;
}
description "AFI,SAFI";
}
leaf enabled { leaf enabled {
type boolean; type boolean;
default false; default false;
description description
"This leaf indicates whether the IPv4 Unicast AFI,SAFI is "This leaf indicates whether the IPv4 Unicast AFI,SAFI is
enabled for the neighbour or group"; enabled for the neighbour or group";
} }
} }
grouping all-afi-safi-common-prefix-limit_config { grouping all-afi-safi-common-prefix-limit_config {
skipping to change at page 54, line 43 skipping to change at page 61, line 12
grouping l2vpn-common { grouping l2vpn-common {
description description
"Common configuration applied across L2VPN address "Common configuration applied across L2VPN address
families"; families";
// placeholder -- specific configuration options that are // placeholder -- specific configuration options that are
// generic across L2VPN address families // generic across L2VPN address families
uses all-afi-safi-common; uses all-afi-safi-common;
} }
grouping bgp-route-selection-options {
description
"Parameters relating to the BGP route selection process";
container route-selection-options {
description
"Parameters relating to options for route selection";
container config {
description
"Configuration parameters relating to route selection
options";
uses bgp-route-selection-options_config;
}
container state {
config false;
description
"State information for the route selection options";
uses bgp-route-selection-options_config;
}
}
}
// *********** STRUCTURE GROUPINGS ********************** // *********** STRUCTURE GROUPINGS **********************
grouping bgp-global-afi-safi-list { grouping bgp-global-afi-safi {
description
"Parameters and route selection options for MP-BGP
specific to the Global AFI-SAFI";
uses bgp-route-selection-options;
}
grouping bgp-group-afi-safi {
description
"Parameters and route selection options for MP-BGP
specific to peer groups";
uses bgp-route-selection-options;
}
grouping bgp-common-afi-safi-list {
description description
"List of address-families associated with the BGP instance, "List of address-families associated with the BGP instance,
a peer-group or neighbor"; a peer-group or neighbor";
list afi-safi { list afi-safi {
key "afi-safi-name"; key "afi-safi-name";
description description
"AFI,SAFI configuration available for the "AFI,SAFI configuration available for the
neighbour or group"; neighbour or group";
leaf afi-safi-name { leaf afi-safi-name {
type identityref { type leafref {
base bgp-types:afi-safi-type; path "../config/afi-safi-name";
} }
description "AFI,SAFI"; description
"Reference to the AFI-SAFI name used as a key
for the AFI-SAFI list";
} }
container route-selection-options { container graceful-restart {
description description
"Parameters relating to options for route selection"; "Parameters relating to BGP graceful-restart";
container config { container config {
description description
"Configuration parameters relating to route selection "Configuration options for BGP graceful-restart";
options"; uses bgp-afi-safi-graceful-restart_config;
uses bgp-route-selection-options_config;
} }
container state { container state {
config false; config false;
description description
"State information for the route selection options"; "State information for BGP graceful-restart";
uses bgp-route-selection-options_config; uses bgp-afi-safi-graceful-restart_config;
} }
} }
uses bgp-use-multiple-paths_config;
container config { container config {
description description
"Configuration parameters for the AFI-SAFI"; "Configuration parameters for the AFI-SAFI";
uses bgp-afi-safi_config; uses bgp-afi-safi_config;
} }
container state { container state {
config false; config false;
description description
"State information relating to the AFI-SAFI"; "State information relating to the AFI-SAFI";
uses bgp-afi-safi_config; uses bgp-afi-safi_config;
skipping to change at page 56, line 49 skipping to change at page 64, line 7
contact contact
"OpenConfig working group "OpenConfig working group
netopenconfig@googlegroups.com"; netopenconfig@googlegroups.com";
description description
"This module is part of a YANG model for BGP protocol "This module is part of a YANG model for BGP protocol
configuration, focusing on operational data (i.e., state configuration, focusing on operational data (i.e., state
variables) related to BGP operations"; variables) related to BGP operations";
revision "2014-12-02" { revision "2015-05-15" {
description description
"Initial revision"; "Initial revision";
reference "TBD"; reference "TBD";
} }
// extension statements // extension statements
// feature statements // feature statements
// identity statements // identity statements
skipping to change at page 59, line 41 skipping to change at page 66, line 46
description description
"BGP capabilities negotiated as supported with the peer"; "BGP capabilities negotiated as supported with the peer";
} }
} }
grouping bgp-neighbor-afi-safi_state { grouping bgp-neighbor-afi-safi_state {
description description
"Operational state on a per-AFI-SAFI basis for a BGP "Operational state on a per-AFI-SAFI basis for a BGP
neighbor"; neighbor";
uses bgp-neighbor-prefix-counters_state; leaf active {
type boolean;
description
"This value indicates whether a particular AFI-SAFI has
been succesfully negotiated with the peer. An AFI-SAFI
may be enabled in the current running configuration, but a
session restart may be required in order to negotiate the new
capability.";
}
uses bgp-neighbor-prefix-counters_state;
} }
grouping bgp-neighbor-prefix-counters_state { grouping bgp-neighbor-prefix-counters_state {
description description
"Counters for BGP neighbor sessions"; "Counters for BGP neighbor sessions";
container prefixes { container prefixes {
description "Prefix counters for the BGP session"; description "Prefix counters for the BGP session";
leaf received { leaf received {
type uint32; type uint32;
skipping to change at page 62, line 35 skipping to change at page 69, line 52
// valid in both the global and per-neighbor // valid in both the global and per-neighbor
// paths // paths
} }
grouping bgp-afi-safi-graceful-restart_state { grouping bgp-afi-safi-graceful-restart_state {
description description
"Operational state information relevant to graceful restart "Operational state information relevant to graceful restart
for BGP"; for BGP";
leaf active {
type boolean;
description
"Whether graceful-restart has been enabled for the AFI,
SAFI for the peer";
}
leaf peer-restart-time { leaf peer-restart-time {
type uint16 { type uint16 {
range 0..4096; range 0..4096;
} }
description description
"The period of time (advertised by the peer) that "The period of time (advertised by the peer) that
the peer expects a restart of a BGP session to the peer expects a restart of a BGP session to
take"; take";
} }
leaf peer-restarting {
type boolean;
description
"This flag indicates whether the remote neighbor is currently
in the process of restarting, and hence received routes are
currently stale";
}
leaf local-restarting {
type boolean;
description
"This flag indicates whether the local neighbor is currently
restarting. The flag is unset after all NLRI have been
advertised to the peer, and the End-of-RIB (EOR) marker has
been unset";
}
leaf mode {
type enumeration {
enum HELPER-ONLY {
description
"The local router is operating in helper-only mode, and
hence will not retain forwarding state during a local
session restart, but will do so during a restart of the
remote peer";
}
enum BILATERAL {
description
"The local router is operating in both helper mode, and
hence retains forwarding state during a remote restart,
and also maintains forwarding state during local session
restart";
}
enum REMOTE-HELPER {
description
"The local system is able to retain routes during restart
but the remote system is only able to act as a helper";
}
}
description
"Ths leaf indicates the mode of operation of BGP graceful
restart with the peer";
}
}
grouping bgp-neighbor-afi-safi-graceful-restart_state {
description
"Operational state variables relating to the graceful-restart
mechanism on a per-AFI-SAFI basis";
leaf received {
type boolean;
description
"This leaf indicates whether the neighbor advertised the
ability to support graceful-restart for this AFI-SAFI";
}
leaf advertised {
type boolean;
description
"This leaf indicates whether the ability to support
graceful-restart has been advertised to the peer";
}
} }
} }
<CODE ENDS> <CODE ENDS>
6. References 6. References
6.1. Normative references 6.1. Normative references
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", RFC
6241, June 2011.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP
Communities Attribute", RFC 1997, August 1996.
[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route
Reflection: An Alternative to Full Mesh Internal BGP
(IBGP)", RFC 4456, April 2006.
[RFC3065] Traina, P., McPherson, D., and J. Scudder, "Autonomous
System Confederations for BGP", RFC 3065, February 2001.
[RFC2439] Villamizar, C., Chandra, R., and R. Govindan, "BGP Route
Flap Damping", RFC 2439, November 1998.
[RFC4724] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y.
Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724,
January 2007.
[RFC6811] Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R.
Austein, "BGP Prefix Origin Validation", RFC 6811, January
2013.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, January "Multiprotocol Extensions for BGP-4", RFC 4760, January
2007. 2007.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991,
July 2013. July 2013.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
skipping to change at page 63, line 48 skipping to change at page 73, line 10
Shaikh, A., Shakir, R., D'Souza, K., and C. Chase, Shaikh, A., Shakir, R., D'Souza, K., and C. Chase,
"Routing Policy Configuration Model for Service Provider "Routing Policy Configuration Model for Service Provider
Networks", draft-shaikh-rtgwg-policy-model-00 (work in Networks", draft-shaikh-rtgwg-policy-model-00 (work in
progress), January 2015. progress), January 2015.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors are grateful for valuable contributions to this document The authors are grateful for valuable contributions to this document
and the associated models from: Ebben Aires, Pavan Beeram, Chris and the associated models from: Ebben Aires, Pavan Beeram, Chris
Chase, Ed Crabbe, Luyuan Fang, Bill Fenner, Akshay Gattani, Josh Chase, Ed Crabbe, Luyuan Fang, Bill Fenner, Akshay Gattani, Josh
George, Vijay Gill, Jeff Haas, Ina Minei, Carl Moberg, Ashok George, Vijay Gill, Jeff Haas, Dhanendra Jain, Ina Minei, Carl
Narayanan, Einar Nilsen-Nygaard, Keyur Patel, Adam Simpson, Puneet Moberg, Ashok Narayanan, Einar Nilsen-Nygaard, Adam Simpson, Puneet
Sood, Jason Sterne, and Jim Uttaro. Sood, Jason Sterne, Jim Uttaro, and Gunter Vandevelde.
Appendix B. Change summary Appendix B. Change summary
B.1. Changes between revisions -00 and -01 B.1. Changes between revisions -01 and -02
The -02 revision generally does not affect the structure of the
model, but there are a number of changes that improve clarity, or
simplify mappings to implementations.
o Reorganized modules to move BGP-specific types, including policy-
related types, to the bgp-types module.
o Added ability to configure route selection options at the global
level. Removed route selection options from per-neighbor AFI-SAFI
since it is not widely implemented.
o Removed a number of presence containers (e.g., in AFI-SAFI,
graceful-restart, and multipath). Presence has been replaced with
an explicit 'enabled' leaf to simplify semantics of inheritance
and override in other parts of the BGP hieararchy.
o Fixed inconsistencies with use-multiple-paths config. Added
'enabled' leaves with default false.
o Updated top level list key to be a leafref in most lists for
consistency with the operational state modeling approach outlined
in [I-D.openconfig-netmod-opstate].
o Some minor renaming / restructuring of routing policy defined-sets
and apply-policy container.
o Added ability to increment/decrement MED value in BGP policy
statement actions.
o Changed local-address leaf to be a union which can specify either
an IP address, or be a reference to an interface.
o Changed ebgp-multihop to add 'enabled' leaf and TTL behavior.
o Changed BGP well-known communities from a enumeration to a
identity. Also made consistent with IANA-defined standard well-
known communities.
o Remove enumeration values from BGP origin type given the
disagreement in RFC 4271 and RFC 4273.
o Added an additional match-options enumerated type for sets that
only support ANY | INVERT, but not ALL behavior.
o Modified prefix-sets to use inet:ip-prefix type and removed range
checking on masklength-range (also added 'exact' specifier for
masklength range).
o Removed send-update-delay timer leaf. Desired behavior is
reflected by minimum-advertisement-interval, i.e., MRAI.
o Changed allow-own-as leaf to allow specification of a number of
occurrences -- some implementations only support 0 or 1, i.e.,
equivalent of a boolean but several others support multiple
occurrences.
B.2. Changes between revisions -00 and -01
The -01 revision reflects a number of changes, many based on feedback The -01 revision reflects a number of changes, many based on feedback
from implementors of the model on various routing platforms. from implementors of the model on various routing platforms.
o Refactored model to explicitly provide 'config' and 'state' o Refactored model to explicitly provide 'config' and 'state'
containers at each leaf node to enable consistent and predictable containers at each leaf node to enable consistent and predictable
access to operational state data corresponding to configuration access to operational state data corresponding to configuration
data. This is based on the model design in data. This is based on the model design in
[I-D.openconfig-netmod-opstate]. [I-D.openconfig-netmod-opstate].
skipping to change at page 64, line 41 skipping to change at page 75, line 15
o Removed neighbor configuration from the peer-group hierarchy. o Removed neighbor configuration from the peer-group hierarchy.
Neighbor configuration now has a peer-group leaf which references Neighbor configuration now has a peer-group leaf which references
the peer group to which the neighbor belongs. the peer group to which the neighbor belongs.
o Several new configuration items added to base bgp module, o Several new configuration items added to base bgp module,
including adding some configuration items to the global hierarchy including adding some configuration items to the global hierarchy
level. level.
Authors' Addresses Authors' Addresses
Anees Shaikh Anees Shaikh (editor)
Google Google
1600 Amphitheatre Pkwy 1600 Amphitheatre Pkwy
Mountain View, CA 94043 Mountain View, CA 94043
US US
Email: aashaikh@google.com Email: aashaikh@google.com
Rob Shakir (editor)
BT
pp. C3L, BT Centre
81, Newgate Street
London EC1A 7AJ
UK
Email: rob.shakir@bt.com
URI: http://www.bt.com/
Keyur Patel (editor)
Cisco
170 W. Tasman Drive
San Jose, CA 95134
USA
Email: keyupate@cisco.com
Susan Hares (editor)
Huawei
7453 Hickory Hill
Saline, MI 48176
USA
Email: shares@ndzh.com
Kevin D'Souza Kevin D'Souza
AT&T AT&T
200 S. Laurel Ave 200 S. Laurel Ave
Middletown, NJ Middletown, NJ
US US
Email: kd6913@att.com Email: kd6913@att.com
Deepak Bansal Deepak Bansal
Microsoft Microsoft
205 108th Ave. NE, Suite 400 205 108th Ave. NE, Suite 400
Bellevue, WA Bellevue, WA
US US
Email: dbansal@microsoft.com Email: dbansal@microsoft.com
Rob Shakir Alexander Clemm
BT Cisco
pp. C3L, BT Centre 170 W. Tasman Drive
81, Newgate Street San Jose, CA 95134
London EC1A 7AJ USA
UK
Email: rob.shakir@bt.com Email: alex@cisco.com
URI: http://www.bt.com/
Aleksandr Zhdankin
Cisco
170 W. Tasman Drive
San Jose, CA 95134
USA
Email: azhdanki@cisco.com
Mahesh Jethanandani
Ciena
1741 Technology Drive
San Jose, CA 95110
USA
Email: mjethanandani@gmail.com
Xyfeng Liu
Ericsson
1595 Spring Hill Road, Suite 500
Vienna, VA 22182
USA
Email: xufeng.liu@ericsson.com
 End of changes. 186 change blocks. 
488 lines changed or deleted 1012 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/