Boy this BGP stuff can get pretty deep.
I've managed to solve enough issues to get a solution to a particularly contorted VRF-based peering with an older non-MBGP neighbor. I won't get into details because this is a pretty unique situation.
However even though I have a solution that will meet my immediate needs, it struck me that it would have been a much more elegant solution if I could just have told MBGP that a particular non-MBGP neighbor should have it's ipv4 family addresses prefixed with a particular VPNv4 family/rd before being put into the RIB.
As it is I have ipv4 family routes being imported into a VRF via a prefix list, and no real interest in having them in the GLOBAL ipv4 family table, not that it matters. Eventually if I have to support a second non-MBGP neighbor, though, things could get ugly, since prefix lists won't cut it at that point.
So did I miss an obvious command somewhere that would allow that -- something like translate-updates except with VRF in mind? I tried a route map but it won't let you "set vrf" on incoming updates...