Inter-AS Option 2b ASBR-to-ASBR - redistribute connected

Has anyone seen an issue where in IOS when you've redistributed connected
the Inter-AS link into IGP (not using next-hop-self under the vpnv4
address-family to your own PE's) then the ASBR does not encode the correct
VPN label meant for his own AS i.e it simply advertises the VPN label
assigned to it from origin AS ?

Topology is simple

(AS1) PE1 ---- (RR) ASBR1------ASBR2 (RR)-----PE2 (AS2)

For example:

vpnv4 label 1 is encoded by PE1 for the customer prefix, ASBR1 sends this
to ASBR2 as label 2 in the NLRI update & for data-plane forwarding over the
mpls bgp forwarding interface...........So now ASBR2 has an out label of 2
and locally assigns an In Label of 3 but instead of sending it's own PE's
the In Label of 3 it sends the Out Label of 2 i.e what ASBR1 sent it to use
as an Out Label - thus when ASBR2 receives the traffic inbound it has no
correlation for this traffic in the MPLS LFIB and blackholes it!!??

--
BR
Tony
Blogs and organic groups at http://www.ccie.net