This HTML5 document contains 18 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
rdfshttp://www.w3.org/2000/01/rdf-schema#
n2http://openconfig.net/yang/rib/bgp#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:path_id
rdf:type
owl:DatatypeProperty owl:FunctionalProperty
rdfs:domain
n2:bgp_loc_rib_key_refs n2:ipvX_srte_policy_common_keys n2:bgp_adj_rib_attr_state n2:bgp_adj_rib_key_refs n2:state n2:route n2:bgp_loc_rib_common_keys n2:ipvX_srte_policy_common_route_state
rdfs:range
xsdh:unsignedInt
rdfs:comment
Reference to the path identifier for the SR-TE Policy SAFI route. The value is only non-zero if ADD-PATHS is not being used. Identifier for the path when using BGP ADD-PATHS for the SR-TE policy SAFI. If the route is learned from a neighbor, the path-id corresponds to the path-id for the route in the corresponding adj-rib-in-post table. If the route is injected from another protocol, or the neighbor does not support BGP add-paths, the path-id should be set to zero, also the default value. Reference : draft-ietf-idr-add-paths - Advertisement of Multiple Paths in BGP Reference to the path-id list key When the BGP speaker supports advertisement of multiple paths for a prefix, the path identifier is used to uniquely identify a route based on the combination of the prefix and path id. In the Adj-RIB-In, the path-id value is the value received in the update message. In the Loc-RIB, if used, it should represent a locally generated path-id value for the corresponding route. In Adj-RIB-Out, it should be the value sent to a neighbor when add-paths is used, i.e., the capability has been negotiated. The default value is : 0