Why is the Label Block mechanism needed in Kompella VPLS?

Question

Computer networks

Why does VPLS Kompella Mode need an automatic label calculation mechanism?
For example, tLDP in Martini Mode sends an individual label to each of its neighbors.
Why not do the same with BGP?
The RFC says in clear white:

Using a distinct BGP Update message to send a demultiplexor to each
remote PE would require the originating PE to send N such messages
for N remote PEs. The solution described in this document allows a
PE to send a single (common) Update message that contains
demultiplexors for all the remote PEs, instead of N individual
messages. Doing this reduces the control plane load both on the
originating PEs as well as on the BGP Route Reflectors that may be
involved in distributing this Update to other PEs.

But what's the difference: we send several copies of the same Update with a Label Block, or as many different messages that transmit a specific label without showing off?
Even when using RR, the gain is not very obvious - only one packet goes to RR - then it still multiplies. I can only bind Inter-AS VPN here - at least somehow it will be justified. And that traffic is now cheap, as well as processor time.
And at the same time, such a decision entails an overrun of tags. For example, a tsiska has 10 labels per block by default. If I have 3 sites, then 8 tags just disappear. And if I distribute the VE-ID at random, it's a disaster.

Answer 1

Java: https://www.tutorialspoint.com/javamail_api/javama...

Answer 2

PHP: https://github.com/PHPMailer/PHPMailer

Answer 3

JS: emailjs.org :D