wimclend,
That's a common point of confusion.
In a VPLS environment there are effectively two planes of operation for LDP.
First, in order to run VPLS, you must have a labeled path to the remote VPLS PE. This is done by looking up the remote PE loopback address to match a FEC (the /32 loopback address of that remote PE router). In JUNOS, either LDP or RSVP will advertise this reachability into the inet.3 routing table. This is where traffic is associated with MPLS labels for forwarding purposes. However, this has no bearing on whether you are using targeted-LDP based VPLS or draft-kompella BGP-based VPLS.
Next, once the remote reachability is advertised, then VPLS must be able to communicate between remote PEs. This done using either targeted LDP or via BGP l2vpn signaling.
So,
- For the outer (tunnel) label resolution you can use either LDP or RSVP. This populates /32 routes for your endpoint PE routers into inet.3
- To resolve the inner (VPN) label, you can use either BGP (l2vpn-signaling) or Targeted-LDP.
In your configuration, you are using BGP-based VPLS, but using LDP for the BGP next-hop to label resolution.
It's worth noting that this is a very common deployment model for draft-kompella VPLS, as it doesn't require a full-mesh of RSVP LSPs.
The [ edit protocols ldp ] stanza, where you added ge-0/0/1.129 and ge-0/0/1.130, JUNOS simply turned on standard LDP FEC advertisement, which should have populated a /32 loopback route for each LDP speaker in the topology. This isn't at all used by VPLS, except to resolve the next-hop. But without it, VPLS won't come up (as the remote sites will be unreachable).
In your VPLS routing-instance where you configured the vrf-target, route-distinguisher and site-ID, you were specifying criteria for BGP VPLS. This instructed JUNOS to auto-discover remote VPLS PEs matching your vrf-target and automatically setup virtual ports (connections) to all discovered PEs (assuming, of course, that BGP is setup with the appropriate l2vpn address family across your network).
If you wish to use targeted-LDP for VPLS signaling, you would first add the lo0 interface to LDP (to enable targeted-mode), and then would specify a vpls-id and a remote neighbor. The remote neighbor IP would be used to start a targeted LDP session to exchange the inner label. Note that the process of adding remote VPLS neighbors is not automatic in LDP-based VPLS, so you have to manually keep all neighbors configured.
For this reason, Juniper recommends using BGP-based VPLS for its autodiscovery capabilities in many environments. In addition, there are some additional advantages in terms of spanning tree mitigation that are only available in kompella-based VPLS.