Hi all, Apologies for the late feedback.
1) It would be good to clarify a requirement that a TLV can only be sent if the value is known to be valid. Do not include TLVs with value 0 when the feature is unsupported / disabled (e.g. no TLV 41 / 42 / 43 if RPKI validation state not available in outbound). Do not include a gauge TLV if it only has partial data. 2) On relationship between defined TLVs, particularly being explicit on whether routes reported by one TLV should be included in other TLVs > Type = 21: (64-bit Gauge) Current number of routes in per-AFI/SAFI Adj-RIBs-In Post-Policy. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge. Type = 23: (64-bit Gauge) Number of routes in per-AFI/SAFI accepted by inbound policy. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge. Some implementations, or configurations in implementations, MAY discard routes that do not match policy and thus the accepted count and the Adj-RIB-In counts will be identical in such cases. Is this about accounting for default accept / deny at the end of policy, or routes accepted by policy but still not "valid" (nexthop resolution failure, or mechanisms not strictly part of import policy like aspath loop prevention, left most AS not matching peer AS). It is not clear to me if TLV 23 should always be greater than TLV 21 >Type = 22: (64-bit Gauge) Current number of routes in per-AFI/SAFI rejected by >inbound policy Should TLV 22 include routes reported by TLV 26/27/28/34/40? 3) On license-customized TLVs, > Type = 31: (64-bit Gauge) Number of routes left until reaching a license-customized route threshold. This value is affected by whether a customized license exists for the relevant address family, and when the customized license is installed. Type = 32: (64-bit Gauge) Number of routes in per-AFI/SAFI left until reaching a license-customized route threshold. This value is affected by whether a customized license exists for the relevant address family, and when the customized license is installed. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge. Is there an expectation that the configured prefix limit (used for TLV 29/30) is not subject to license-customized limit? Should it use enterprise-specific TLV as discussed in https://mailarchive.ietf.org/arch/msg/grow/w85iHqlOgRejTSdFaoDG3pmwJ7A/ ? Cheers, Yang _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
