What is the point of poison reverse?

in CCNA & CCENT
Really? What is the point of suspending split horizon to hear about a connected route that is down from a neighboring router? If that router knows that one of it's connected routes is down why would it need to have another router tell it something it already knows?
Comments
to other routers so they do not send the packets in that directions...if it is not reported then it is wasted bandwidth to send packets to a router that is dead or route is dead 16 hops shows dead or posioned!
that is what I think by instinct but do a google on posion reverse RIPv1 hop count posioned 16 hops..
found this definition on the internet..kinda says same thing I said. Just a way to notify other gateways that a gateway down the route is down to stop from sending packets that way.
I think dtlokee sums it up best: "I think your original question may be based on the idea that the failed route is directly attached to the router, but what if it is not?"
We need poison reverse to know what routes have failed. Try to convince yourself of this by walking through the algorithm with a bunch of different topologies.
Its kind of like telling a Rumor to a friend, and that friend turns around and tells you the same exact Rumor that you just told them.
I can see the point, kind of, of poison reverse but I still want more of an explanation of it.
http://www.cisco.com/en/US/docs/internetworking/technology/handbook/RIP.html#wp1020565
My question was the same as yours: why not just start the timer immediately upon learning of a failed connected link? Why wait for confirmation of something you already know? The answer is because the routing protocol treats failed links as a general instance. It is repetitive to swap a poisoned route, but what's the alternative? Re-design the entire protocol based on one little annoyance? It's easier to receive a notification of a failed link you already know about then to create a special workaround solely for failed connected links. I think that's the jist of it.