Like you said before Daniel, its all interpretation.
To me, Vectors are not altitudes, they are headings.
Headings that take you into a mountain.. how can those be called suitable? Just curious. I never said vectors are altitudes, vectors are nothing except headings. However, a vector into a solid object is or should be an unsuitable vector.
You also have this, III(D)(3) which covers altitudes (specific descents)
[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]3: Issues descent and provides runway assignment or reiteration[/quote]
And then you have the ambiguous coverage of III(G)(2)
[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]2: Provides additional information or navigation service[/quote]
Navigation service can also be used to say "Keep them vectored away from those dangerous pixels". I don't think ensuring APP/DEP controllers know and follow an MVA can be classified as something the GRP was attempting to prevent a controller from knowing. After all, imagine the outcry from pilots if controllers in ZSE, ZLC and ZDV started vectoring people into the mountains, or ZNY and ZLA controllers started vectoring people into the major downtown cities. I think, if anything, it's unjustifiable and a disservice to everyone (pilots and students) to say "Oh, since the GRP doesn't specifically say they have to know about MVAs then they aren't included".