Now coming to the actual problem, we need to understand that ASBR uses bgp.l3vpn.0 table (Option B in this case) for importing and exporting VPN-IPv4 routes.
AFAIK, this is as per the JUNOS implementation.
http://www.juniper.net/techpubs/en_US/junos11.4/information-products/topic-collections/nce/mpls-vpn-opt2/implementing-interprovider-layer-3-vpn-option-b.pdf
With PE, NOT BEING AS ASBR, bgp.l3vpn.0 table contains only routes received by remote PE while VPNA.inet.0 table contains all the VPN routes (including the ones
from rib-group)
suryak@PE# run show route table bgp.l3vpn.0
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100:2:172.169.1.0/30
*[BGP/170] 00:00:57, localpref 100, from 3.3.3.3
AS path: I, validation-state: unverified
> to 10.0.1.2 via ge-2/1/6.0, label-switched-path hun-box
100:2:200.0.0.0/24
*[BGP/170] 00:00:57, localpref 100, from 3.3.3.3
AS path: 65002 I, validation-state: unverified
> to 10.0.1.2 via ge-2/1/6.0, label-switched-path hun-box
suryak@PE# run show route table VPNA.inet.0
VPNA.inet.0: 13 destinations, 13 routes (12 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.1/32 *[Direct/0] 02:39:21
> via lo0.0
10.0.1.0/30 *[Direct/0] 02:39:21
> via ge-2/1/6.0
10.0.1.1/32 *[Local/0] 02:39:21
Local via ge-2/1/6.0
10.255.178.43/32 *[Direct/0] 02:39:21
> via lo0.0
88.1.1.0/30 *[Direct/0] 02:33:17
> via ge-2/1/1.0
88.1.1.1/32 *[Local/0] 02:33:17
Local via ge-2/1/1.0
172.168.1.0/30 *[Direct/0] 02:52:17
> via ge-3/0/0.0
172.168.1.1/32 *[Local/0] 02:52:17
Local via ge-3/0/0.0
172.169.1.0/30 *[BGP/170] 00:01:08, localpref 100, from 3.3.3.3
AS path: I, validation-state: unverified
> to 10.0.1.2 via ge-2/1/6.0, label-switched-path hun-box
200.0.0.0/24 *[BGP/170] 00:01:08, localpref 100, from 3.3.3.3
AS path: 65002 I, validation-state: unverified
> to 10.0.1.2 via ge-2/1/6.0, label-switched-path hun-box
200.1.0.0/24 *[BGP/170] 00:20:47, localpref 100
AS path: 65001 I, validation-state: unverified
> to 172.168.1.2 via ge-3/0/0.0
200.2.0.0/24 *[BGP/170] 00:20:47, localpref 100
AS path: 65001 I, validation-state: unverified
> to 172.168.1.2 via ge-3/0/0.0
As we see, in this case the routes from VPNA.inet.0 table is being exported to remote PE (3.3.3.3)
suryak@PE run show route advertising-protocol bgp 3.3.3.3
VPNA.inet.0: 13 destinations, 13 routes (12 active, 0 holddown, 1 hidden)
Prefix Nexthop MED Lclpref AS path
* 1.1.1.1/32 Self 100 I
* 10.0.1.0/30 Self 100 I
* 10.255.178.43/32 Self 100 I
* 88.1.1.0/30 Self 100 I
* 172.168.1.0/30 Self 100 I
* 200.1.0.0/24 Self 100 65001 I
* 200.2.0.0/24 Self 100 65001 I
Now with PE, BEING AS ASBR, the routes from bgp.l3vpn.0 are advertised to PE (3.3.3.3)
suryak@PE run show route advertising-protocol bgp 3.3.3.3
bgp.l3vpn.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
100:1:172.168.1.0/30
* Self 100 I
100:1:200.1.0.0/24
* Self 100 65001 I
100:1:200.2.0.0/24
* Self 100 65001 I
As only VPN-IPv4 routes are stored in bgp.l3vpn.0 table, you will not see routes that are from rib-group being advertised.
Now comes the million dollar question, how would the routes from local CE would be advertised to remote PE?
While in this case, the routes from local CE are also moved to bgp.l3vpn.0 table as VPN-IPv4 routes.
Hence in this case you see both local CE and remote PE routes in bgp.l3vpn.0 table
suryak@PE run show route table bgp.l3vpn.0
bgp.l3vpn.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100:1:172.168.1.0/30
*[Direct/0] 00:02:49
> via ge-3/0/0.0
100:1:200.1.0.0/24
*[BGP/170] 00:02:49, localpref 100
AS path: 65001 I, validation-state: unverified
> to 172.168.1.2 via ge-3/0/0.0
100:1:200.2.0.0/24
*[BGP/170] 00:02:49, localpref 100
AS path: 65001 I, validation-state: unverified
> to 172.168.1.2 via ge-3/0/0.0
100:2:172.169.1.0/30
*[BGP/170] 00:02:17, localpref 100, from 3.3.3.3
AS path: I, validation-state: unverified
> to 10.0.1.2 via ge-2/1/6.0, label-switched-path hun-box
100:2:200.0.0.0/24
*[BGP/170] 00:02:17, localpref 100, from 3.3.3.3
AS path: 65002 I, validation-state: unverified
> to 10.0.1.2 via ge-2/1/6.0, label-switched-path hun-box