I have an strange issue with LDP label mapping message. In my lab I have 3 routers. Asr903 and ALU are PE, while asr9922 is P router. I have create xconnect session between asr903 and ALU PE. What I found is asr903 send LDP label mapping message to ALU router over targeted LDP session and that message is included routes learned from asr9922 which is strange. Per my understanding, link LDP will include all routes known by that router which is make sense but targeted LDP which is usually for creating service should not contain dynamic routes learn by that router.
Imagine if we create xconnect session between PE routers then the label mapping message exchange all known routes. It will be a waste of router resources. So, can I make change on asr903 to advertise only connected interface to targeted LDP peer instead of advertise all known routes.