Hi,
I agree that it simplifies configuration of some cases. And that is good. But I see two concerns here. May be it can be done by other means to keep simple configuration on the one side and make it more flexible on the other. For example make "rs client" option not boolean, but with some additional possibility, so boolean values work as they do now, but it is also would be possible to say, for example, "rs client always" and it that case it skips prepend no matter how and where the route was received.
And here is my concerns:
1) There is no way to remove this prepend, becase it is done after the filters now and can not be affected in any way. On the other side if "rs client" never recieved prepend, we could add it ourselves with filters when needed (for other eBGP non-"rs client" sessions for example). And even if it were possible to do with filters - we can not remove exactly one element from the aspath.
2) It the other thread someone mentioned that other verndors behave differently with similar option and that could be confusing.
We ourselves using BGP also for internal routing with routes originated from peers or internal sources (kernel, static). But those routes can be exported to peers too so we need to be precise with aspath there. Fortunately, in my case I have control on both sides of the session, so I can redo the configuration with iBGP and route reflection or maybe confederations. But eBGP in that place looks more logical and convenient.