Hi Paolo, Yunan, Is BMP v4 the right place to address points discussed in thread https://mailarchive.ietf.org/arch/msg/grow/bREVHXC0hd82E-3dZvVpFEM3fFQ/
1) clarification on EoR in the context of AF, pre/post policy, rib-in / rib-out / loc-rib Making context specific EoR mandatory or defining a new TLV to signal completion of the given context? 2) clarification on timestamp in Per-Peer Header related discussion https://mailarchive.ietf.org/arch/msg/grow/W-pEzcOihDSIsvzj4db8StBdUpY/ with TLVs in Route Monitoring message, different types of timestamp (time when route was learned vs time when BMP message was generated) could be represented. Current Section 6 Mandatory Timestamp still permits inconsistent types of timestamp to be used in Per-Peer Header? 3) handling of route-refresh * propagation of Route-REFRESH messages in rib-in / rib-out? * state compression in pre / post policy (for route-refresh on rib-in post-policy, is it expected for clients to see no route monitoring messages?) Cheers, Yang _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
