At the very least, the registrant should be informed
I was up half the night arguing about this with my wife, who is of the "GoDaddy should be held responsible persuasion".
I didn't win the argument with her, but then again, she doesn't post at DNForum, so you'll only get my side of the argument.
I agree with Raider's observation that things at GoDaddy have an odd habit of changing, and they use a number of slick techniques to present parking pages.
There are so many issues that come up from time to time where someone concludes, "Registrants should be informed of X", whether X is expiration policy, transfer policy, basic security against hi-jacking, and so on. Well, yes, registrants should be informed of a lot of things, but it all boils down to registrants should know what they are doing. People who drive cars should know what the pedals do, and we don't let people drive cars unless they have demonstrated they indeed know what the pedals do. However, the sole qualification for registering a domain name is having the ability to pay for it. It is as if we let people drive, so long as they can buy a car.
That said, I also agree with the "you don't have to use their nameservers" line of thought, and I would guess that the longer one has been around, the more weight one would put on that sentiment. After all, it used to be that when you registered a domain name, that was that. Nameservers, DNS, hosting, email... all of that stuff you had to go get on your own. Even when NSI started providing default nameservers, I can't imagine the bandwidth NSI bought in order to display the little digging man and the "under construction" page on countless computer screens.
Http queries to unused names have to go somewhere, and if you are using the registrar's nameservers, they are going to go where the registrar points them, and the registrar is paying for that bandwidth.
Now, yes, a few years ago, some guy sued Register.com because he hadn't read the registration agreement, and he was shocked to find that Register.com had put paid links on the page. Long story short, I thought it was a dumb lawsuit four years ago, and the court agreed:
http://www.icannwatch.org/article.pl?sid=03/08/20/1733243
This is more like me tying my horse to a tree in your yard, and then complaining to you that your grass gave my horse indigestion.
But, back to the situation at hand, the guy has a viable defense. Domain disputes are nothing remarkable, however, so the point of grandstanding about his case before he's even filed a response escapes me.
There's nothing particularly remarkable about this situation. It is obvious that Red Bull is not going after his other name, and if he'd pay attention to his forwarding configuration, they wouldn't have gone after this one either.