| bandwidth-ieee-float32 |
string |
Bandwidth in IEEE 754 floating-point 32-bit binary format:
(-1)**(S) * 2**(Exponent-127) * (1 + Fraction),
where Exponent uses 8 bits and Fraction uses 23 bits.
The units are octets per second.
The encoding format is the external hexadecimal-significant
character sequences specified in IEEE 754 and ISO/IEC C99.
The format is restricted to be normalized, non-negative, and
non-fraction: 0x1.hhhhhhp{+}d, 0X1.HHHHHHP{+}D, or 0x0p0,
where 'h' and 'H' are hexadecimal digits and 'd' and 'D' are
integers in the range of [0..127].
When six hexadecimal digits are used for 'hhhhhh' or
'HHHHHH', the least significant digit must be an even
number. 'x' and 'X' indicate hexadecimal; 'p' and 'P'
indicate a power of two. Some examples are 0x0p0, 0x1p10,
and 0x1.abcde2p+20. |
| bandwidth-ieee-float32 |
string |
Bandwidth in IEEE 754 floating point 32-bit binary format:
(-1)**(S) * 2**(Exponent-127) * (1 + Fraction),
where Exponent uses 8 bits, and Fraction uses 23 bits.
The units are octets per second.
The encoding format is the external hexadecimal-significand
character sequences specified in IEEE 754 and C99,
restricted to be normalized, non-negative, and non-fraction:
0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D
where 'h' and 'H' are hexadecimal digits, 'd' and 'D' are
integers in the range of [0..127].
When six hexadecimal digits are used for 'hhhhhh' or 'HHHHHH',
the least significant digit must be an even number.
'x' and 'X' indicate hexadecimal; 'p' and 'P' indicate power
of two.
Some examples are: 0x0p0, 0x1p10, and 0x1.abcde2p+20 |
| generalized-label |
binary |
Generalized Label. Nodes sending and receiving the
Generalized Label are aware of the link-specific
label context and type. |
| generalized-label |
binary |
Generalized label. Nodes sending and receiving the
Generalized Label know the kinds of link they are
using. Hence, the Generalized Label does not identify
its type. Instead, nodes are expected to know from
the context and type of label to expect. |
| ip-multicast-group-address |
union |
This type represents a version-neutral IP multicast group
address. The format of the textual representation implies
the IP version. |
| ip-multicast-group-address |
union |
This type represents an IP multicast group address and is IP
version neutral. The format of the textual representation
implies the IP version. |
| ipv4-multicast-group-address |
string |
This type represents an IPv4 multicast group address,
which is in the range from 224.0.0.0 to 239.255.255.255. |
| ipv4-multicast-group-address |
string |
This type represents an IPv4 multicast group address,
which is in the range of 224.0.0.0 to 239.255.255.255. |
| ipv4-multicast-source-address |
union |
Multicast source IPv4 address type. |
| ipv4-multicast-source-address |
union |
Multicast source IPv4 address type. |
| ipv6-multicast-group-address |
string |
This type represents an IPv6 multicast group address,
which is in the range of FF00::/8. |
| ipv6-multicast-group-address |
string |
This type represents an IPv6 multicast group address,
which is in the range of ff00::/8. |
| ipv6-multicast-source-address |
union |
Multicast source IPv6 address type. |
| ipv6-multicast-source-address |
union |
Multicast source IPv6 address type. |
| ipv6-route-origin |
string |
An IPv6 Route Origin is a 20-octet BGP IPv6 Address
Specific Extended Community serving the same function
as a standard 8-octet route, except that it only allows
an IPv6 address as the global administrator. The format
is <ipv6-address:2-octet-number>.
Two valid examples are 2001:db8::1:6544 and
2001:db8::5eb1:791:6b37:17958. |
| ipv6-route-target |
string |
An IPv6 Route Target is a 20-octet BGP IPv6 Address
Specific Extended Community serving the same function
as a standard 8-octet Route Target, except that it only
allows an IPv6 address as the global administrator.
The format is <ipv6-address:2-octet-number>.
Two valid examples are 2001:db8::1:6544 and
2001:db8::5eb1:791:6b37:17958. |
| link-access-type |
enumeration |
Link access type. |
| link-access-type |
enumeration |
Link access type. |
| mpls-label |
union |
The 20-bit label value in an MPLS label stack as specified
in RFC 3032. This label value does not include the
encodings of Traffic Class and TTL. |
| mpls-label |
union |
The 20 bits label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live). |
| mpls-label-general-use |
uint32 |
The 20-bit label value in an MPLS label stack as specified
in RFC 3032. This label value does not include the
encodings of Traffic Class and TTL (Time to Live).
The label range specified by this type is for general use,
with special-purpose MPLS label values excluded. |
| mpls-label-general-use |
uint32 |
The 20 bits label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).
The label range specified by this type is for general use,
with special-purpose MPLS label values excluded. |
| mpls-label-special-purpose |
identityref |
This type represents the special-purpose Multiprotocol Label
Switching (MPLS) label values. |
| mpls-label-special-purpose |
identityref |
This type represents the special-purpose MPLS label values. |
| percentage |
uint8 |
Integer indicating a percentage value. |
| route-distinguisher |
string |
A route distinguisher is an 8-octet value used to distinguish
routes from different BGP VPNs (RFC 4364). A route
distinguisher consists of three fields: A 2-octet type field,
an administrator field, and an assigned number field.
According to the data formats for type 0, 1, and 2 defined in
RFC4364, the encoding pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
2-octet-other-hex-number:6-octet-hex-number
Some valid examples are: 0:100:100, 1:1.1.1.1:100, and
2:1234567890:203. |
| route-distinguisher |
string |
A Route Distinguisher is an 8-octet value used to
distinguish routes from different BGP VPNs (RFC 4364).
A Route Distinguisher will have the same format as a
Route Target as per RFC 4360 and will consist of
two or three fields: a 2-octet Type field, an administrator
field, and, optionally, an assigned number field.
According to the data formats for types 0, 1, 2, and 6 as
defined in RFC 4360, RFC 5668, and RFC 7432, the encoding
pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number
6:6-octet-mac-address
Additionally, a generic pattern is defined for future
route discriminator types:
2-octet-other-hex-number:6-octet-hex-number
Some valid examples are 0:100:100, 1:1.1.1.1:100,
2:1234567890:203, and 6:26:00:08:92:78:00. |
| route-origin |
string |
A Route Origin is an 8-octet BGP extended community
identifying the set of sites where the BGP route
originated (RFC 4364). A Route Origin will have the same
format as a Route Target as per RFC 4360 and will consist
of two or three fields: a 2-octet Type field, an
administrator field, and, optionally, an assigned number
field.
According to the data formats for types 0, 1, 2, and 6 as
defined in RFC 4360, RFC 5668, and RFC 7432, the encoding
pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number
6:6-octet-mac-address
Additionally, a generic pattern is defined for future
Route Origin types:
2-octet-other-hex-number:6-octet-hex-number
Some valid examples are 0:100:100, 1:1.1.1.1:100,
2:1234567890:203, and 6:26:00:08:92:78:00. |
| router-id |
string |
A 32-bit number in the dotted quad format assigned to each
router. This number uniquely identifies the router within an
Autonomous System. |
| router-id |
string |
A 32-bit number in the dotted-quad format assigned to each
router. This number uniquely identifies the router within
an Autonomous System. |
| route-target |
string |
A Route Target is an 8-octet BGP extended community
initially identifying a set of sites in a BGP VPN
(RFC 4364). However, it has since taken on a more general
role in BGP route filtering. A Route Target consists of two
or three fields: a 2-octet Type field, an administrator
field, and, optionally, an assigned number field.
According to the data formats for types 0, 1, 2, and 6 as
defined in RFC 4360, RFC 5668, and RFC 7432, the encoding
pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number
6:6-octet-mac-address
Additionally, a generic pattern is defined for future
Route Target types:
2-octet-other-hex-number:6-octet-hex-number
Some valid examples are 0:100:100, 1:1.1.1.1:100,
2:1234567890:203, and 6:26:00:08:92:78:00. |
| route-target |
string |
A route target is an 8-octet BGP extended community
initially identifying a set of sites in a BGP
VPN (RFC 4364). However, it has since taken on a more
general role in BGP route filtering.
A route target consists of three fields:
a 2-octet type field, an administrator field,
and an assigned number field.
According to the data formats for type 0, 1, and 2 defined in
RFC4360 and RFC5668, the encoding pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
Some valid examples are: 0:100:100, 1:1.1.1.1:100, and
2:1234567890:203. |
| route-target-type |
enumeration |
Indicates the role a Route Target takes in route filtering. |
| route-target-type |
enumeration |
Indicates the role a route target takes
in route filtering. |
| timer-multiplier |
uint8 |
The number of timer value intervals that should be
interpreted as a failure. |
| timer-multiplier |
uint8 |
The number of timer value intervals that should be
interpreted as a failure. |
| timer-value-milliseconds |
union |
Timer value type, in milliseconds. |
| timer-value-milliseconds |
union |
Timer value type, in milliseconds. |
| timer-value-seconds16 |
union |
Timer value type, in seconds (16 bit range). |
| timer-value-seconds16 |
union |
Timer value type, in seconds (16-bit range). |
| timer-value-seconds32 |
union |
Timer value type, in seconds (32-bit range). |
| timer-value-seconds32 |
union |
Timer value type, in seconds (32 bit range). |
| timeticks64 |
uint64 |
This type is based on the timeticks type defined in
RFC 6991, but with 64-bit width. It represents the time,
modulo 2^64, in hundredths of a second between two epochs. |
| uint24 |
uint32 |
24-bit unsigned integer. |