No No No,dude i dont mean to be rude but you are completely wrong. In these past few months their has been a increased amount of host booting on games. Mainly WWE12, CODMW2 , MW3, and NBA2k12 seem to be popular hits. what Rouge said was completely wrong, as 1.Ive experienced getting host booted myself 2.Im an I.T student and have a strong knowledge of networks. 3. I know what software is being used to do this. DDOS attacking is illegal. Sadly theres nothing we can do about it and my confidence in Microsoft is dwindling as ive contacted them before and just be shoved aside and didnt even recieve replys from their security team. However there are some steps you can take to avoid this.
1.Since these players have your IP, you will need to turn your router off for about 20-30 minutes. This gives your router time to reset and 80% of the time will assign you a new IP. (If this step works for you then your free to play again Note however if you rejoin the same person who booted you/or sadly you run into another boooter repeat this step)
2. Sometimes the first step wont work and you may need to leave your router off longer. The suggested time is usally 8-10 hours (I know its a long time without online gaming but you gotta do it to fix the problem)
2. Sadly if your ISP assigns you a Static IP Address you have to go abit further to solve this problem. Youll need to contact your ISP and explain to them that your are being DDOSed off Xbox Live and your attackers will be able to strike again, if they assign you a static ip they will see it when they check your account and usally they will change it for you, the downside tho is that if your attacker gets your ip youll have to go through this step all over again)
And to sum it up , make sure you file a complaint (Tampering===>XBL Tampering) Avoid the Player (Quit Early), also inform your XBL friends about the GT who attacked you , and post again in the forums, i know for a fact alot of people experience this but unless more people post about this MS wont do anything. Im hoping somebody from MS reads this and fixes this problem.