The only issues I can see arising from this is cookie-related.
Currently, cookies are written for
www.lag.tv, so changing would mean
the forgetting of login credentials (Which is hardly that much of an
issue, but an issue nonetheless). As SSL is covered (While the
certificate is issued to "
www.lag.tv", it has "
lag.tv" listed as an
approved alternate, which IIRC will mean it's accepted there), this is
the only real issue.
Personally, I'd set the URL to redirect www. to non (As in #3), but to
preserve any other subdomain. So, perhaps at a later date, the site can
be expanded to include other areas. So, for instance:
http://starcraft.lag.tv,
http://minecraft.lag.tv,
http://versus.lag.tv,
http://forums.lag.tv and so on.
Oh, and while I'm at it, what's with the goofy forum URLs?
(
http://lag.tv/forums/forums/PC seems a little redundant to me. Wouldn't
it be better to have something along the lines of
"
http://lag.tv/forums/Platforms/PC"? And using that wonderful rewrite
engine you have to put "
http://lag.tv/forums/Platforms/PC/2" instead of
the Query parameter...).
Just a thought.