encoded as a 1- or 2-octet NLRI length field followed by a variable-length NLRI value. The NLRI length is
expressed in octets.
The Flow specification NLRI-type consists of several optional sub-components. A specific packet is considered
to match the flow specification when it matches the intersection (AND) of all the components present in the
specification. The following are the supported component types or tuples that you can define:
Tuple definition possibilities
Value input methodDescription and Syntax ConstructionQoS match fieldsBGP
Flowspec
NLRI type
Prefix lengthDefines the destination prefix to match.
Prefixes are encoded in the BGP UPDATE
messages as a length in bits followed by
enough octets to contain the prefix
information.
Encoding: <type (1 octet), prefix length (1
octet), prefix>
Syntax:
match destination-address {ipv4}
address/mask length
IPv4 Destination
address
Type 1
Prefix lengthDefines the source prefix to match.
Encoding: <type (1 octet), prefix-length (1
octet), prefix>
Syntax:
match source-address {ipv4}
address/mask length
IPv4 Source addressType 2
Multi value rangeContains a set of {operator, value} pairs that
are used to match the IP protocol value byte
in IP packets.
Encoding: <type (1 octet), [op, value]+>
Syntax:
Type 3: match protocol {protocol-value
|min-value -max-value}
IPv4 last next header
Protocol
Type 3
Routing Configuration Guide for Cisco NCS 6000 Series Routers, IOS XR Release 6.4.x
106
Implementing BGP Flowspec
Supported Matching Criteria and Actions