Resolution:
Most of the RV advisories are not broadcasted on the network at large.  For routing broadcasted advisory messages belonging to the “_RVCM.>”, “_RVFT.>”, or the “_RVCMQ.>” subject groups, the respective subject needs to be imported/exported in the RVRDs configuration.  This however, does not apply to advisories from “_RV.>” groups, as even if this subject is duly imported/exported at the RVRD, the subject interest for these messages are not forwarded to the neighbours, and as a result the neighbours do not forward the advisories back.  This check is explicitly added to avoid flooding of the neighbour’s network with RV protocol messages and advisories.

However, importing/exporting the subject “>” gets the RVRD to forward all messages if a subscription exists, thus circumventing this check and forwarding the “_RV.>” advisories.  This is also part of the reason we generally discourage users from importing or exporting “>”.

Are RV advisories routable across RVRDs?