Yes. The presentation is the view's domain, without a doubt. One of the big problems that people have with MVC is that, while the seperation between the Model and the View is quite clear, the seperation between Model and Controller and between View and Controller isn't. My approach is to move as much as logic as possible into the View and the Model, leaving the Controller as the bare bare minimum required to connect the two. There should be as little coupling as possible so that the model and the view used can be changed without having to modify the controller.
Regarding the Controller, I think a good rule of thumb would be that you should be able to make most (and even large) changes to the content of the presentation, whether contained in the View or Model, without having to touch the Controller.